----- Original Message -----
From: "ben gomez farrell" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list" <[email protected]>
Sent: Monday, December 17, 2007 5:07 PM
Subject: [Flashcoders] Another sort of Off Topic Flex question
First of all, I'll ask this....
Where is that flexcoders list you all talk about? I don't see anything
under figleaf, and the only Flex coders list I found on google is a yahoo
groups one, and I haven't gotten a single email from them yet - so I'm
thinking there's some kind of SECRET one.
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
Anyway, my question that I will post once I find the flexcoders list ties
into the Flash 9 player, and I guess is really both a Flex AND Flash
question, so I'll ask you guys first.
I'm working with an application in Flex, and using states to switch back
and forth between components. You can kind of think of each component as
a "page" of my Flex application, and each "page" is a state that I go back
and forth to from a main navigation.
It first occurred to me that my states don't really go away when I had an
enter frame event attached to one of my component pages. Of course it's
easy and good practice to clean those kinds of things up when I'm not
using them - but even then - when I go back to my component page, it's in
exactly the same state as I left it. Anything I interacted with on screen
is there in the exact same state and position.
So this stuff is not going away when I switch states. I guess, when I
think about it, it makes sense. But I'm wondering if I should be worried
as my application picks up complexity? Essentially, it's a question of
when I remove children from the stage - should I worry they still exist?
A lot of people use states to control viewstacks that represent a page of
the application. It all depends what you are trying to achieve.
I guess its a question of best practices in Flex. Do you folks author
applications in this way - using states to navigate between several large
component pieces? Or do you get smarter and break it out into smaller
SWFs using an AS3 only shell to do all the garbage collecting yourself of
the SWFs?
I don't do that, but Flex does have modules.
Paul
Thanks! Things seem to work pretty well right now, but I'd just hate at
the end of this project when we have all our graphics in that it runs all
sluggishly because everything's running at once.
ben
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
