Thanks. I thought this was the situation, but I wanted to check. Nice work on the werkzeug documentation. It doesn't seem complete to me but I think it gives me a pretty good idea how to read the source to get the full picture.
One complaint: I personally don't find the tutorial easy to follow because of the external dependancy on sqlAlchemy. This is a particularly sticky issue with me because I find all OR mappers irritating because I know I could understand everything if I could just see the actual SQL. Suggestion: Why not factor out the data access layer into a module that you take as "given" and leave just the werkzeug stuff exposed in the tutorial. I would even advocate removing the template dependancy. Otherwise you almost have to read two other tutorials in preparation for the werkzeug tutorial. Thanks! -- Aaron Watters On May 1, 5:58 am, Armin Ronacher <[EMAIL PROTECTED]> wrote: > Hi, > > Aaron Watters wrote: > > If this makes any sense, what do you think? And have > > you implemented it? Could it be added easily to > > one of the pocoo libs if not? > > Our only library that deals with the technologies mentioned is werkzeug > and that's just a toolkit to create web applications but doesn't enforce > any direction. If you want to do something like that I would suggest you > create a microframework on top of Werkzeug. > > Regards, > Armin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
