Mihai,
This is the projects [1] which you have to import to intellij in order to
have compilation through IDE.
automation_apps general config [2]
automation_apps dependencies [3]
You will have to add also CONFIG::minimaltests property in Compiler options.
automation_core general config [4]
autom
Ok ... so I added the "-dump-config" option to the Ant build and compared the
generated config with the one Flexmojos generated and kept on statically adding
options that were missing. In the end the configs were pretty much the same and
now I can confirm that Flexmojos successfully compiled bot
I’m going to see what compiler changes are needed for this.
-Alex
On 9/18/15, 4:56 PM, "Josh Tynjala" wrote:
>Here's the section on reserved words in the ES5.1 spec:
>
>http://www.ecma-international.org/ecma-262/5.1/#sec-7.6.1
>
>And the same section in the ES6 / ES2015 spec:
>
>http://www.ecma
OK, I think I got this working and pushed it to the JsToAs branch of
Falcon.
I’m going to take on allowing keywords to be used for function names and
some other places as I noticed it is affecting the JS to AS port as well.
-Alex
On 9/19/15, 1:57 PM, "Josh Tynjala" wrote:
>Yeah, changing Falco
OK great. Hopefully Peter will catch up on this thread and figure out
what was supposed to happen with these files.
-Alex
On 9/22/15, 10:51 AM, "Christofer Dutz" wrote:
>Well I took the opportunity to fix the two files and with these changes I
>was able to build the examples :-)
>
>Chris
>
>__
Well I took the opportunity to fix the two files and with these changes I was
able to build the examples :-)
Chris
Von: Christofer Dutz
Gesendet: Dienstag, 22. September 2015 19:30
An: dev@flex.apache.org
Betreff: AW: AW: [FLEXJS] Maven Packaging and Fle
Well regarding the ILayoutParent ... it seems to be used in the HTML project:
/flex-asjs/frameworks/projects/HTML/as/src/org/apache/flex/core/IScrollingLayoutParent.as
/flex-asjs/frameworks/projects/HTML/js/src/org/apache/flex/html/beads/ListView.js
/flex-asjs/frameworks/projects/HTML/js/src/org/ap
Hi Piotr,
no worries, I found the reason why Firefox was closing unexpectedly:
when ran from ant, the ant task tries to make sure the browser is
closed once it finishes analysing the results. So then I could just
refresh the VellumUnit page in Firefox (rather than run it from ant)
and debug without
I think a prefix is acceptable.
- Josh
On Tue, Sep 22, 2015 at 8:34 AM, Alex Harui wrote:
>
>
> On 9/22/15, 7:25 AM, "Josh Tynjala" wrote:
>
> >No, this particular option of the Closure compiler is currently
> >hard-coded.
> >
> >As for making it a compile-time option, we should keep in mind t
On 9/22/15, 8:54 AM, "Christofer Dutz" wrote:
>Ok .. so I updated everything and re-built but couldn't see anything
>improving.
>Digging a little deeper, it seems that a resource seems to have been
>renamed and officially a ILayoutParent no longer exists. Unfortunately
>the monkey-patching usi
On 9/22/15, 8:44 AM, "Christofer Dutz" wrote:
>So in general I shouldn't need to worry about that directory and all
>should be in the core.swc for example (This would have been where I would
>be expecting it to be).
Yes, everything should be in the SWCs. The default scripts that launch
mxmlc
Ok .. so I updated everything and re-built but couldn't see anything improving.
Digging a little deeper, it seems that a resource seems to have been renamed
and officially a ILayoutParent no longer exists. Unfortunately the
monkey-patching using the framework/js/FlexJS directory seems to prevent
So in general I shouldn't need to worry about that directory and all should be
in the core.swc for example (This would have been where I would be expecting it
to be).
Ok ... that makes me happy as I was preparing myself for some need to start
hacking stuff but this way hopefully I won't need to
On 9/22/15, 7:25 AM, "Josh Tynjala" wrote:
>No, this particular option of the Closure compiler is currently
>hard-coded.
>
>As for making it a compile-time option, we should keep in mind that not
>all
>emitters will necessarily use Closure compiler in the future. This may
>affect how the option
On 9/22/15, 8:19 AM, "Christofer Dutz" wrote:
>Hi,
>
>
>So I got a lot further in my efforts to adjust Flexmojos to support
>FlexJS (Even if I thought I already did).
>
>I added a new artifical artifact
>"org.apache.flex.flexjs.framework:framework:pom and zipped the xml files
>in the framework
Hi,
So I got a lot further in my efforts to adjust Flexmojos to support FlexJS
(Even if I thought I already did).
I added a new artifical artifact
"org.apache.flex.flexjs.framework:framework:pom and zipped the xml files in the
framework directory. I even added all "project/*/*-manifest.xml" f
No, this particular option of the Closure compiler is currently hard-coded.
As for making it a compile-time option, we should keep in mind that not all
emitters will necessarily use Closure compiler in the future. This may
affect how the option should be named, or how it gets parsed and validated
I realise that I'm making the assumption that my latest tlf sources
are used (which include your fix), although I'm not sure if that's
true. (I think it is, because the fatal in the bug itself seems to not
be thrown.)
On 22 September 2015 at 12:55, Mihai Chira wrote:
> I somehow managed to get tw
I somehow managed to get two test functions running correctly (for
some reason, the third one fails with a fatal - see below [1]). It
would really help if you took a look at the test (just committed) to
see if I started in the right direction. For now I'm just checking the
plain text result, not fo
Mihai,
I will try to describe it for you later today. :) It's a matter of import
some modules and dependencies, but it is a bit tricky.
We had with Harbs one session on skype and he was able to do this in Flash
Builder as I remember.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
Vi
It's not that. The whole of Firefox shuts down (without warning, as if
I had closed it), not just the plugin. Same after changing the setting
you suggested. (I have the latest version of Firefox and of the Flash
content debugger.)
Do you know how I can use the projector debugger instead?
On 22 Sep
You probably have the timeout set in Firefox and need to disable it. Check this:
https://support.mozilla.org/en-US/questions/705051
On Sep 22, 2015, at 12:44 PM, Mihai Chira wrote:
> That's great to know, Piotr. Yes, I was debugging using ant, and with
> Alex's suggestion (thanks!) I could get t
That's great to know, Piotr. Yes, I was debugging using ant, and with
Alex's suggestion (thanks!) I could get the test to run in Firefox, to
which I could connect with a remote debugging session. The problem is,
most times the browser simply shuts down in the middle of debugging,
which isn't a way
Makes sense to me. Of course I have not deep-dived into this stuff yet.
It seems to me that these levels should be a compile-time option which could be
easily changed. Is that the case now?
Harbs
On Sep 22, 2015, at 9:37 AM, Josh Tynjala wrote:
> The Closure compiler has three compilation lev
24 matches
Mail list logo
