I buy the 80-20 rule. But that is a self-fulfilling prophecy. I think you are all doing a great job developing web2py, however, in my opinion Web2py tends to cater too much to users who develop web 2.0 applications, to some degree disregarding users who use web2py to provide a web interface for existing information systems or require a different workflow.
I have a normalized database containing a.o. a company table which is referenced by 10 other tables (address, nfa, et cetera). The database will contain thousands of companies, only a percentage of these companies will manage their own data on two levels (core and site). These companies apply for a username and password by sending an application form to the site administrator. The site administrator will perform user registration and no verification mail will be sent. Contrary to the workflow in web2py users will register after their records have been created, at this point problems emerge. Furthermore, I divided my application into sub-applications (database (to keep me out of DAL trouble ;-), cms, b2c, b2b (both read-only) etc.), from this perspective web2py is the database-driven web application. This perspective also enables me to turn some of the sub- applications into appliances and re-use them. Kind regards, Annet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
