Hey Rupert, Yes, I intended to send this to the mailing list. (I think I forgot to add trac-dev in the recepient list .. argh)
Thank you, Catalin Balan rupert THURNER wrote: > many thanks for the information! probably you intended to send this to > the mailing list? > > On Thu, Dec 11, 2008 at 15:52, [email protected] > <[email protected]> wrote: > >> Hi trac-dev, >> >> Just a small update regarding this feature. >> The hierarchical wiki implementation based on resource tools plugin >> can be seen in action here: >> http://code.optaros.com/trac/oforge/wiki/TitleIndex (the content of >> that page is provided by ShowTree macro) >> >> ShowTree macro's code is available here:.http://code.optaros.com/trac/ >> oforge/browser/trunk/plugins/wikitoolsplugin/tracwikitools/relation/ >> wiki.py#L77 >> >> Thank you, >> Catalin Balan >> >> On Oct 1, 7:13 pm, "[email protected]" >> <[email protected]> wrote: >> >>> On Sep 30, 10:53 am, Catalin Balan <[email protected]> wrote: >>> >>> >>> >>> >>>> Hi trac-dev, >>>> >>>> In case anyone is still interested in this issue, I have it implemented >>>> here: [1] >>>> WikiToolsPlugin provides a set of features like wiki custom fields and >>>> page/resource relation, based on resource tools. >>>> >>>> Some feedback would be very nice. >>>> >>>> [1]http://code.optaros.com/svn/oforge/trunk/plugins/resourcetoolsplugin/ >>>> [2]http://code.optaros.com/svn/oforge/trunk/plugins/wikitoolsplugin/ >>>> >>>> ps. No documentation yet available, since this feature is still under >>>> development. >>>> >>>> Thank you, >>>> Catalin Balan >>>> >>> it like the code. the features we lack here are: >>> * simple fine grained access control on wiki pages, maybe like >>> http://moinmo.in/HelpOnAccessControlLists >>> (people like to use the wiki as scratchbook and note their not-so- >>> important passwords ...) >>> * some "sign off" or "quality mark" which somehow works like >>> mediawiki stable versions >>> * language the page is written in >>> >>> for hierarchical wiki page organization i think the url solution would >>> be better, i.e. trac.edgewall.org/wiki/TopLevel/Hierachy. >>> >>> for the metadata i am not sure if separate fields will be the optimal >>> solution, or just putting additional text in the wikitext would be the >>> better option. but i am unsure how e.g. setting an approve or changing >>> the access could go together with that. what do you think? >>> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
