On Dec 5, 2010, at 2:34 PM, Ben Bangert wrote: > 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.
I think a Project Design Patterns section might be laid out in a similar manner to how these books handle them: http://www.enterpriseintegrationpatterns.com/toc.html http://martinfowler.com/eaaCatalog/index.html So we divide common design/layout patterns by type, situation they address. List how to implement it (add this file here, etc.), and the problem is solves. In retro-spect, we probably should've had something like this for quite awhile, as the default Pylons project failed to address various problems many ppl have asked me about, which generally have a common "best approach" reply. It would also probably be easier to keep the patterns up to date as they don't rely on as specific of things in a project, and people can combine them as needed. I'm sure there's also "best practices" that some of the more advanced Mako/SQLAlchemy/etc projects have that aren't well documented, if documented at all. Though I'd be wary of including design patterns for other projects, as they should really have sections on their sites for that. 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.
