Comments on: Loading Flex Applications Into Flex Applications Gotcha: App Resizing https://jessewarden.com/2007/05/loading-flex-applications-into-flex-applications-gotcha-app-resizing.html Software | Fitness | Gaming Sun, 13 May 2007 02:17:03 +0000 hourly 1 By: MIke Britton https://jessewarden.com/2007/05/loading-flex-applications-into-flex-applications-gotcha-app-resizing.html/comment-page-1#comment-4279 Sun, 13 May 2007 02:17:03 +0000 http://jessewarden.com/?p=1158#comment-4279 I really think there are three options, and using SWFLoader isn’t one of them, as we found out. One is to use modules. Another is to make the child app a library project or SWC, and create mxml components inside the original app that consume data from the SWC. The last solution is to merge the business logic between the two apps. I like the latter of course, since there’s more separation of business logic from presentation. However there’s still the problem of two apps using the same version of Cairngorm. Now that 2.2 is a fraction of the size of 2.1, that’s not a show-stopper. But why should two separate apps compile with their own Cairngorm? Now we get into the architecture more hard-core, and it becomes apparent that a central SWC for business logic is needed for the two apps to play nicely. So…the SWC being used to return your service calls should have hooks for my service calls. That way I can elegantly blend in my code with yours, and we all win, in theory, because there’s a central API for all of it. This may be the direction we should go.

Thoughts?

]]> By: Tracy https://jessewarden.com/2007/05/loading-flex-applications-into-flex-applications-gotcha-app-resizing.html/comment-page-1#comment-4278 Thu, 10 May 2007 12:45:08 +0000 http://jessewarden.com/?p=1158#comment-4278 Hi Jesse

We had a similar issue where we had to load 1 Flex app into another with a similar codebase. We went the route of loading the 2nd app via SWFLoader (fortunately the 2nd codebase was so small that we could get around the similar codebase issue by changing its package structure without too much bloat in the runtime code)

Everything has been running smoothly, but I checked for the bug u described this morning and whooa – it broke. With our app we add & remove it to a DisplayObject on the stage to control its visibility. Our 2nd app doesnt make too much use of the stage object, so again I could get away with a simple quickfix by just checking whether the stage is null.

Thanks for the tip off, very useful :)

]]> By: Mike Britton https://jessewarden.com/2007/05/loading-flex-applications-into-flex-applications-gotcha-app-resizing.html/comment-page-1#comment-4277 Thu, 10 May 2007 00:10:20 +0000 http://jessewarden.com/?p=1158#comment-4277 Yep, seems like it’s either modules, components or SWCs.

]]>