Hi, See below, On Wed, Nov 26, 2008 at 8:30 AM, Marius Dumitru Florea < [email protected]> wrote:
+1 for 3.
I would also like to see the number of child nodes for a parent node, without expanding it. This way I won't be surprised that expanding a node with >1000 child nodes takes so long (either because of the DB, network or DOM).
Now, regarding the three proposed ways of adding new nodes:
-1 for A and B since I'd like to be able to add a child node without expanding the parent (especially when I see it has >1000 child nodes already). How can I know that the name I want it's not taken? The UI (input dialog or filter) should tell me. I don't want to scroll through 1000 (not even 100) nodes to find that by myself.
-0 for C since, although it seems scalable, it isn't. The problem is when the name of the parent node is really long and there are many actions on the right of it.
So to me C seems better than A and B, but not perfect. Unfortunately I don't have a better solution.. thinking..
I also think 3C is the best solution. It is almost similar with what I have in XWord. The difference is that I use a context popup menu for the actions applicable to the selected node. While pretty popular, the disadvantage of the contextual menu is that is not intuitive enough because the user has to right click to see it. To compensate, I created a syncrhonized buttons group in the Ribbon UI of Word. In other words that buttons group will show only the buttons with actions regarding the selected node in the tree. I dont think this is easily applicable on your web-based interface, but I sure need some feed-back on my implementation. I'll send you guys a screenshot of the latest build of XWord right away I have access to a machine that has one installed. It's really nice that XE, WebDav, XEclipse and XWord are convering to the same type of navigation.
Jean-Vincent Drean wrote:
In a previous thread we've discussed about how to add a link in the WYSIWYG editor, and more generally, how to browse the wiki from a WYSIWYG dialog box (See http://markmail.org/message/tyxrcr24w3n6m2pn for more details).
After some thinking and a discussion with Laurent Lunati, I'd like to suggest a 3rd way of browsing the wiki from the WYSIWYG: an enhanced tree menu.
I've put the mockups and Pros/Cons on this wiki page : http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorWikiExplorer This wiki explorer widget would be used in the link dialogs, image dialogs, file (attachment) dialogs.
Here's my +1 for 3) A). +1 for 3) with filter option.
From the implementation POV 3) is probably the most difficult proposal and 1) the simplest one. Widget 3) would need to be a reusable (and highly configurable) GWT component so that we could use it as our main navigation/reorganization tool in the future. This tree would replace our current treeview (Main.AllDocs) which is AFAIR the only page using the YUI library in XE.
Thanks, JV. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs