Hi,

I'm writing my first flex app.
So far it all works, but I'm getting to the point where I need to start
structuring it, for ease of further development.
Right now I simply have many functions defined within the <script> tag
within the <application>.
I'm now thinking through my options for structuring this better. I'm not
asking for *specific* structuring recomendations, as I know that would be
imposisble w/o you knowing the specifics of what I'm doing.

What I'm looking for is a good place to read about the different options, so
I can learn about them.
Preferable free online, or in Safari Books Online.

To be clear: when I say structural options I mean things like:
a) having all the code in the <script>
b) putting the code in a seperate .as and point <script source=""> at it (I
know this is very similar to (a) )
c) using static methods in a 'static' class
d) creating classes to fully OOize the code
e) something else I dont yet know about...

I'm reading 'Advanced Action Script 3 with Design Patterns', which I hope
will help, but I would like to have some flex specific knowledge also, so
that I can see examples of how to allow objects outside the <application> to
access those defined by mxml within the application (like buttons). I'm
concerned that will end up with a lot of Application.application.foo type
code - is that 'normal'?

I'm hoping this makes enough sense...

thanks

tom

Reply via email to