Question

I we have been working for some years in a flex (cairgorn)+spring+blazeDataservice application using blazeDataservice to connect to the back end, now its getting kind of big and takes too much time too load, and people who use it, normally need it to use it regulary.

My country’s internet bandwith is not getting better, actually it´s getting worse, so the app gets bigger and bandwith gets worse so loading it it’s getting slower by the day.

I was wondering how could I get the client to be installed on peoples computers, I would be turning a flex online app into a desktop app WITHOUT REWRITING IT. I only need someone to point me in the right direction, i was thinking about 2 options:

1.- Can it be turned into adobe air ? is in´t adobe air desktop ?

2.- Maybe a flash that runs in peoples desktop ?

I need everything to work against the host spring backend just like it does today

Thank you very much!

Answer 1

Just to be clear:

If it is the size of the app (SWF) itself, rather than the queries being performed, an another alternative to speed things up, without building a Desktop (AIR) version, would be to use what Flex calls Modules.

Basically you would be breaking your app into smaller pieces that get loaded only as necessary.

If you do go the Desktop (AIR) route, you may also want to explore a local SQLite database that Syncs with your server only as needed, thus further reducing the internet connectivity issues.

This would of course add to your development time, but it seems like it might be a good bet given the situation you describe.

As for where to start, switching from a Web to a Desktop (AIR) app can be as simple as changing the main MXML tag from (in Flex 3) mx:Application to mx:WindowedApplication and launching your app.

UPDATE in response to follow up question:

Hard to say how much rewriting would be involved without knowing how your code is currently structured, but doubtful it would be a major rewrite.

As an experiment, I would suggest the following:

1. Create a new Flex application.
2. Create a new Module.
3. Add some simple MXML and Actionscript to the Module.
4. Add an instance of the Module to your Main view.
5. Run/Compile.

What you should see is that you might as well have not wrapped it in a Module at all, from a functionality or coding perspective, but the Module will have been compiled into a separate SWF, and Flex will handle loading it as needed.

If that all works and makes sense, I would start breaking up pieces of your code into Modules and see if that begins to solve your problem.