Chris McDonough wrote:
Here's an example of some ZCML that would create a Routes route:
route
name=blog_entry
path=/blog/:id/:view_name
context_factory=.blog.BlogEntry
context_interfaces=.interfaces.IBlogEntry .interfaces.IContent
/route
There's something about
Malthe Borch wrote:
Chris McDonough wrote:
Here's an example of some ZCML that would create a Routes route:
route
name=blog_entry
path=/blog/:id/:view_name
context_factory=.blog.BlogEntry
context_interfaces=.interfaces.IBlogEntry .interfaces.IContent
/route
2009/1/19 Chris McDonough chr...@plope.com:
``factory`` would be fine. ``for`` doesn't describe what context_interfaces
does properly; ``provides`` might be better.
I like that. As I understand it, you want to be able to attach a
marker-interface based on the route that lead to that particular
I think possible routes users are more likely to be regular Python
developers with no Zope background, so I would suggest adding some mechanism
to accomplish this using Python. Maybe extend the repoze.bfg.convention
package for this.
Carlos de la Guardia
I made a mistake by adding the current generation of URL-dispatch behavior to
repoze.bfg.
Currently, repoze.bfg allows you to use Routes to invoke a bfg view with a
manufactured context based on a route match. To do so, you configure a
repoze.bfg.urldispatch.RoutesMapper as the bfg get_root
