Yes, you can keep the AIR and FP specific code in separate modules and load them in to inject. That keeps your initial swf size small.
Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of handitan Sent: 11 February 2009 21:32 To: [email protected] Subject: [flexcoders] Re: Discussing "Shared Codebase between Flex and AIR project" Hi Gregor, Thank you for your suggestion. It took me a while to digest your suggestion but I think I got a working example. If I had followed your suggestion correctly, the "front end" is becoming fat. What I meant by that is the front end is where all interface implementations resided and have those implementations assigned to the appropriate classes, which the modules are going to be using. I hope that I interpret your suggestion correctly. --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Gregor Kiddie" <gkid...@...> wrote: > > We've used the strategy pattern for this. > > We do something similar to how ToolTipManager uses toolTipClass. > > When the app starts up (or module is loaded), the correct classes are > injected into the files which have AIR / player differences. > > We also have two "front end" swfs which are little more than preloaders > primed with appropriate classes for the rest of the application. > > > > As an example, we've used this mechanism to cache the same data in the > SQLite DB in AIR, or a Shared Object in the Flash player via the same > call (i.e. the rest of the app was agnostic to whether it was in AIR or > FP) > > > > Gk. > > Gregor Kiddie > Senior Developer > INPS > > Tel: 01382 564343 > > Registered address: The Bread Factory, 1a Broughton Street, London SW8 > 3QJ > > Registered Number: 1788577 > > Registered in the UK > > Visit our Internet Web site at www.inps.co.uk > <blocked::http://www.inps.co.uk/ <http://www.inps.co.uk/> > > > The information in this internet email is confidential and is intended > solely for the addressee. Access, copying or re-use of information in it > by anyone else is not authorised. Any views or opinions presented are > solely those of the author and do not necessarily represent those of > INPS or any of its affiliates. If you are not the intended recipient > please contact is.helpd...@... > > ________________________________ > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of handitan > Sent: 11 February 2009 16:31 > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Discussing "Shared Codebase between Flex and AIR > project" > > > > Hi gang, > > Yes, it's another one :) But I am going to approach it a different > way. > My question is based on David Coletta's MAX presentation. > If you haven't seen his presentation, please watch here: > http://tv.adobe.com/#vi+f15384v1022 <http://tv.adobe.com/#vi+f15384v1022> > <http://tv.adobe.com/#vi+f15384v1022 <http://tv.adobe.com/#vi+f15384v1022> > > > The slides are available here: > http://www.slideshare.net/dcoletta/DavidColettaArchitecting-a- <http://www.slideshare.net/dcoletta/DavidColettaArchitecting-a-> Shared- > <http://www.slideshare.net/dcoletta/DavidColettaArchitecting-a- <http://www.slideshare.net/dcoletta/DavidColettaArchitecting-a-> Shared-> > Codebase-for-Browser-and-DesktopFinal > > To everyone who has seen his presentations, could you help me out in > understanding how his "Browser SWFs included in AIR file" works to > solve the "Shared code packaging" ? > > This is what I understand on what he did with that approach: > 1. Only have one AIR project that contains all AIR implementation. > 2. Each of your module's common functionality, extract them out to an > interface and then have Flex-specific and AIR-specific class > implements the interface. > > So I am kind of get the idea but I have a very hard time understanding > on how he was able to get each module to have the AIR project to serve > the module's AIR-implementation needs? > > Thanks! >
