Thanks Robert, looks interesting! The Ant idea was interesting too, but I have a feeling that in the future we'd want to use some AIR-specific APIs, and I don't think an Ant task could accomplish that. The pattern that article outlines sounds just right for the job.
~Geoff --- In flexcoders@yahoogroups.com, "Robert Cadena" <[EMAIL PROTECTED]> wrote: > > Hi Geoff, > > Here's a link that should be helpful: > http://www.adobe.com/devnet/air/flex/articles/flex_air_codebase.html > > Some time ago I dealt with the same issue on Flex 2 beta. Basically, the > way I dealt with it was to extract all the functionality into a Library > Project, then create an AIR and a Flex project that is simply a "shell" > that brings in the library project. > > I did this when I was too lazy to make an ant build file that could generate > both Flex and AIR from the same project and because it was easier for > developers not used to ant to pick up and use in Flex Builder. If I had the > time I would make an ant file but separating into a library is quick and > easy. > > best of luck > > /r > http://www.searchcoders.com/ > > > On Wed, May 7, 2008 at 10:18 AM, Geoffrey <[EMAIL PROTECTED]> wrote: > > > I have an existing Flex app... a pretty complex one. Multiple > > projects, J2EE backend, RemoteObject calls, BlazeDS messaging with > > JMS, etc, etc. > > > > What's the best way to convert this existing app to an AIR app? Would > > it be possible to just reference the SWF from the "main" Flex app? > > I'd rather not copy the entire "main" flex project into the newly > > created AIR package. That would be a lot of duplicate code. > > > > Thanks, > > Geoff > > > > > > ------------------------------------ > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > > Links > > > > > > > > >
