Employee Directory
Return to table of contents Let’s say you want to modify Employee Directory for your own company and you want to add another filed (fax) to the employee data. How to do this? In EmployeePanelDetail.mxml, add the following block. <!-- fax --&
Employee Directory is an AIR sample application from which I learned a lot. (try it) Here I post some of what I learned here. 1. introduction 2. structure 2.1 singleton 2.2 command 2.3 Cairngorm 3. ui 3.1 style 3.2 size 3.3 component 4. flow 5 events
Return to table of contents ED’s custom events don’t override the clone() method: it doesn’t need because the events are never redispatched. When I test one of my applications I kept getting the following error: Error #1034: Type Co
Return to table of contents ED defines 4 custom events,CommandCompleteEventCommandProgressEventDataSynchronizationEventSelectedItemChangeEvent The main job of these custom events seems to define constant (say public static const COMPLETE : String = &
Return to table of contents All command classes are inherited from class Command. By name, commands perform something. Every command has execute() which does the job, and emits progress and complete event, and possibly error event. The base class, Co
Return to table of contents 1. CustomAutoComplete This component can be very useful. It pops up a list of suggestions based on characters entered by the user. This is a very simple example on how to use it: <controls:CustomAutoComplete id="se
Return to table of contents After the application is initialized, Event “applicationComplete” is dispatched and the following function is called: // in employeedirectory.mxml ui.init(); Go to ApplicationUI.mxml, we find ui.init() issues t
Return to table of contents In ApplicationUI.mxml (init()), you will find the following two lines: // in ApplicationUI.mxml, in init() titleControls.addEventListener( "showHelp", showHelpScreen ); addEventListener( "close", closeP
Return to table of contents Which line(s) in the code determines the size of the application? This seemingly simple question did take me some time. The answer lines in the following two lines: // in ApplicationUI.mxml <mx:vbox id="contentBox&
