I also have an opinion of this;
Seeing as the code is getting large, I am going to suggest in the
future before any 1.0 release that we create a whole new sub project
repo with all the emitters and publishers.
From a framework perspective and the future of falconjx, I don't
think its wise to have all of the emitter implementations in the core
compiler.jx project repo. This adds jars that arn't required for
parts, IE the closure compiler should not be a dependency to use the
falconjx framework, which currently it is.
In the future, this framework could be used by various other tools and
allowing a developer to just checkout compiler.jx for it's core
visitor framework is a good idea in my opinion. If they want the
emitters, they can then check out that project. The core project would
have the base as and js emitter cores.
Mike
Quoting Alex Harui <aha...@adobe.com>:
On 3/22/13 12:36 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
I think both the FlexJS as well as VanillaSDK frameworks can benefit
from this. So it should be available to both. I don't know much about
XSLT, but if it 'converts one into another', I think it should
ultimately go with that other thing that 'converts one into another',
FalconJx.
But for now, as it is a work in progress, I think it's best place is
in ASJS, in the root, next to my 'publisher'. The publisher was also a
proof of concept, that has since been integrated into FalconJx.
Clear as mud, right?
I hope to get a look at FalconJX shortly, but in theory, you haven't changed
the FXG subcompiler and I think that's where this XSLT will eventually go.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
