On Apr 30, 4:19 pm, [EMAIL PROTECTED] wrote: > On Fri, 27 Apr 2007 at 15:06, batok wrote: > > Take a look at TGNewTraversal > > > The url handling idea is borrowed from Nevow ( another web > > framework ). > > This looks like it does what the first poster described, but packaged > neatly, which is appealing :). I've installed it and am trying it, > but so far I haven't gotten the child traversal to work. I'll keep > noodling; I need to build a simplified test ap since my existing code > is obscuring the picture currently.... > > --David
They do indeed look similar - I wish I'd found that project before I came up with the above. The end result does seem to be very similar - in my version you override get_controller_for_resource, and in TGNT you override childFactory. I'd be interested to know if the TGNT version works with all the other parts of TurboGears. In particular, do the CherryPy filters still work? TurboGears only installs filters at '/', so I guess they probably do. Also, (from a VERY brief look at TGNT's code, and not having actually run it), it doesn't look like it checks for an 'exposed' attribute on the methods that it calls. Does that mean that _any_ method or callable attribute on your resource class is exposed? As far as packaging goes, if you remove the docstring and the not- strictly-necessary default implementation of get_controller_for_resource, the ContainerController is only 14 lines of python, so it hardly seems worth it ;-) Anyway, I'd like to hear more about TGNT (and Routes, if you end up trying it). Good luck... Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
