On Mon, 30 Apr 2007 at 14:29, Simon King wrote: > 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.
I haven't looked at filters yet, so I don't know what they do, so I don't know if they are working or not :) > 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? Yep, that's a bug. > 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 ;-) Well, true. I guess there's a certain feeling of comfort from having a "project" and tracker and an easy_installable egg, but that comfort may be illusory :) > Anyway, I'd like to hear more about TGNT (and Routes, if you end up > trying it). Good luck... Thanks. Right now I'm looking for "fast path to production" over "doing it _exactly_ the way I want", so I think I'm going to skip Routes for now, since I'd rather hold off on that until TG is using CP3 in a released version, since CP3 supports Routes directly. If I can't get TGNT to work easily I'll probably use your code :) I did get the simple example from the wiki working, although the URLs don't match what the WIKI says they are. --David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
