Re: [flexcoders] Spltting up code (best practice)

[Anatole Tartakovsky]

#include is the same format as C ie #include "../mycode/code.as" The link for RSL - http://www.macromedia.com/devnet/flex/articles/rsl.html - the article lists available syntax rules and explains tradeoffs - you can also read any article on dynamic linking for any other environment . HTH, Anatole   ----- Original Message ----- From: Jonathan Miranda To: flexcoders@yahoogroups.com Sent: Monday, February 13, 2006 1:48 PM Subject: RE: [flexcoders] Spltting up code (best practice) Got any place I can read more about RSLs? And using the #include how do you include in my example? So the form would have #include ../../main.mxml while the main would have #include com/mine/form.mxml? _________________________________________ Jonathan Miranda Flexible Master of the Web "In the game of chess, it's important to never let your opponent see your pieces."   From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Anatole Tartakovsky Sent: Monday, February 13, 2006 11:11 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Spltting up code (best practice)   You can use #include statement the same way you would use it in C. That pretty much solves the issues of code separation. The way you slice it is very much up to your preferences - as it does not really serves the code partitioning, but rather readability purposes. The fun begins when you decide to abandon static code linkage and go dynamic. That is important in the event when you develop application thet would be dynamically configured by the end-users. You need to package your software in a way it can be assembled in the run-time - with minimal overhead. That very much call for usage of RSLs for large components, data-driven UI and ability to dynamically create/cache compiled code. Depending if you are interested in "readability" or "dynamics" of the code different solutions can be derived Here is the brief internal training video of the component that utilizes dynamic classes : http://demo.xmlsp.net/dataservice%206/dataservice%206.html Hope this helps, Anatole Tartakovsky   ----- Original Message ----- From: Jonathan Miranda To: flexcoders@yahoogroups.com Sent: Monday, February 13, 2006 12:10 PM Subject: [flexcoders] Spltting up code (best practice)   Alright, I have a main.mxml application file and an actionscript file that gets included. In the application let’s say I have a Form, that I want to pull out into another file. What’s the best practice for how this is accomplished if the Form needs to reference id’s in the main app, functions in the actionscript file, and the app/as to the form. I’ve already got some bad habits with coldfusion, rather get into the habit of doing this “the right way” – if there is one. _________________________________________ Jonathan Miranda Flexible Master of the Web "In the game of chess, it's important to never let your opponent see your pieces." -- 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 Web site design development Computer software development Software design and development Macromedia flex Software development best practice YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.