On Tue, Nov 23, 2010 at 7:50 PM, Chris McDonough <chr...@plope.com> wrote: > On Tue, 2010-11-23 at 15:29 -0800, Ben Bangert wrote: >> Since both Mako and Chameleon are configured out of box, no additional >> config/options are necessary to support it. There is nothing in the >> template that configures traversal, or a database, or what exactly the >> models are. The __init__ merely has the basic config for the project. > > I'd suggest instead: > > newproj/ > __init__.py > views.py > tests.py > models.py > templates/ > mytemplate.pt > static/ > <various static files> > > Such a template might be named "pyramid_diy". "pyramid_diy" would be a > template used by folks whom: > > - already know how to create packages and whom understand that it's > possible and trivial to turn a module into a package when such an > occasion is required (it needn't be done preemptively for them). > > - realize that there are not any incontravertable decisions implied > by the filesystem layout generated by a paster template. > > This would essentially just be the "pyramid_starter" template renamed. > It would be the only paster template that ships with Pyramid itself.
Then why not call it 'pyramid'? You're also switching the original template from Mako to Chameleon/ZPT. We need to make a conscious decision on this, and not just go with your inclination here. The tutorials are either going to have to be in that language or say that they're switching. My impression, perhaps biased, is that Mako is much more widely known and used at this point, while an XML-based template is more of a niche product. Not that it's unimportant, just that it may not be the best default nowadays. > The wiki tutorials in the docs > (http://docs.pylonshq.com/pyramid/dev/#tutorials) also make reference to > specific files, but I'd suggest moving both of those tutorials to its > most closely related external template package. That would also be easier for tutorial writers, to not have to modify the Pyramid core. > There are a few other spurious references to ``views.py`` or > ``models.py`` in other places in the Pyramid docs (the templates and > resources chapters, for example) but these can be changed to "views > module/package" or "models module/package" as necessary. If we go with views.py and models.py, it's sufficient to just mention in one place that they can be converted to packages by creating a "models" directory and renaming "models.py" to "models/__init__py". Then you can just call them a "module" in the rest of the manual, and those who have converted them to packages will know to substitute "models package" whenever they see "models model". The 'meta' issue won't come up if the SQLAlchemy template is moved out of the core, and it sounds like Ben's new layout would eliminate 'meta' entirely. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
