Christian Boos wrote:
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.
(why don't you post directly within the topic?)
Having a pseudo-hierarchy built from page names is a good thing, as it's
easily understandable by the users.
It does not need many expertise to see:
Encoding multiple directory names directly into a filename is a 'bad'
thing.
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).
You should take the challange to implement a "folder" construct,
instead of encoding folder-information within the resource names.
But I agree that having a bit more support from the system would be
... (plans interweaving several other constructs)
reading this elaborations of the responsible developer, I see that I've
choosen the right title:
WARNING - Encoding Hierarchy into the Wiki Name
http://groups.google.com/group/trac-dev/browse_frm/thread/2c613ff7b10859ff
If you keep and build uppon the current concept, you'll just ruine the
elegance of the wiki/trac implementation.
If you cannot resist, then _please_ keep this stuff in external
plugins, thus at least the trac core is not affected by this
'pseudo-hierarchy-design'.
.
--
http://case.lazaridis.com/ticket/39
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
