Currently, we use jsTree as the front-end library, but I'm not happy about it and after speaking with @dbu and @dantleech I discovered they don't either.
This morning, I started looking at some alternatives, also speaking with the core dev of Typo3 Neos. They currently use DynaTree, but are not happy about it. Mostly, since it's no longer maintained. He gave me some alternatives he found while looking for a replacement. There sure can be others, but I listed the once that jumps out when I searched a bit. I'm happy to know what you think (and if we should move to another lib at all).
Currently, we use jsTree as the front-end library, but I'm not happy about it and after speaking with @dbu and @dantleech I discovered they don't either.
This morning, I started looking at some alternatives, also speaking with the core dev of Typo3 Neos. They currently use DynaTree, but are not happy about it. Mostly, since it's no longer maintained. He gave me some alternatives he found while looking for a replacement. There sure can be others, but I listed the once that jumps out when I searched a bit. I'm happy to know what you think (and if we should move to another lib at all).
FancyTree
This library seems to be recommended by a lot of people. It's full of features and has an easy to use and understand interface.
Pros
Cons
Ext JS Trees
This is the tree library of the Ext JS framework.
Pros
Cons
jqTree
Just another jQuery tree plugin which seems to work pretty well.
Pros
Cons