Christian Boos wrote:
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).
...snip...
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.

Yes, I think that for the moment we should stick to the current scheme
of using page names structured with "/" separators.  As you've said you
can move a subset of the heirarchy by selecting all page names starting
with a prefix and replace that part of the name with the new
destination.

The suggestions of simply creating a "parent" field do not address the
fact that you could have the same name reused in different parts of the
Wiki.  For example if you have a page located at "PageName/PageName"
you would create a naming conflict between the parent and child pages,
both named "PageName".  Recreating the heirarchy also incurs the cost
of recursively looking up each parent, resulting in needing "n" queries
of the database to find the full path of a page "n" levels deep.

The current structure is not perfect, but it works OK for the current
database Wiki storage.  The discussions of storing Wiki pages in under
Subversion (or other VC backend) have been revived and I think will be
a good time to explore the use of a more robust heirarchy.  I think we
should wait to see what comes out of the VC storage efforts before
attempting to overhaul the database storage for Wiki pages.

-- Matt Good


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to