# ARP workflow with FAMES/MTASC **URL:** \ **Category:** flash\ **Created:** [December 14, 2005, 7:17pm UTC](https://forum.kirupa.com/t/arp-workflow-with-fames-mtasc/172483 "2005-12-14T19:17:11Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![celoserpa](https://avatars.discourse-cdn.com/v4/letter/c/cdc98d/32.png) [@celoserpa](https://forum.kirupa.com/u/celoserpa)\ **Post date:** [December 14, 2005, 7:17pm UTC](https://forum.kirupa.com/t/arp-workflow-with-fames-mtasc/172483/1 "2005-12-14T19:17:11Z")
Which would be the best way to implement an ARP-based application in FAMES/MTASC platform, the one which would provide the best workflow? I thought in doing this way: [list] [_] Create the main (shell) form class that extends the com.ariaware.ArpForm class; this form would load all the other forms on demand, at runtime; [_] Create the other child forms that would also extend the com.ariawarte.ArpForm; these forms would be loaded by the main (shell) form. [_] Do the layout inside of the forms inside the Flash IDE and don´t do any class linking yet (as this will be done trough code). [_] Implement the main form shell engine first (the pre-loading code, the main interface, etc) also the graphic design will be done in flash and the class linking and compilation via code. [\*] Implement the child forms following the same workflow. [/list] I guess that this way I could use the flash IDE ONLY for graphics design and FAME for all the coding and compilation work… what do you think? Another doubt is regarding Application initialization… the main form, the one which will have the static entry point main() will have to create a instance of itself and register the library symbol to **itself** , then attach the movie to the \_root, or should I already place a instance of the ApplicationForm movieclip in the stage trough the Flash IDE, but this way I would have to do the class linking via the IDE, am I right? Thanks in advance! 🙂