Folder structuring icons TAMBOTI Collections TREE

[jodevelops]

related to #26

When tamboti is opened / refreshed, ALL folders have a bluish "juncture knot" icon, why do ALL folders have that same icon? It does not make a difference that makes a difference, although it would be a great opportunity to indicate WHETHER A FOLDER HAS CHILD ELEMENTS OR NOT.

(The "expand/ collapse all" option on top is a solution to check, if any of the folders has child elements, though this can become quite bulky, especially when the collections are growing. I found, that with clicking "expand all" and "collapse all" immediately after, plus signs will show up instead of the bluish icons, wherever child folders are present and blue icons stay, wherever there are NO such child folders, but hmmm...I don't know if that's the way to go).

Freshly opened:

After clicking expand/ collapse all:

However: When the blue icon is clicked on, child elements become visible - if there are some at all - the blue juncture knot icon changes to a [-] icon, EVEN if there are NO child elements at all. At the same time second-level elements get their individual blue juncture knot icons, ALTHOUGH THEY DO NOT NECESSARILY HAVE CHILD ICONS THEMSELVES (but nonetheless MAY HAVE them). Here, again, there is an opportunity to differenciate between true parent folders and mere child elements containing "only" plain records (of any kind):

Then, again, when the user closes the collection branch, the icon HAS CHANGED to a [+] sign (FINALLY INDICATING, that there is MORE structured content in it).

Couldn't this be a general solution from the very beginning?:

• IF a folder DOES have child elements (subfolders), THEN assign a PLUS sign.
• IF it DOES NOT have child elements (subfolders), DO NOT assign any sign at all.
• CONNECT ALL folders in the tree with a DOTTED LINE, like the present state

About like this:

Clicking behaviour:

• double clicking the NAME of a collection should not only add the collection to the search filter, but also show the next level of child elements, so that it becomes OBVIOUS for the user, which CHILD collections are part of the search and clear the way for a more fine-tuned search filtering options immediately.
• Actually seeing those subfolders included in a search is a big advantage for someone who performs a search.
• I believe in "Don't make me think" here.

for the navigation, I suggest:

• SINGLE click on [+] EQUALS a DOUBLE click on the collection's NAME (it opens the tree at that particular juncture).

We should never presuppose, that a user knows EXACTLY what is in the collection, especially if we are envisioning explorative work throughout the materials.

_SUBFOLDERS COLLAPSE_

When double clicking a sub-collection (child element), that collection collapses to the top level / next-higher level, first: a double click to "show all records"

But then it collapses, but I believe, hat it'd be of advantage if that tree stayed open on the level being shown.

[jensopetersen]

We here use a version of the dynatree library, https://code.google.com/p/dynatree/, and I do not think we will tinker with the (complicated) code ourselves. As I have written before, we are thinking about using another (version of the) library, so efforts should go towards finding the best library to substitute for the present.

The Folder View does not show where a search has been done. Where a search has been done is shown in the coming version of Tamboti in the line where the number of hits is reported. The Folder View is a tool for changing the search path for the following search, shown in the path following "inside". Please reply to the other issue where this is discussed.

[jensopetersen]

You could feed your suggestions to https://code.google.com/p/dynatree/issues/list.

[claudius108]

Can we update to dynatree 1.2.5?

[jensopetersen]

Have you tested locally?

[claudius108]

I will do, then.

[claudius108]

Installed, tested, seems to work fine.