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
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
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
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
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
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.
>
>
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
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
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
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
On Fri, 2010-12-03 at 17:33 -0800, Seth wrote:
> I've been a TurboGears user for most of my projects but have just been
> hired to start a new Pyramid project. Naturally, I'm interested in the
> traversal approach to views and routes, but am having trouble figuring
> out from the documentation exac
I've been a TurboGears user for most of my projects but have just been
hired to start a new Pyramid project. Naturally, I'm interested in the
traversal approach to views and routes, but am having trouble figuring
out from the documentation exactly how traversal would work when
spanning across multi
12 matches
Mail list logo
