On 2/9/17, 11:07 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>HI Alex, > >Swiz use ApplicaionDomain extensively. If we don't have yet and doesn't >have sense in FlexJS world I can try to remove it. What is it using ApplicationDomains for? IOW, if it is just as the wrapper for reflection APIs, it should be straight forward to emulate. Every single-swf application has only one ApplicationDomain. Even apps that only use RSLs have only one ApplicationDomain. I would assume Swiz worked fine for those? It is only when you get into unloadable modules or SWFLoaders that load sub-applications that you really need ApplicationDomains concept of domains of classes. When I was doing the spark "port", I created the following class in the Spark branch to emulate the main ApplicationDomain APIs frameworks/projects/MX/src/main/flex/flex/system/DefinitionManager.as Maybe it will help you. It wasn't been fully tested. -Alex
