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

Mon, 13 Feb 2006 11:34:23 -0800

>But my favorite (which requires a bit more work) is to make your application implement an interface that you define:

I think this is a very good way also. As far as includes, don't laugh but, I would lean away from this technique because Flex isn't C.

I have started using a Manager class to 'register' components on intertwined main apps.

    public final class ExpressionsPaneManager
    {
        private static var library:ExpressionsLibraryPane;

        /**
         *
         */
        public static function getLibraryPane():ExpressionsLibraryPane
        {
            return library;           
        }
       
        /**
         *
         */       
        public static function registerLibraryPane(value:ExpressionsLibraryPane):void
        {
            library = value;           
        }
}

I know there are other ways but this seems to be a really fun way of doing it. I really depends on your implementation. Just like in oop patterns, you can't always apply a 'certain' pattern to a ceratin problem. You have to mix the implementation abit.

This provides two major things for me;

1. Even though static, it creates an interface for your main application. You are defining your 'main' components/modules of the application. (obviously this will not work in all situations)

2. You are creating a single acces point for all components to share. There is no dependency on a setThis(this) routine. (but I also use this in different situations) I would use the setRef(this) when you are not dealing with aggragated components, more of a smaller view into a single component or small app.

Anyway, I can't bring myself to use include but, I have not programmed C either :)

Peace, Mike

PS One other thing that starts to get interesting is; your manager class could start to do things even more intelligent like manage component transitions, positions, states. Real fun, look at is as the center of the wheel and your application forms fan out around it like spokes.



On 2/13/06, Anatole Tartakovsky <[EMAIL PROTECTED]> wrote:
#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 -----
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: [email protected] [mailto: [email protected]] On Behalf Of Anatole Tartakovsky
Sent: Monday, February 13, 2006 11:11 AM
To: [email protected]
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 -----

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





--
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



Reply via email to