On Dec 14, 12:55 am, Michael Merickel <[email protected]> wrote: > On Tue, Dec 13, 2011 at 2:29 PM, rihad <[email protected]> wrote: > > I totally agree. But this comes at a cost: you have to be nearly just > > as proficient and experienced as its authors to appreciate its full > > power. > > Actually it just means you have to read the documentation to use it. You > can't just sit down and magically write a blog in 5 minutes while not > caring about where the forms, data, sessions, auth, etc are coming from. > You'll need to read the docs eventually anyway, but to use something that > isn't full stack, you usually have to read the docs first.
Actually I've spent a few days to read all the docs to get as much info as possible (http://docs.pylonsproject.org/projects/pyramid/en/ 1.3-branch/), and the SQLalchemy wiki tutorial before attempting to start a project I had on my mind. But I still wasn't sure which high- quality extension to pick to generate forms, validate the data etc., at least not until I knew that the author of Pyramid also wrote Deform. So I'll be starting from there. But it's a pity if if that would require me to duplicate data in more than one place (model/form/ validation). Deform docs (http://docs.pylonsproject.org/projects/ deform/en/latest/basics.html) seem to completely ignore any notion of models, or data sources, offering users to create a schema anew. Sometimes some kind of coupling is needed. -- 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.
