The example in the documentation for the Button class shows a very simple example of this concept. http://livedocs.adobe.com/flex/3/langref/mx/controls/Button.html
I came from an AS1/AS2 background as well and there was definitely a learning curve but there is plenty of good information out there, including the docs themselves. I would suggest sitting down and reading through most of http://livedocs.adobe.com/flex/3/html/help.html?content=Part6_ProgAS_1.html and thoroughly studying http://livedocs.adobe.com/flex/3/html/16_Event_handling_1.html until you understand the event model. I think that was even a realization I came to at one point is that AS3 is ALL ABOUT the event model. Dispatching, capturing, handling, etc. If you don't understand events in AS3/Flex you are going to have a very hard time being productive. HTH, Ben --- In flexcoders@yahoogroups.com, "Jason The Saj" <[EMAIL PROTECTED]> wrote: > > "This may seem like a major restriction, but we had no problem writing > all the Flex components with this event model." > > And I am sure that most of the Adobe people who wrote the components > had training to use such methodology either in AS3 or other languages. > > Being newer to this structure, I find little documentation or basic > examples for this. While at the same time, I do question if having to > write a couple of pages worth of code just to pass an argument is > progress. > > Maybe it is better for certain enterprise level design. Maybe it's > better coding. But I think Adobe needs to do a better job helping > individuals transition such a change. > > And I am not the only one, I am hearing this from a number of friends > of mine. That said, I really like Adobe Flex. But I think Adobe > could make it a bit easier for it's older Flash developers to migrate > to. I really feel as if Adobe is catering to Java developers. And is > not doing as much to bring those developers who have mostly programmed > in AS1/AS2. > > - Jason >
