I think the whole tree needs a complete rethinking in general.
For a lot of admin functions, its completely unnecessary (e.g., site configuration, creating users, etc.).
For working with pages, it should be much more prevalent and serve as the starting board for changes with the resulting "target" page either being in a new window, or loading on top of the tree. When you're done editing the page, return to the tree view.
I would like to see a narrower, persistent navigation menu on the left column, with a tree view as appropriate taking up the majority of the browser space, add to this the ability to have checkboxes for "bulk operations" on pages (e.g., reassign templates, update a TV, etc.), and I think we get a little bit closer to a more intuitive Manager.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
While we're further on the subject of overhauling the tree, we should also consider using Ajax if at all possible. How about as a first step using it simply to sort the menu index.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Indeed, I've been fiddling around with this for a few days now; still haven't gotten anywhere, but I'll keep at it until I do. I really never cared for frames , unless maybe an iframe for really dynamic stuff like chat pages. But if I am understanding what I'm learning about Ajax correctly, it shouldn't even need an iframe, just a <div> section or something.
Does anyone have any suggestions for their favorite explanations/tutorial etc on Ajax (other than the ones already mentioned)? I usually have to get beaten over the head pretty thoroughly with something before I "get it", and the more sources of input the better.