Hi-

Just wanted to offer my thoughts on this (QuickWiki) - I think it's a
great addition - the only aspect that strikes me as off-key is the
sections covering app distribution, paster (other than minimum for
creating/running Pylons projects), ez_setup and friends.

While I realize the usage of these tools is considered an important
feature, I think going into them in an intro tutorial (also called
"Main Pylons 0.9 Getting Started Tutorial" on the wiki front page) is
both distracting and a bit off-putting. I think it's no secret many
people initially (and still perhaps) find setup tools and less common
paste utils a bit confusing.

Covering the minimum paster/ez to create/develop/run Pylons projects
would be more sensible it seems to me -- having steps with these other
tools makes basic Pylons usage look a lot more complicated than it
really is. That said, they're certainly useful topics that could
definitely use the information and coverage in a tutorial -- just not
in an intro one.

Also I could be totally wrong, but my guess is the number of people who
need to bundle their apps for distribution to the world in general
(cheeseshop) is much smaller than those who would benefit from learning
how to use ez/paste to handle issues of in-house deployment and
upgrading of Pylons installs/apps. I would assume the overall methods
would be similar but think the change in focus would be helpful to more
people...

Sorry to critique without offering a concrete solution, but thought it
was worthwhile to mention how it strikes someone a bit less initimate
with the libs than you (James and others). And maybe others here will
disagree but I figure a few newcomers might agree!


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to