> Thanks Gavin. Well, I've spoken with a couple people from Daemon (not > sure if I mentioned it to Geoff though) and they were interested in > considering this for v2.4. But that was over a month ago and I haven't > approached the idea since. If people are interested in it (including > Daemon) I'll spend some time working on it.
I'd sure be interested in it. FUs are great, until you have a large and deep site. Then your FUs are way too long to be useful.... not really "friendly urls" any longer. > The final result would allow people to use FU's the old way or the new > way. I prefer the new way for many reasons. One main reason is because > it doesn't use a text file anymore (this takes care of the corruption > issue many people are having), rather it builds the links on the fly > (and can cache newer links so that speed is not an issue. Although I am > not caching mine and I haven't seen any speed issues). Sounds good. I've had that corruption problem a few times myself. > Thanks. I'm not very happy with it though and am considering pulling > it. I had to rewrite getDescendants() though (Spike helped me out with > that one). It is backwards compatable, but I never sent it into Daemon. > In reality the same code changes should be made to getAncestors(), > getChildren(), etc (but I never got around to it). The modification > does an extra check. When getting nav nodes, not only does it check if > the node is 'approved', but it also makes sure it has a valid object > under it to display (ex: dmLink, dmHTML, dmInclude, etc). It chekcs > against a list of objects as an argument so that you can send in your > own custom objects should you have any (or tell it to only check against > a specific custom list). > > I had previously written a custom method (posted here back in Jan) that > did the same thing, but it caused major performance issues (it required > you to loop over the results from getdescendants and run this method > each time which required a query within each loop... not good). By > editing the single query within getDescendants() the result is "much" > faster and more reliable. I guess, the only criticism would be that you don't display siblings, so if the user wants to browse a whole section, it becomes difficult. This, as i said, is something i've been struggling with... you don't want to be showing a whole site map on every page either! > If you really want more info on this I'd be happy to share my code (send > me an email off-list). I should probably write about it in more detail > on my blog because I've had a few people ask me about it. As for that > page (The General Info page) I never had time to break that up into sub > pages, but I really should. It looks aweful all on one page like that > (I was being rushed to get the site up so there were several areas where > shortcuts had to be taken. This was one of them). I'd certainly be interested in having a read of this, yeah. Cheers Gav --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
