There currently aren’t any options for true multi-threading in Flex or AIR. Apparently, Adobe thinks that every app that exists is nothing more than a webapp that needs one or two desktop capabilities. Projects such as Merapi prove that developers greatly desire much more power than is currently being given to us. For my own application WCAP, I need to do some pretty heavy-duty computations and matrix manipulations to analyze a schematic. Right now, I’m simulating threading by breaking up the calculations into chunks and updating the UI with a progress bar between each chunk. This always uses only one of my two processor cores and ends up taking a significant amount of time because my software is crippled. I don’t use Merapi because it’s not easily deployable/updatable along with my AIR app.
It’s also not feasible for me to put the calculation logic on a server and have it calculate remotely. This software needs to be able to run out in the field or at the job site where a net connection may not be available.
I made a video (click the picture above) of my software just so folks can get a good understanding of why this is really needed and not just a want.
January 15th, 2009 at 1:45 pm
Have you had a look at pixel bender? – http://labs.adobe.com/technologies/pixelbender/
November 29th, 2009 at 6:26 pm
I’m starting to develop a large app in AIR. Looks like you are a really experienced developer with Flex, etc. In your opinion, is AIR ready for prime time?
March 5th, 2010 at 10:53 am
Maybe you could have a C# app with a httplistener listening for calls on a localhost port. Flex could then send HttpService requests to this pseudo-server, which could carry out the logic. I think.
March 5th, 2010 at 11:39 am
@Brian,
I’m probably going to end up writing a native C++ app to handle the calculations once AIR 2.0 is released. Although, that really defeats the purpose of AIR being cross-platform. You then lose the capability to use the AIR updater and you have to compile for windows/mac/linux separately.