On Nov 24, 11:39 am, Mike Orr <[email protected]> wrote: > > [...] > > That would be great. The data structures in Mapper and Route are > rather opaque and underdocumented though. We're considering a more > transparent structure for a future version of Routes.
Sign me up for that, at least as an interested party. I'm responsible for the current `parent_resource` business, and I've always felt that it was somewhat of a hack, and it only works for a limited set of use cases. I've had some ideas about the resource side of things, like creating a Resource class with a parent attribute, etc (though I'm not saying that's necessarily the best approach). I wish that I could take more up front initiative on this, but I can at least offer some assistance once things get rolling. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
