Hi Peter, ok, I couldn't try it yet, but I understand the purpose of that class. Maybe a Module is something different since in Flex a module had some characteristics:
1.- can't be loaded alone or without an Application hosting it 2.- can share (or not) the same ApplicationDomain (don't know exactly if we that concept in flexjs already) 3.- we had a ModuleLoader and a Module class. The later was the root class. 4.- we can have a project with multiple Modules inside and compile it as we compile the Application. One important thing was sharing data between application and modules, and between modules. I think SubAppLoader is the minimum we need for now and can wait for Modules. Maybe the name could be directly "ApplicationLoader" (what sounds better to me than SubAppLoader), what do you think? Thanks! 2017-02-03 22:43 GMT+01:00 Peter Ent <p...@adobe.com>: > I've renamed "Module" class to "SubAppLoader" since it is really just > loading one app into an another and not really what you'd expect "Module" > to do. > > The flexes-tour has also been updated to reflect that change. > > ‹peter > > On 2/2/17, 5:05 PM, "Peter Ent" <p...@adobe.com> wrote: > > >I've pushed a new HTML component to the develop branch. The component is > >"Module" and it can load .swf or .html files, depending on the runtime > >platform. I've incorporated this component into the TourJS project. > > > >If you build the flex-tourjs project, run either the > >TourJS/bin/js-release or TourJS/bin-debug version. Each has a few > >quirks/bugs to work out, but in general the Alert and Button examples > >will run (note: the SWF version does not run the ImageButton example yet). > > > >Regards, > >Peter Ent > >Adobe Systems/Apache Flex Project > > > > -- 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.