Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Florent Aide
On Mon, Dec 6, 2010 at 9:49 PM, Chris McDonough wrote: [...] >> I originally thought Traversal was the same as TurboGears dispatch and >> wrote that in some documentation; I'll change those. The truth may be >> that TurboGears has a dispatching model that is not in Pyramid, but I >> don't see wh

Re: URL dispatch vs traversal

2010-12-06 Thread Daniel Holth
I don't know what all you guys are smoking with this half-cocked "routes" system. Personally it makes no sense to me. I started developing web pages by putting index.html in a folder, and if I visited that folder I would see index.html. Now I put an object in a nested dict, the framework finds it,

Re: URL dispatch vs traversal

2010-12-06 Thread Mike Orr
On Mon, Dec 6, 2010 at 8:01 PM, jorge.var...@gmail.com wrote: > On Nov 24, 2:41 am, Mike Orr wrote: >> the first matching route specifies which view callable to invoke. The >> other way is called Traversal, which is familiar to BFG, TurboGears, >> and Zope users. ^Wrong. This is whe

Re: URL dispatch vs traversal

2010-12-06 Thread jorge.var...@gmail.com
On Nov 24, 2:41 am, Mike Orr wrote: > On Tue, Nov 23, 2010 at 8:21 PM, Mike Orr wrote: > > On Tue, Nov 23, 2010 at 8:00 PM, Chris McDonough wrote: > >> On Tue, 2010-11-23 at 19:35 -0800, Mike Orr wrote: > >>> I wonder if it would be clearer to to put the URL Dispatch chapter > >>> before Context

Re: Pyramid project templates

2010-12-06 Thread jorge.var...@gmail.com
On Nov 23, 9:48 pm, Ben Bangert wrote: > On Nov 23, 2010, at 5:30 PM, Mike Orr wrote: > > > It sounds good in general. Will it still have a default index view > > with a welcome page? I think that's a good minimum to get people > > started. It saves user frustration and questions on the list, "How

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Seth
Chris/Mike/Rob, *Thank you!* This discussion has help me immensely. I can see now that the config.add_handler() / @action combination is probably the best path for someone in my position to go down, and that I was probably mixing the traversal/context stuff up with my TurboGears-ish thinking. I h

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Chris McDonough
On Mon, 2010-12-06 at 16:27 -0500, Chris McDonough wrote: > On Mon, 2010-12-06 at 13:13 -0800, Mike Orr wrote: > > On Mon, Dec 6, 2010 at 12:49 PM, Chris McDonough wrote: > > >> This move is natural based on BFG's history, and the new situation of > > >> future Pylons newbies, which is forcing Pyr

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Chris McDonough
On Mon, 2010-12-06 at 13:13 -0800, Mike Orr wrote: > On Mon, Dec 6, 2010 at 12:49 PM, Chris McDonough wrote: > >> This move is natural based on BFG's history, and the new situation of > >> future Pylons newbies, which is forcing Pyramid to be more accessible > >> and simpler out of the box, rather

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Rob Miller
as a former zope / plone developer, i've got quite a lot of experience with traversal and view lookup, so maybe i'll be able to help here. On 12/6/10 10:43 AM, Seth wrote: Okay, so I think I'm just having a hard time grokking the idea of a "context" (even after beating myself to death with the

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Mike Orr
On Mon, Dec 6, 2010 at 12:49 PM, Chris McDonough wrote: >> This move is natural based on BFG's history, and the new situation of >> future Pylons newbies, which is forcing Pyramid to be more accessible >> and simpler out of the box, rather than just being a "hackers' >> framework" as BFG was. > >

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Chris McDonough
On Mon, 2010-12-06 at 12:14 -0800, Mike Orr wrote: > On Mon, Dec 6, 2010 at 10:43 AM, Seth wrote: > > 1. What would a larger Pyramid app look like directory/module wise? > > Wouldn't this look more like a default Pylons 1/TG 2 setup? > > (controllers-*ahem*-views in a "views" dir, models in a "mod

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Chris McDonough
On Mon, 2010-12-06 at 10:43 -0800, Seth wrote: > Okay, so I think I'm just having a hard time grokking the idea of a > "context" (even after beating myself to death with the documentation). > > > With that in mind, let me rephrase my initial question with a more > high-level question: > > How is

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Mike Orr
On Mon, Dec 6, 2010 at 10:43 AM, Seth wrote: > 1. What would a larger Pyramid app look like directory/module wise? > Wouldn't this look more like a default Pylons 1/TG 2 setup? > (controllers-*ahem*-views in a "views" dir, models in a "models" dir, > etc) URL Dispatch has "view handlers", which a

Re: Understanding traversal from a TurboGears perspective

2010-12-06 Thread Seth
Okay, so I think I'm just having a hard time grokking the idea of a "context" (even after beating myself to death with the documentation). With that in mind, let me rephrase my initial question with a more high-level question: How is a large web application in Pyramid supposed to look? Yes, th