On Wednesday 23 August 2006 02:03, Darren Houle wrote:
> Very true. Alternatively you could create these three data structure
> within the one ModelLocator and refer to them like...
> model.biz.userRole = ...
> model.core.adminViewStackState = ...
> model.icon.deleteButton = ...
I would tend to g
>Start off with one model for your app and as your application grows, you
>will probably see the need to refactor. At that time, create a second model
>and so on and so forth. Just to give u a quick idea, I have 3 models in my
>current project:
>BizModel - hold main data that actually goes back
Start off with one model for your app and as your
application grows, you will probably see the need to refactor. At that time,
create a second model and so on and so forth. Just to give u a quick idea, I
have 3 models in my current project:
BizModel - hold main data that actually goes bac
Yup, you got it. To be even more specific...
1:N Views
A) bind to data in the
1 ModelLocator (which contains 0:N Models/VO's)
and B) broadcast
1:N Events
to the
1 FrontController
which maps Events to
1:N Commands
which may create
0:N Delegates
which trigger
0:N Services (using 1
Yes, although i have heard of succesful implementations
that use more than 1 controller and locator.
I think that, that is the idea until it doesn't satisfy
your requirements anymore
Regards,
Bjorn Schultheiss
Senior Flash Developer
QDC Technologies
From: flexcoders@yahoogroups.com
5 matches
Mail list logo