Consider an application like Netvibes. You load lots of widgets at runtime, based on user config.
hi again,
just to clarify, when there is no interaction between other applications a split should be considered?. it seems this area could become gray went a little interaction may be called for.
ie. in the case off Netvibes , a widgets location or perhaps what widget to load etc.
On a side note:
It feels to me much confusion lies in the what, where, why. with regards to pureMVC. looking into the code definitely helps but as a newbie it would be nice to see just the outline of what went where why, even perhaps if they where theoretical and there was no source code.
eg.
FOO COMPANY:overview:
basically a page allowing a login process, user details and their account details, Singleton method used.
models:
user - Basic user details, ID password
account - basic account details, name address
Views:
login UI
user details
basic account details
advanced account details
controller:
etc.
Other stuff Im unsure about: ...lol
This of course is a very simple outline and majority of websites would be far more complex with transition management, multiMVC's, deep linking or state machines.
I'm not sure if you would find this helpful to have in the Docs section
I'm willing to work through the current demo source code and extrapolate into some form of overview but it would also be nice if others with far more experience upon completing their project would consider this form of breakdown.
Anyway just a thought.
Many thanks for the time you've invested in pureMVC