Hi Carlos, Are you sure you don't just want to try to port Swiz? I think Harbs/Yishay and maybe others got some other framework to port over. If you port, you know the untouched code paths are operational. If you start over you have to prove every line of code. And if you do port Swiz, that will attract a few migration candidates.
Thanks, -Alex On 2/9/17, 1:52 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote: >Thanks Alex, > >I'll try to make things simple and bypass class domain stuff. If at the >end >I need it I'll check that. My approximation is get the most simple engine >working and then make progress from there. > >Thanks! > > >2017-02-09 21:14 GMT+01:00 Alex Harui <aha...@adobe.com>: > >> >> >> 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 >> >> > > >-- > >Carlos Rovira >Director General >M: +34 607 22 60 05 >http://www.codeoscopic.com >http://www.avant2.es > >Este mensaje se dirige exclusivamente a su destinatario y puede contener >información privilegiada o confidencial. Si ha recibido este mensaje por >error, le rogamos que nos lo comunique inmediatamente por esta misma vía y >proceda a su destrucción. > >De la vigente Ley Orgánica de Protección de Datos (15/1999), le >comunicamos >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC >S.A. La finalidad de dicho tratamiento es facilitar la prestación del >servicio o información solicitados, teniendo usted derecho de acceso, >rectificación, cancelación y oposición de sus datos dirigiéndose a >nuestras >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación >necesaria.
