Doug Douglass wrote:
Just a few comments...from a users perspective... I don't believe that separation of pagename from hierarchy is as simple as you suggest. And, IMHO I don't think the two should be functionally separated. In the simple case you describe of a field that is the name of the "parent" page, with no changes to the page reference syntax ( i.e., CamelCase), all pages would still need to have unique pagenames, would they not?
After good night sleep I think I got hang of it what mr Lazardis tried to say. Basically there is only need to have unique identifier for each page, preferably something autogenerated (like a number). Currently there is none. So you could always point to absolute page just by having it's number (like permalinks in many blog/news systems). So in theory you could have "http://trac.foobar.invalid/wiki?page=123"; that points to absolute page. Then you can name your pages (that is separate to identifier) as you wish. Then add new property, parent that would be like foreign key to some unique id and you're done. This way managing hierarchies (in point of user) would be simple. Only problems will arise when you start to refer absolute pages from other pages. How you refer to them? By using absolute page number? Writing expanded path that engine would encode *before* saving to absolute number. Write it as it is now and wish that no-one does reparenting? Can two pages under same parent have same name or do they need to be unique in that context? -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
