there have been replies to most of this, except for one: On Fri, Oct 23, 2009 at 5:02 AM, Doxaliber <[email protected]> wrote:
> > Hello everybody, > > > ...... > The cons (for now!): > 1) SQLFORM > 2) CRUD > 3) AUTH system > I'm not sure what you see as the CON for the AUTH system.... perhaps you could say more (I also didn't see anything particular for the CRUD either, but that perhaps is less interesting). Also, as for the object notation of an ORM: this is just at a different level of abstraction, and handy for programming. The DAL, being closer it the table definition (e.g. data definition) is really no harder to understand, but does make for a few effects: easier to prototype data (e.g. one type of prototype, early on, as forms and filling in can be automatic, and complete before all needed actions / behaviors are clear). Conceptually, it would not be impossible to have an ORM translate to the DAL as a backend, and thus have the best of both worlds. As it is, web2py development is decidedly not object / class oriented, and this has some current implications... but that topic can raise a lot of discussion among programmers, particularly beginners, or those not versed in the "language" of developing from human language / descriptions to objects (a benificial thing, for those who have experienced it). Regards, - Yarko > > That's all for now. I hope that the criticisms set out here can help > improve web2py. I apologize in advance for my bad English. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
