-1 for yet another complication on the scaffolding app. @Joe: web2py has several ways to accomplish what you want, but all of them come with a cost (as anything else called "feature" in every framework of every programming language). There isn't a silver bullet that goes well with all kinds of "business requirements". Yep, ajax is fun but having a page with 64 'loading...' fragments is not going to be a nice page both from the user perspective and for your server, that needs to "reply" 64 times instead of just one to build the page. Same thing goes for web2py having to dinamically figure out 64 "fragments" and compile them every time a user hits the page. On the other end, you may find that your site needs a "modularized" approach only on some pages, and nothing in web2py prevents you to have different layout.html written as you wish, called as you like. On the argument of having scripts, css and such inserted dynamically in fragments only when they're needed...unless you have 1MB of gzipped css and js.....it's really not a valid argument. Just include all of them on the "index" page, and if cached correctly only the first page will be slowed down (maybe for 200ms ?!) . All subsequent fragments will not have to deal with them, as they are fetched from the browser's cache.
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
