Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Mark Ramm
On Sat, Jan 15, 2011 at 7:23 PM, Alice Bevan–McGregor wrote: > On 2011-01-15 04:07:24 -0800, Alessandro Molina said: > >> I'm really new to pyramid, so I might be wrong, but probably something >> like that can be quickly achieved by implementing your Controller base class >> on Pyramid overridding

Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Chris McDonough
On Sat, 2011-01-15 at 16:23 -0800, Alice Bevan–McGregor wrote: > On 2011-01-15 04:07:24 -0800, Alessandro Molina said: > > > I'm really new to pyramid, so I might be wrong, but probably something > > like that can be quickly achieved by implementing your Controller base > > class on Pyramid over

Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Alice Bevan–McGregor
On 2011-01-15 04:07:24 -0800, Alessandro Molina said: I'm really new to pyramid, so I might be wrong, but probably something like that can be quickly achieved by implementing your Controller base class on Pyramid overridding the __getitem__ method to use for example Crank. Unless someone can

Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Alice Bevan–McGregor
On 2011-01-15 09:26:38 -0800, Chris McDonough said: The main thing that object dispatch and traversal have in common is that both involve a tree. Otherwise, they're not very similar. In object dispatch, the tree is the "view" code. In traversal, the tree is essentially data that can be viewed

Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Alice Bevan–McGregor
On 2011-01-15 04:07:24 -0800, Alessandro Molina said: The main difference that I see between object dispatch and traversal is that object dispatch requires an additional functionality to specify what you want to expose of your class and what you don't (like a decorator), while both traversal a

Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Chris McDonough
On Sat, 2011-01-15 at 13:07 +0100, Alessandro Molina wrote: > On Sat, Jan 15, 2011 at 9:42 AM, Alice Bevan–McGregor > wrote: > > On 2011-01-14 22:53:03 -0800, Rob Miller said: > > > >> Object dispatch is a TurboGears concept, not Pylons. > > > > I've retrofitted it to almost every web framework I'

Re: Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Alessandro Molina
On Sat, Jan 15, 2011 at 9:42 AM, Alice Bevan–McGregor wrote: > On 2011-01-14 22:53:03 -0800, Rob Miller said: > >> Object dispatch is a TurboGears concept, not Pylons. > > I've retrofitted it to almost every web framework I've ever used from WebPy > and CherryPy through to Pylons.  Routes are an i

Re: Pyramid for Pylons users guide

2011-01-15 Thread Eric Lemoine
On Sat, Jan 15, 2011 at 4:53 AM, Mike Orr wrote: > Hi all, I'm starting an article on Pyramid for Pylons 1 users, > focusing on the differences between the frameworks and how to do > familiar things in Pyramid. It'll also cover add-on stuff like forms > and auth, or at least list the alternatives

Traversal / Object Dispatch / Routes [was: Pyramid for Pylons users guide]

2011-01-15 Thread Alice Bevan–McGregor
On 2011-01-14 22:53:03 -0800, Rob Miller said: Object dispatch is a TurboGears concept, not Pylons. I've retrofitted it to almost every web framework I've ever used from WebPy and CherryPy through to Pylons. Routes are an inherently limiting thing to me (one app I worked on actually exceede