> > The namespace and MVC in in the new AS/JS framework but I don't think > there is anything in the current FlexJS setup what would block you from > swapping in a set of SWCs that use the mx and/or spark NS. >
No, I'm actually swapping OUT the mx and/or Spark NS from the regular SDK. VF2JS projects are regular Flex projects, using the 4.13.0 SDK or whatever is current at the time. User code normally, with the regular Flex namespaces. They use the normal workflow to debug and publish their projects to SWF. Only when the chose to publish to JS the fun starts. I create a copy of their regular MX/Spark project, swap out the 's' and 'mx' namespaces for the new ones I created and feed that temporary copy to FalconJX. Since it uses the new namespaces, the compiler will compile against the shim components I created in the accompanying projects. That way if there are APIs used in the regular Flex project that are not supported in the JavaScript framework - and therefor not present in the shims- the compiler will warn the user and ignore that API. >On the JS side, > >no MXML as data, just objects/components and much more integration with > >the > >GC Library (createDom, enterDocument and Dispose for life cycle of any > >component; event handling through current API instead of deprecated stuff; > >ES5 and 6 etc.). > Other than MXML as data, I don't think there is anything about current > FlexJS that would prevent you from building out a JS library that uses > more of GC as you want. I hope there will be libraries that live on top > of Jquery, Angular, etc > Trust me, I build a lot of the FalconJX code that translates AS/MXML to JS, as well as some of the core functionality of the JS framework and there is a lot of room for improvement in there. > I'm just looking for ways to avoid us doing some things twice. > I've been doing that as well for the last couple of years. I spent most of my time getting FlexJS off the ground. But I don't agree with some of the basic assumptions and choices that FlexJS has made. I said little or nothing about it to give FlexJS a proper head start and to keep you and Peter going. But now that I have re-evaluated what the project means to me, and what I would like to spend my time on when contributing, and I have to give my take on Flex to JS a try. I will keep supporting FlexJS where it concerns changes/enhancements that need to be made to FalconJX, of course. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
