On Feb 27, 2007, at 12:58 PM, Christoph Haas wrote: > AFAIK there is a > plan to > write a more complete handbook for Pylons at > http://pylonshq.com/project/pylonshq/wiki/DocLayoutProposals
I added a few things including an introduction/history, what are sessions/templates, other deployment strategies (standalone httpserver, mod_scgi + SWUP, mod_wsgi), and setting up a daemon. A few perhaps controversial points: if we're going to switch to Mako and ToscaWidgets, we should do it now. There's no reason to continue documenting a lame-duck system; it just makes newbies' applications less forward-compatible. Myghty in particular has baggage which doesn't belong in a template system, and it just confuses newbies to read stuff in the Myghty documentation that doesn't apply to Pylons. Whether it's in the main book or in a second book about optional packages, we should describe Genshi, both because it's a representative of the XML-parsed templates and because it has features Myghty/Mako don't that users may need. Likewise, MochiKit and Pyjamas have features WebHelpers doesn't, which users may need, so we should mention them somewhere. I moved the introduction to REST to after the basic Routes configuration. More users will want to modify routes than want to implement REST, and introducing REST before Routes is giving newbies too much information up front. Users need to know how to change routes before they get into the agonizing decisions of designing a perfect URL map for their application. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
