On 2/2/17, 10:59 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>I was going to suggest something down the path of: creating the primary
>artifact which contains library.swf and library-is.swf. We could use
>these in Ant, Maven and newer IDEs and additionally continue to produce a
>separate js-swc (a
f: Re: [FALCONJX] Combining SWF and JS compilers (was Re: AW:
[FalconJX][FlexJS] COMPJSC and Build order)
I'm going to try to respond to both you and Carlos.
IMO, there are "Application Developers" (AppDevs) and "Component/Framework
Developers" (CompDevs). Today, in FlexJS
I'm going to try to respond to both you and Carlos.
IMO, there are "Application Developers" (AppDevs) and "Component/Framework
Developers" (CompDevs). Today, in FlexJS, an AppDev can write MXML and AS
and use certain APIs and his/her code will run compile into a SWF or a
pile of JS.
But some Com
Hi Alex,
all I’m currently concerned about is that it will be painfull for our users.
And for us, because as soon as no-brain-developers will start using FlexJS, we
will probably be swamped with support requests. And I remember myself being
quite confused about it even now … so I usually try to
2017-02-02 17:38 GMT+01:00 Alex Harui :
>
>
> I have not worked with ANEs, but AIUI, there is one API definition and
> multiple platform object codes. For FlexJS SWCs there are different API
> definitions per platform.
Diferent APIs? mmm I thought that our objective was to have one API that
enca
There are already two lib folders (actually three). Today we have:
Frameworks/libs: XXX.SWC contains:
-Flash-based Class Definitions
-JS files for JS compiles
Frameworks/js/FlexJS/libs: XXXJS.SWC contains:
-JS.swc-based Class Definitions
Js/libs: SWC contains
-JS.swc-based Clas
I think self contain is better too. For example Adobe AIR does the same
with Multiplatform ANEs. If the ANE is implemented for iOS, Android, and
more,...all goes in the same .ane and I think that's really good, since the
library is in fact Multiplatform and ready to use for anyone in anyplace :)
2
Would it be somehow possible to make the swcs self-contained?
Right now they contain catalog.xml and library.swf … couldn’t this contain
something like a “catalog-js.xml” and a “library-js.swf” … this way we could
just add a dependency to a SWC and the compiler could internally grab what he
nee
So there would be two different lib folders? One for swf compilation and
another for js compilation? Maybe a third lib folder for “dual” compilation?
Here’s a thought: Would it be possible to create a “dual” swc which would
contain the definitions for both JS and SWF? And have falcon understand
I personally don’t care that much about Flash Builder. I’m moving more and more
over to VS Code. AIUI, VS Code picks up the compiler settings, so if there’s
both a js and swf library path, I’m thinking that it should work. Josh could
give a more definitive answer on that.
Our JS projects don’t
Hi Alex,
to figure about time schedules, it seems you have this already working on
your machine and need some latest touches and refienments right?
So in case I'll separate basic clases and tags, I think it would be better
to do after your change right?
Other way could be to introduce the tags in
On 2/1/17, 1:41 PM, "Harbs" wrote:
>One question: How do you envision swc for third party libraries if both
>JS and SWF swcs are being used?
>
>Is this strictly an SDK thing or would there be some mechanism for having
>split swcs for libs as well?
I think third-parties will also have to distri
On 2/1/17, 1:33 PM, "Harbs" wrote:
>This! I like!
>
>Theoretically it should make it possible to get correct code completion
>in both COMPILE::SWF and COMPILE::JS blocks. That would be a huge help!
Hmm. Not so sure about that. For one FB project, there is only one set
of SWCs and I don't kno
g without break Maven build I
>> think we should do this, but not in 0.8.0. We have now enough content to
>> release.
>>
>> Piotr
>>
>>
>>
>> -
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context:
>> ht
This! I like!
Theoretically it should make it possible to get correct code completion in both
COMPILE::SWF and COMPILE::JS blocks. That would be a huge help!
> On Feb 1, 2017, at 6:22 PM, Alex Harui wrote:
>
> And, FWIW, AUTO when used for -define=COMPILE::SWF,AUTO and
> -define=COMPILE::JS,AU
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FALCONJX-Combining-SW
>F-and-JS-compilers-was-Re-AW-FalconJX-FlexJS-COMPJSC-and-Build-order-tp556
>24p58914.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
.n4.nabble.com/FALCONJX-Combining-SWF-and-JS-compilers-was-Re-AW-FalconJX-FlexJS-COMPJSC-and-Build-order-tp55624p58914.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi Carlos,
In that case they belong into separate modules. Besides this being work, what
other reason would there be to keep them in the same module?
Producing two primary artifacts for one module is actually not discussable if
we want to keep Maven support working cleanly without hacks.
Chris
Hi Chris
2017-02-01 11:34 GMT+01:00 Christofer Dutz :
> Hi guys,
>
> I’d love to see basic go away. I already excluded it from the maven
> distribution to avoid problems in IntelliJ.
>
>
But, if my proposal of separating flexjs components from basic html tags
are ok, we'll end with two. Right now
Hi guys,
I’d love to see basic go away. I already excluded it from the maven
distribution to avoid problems in IntelliJ.
Didn’t see that “question 3” … what would these two swcs be? I am asking
because Maven has the concept of one primary artifact per module. We are
currently producing one mai
HI Alex,
2017-01-31 18:41 GMT+01:00 Alex Harui :
> OK, I have something working. It is in the "dual" branch I just pushed.
>
great :)
> But there is a catch: MXMLJSC requires Java 7 or greater and Flash
> Builder is packaged with Java 6. So, in order to use this capability from
> FB, you w
CONJX] Combining SWF and JS compilers (was Re: AW:
[FalconJX][FlexJS] COMPJSC and Build order)
On 1/31/17, 12:43 PM, "Christofer Dutz" wrote:
>Would it be a valid compromise to have two Cordova outputs … one that
>dumps the config.xml and one that also runs Cordova?
>I could live
On 1/31/17, 12:43 PM, "Christofer Dutz" wrote:
>Would it be a valid compromise to have two Cordova outputs … one that
>dumps the config.xml and one that also runs Cordova?
>I could live with that. Then I could continue to run Cordova in the
>packaging phase.
Is there already a config.xml being
Would it be a valid compromise to have two Cordova outputs … one that dumps the
config.xml and one that also runs Cordova?
I could live with that. Then I could continue to run Cordova in the packaging
phase.
Chris
Am 31.01.17, 21:23 schrieb "Alex Harui" :
On 1/31/17, 11:51 AM, "C
On 1/31/17, 11:51 AM, "Christofer Dutz" wrote:
>So if I understand you correctly, FlexJS would be outputting an
>“apk”-file because it invokes Cordova internally?
>
>I would vote -1 on that.
>
>The problem here is that we are tightly coupling FlexJS and Cordova. We
>then have one execution, tha
So if I understand you correctly, FlexJS would be outputting an “apk”-file
because it invokes Cordova internally?
I would vote -1 on that.
The problem here is that we are tightly coupling FlexJS and Cordova. We then
have one execution, that does generation, compilation and packaging (Maven
te
On 1/31/17, 10:16 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>I’ll have a look at the changes and eventually try to prepare the maven
>plugin for these changes.
In theory, MXMLJSC is backwards compatible. I will try to remember to
make sure of that before merging to develop.
Longer term, I lea
Hi Alex,
I’ll have a look at the changes and eventually try to prepare the maven plugin
for these changes.
Just to be on the safe side … with “cordova” you mean producing a directory
that I can pass into cordova. Not include the cordova functionality in Flex,
correct?
Chris
Am 31.01.17, 18:4
OK, I have something working. It is in the "dual" branch I just pushed.
I added a -compiler.targets option. It allows you to specify a list of
targets. I am deprecating -js-output-type. It should still work for now,
but it only specified a single output for JS compilation. With
-compiler.targ
>>>>> > NODE generates an index.js that bootstraps things for
>Node.js.
>>It is
>>>>>> > exposed through the js/bin/asnodec executable, which it
>loads
>>the
>>>>>> > frameworks/node-config
lers. Currently the supported
>compilers
>>>are limited by the JsOutputType enum. If we however used something
>like
> >>the Java service thing I used for the Flex Tool Groups, we could
>allow
>>>new experiments to start i
;>>>
>>>>On Thu, Oct 6, 2016 at 2:55 PM, Carlos Rovira
>>>> >>>> wrote:
>>>>
>>>>> I want to propose the same. I something was an experiment and is
>no
>>>>>more
>>>>> developed
ed for the Flex Tool Groups, we could allow
>>new experiments to start in dedicated Jars and we wouldn't have such a
>>mixture in case someone wants to try something out.
>>
>>
>>Chris
>>
>>________________
&
ing I used for the Flex Tool Groups, we could allow
>>new experiments to start in dedicated Jars and we wouldn't have such a
>>mixture in case someone wants to try something out.
>>
>>
>>Chris
>>
>>________________
>>Von: Alex Harui
Assuming "build package" means run the Ant or Maven build, there is no
need to copy generated-sources any more as all the js files are packed
into the SWC. Should make updating faster because there will be fewer
files to copy. But then I think you may have to shut down and restart FB
as I've seen
\nightly_07\frameworks\js\FlexJS\generated-sources/
This isn't really efficient so I'm assuming there's a better way to do it.
Can you share your build workflow, or recommend one?
Thanks.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com
Chris
>
>
>Von: Alex Harui
>Gesendet: Freitag, 7. Oktober 2016 00:25:30
>An: dev@flex.apache.org
>Betreff: Re: [FALCONJX] Combining SWF and JS compilers (was Re: AW:
>[FalconJX][FlexJS] COMPJSC and Build order)
>
>+1. Bonus points for ma
Harui
Gesendet: Freitag, 7. Oktober 2016 00:25:30
An: dev@flex.apache.org
Betreff: Re: [FALCONJX] Combining SWF and JS compilers (was Re: AW:
[FalconJX][FlexJS] COMPJSC and Build order)
+1. Bonus points for making a tag and/or branch before deleting.
-Alex
On 10/6/16, 3:02 PM, "Josh Tynja
>> >
>> > Von: Josh Tynjala
>> > Gesendet: Donnerstag, 6. Oktober 2016 17:13:49
>> > An: dev@flex.apache.org
>> > Betreff: Re: [FALCONJX] Combining SWF and JS compilers (was Re: AW:
>> > [FalconJX][Fl
to some sort of attic. What do you think?
> >
> >
> > Chris
> >
> >
> > Von: Josh Tynjala
> > Gesendet: Donnerstag, 6. Oktober 2016 17:13:49
> > An: dev@flex.apache.org
> > Betreff: Re: [FALCONJX] Combining SWF and JS
SWF and JS compilers (was Re: AW:
> [FalconJX][FlexJS] COMPJSC and Build order)
>
> JSC is meant to be purely an ActionScript to JavaScript transpiler without
> any frameworks. By default, it doesn't export an HTML file, but it will
> optionally support custom HTML templat
SWF and JS compilers (was Re: AW:
[FalconJX][FlexJS] COMPJSC and Build order)
JSC is meant to be purely an ActionScript to JavaScript transpiler without
any frameworks. By default, it doesn't export an HTML file, but it will
optionally support custom HTML templates in 0.8.0. It is exposed th
is
>> would be really helpful.
>>
>>
>> So far I see these output types:
>>
>> AMD
>> FLEXJS
>> GOOG
>> VF2JS
>> FLEXJS_DUAL
>> JSC
>> NODE
>>
>> And I guess I only used no value and FLEXJS
>>
>>
>> Chris
&
SC
> NODE
>
> And I guess I only used no value and FLEXJS
>
>
> Chris
>
>
> Von: Alex Harui
> Gesendet: Donnerstag, 6. Oktober 2016 07:45:48
> An: dev@flex.apache.org
> Betreff: [FALCONJX] Combining SWF and JS compilers (was Re: AW:
treff: [FALCONJX] Combining SWF and JS compilers (was Re: AW:
[FalconJX][FlexJS] COMPJSC and Build order)
Fred Thomas did some work in this area about a year ago. In the
flex-oem-compiler module that FB (and maybe other IDEs) use to talk to the
compiler, he added a FLEXJS_DUAL -js-output-type. Not
Fred Thomas did some work in this area about a year ago. In the
flex-oem-compiler module that FB (and maybe other IDEs) use to talk to the
compiler, he added a FLEXJS_DUAL -js-output-type. Not sure how well it
works.
Thinking about this some more we'd have to have the same configuration
options
That would be ideal!
- Josh
On Oct 1, 2016 10:47 PM, "Alex Harui" wrote:
> One more thought on this: now that COMPJSC can more or less build its own
> output instead of relying on COMPC to package its pile of .js files, it
> might be worth experimenting with combining Falcon and FalconJX so CO
One more thought on this: now that COMPJSC can more or less build its own
output instead of relying on COMPC to package its pile of .js files, it
might be worth experimenting with combining Falcon and FalconJX so COMPC
can produce a SWC or a SWC with JS files based on some configuration
parameter.
Hi Chris,
When I read this, I realized I already pushed the changes when I pushed
some other changes yesterday. If the Maven build didn't blow up, it is
probably because it is using its own compile-xx-config.xml files so is
still generating a pile of .js files and packaging them up on the SWF
COM
the stuff is in and I'll try to sort out the
Maven issues.
Chris
Von: Alex Harui
Gesendet: Donnerstag, 29. September 2016 19:59:53
An: dev@flex.apache.org
Betreff: [FalconJX][FlexJS] COMPJSC and Build order
Hi,
I'm finishing up changing the way COMP
Hi,
I'm finishing up changing the way COMPJSC works. Right now, it generates
a pile of .js files in a folder. Our build process requires that you then
run COMPC and specify the -include-files option to include that pile of
.js files into a final SWC.
This is insufficient for IDE users. If you
51 matches
Mail list logo