[web2py] Here's a theory question

2010-03-30 Thread Thadeus Burgess
How do you MVC a javascript client application? So I have web2py acting as the server, and I write a Javascript GUI (based off extjs or similar library). So of course this goes in the View files... The interesting question is that these client side js have their own MCV on top of that (models

Re: [web2py] Here's a theory question

2010-03-30 Thread Timothy Farrell
This is my best understanding (using ExtJS as an case-study): Models -- Stores (Generally these communicate with the server side) Views -- Layouts + Widgets (these generate and respond to events) Controllers -- Events that control interactions between widgets and stores Ext has simplified

Re: [web2py] Here's a theory question

2010-03-30 Thread Thadeus Burgess
Aye, this I understand, but for every web2py view, you need a js (model, view, controller). The question is how should these be physically laid out while still keeping symbolism as they all are apart of the same web2py view? -Thadeus On Tue, Mar 30, 2010 at 1:45 PM, Timothy Farrell

Re: [web2py] Here's a theory question

2010-03-30 Thread Timothy Farrell
I think you're trying to over-complicate things. web2py is built around the idea of the server-client (or request-response) relationship. While capable of Ajax, the default paradigm of web2py reloads pages on most requests. In this model (not to be confused with the Model portion of MVC),