Hello XWiki developers,
For what it's worth, Curriki has a TOC panel, based on XWiki's model of trees
(which is somewhat independent of the parent relationship of pages.
In particular, it allows multiple parent pages (and carries them, sometimes,
with the bc parameter):
It can be seen here:
http://www.curriki.org/xwiki/bin/view/Coll_Group_WhatsYourOpinion/DuckieDeckcomPre-KGames
It works with, mostly, the TOCMacro:
https://github.com/xwiki-contrib/currikiorg/blob/master/wiki/src/main/pages/PanelIncludes/TOCPanel.vm
which creates a JavaScript array from the tree of table of contents and renders
it after page load (using the ExtJS tree).
Thus far, it has shown somewhat fragile but I think Curriki users find it quite
important to allow multiple inheritance.
Another tree view is the Curriki "Menu" (the "Home > Resources and Curricula"
etc box): this one has the nice property to store its open/closed state (in a
cookie). Such a feature is rarely available.
We have experienced, however, that such trees are rather fragile for tablets or
mobile phones and have decided, for Curriki Geometry, to do without such a tree
and, instead, enhance the up-down prev-next navigation. See e.g.:
http://www.curriki.org/xwiki/bin/view/Coll_CurrikiGeometryStudents/WhatsYourAnglePythagoras?bc=Coll_CurrikiGeometryStudents.CourseView#.UxtwyfSwauI
This could, in theory, be combined with a smooth transition system where the
2-dimensional-navigation effect may be even more visible, yet without a
fold/unfold action which I have seen only really natural in old-style outliners
with a keyboard.
paul
Le 4 févr. 2014 à 13:33, Clemens Klein-Robbenhaar <[email protected]> a
écrit :
> On 02/04/2014 09:57 AM, [email protected] wrote:
>> Hi devs,
>>
>> I’ve noticed a recurring trend from our users: a lot of them seem to wish to
>> display Tree views/navigation view of their wiki pages either in page
>> content or in a panel.
>>
>> When they go to e.x.o, there’s a lot of extensions listed (showing that
>> other users had this need previously) but none really work well:
>> http://extensions.xwiki.org/xwiki/bin/view/Extension/WebHome#|t=extensions&p=1&l=30&s=doc.creationDate&d=desc&name=tree
>>
>> We do have a tree view in AllDocs but it’s not perfect and it’s not easily
>> reusable.
>>
>> Thus I believe we need to find an official solution to this tree view issue.
>>
>> The easiest solution could be to create a wiki macro based on our current
>> tree view so that it can be reused in wiki pages and more importantly in a
>> panel. Having a “spaces” parameter to restrict the list of spaces to display
>> would be nice too.
>>
> I remember a colleague of mine tried to get the document tree working inside
> of a panel, but that did not really work, because the tree unfolded itself
> outside of the panel, always extending page names into the content area of
> the page.
> Maybe it was just a simple CSS thing we both failed to find, but maybe it is
> worth keeping this in mind. (Aside of that a macro that works nice inside the
> content area might not be suitable as a panel, simply because it is too wide
> to fit in the panel column.
>
>> WDYT?
>>
>> Any other idea?
>>
>
> Around here folks are currently using a small panel that lists the pages of
> the current space in a nested list. This is done directly on the server via
> several HQL queries however, and especially not very efficient for a space
> with a lot of pages.
> Most probably there are better solutions, even those that can be cobbled
> together in a day, but I wanted to mention it anyway.
>
> Clemens
>
>> Thanks
>> -Vincent
>>
>> _______________________________________________
>> devs mailing list
>> [email protected]
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
