Hi all,
In a current application I am building, the administrative application
has a screen (We'll call it Products) with no less than 30 various
components gathering data to be fed to a CFC and consequently to a SQL
Server database.
I easily can load the options from the server and bind them to the
controls via my RPC calls and a little elbow grease in the model to
format the data. No problem there.
All components are bound to their respective properties in my
OptionsVO (A special Value Object created to hold all the server data
returned)
Now, it's time to store all the selected data on the client and it
seems I am left with some options.
My first instinct is to fire custom events (which, in Cairngorm, are
translated to Commands, etc.) for each time the Component changes via
the "change" property. So, for example <mx:List id='myList'
change={EVENT CODE}/> - Then the commands mapped to the Events do the
work of updating the VO storing the data.
But if a user is going through the form fast, I have two concerns:
1. Wouldn't 30 events firing off in a row cause the app to be sluggish?
2. There has to be an easier way to store all that data without
writing 30 separate commands/events, one for each component.
---
I guess I could just use the change event to update the model
directly... but from what I understand that is a big no no in proper MVC.
Any help is much appreciated. Sorry for the long post. :)
-Kenny
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
