Erik,
I'm not talking about compiler plugins here. But yeah I see your point
with the MXMLJC front end.
Don't worry about it, I just wanted to put it on the record. If there
was a change I will probably be the one that does it. :)
Anyway, as long as we keep doing it the way were are, the only coupled
part to this change is the MXMLCJS front end which would then become
abstract an call backends through a standardized API (with plugins).
Mike
Quoting Erik de Bruin <e...@ixsoftware.nl>:
If I remember correctly, didn't you and Roland have some idea on how
to implement this? I wouldn't know where to begin ;-) I'm afraid that
until some of you coding demi-gods can spare the cycles to build this
to a point where mere mortals can take over and implement, the only
way forward is "monolithic".
EdB
On Fri, Mar 22, 2013 at 2:55 PM, Michael Schmalle
<apa...@teotigraphix.com> wrote:
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
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
