Re: [Repoze-dev] url dispatch, args, matchdicts

2010-06-02 Thread Iain Duncan
> > > > Hmm, what about adding another optional param to route tags? something > like > > use_global_views, but as a flag for the passing in named args > > automatically? I would think a lot of people coming to bfg from other > > frameworks and using it as a micro-framework would really like that.

Re: [Repoze-dev] url dispatch, args, matchdicts

2010-06-02 Thread Wichert Akkerman
On 2010-6-2 21:48, Iain Duncan wrote: > Hmm, what about adding another optional param to route tags? something > like use_global_views, but as a flag for the passing in named args > automatically? I would think a lot of people coming to bfg from other > frameworks and using it as a micro-framework

Re: [Repoze-dev] url dispatch, args, matchdicts

2010-06-02 Thread Iain Duncan
> > Iain Duncan wrote: > > Hi bfg folks, one feature I miss from pylons is having elements from the > > route parsing be automatically passed to controller methods as named > args. I > > expect this got some thought and was decided against, I'm curious why? It > > seems to me it would be nice if th

Re: [Repoze-dev] url dispatch, args, matchdicts

2010-06-02 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Iain Duncan wrote: > Hi bfg folks, one feature I miss from pylons is having elements from the > route parsing be automatically passed to controller methods as named args. I > expect this got some thought and was decided against, I'm curious why? It > s