Re: [web2py] large sites/application.

2010-05-13 Thread Álvaro Justen
On Thu, May 13, 2010 at 23:07, Thadeus Burgess wrote: > But the problem with web2py is that what if you don't want portal > models to execute when they are on the public portion of the site? But > the public depends on the portals models and visa versa. No matter > which way you hash it, your goin

Re: [web2py] large sites/application.

2010-05-13 Thread Thadeus Burgess
But the problem with web2py is that what if you don't want portal models to execute when they are on the public portion of the site? But the public depends on the portals models and visa versa. No matter which way you hash it, your going to have a massive web2py spaghetti on your plate with some gi

Re: [web2py] large sites/application.

2010-05-13 Thread Alexandre Andrade
to build large app, you can: 1. split you tables over several models, like db.py db_000_user_management.py db_001_portal.py db_002_ecommerce.py and so on. 2. split your code and html over several controllers: default.py portal.py shop.py views/default/*.html views/portal/*.html views/shop/*.ht

[web2py] large sites/application.

2010-05-13 Thread thedangler
I'm confused when to make apps. I'll be making a pretty decent size website and it has over 30 tables. The site will have different functionalities and for the most part i have only seen code for apps that do two or one thing. So do i make multiple apps. If so how do i know when to make a new one.