What name would you like ? macro-tree ?

On Mon, Mar 24, 2014 at 2:33 PM, Haimerl, Josef
<[email protected]> wrote:
> Hi devs,
>
> I recently made a XWiki Explorer based on jstree (http://jstree.com/). 
> Actually it was made to use outside of xwiki. I made a XWiki Macro out of it, 
> it's pretty basic, but it has potential for extension. If you think it could 
> be useful for the community, I would like to contribute that (under 
> http://github.com/xwiki-contrib?). Maybe there will come up some ideas for 
> improvement.
>
> Thanks and regards,
> Josef
>
>> -----Ursprüngliche Nachricht-----
>> Von: devs [mailto:[email protected]] Im Auftrag von Ludovic Dubost
>> Gesendet: Mittwoch, 19. März 2014 17:55
>> An: XWiki Developers
>> Betreff: Re: [xwiki-devs] Users are in need of a reusable Tree view of 
>> pages,what can
>> we do?
>>
>> I had a look of the multiple extensions that seem to do that.
>>
>> And while some are close not do handle a tree view that can scale and works 
>> from one
>> specific parent node.
>> The XWiki tree view is AJAX but only works for a full space or wiki.
>> Initially it had the tree from one parent in the spec but I tried it and I 
>> think it never
>> really worked. Generally I don't like the XWiki tree view because it's very 
>> complex to
>> debug and work with. Everytime I tried to have a look I had a really hard 
>> time to
>> understand how it works.
>>
>> The hierarchy macro is not AJAX and also takes the whole set (including the 
>> orphans).
>>
>> Now in view mode it might not be that complicated to make the hierarchy 
>> macro AJAX
>> as there are already REST urls to read the childrens of a specific page. 
>> Another aspect
>> that is also needed is some sort of way to "remember" what has been opened 
>> OR to
>> open the tree on the page that is currently active.
>>
>> Another general issue is inserting a tree in a limited width panel, 
>> particularly when long
>> titles are used. This causes CSS issues that are hard to handle. It might be 
>> needed to
>> allow the width of the panel to auto-expand when the tree needs it.
>>
>> The hierarchy macro is interesting because it has a way to update your tree. 
>> It could
>> also be interesting to add a feature to add a page in the tree.
>>
>> Ludovic
>>
>>
>> 2014-02-04 9:57 GMT+01:00 [email protected] <[email protected]>:
>>
>> > 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=extens
>> > ions&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.
>> >
>> > WDYT?
>> >
>> > Any other idea?
>> >
>> > Thanks
>> > -Vincent
>> >
>> > _______________________________________________
>> > devs mailing list
>> > [email protected]
>> > http://lists.xwiki.org/mailman/listinfo/devs
>> >
>>
>>
>>
>> --
>> Ludovic Dubost
>> Founder and CEO
>> Blog: http://blog.ludovic.org/
>> XWiki: http://www.xwiki.com
>> Skype: ldubost GTalk: ldubost
>> _______________________________________________
>> devs mailing list
>> [email protected]
>> http://lists.xwiki.org/mailman/listinfo/devs
>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs



-- 
Thomas Mortagne
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to