> There's not that much auxiliary code in the tutorial really. If you > removed the database and template stuff you'd be left with a nice > short snippet but not really a functional example application.
I'm not advocating removing the database stuff, just factoring it out of the main line of the tutorial. In fact if you could simplify things so that the tutorial just used pickles in a file rather than a full blown relational database that would make it a lot easier to try out the tutorial without having to install other packages on your laptop.... The problem is that the auxiliary code makes the tutorial difficult to understand without reading other tutorial. And if you want to try out the tutorial you might have to install quite a few other packages before you could even begin. I think nice short snippets make great tutorials. In this case you could say "in order to make this example complete we need dataAccess.py which you can find at <link>... here we will only explain the werkzeug specific code... Not to brag or anything but I'm kinda proud of the Nucular API guide (tutorial) http://nucular.sourceforge.net/APIExamples.html and the gadfly overview http://gadfly.sourceforge.net/gadfly.html and the ReportLab API user guide http://www.reportlab.com/docs/userguide.pdf (except for some of the parts I didn't write) which I would offer as models. In these cases I could have started with "First download Zope..." but I didn't think that was a good idea. Werkzeug looks like great stuff. I think a more accessible tutorial would greatly improve its future acceptance. -- Aaron Watters --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" 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/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
