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
The slides are available here: 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!
