Hi, I'm currently working on some different ways to implement the breadcrumb and a Table of Content on a project.
It's using some of the ideas that are currently implemented in Curriki. See this example: http://www.curriki.org/xwiki/bin/view/Coll_curriki/RefineyourSearchforLearningResources?bc=;Coll_curriki.CurrikiHelp;Coll_curriki.HowtoSearchBrowseCurriki_0 One of the differences for breadcrumbs and toc in curriki is that your context depends on your navigation (in addition to the parent child relationships of pages). This is necessary because in Curriki pages can have multiple parents and you would like to keep the breadcrumb and TOC of where you came from (the actual parent is the default). It's the bc= parameter in the URL that keeps the navigation context. Also in Curriki the breadcrumb and the TOC has an entry point. In Curriki it is "Collections" that serve as entry points. The TOC or BC will always start from such a page. In the other project I'm working on we also have such a structure that serves as the entry point. It's actually important to have such a structure to decide when to stop going up the parent child relationship. Otherwise you could get a pretty huge TOC. Maybe we would need to have a special parameter for pages that we can check to decide this is such a page which would be the top of a TOC. Or we could decide that spaces home pages are such pages. This is the main problem to solve. Once you have this you can play around with AJAX trees to have nice open/close status of the tree itself and you can nicely see your page in the context of your tree. Indeed this is key to great navigation inside your wiki. I should soon be able to share the special breadcrumb and TOC code (it's not AJAX at this point). Ludovic Manfred a écrit : > Hi JV and Vincent > > Fabulous to hear :-) Yes that's IMO useful as a "tree" index" and would also > be workable but it would be clumsy for what I really desire as a wiki nested > page navigation menu. > > To be workable from the main page or subpages IMO one needs a subset of this > in the side panel to work as a hierarchical table of contents - think like > the windows explorer file manager view when it shows directories - the drive > letters and names would be the spaces, then the next link down would be the > first wiki page of that space and then the next drill down would be the next > wiki page below the first wiki page. > > As one navigates to the first wiki page further deeper wiki page levels would > be shown. The way it works with Dekiwiki is as one drills deeper the upper > levels displayed are "closed" - i.e all upper levels are indented to the 0 > position - so that the hierarchy width doesnt grow wider than the initial > panel size. > > Also looking at the tree display currently in XE 1.8, to be practical and not > confuse users when used as a sidebar, the wiki page navigation panel one > would need the option of "hiding" certain spaces. Many of the spaces created > by the application import for example one doesnt necessarily want to display, > often just the user spaces would be what is desired to display. So if one > creates say a 'department' space then a user might want to browse around in > that to navigate to a specific page they want quickly. > > Really what I mean is like in XE we have spaces which in turn have pages, I'd > like within each space to have subpages of main pages which are intuitive for > users to navigate, almost like subspaces within a main space. > > At present it appears to me as if all wiki pages within a space are at the > same hierarchical level, which of course makes managing multiple pages on a > certain topic/theme a bit of a challenge. > > Also having this tree space context aware would be wonderful so that if one > is in a space then the "tree sidebar" navigator shows only the pages in the > space. One could have a main menu option so that a user can always get back > to the home/main page but then again the "quicklinks" could also be used for > that, but it might be more intuitive if its listed on the "tree sidebar" > right as the first entry as well. > > I did attach an example jpg to this mail but it appears it didnt get through > so hopefully you don't mind that I have emailed it directly FYI. I can create > a short video clip of it if you want as well to show how one can navigate > pages easily in this manner. > > Thanks for your interest. Integrating such a feature in the main sidebar > would make Xwiki wiki pages considerably more navigable. > > Thanks, Cheers > > >> We are actively working of an improved version of the treeview. It will be >> shipped with XE 1.8.1. Here's a preview: >> http://www.jean-vincent.org/xwiki/bin/download/Main/Screenshots/treeview.jpg >> Is this what you had in mind ? >> > > >> Note that this tree is highly customizable and that it will be >> possible to put it in a side panel. >> > > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users > > -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
