The best clientside solution is splitting up the task in small subtasks and using a timer. The good thing about timers is, that their processing is skipped, if the player is under heavy demand, whereas frames are excuted in any case, which might make your ui unresponsive.
Cheers Ralf. On Nov 10, 2007 11:08 AM, barry.beattie <[EMAIL PROTECTED]> wrote: > > > > > > > > > People have been begging for some kind of threading for a long time, > > but the Flash Player team seems pretty adamant that this won't happen > > any time soon. > > and, IMHO, fair enough too. The SWF is just the UI, it's not the whole > application**. There's async calls to the server and Java (and ow > CF)have threading as well. Just how much of the layers of an > application do people want the UI to do? > > And it's quite possible that it won't just be the CF/PHP/Java code > that does the heavy lifting either (well, maybe not in this case...) - > it could very well be the database doing hundreds of lines of SQL > munging to get data to run some charts (eg: it doesn't make sence to > pull raw data into the SWF - then do a ton of processing on a single > thread - just to run some charts). > > Onions - they have layers. Ogres - they have layers. Applications - > they have layers too. > > ** OK, so there are some grey areas where applications are ALL UI and > very little else. Still.. > > >
