On 10/1/06, Douglas Knudsen <[EMAIL PROTECTED]> wrote:
Ok, going through some discussions with some fellow employees on this. What is a best practise for exposing data in custom components?
case 1: simple data. eg, a fancy date selection component that exposes a selectedDate value. Seems in this case a custom getter method in front of a privte variable. Can you bind on this well enough? Looking at DateChooser.as as a example, it appears this is a typical way.
case 2: complex data. eg, a custom component that does a employee search dumping data into a EmployeeVO object. How to expose? Same as in case 1? OR should there be a custom event thrown containing the EmployeeVO object as a payload? Should something like this expose the data in a generic AS Object to be more easily used perhaps, ie no need to import EmployeeVO?
thoughts?
--
Douglas Knudsen
http://www.cubicleman.com
this is my signature, like it
--
Douglas Knudsen
http://www.cubicleman.com
this is my signature, like it? __._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Software development tool | Software development | Software development services |
| Home design software | Software development company |
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
__,_._,___
