Trac works nice, but has several deficits. One of the deficits are the missing possibility to apply a hierarchy to the wiki documents.
I've noticed that the trac-team uses a construct, which can best be rated as a "temporary workaround". ProjectPlans/DoingThis here, the hierarchy-information is 'hardcoded' into the wiki-page-name, which makes "the change of hierarchy" very difficult. A main benefit of wiki's is lost: The ability to create documents on-the-fly, whilst applying (or changing) hierarchy to a later point. The trac team should not use this workaround further, but instead provide a _real_ hierarchy for the wiki (it's just a field "parent" within the wiki model). . -- http://dev.lazaridis.com/base/ticket/2 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
