Switching topic thread, as the Pylons Podcast thread forked.

On Dec 5, 2010, at 1:57 PM, blaflamme wrote:

> I must agree that pyramid_pylons is not a good name to use because now
> we'll get 3 levels of explanations and it's event more confusing:
> 
> 1. Pylons 1, now the «Pylons Framework»
> 2. The Pylons Project
> 3. Pyramid Pylons, the pylons way to do pyramid
> 
> If docs and communication are clear I see no problem using a different
> name, and it'll open ways to do things differently than how Pylons 1
> actually works, by using Pylons in the name people would assume it
> should be or work or have the same behaviour than before.

Alternatively, I think doing something as some people suggested earlier might 
work better. That is, a piece of documentation about patterns and application 
design that go over how to setup a 'Pylons 1.0' style, or part of it that one 
might want to have. Personally, for me already, several of my smaller pyramid 
services were fine using the most basic pyramid template. But two larger 
Pyramid apps quickly had me using tmpl_context and the helpers layout pattern 
with a template globals subscriber.

Documenting the 3 or 4 design patterns that people associate with 'Pylons' so 
there is a standard reference would likely be the most useful approach, so 
people could apply the ones desired, and still have a uniform way to refer to 
its implementation. This would likely negate the immediate need for a paster 
template, unless someone wanted a quickstart that just had "all" the patterns 
implemented at once, though its possible we might have other useful web 
application design/layout patterns to add later that can't all be used at once.

As many people already ask about "best project layout" type choices, the page 
would have a lot of utility for people in different circumstances.

Cheers,
Ben

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to