I think of the QuickTour as an exec summary. I've gone through similar overviews in other frameworks/projects/etc been instantly in love, or will summarily dismiss it. Why? Because some overviews make it seem like you only have one option/method of getting something done ( which is true for many application libraries ). So while it's nice to show that you can easily do xyz in pyramid using abc... I think it's really important to underscore that this is just an example, and point to docs that show a range of other options. (deployment, databases, etc)
In the MVC realm, I do think its important to note that Pyramid holds true to this "style" or "concept" or application design. It's not important to get across the peculiarities of how pyramid fits in -- but that its similar with prevailing approaches, there's a strong separation of code, and anyone with experience in MVC or compatible approaches will feel right-at-home. The folks who look at the quicktour will probably be wondering if its more like Django or Rails than web.py; or PHP/ASP vs CakePHP (or whatever library). -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
