Hello,
I've noticed some discussion about this topic, but I have the feeling
that it's not fully in sync with the latest developments and discussions
in tickets on t.e.o.
So here are a few informations that you might find useful.
Having a pseudo-hierarchy built from page names is a good thing, as it's
easily understandable by the users. It's also something that would
naturally translate to other kind of resources than the wiki (source
files of course, but also milestone names for submilestone).
But I agree that having a bit more support from the system would be
helpful. Currently, there's the TitleIndex macro, which can provide a
list of the subpages, but all of them instead of all the children pages.
This should eventually be addressed (the HierWikiPlugin has a
ChildrenPage macro or something similar).
Then, the semantic of relative links has changed in 0.11, as the
semantic used for 0.10, designed to match the one of URLs, was next to
useless. See r4442 for the changeset and
http://trac.edgewall.org/ticket/4411#comment:7 for a more detailed
discussion about the reasons for the change.
Relative links make now easy to write "relocatable" subsets of the Wiki,
by creating links to sibling pages (e.g. [../SiblingPage]), to parent
page (e.g. [.. the Parent]), to child pages (e.g. [./ChildPage]).
What's missing is an effective tool for doing this relocation. For that,
I've proposed a prototype UI for the Wiki Rename feature which would
allow multiple renames in one operation and that can be suited to move
whole hierarchies around, see
http://trac.edgewall.org/ticket/4412#comment:8.
-- Christian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
