I suspect that the if(b == true) and if(b == false) patterns aren't out of
the ordinary in real-world code. I hope the default will be to initialize
Booleans to false and that you'll need to opt into the other behavior.
- Josh
On Fri, Jun 9, 2017 at 3:38 PM, Alex Harui wrote:
> Thanks for point
I agree that this is a serious bug.
- Josh
On Jun 9, 2017 10:49 PM, wrote:
> Hi,
>
> I think we may be talking cross purposes here to be clear - IMO this is
> not an optimisation issue this it’s a serious bug.
>
> Justin
I doubt Moonshine will be able to build anything with the compiler alone.
It'll need a full FlexJS SDK, including the framework.
Also, I don't think they've merged my most recent changes that add support
for the "dual" stuff.
- Josh
On Jun 10, 2017 8:50 AM, "piotrz" wrote:
Alex,
In my system
It's worth noting that we already have a release branch, and it is named
release0.8.0. While the Maven release instructions that Chris wrote say
that you should create a release/version branch, that's for future releases
where a branch doesn't already exist.
- Josh
On Wed, Jun 14, 2017 at 6:45 AM
It looks to me like there are two things that need to be done because we
already have a release branch that wasn't created with Maven.
1) The develop branch should be updated to 0.9.0-SNAPSHOT. You've already
done this, and that seems fine.
2) Start at step 4 with our existing release0.8.0 branch
I'm not saying that we shouldn't make a Maven release. I'm saying that the
process that Chris suggested needs to be modified one time because we've
already done some of the things manually.
- Josh
On Wed, Jun 14, 2017 at 6:46 AM, piotrz wrote:
> Josh,
>
> For me that was point of that discussio
Yeah, I think we need a fix for the SVG patch issue before we can create
RC2.
- Josh
On Wed, Jun 14, 2017 at 6:55 AM, piotrz wrote:
> Ok I will change only typedefs manually without creating branch.
>
> As for the step 4 it look like I need to wait for fix for this problem in
> [Discuss] thread
As I understand it, we need the pom.xml versions to be updated to 0.8.0
before we cut the RC. That was the biggest issue. The RC can't have
0.8.0-SNAPSHOT in it.
- Josh
On Thu, Jun 15, 2017 at 3:02 AM, piotrz wrote:
> Hi,
>
> Here is my understanding what need to be done in this release.
> 1) F
You're going to want to get your signing key ready:
https://www.apache.org/dev/release-signing.html
- Josh
On Fri, Jun 16, 2017 at 11:40 AM, piotrz wrote:
> Hi Alex,
>
> I think option 3 is almost what I think we should do.
>
> - Ant - examining should be same as it was by Approval script - No
In the Feathers SDK Manager, I also had the same issue with Error #1000 on
Windows as we're having with the Flex SDK Installer. I was able to come up
with a solution for this issue.
To recap, on Windows, the Installer currently allocates more memory than is
allowed by a 32-bit process. The file si
+1 (binding)
Package https://dist.apache.org/repos/dist/dev/flex/flexjs/0.8.0/
rc2/apache-flex-flexjs-0.8.0-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.12.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licen
+1 (binding)
Package https://dist.apache.org/repos/dist/dev/flex/falcon/0.8.0/
rc2/apache-flex-falconjx-0.8.0-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.12.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
README_JX is ok: y
RELEASE_NOTES is ok: y
RELEASE_NOTES_JX is ok: y
NOTIC
our installer running an MD5 computation on these
> huge AIR SDKs? I'm wondering if that step has enough memory. If it is
> working for you then it probably does.
>
> Thanks,
> -Alex
>
> On 6/20/17, 3:13 PM, "Josh Tynjala" wrote:
>
> >In the Feathers
see a 64-bit Native Installer beta from Adobe? Maybe that
> will be released soon and we can use that to solve this problem?
>
> -Alex
>
> On 6/21/17, 8:57 AM, "Josh Tynjala" wrote:
>
> >For the Feathers SDK Manager, I ripped out the MD5 part because I didn't
&g
I'm +1 on changing to null by default on objects and strings. I know this
will improve compatibility with real world ActionScript code that expects
null. We can include these in the compiler option to default back to
undefined, for anyone that prefers that behavior.
- Josh
On Jun 23, 2017 7:45 PM
rther than that.
Harbs
> On Jun 24, 2017, at 8:04 PM, Josh Tynjala wrote:
>
> I'm +1 on changing to null by default on objects and strings. I know this
> will improve compatibility with real world ActionScript code that expects
> null. We can include these in the comp
I have yet to hear a good reason not to default to null either. Why are you
fighting this so hard? All of your arguments that I can recall seem to be
that Justin's performance claims aren't as big as he says. Is there more
that I missed? Because if it's little more than that, then, at the very
leas
I should make clear that even though I said "at the very least", which
might sounds like it's minor, I actually think this parity is more
important than any performance improvements.
- Josh
On Jun 25, 2017 9:36 AM, "Josh Tynjala" wrote:
> I have yet to hear a good r
t adding strict
equality would add 3KB to my file size. (out of 1.8 MB, but still...)
It would be an interesting exercise to see much much adding null
initialization would add to file size. I would guess that it would be
significant.
> On Jun 25, 2017, at 7:36 PM, Josh Tynjala wrote:
>
> I
I installed the npm version, and it looks good to me!
- Josh
On Tue, Jun 27, 2017 at 10:52 AM, OmPrakash Muppirala
wrote:
> FlexJS 0.8 has been published to npm.
>
> Please test using:
> npm install flexjs -g
>
> Thanks,
> Om
>
> On Tue, Jun 27, 2017 at 10:46 PM, OmPrakash Muppirala <
> bigosma
We should remove the part about MXML source maps from the announcement (too
late for the release notes, unfortunately). As I was writing a new
tutorial, I found that they fail to work in critical situations. The source
map directive references the wrong file extension (the compiler emits
.mxml.map
les)?
>
> -Alex
>
> On 6/28/17, 3:35 PM, "Josh Tynjala" wrote:
>
> >We should remove the part about MXML source maps from the announcement
> >(too
> >late for the release notes, unfortunately). As I was writing a new
> >tutorial, I found that the
a/beta, so I think is more important to point
> features than remove them due to some problems. Is a marketing thing for me
> that could not be the same after 1.0
>
> Just my 2
>
> Thanks
>
> 2017-06-29 0:43 GMT+02:00 Josh Tynjala :
>
> > Yeah, manually renaming each of the .j
The documentation for the VSCode extension explains how to launch a SWF
embedded in HTML in a specific web browser:
https://github.com/BowlerHatLLC/vscode-nextgenas/wiki/Debug-a-SWF-embedded-in-HTML-with-Visual-Studio-Code
- Josh
On Fri, Jun 30, 2017 at 5:56 AM, yishayw wrote:
> allenyyang wro
If you use the new Express components in FlexJS 0.8, binding beads should
be added automatically, so that's one place where things might not
necessarily be too different!
- Josh
On Fri, Jun 30, 2017 at 5:48 AM, Harbs wrote:
> I suggest you watch the getting started video by Yishay and the VS Co
Some folks mentioned that the compiler has gotten slower after the dual
merge. I recall that it's true even with a debug build and only a single
target. It occurred to me that this could be because the compiler writes
significantly more to the console in 0.8 than it did in previous versions.
Now, I
Yeah, I guess that's fine.
- Josh
On Fri, Jun 30, 2017 at 7:36 AM, Alex Harui
wrote:
> Waiting for Josh to decide on the MXML Source Map issue. I prefer
> positivity, so I'd suggest rewording from:
>
> - The -source-map compiler argument now also generates source maps for
> scripts in MXML fil
I can see the announcement in the official archive for users:
mail-archives.apache.org/mod_mbox/flex-users/201706.mbox/
It's possible that Nabble doesn't know how to handle a message that was
sent to multiple mailing lists simultaneously.
- Josh
On Fri, Jun 30, 2017 at 10:03 AM, piotrz wrote:
Classes with [Mixin] metadata have their static init() method called while
a Flex app is initializing. I assume that FlexJS continues to use [Mixin]
the same way.
- Josh
On Jul 4, 2017 12:36 AM, "yishayw" wrote:
> BTW, I noticed Camera is declared with a [Mixin] metatag. What is that?
>
>
>
> -
I don't remember exactly what I did, but in order to get trace() working in
Node.js, I had to figure out how to find the console object on window
versus global. I feel like I remember using typeof, but maybe it was
something else. Take a look at the implementation of Language.trace() to
see what I
f console !== "undefined")
> >>> {
> >>> theConsole = console;
> >>> }
> >>>
> >>> Did you define console in a typedef maybe?
> >>>
> >>> I’m thinking that Falcon should really allow undefined variables when
I'm trying to create a new FlexJS 0.8.0 project in IntelliJ IDEA, and I'm
getting the following output when I try to build the project:
Information:[HelloIDEA]: Starting Flex compiler:
"/Applications/IntelliJ IDEA.app/Contents/jdk/Contents/Home/jre/bin/java"
-Dapplication.home=/Users/joshtynjala/D
While full support for FlexJS in IntelliJ IDEA would be great, I think it's
critical that we fix this issue to at least get back to the baseline we had
in 0.7. A FlexJS project required a little bit of extra configuration with
0.7, but at least we could get the compiler to work inside IntellIJ.
Ma
I have also gotten this error before. I remember that I had to manually set
playerglobal.version (and maybe also playerglobal.swfversion) in my
env.properties to get the build to pass.
- Josh
On Tue, Jul 4, 2017 at 12:14 AM, yishayw wrote:
> I was having a problem building the Mobile package. I
g specified. Is there a
> way to specify compiler.targets in additional compiler options in IJ?
> There is in FB.
>
> -Alex
>
> On 7/6/17, 8:34 AM, "Josh Tynjala" wrote:
>
> >While full support for FlexJS in IntelliJ IDEA would be great, I think
> >it's
gt;
> Did the new output log of compiler options reflect that it recognized that
> option? Also, I'm not sure that -targets will work, it might have to be
> -compiler.targets
>
> HTH,
> -Alex
>
> On 7/6/17, 9:23 AM, "Josh Tynjala" wrote:
>
> >I tried sp
ted as well?
>
> > On Jul 6, 2017, at 9:06 PM, Josh Tynjala wrote:
> >
> > I don't see why -targets wouldn't work when it works elsewhere, but I
> just
> > tried -compiler.targets too, and that also failed.
> >
> > Looking at the source code for flex
0.8.0. If I understand the dual changes correctly, MXMLJSC now
automatically creates an IBackend based on the -targets value. It looks
like this code does indeed still need changes to support dual.
- Josh
On Wed, Jul 5, 2017 at 3:09 PM, Josh Tynjala wrote:
> I'm trying to create a new
since the
> switch to dual. Maybe that’s related as well?
>
> > On Jul 6, 2017, at 9:06 PM, Josh Tynjala wrote:
> >
> > I don't see why -targets wouldn't work when it works elsewhere, but I
> just
> > tried -compiler.targets too, and that also failed.
>
successfully build some projects in IntelliJ with -targets
set to JSFlex, SWF, and also JS.
- Josh
On Thu, Jul 6, 2017 at 11:21 AM, Josh Tynjala wrote:
> The problem looks to be related to this line:
>
> compiler = COMPILER.getDeclaredConstructor(IBackend.class).newInstance(
On Jul 6, 2017 1:47 PM, "Alex Harui" wrote:
> Thanks for noticing that. So does that mean a workaround for 0.8.0 is to
> define in additional compiler options:
>
> -js-output-type=FLEXJS
>
> -Alex
>
> On 7/6/17, 11:46 AM, "Josh Tynjala" wrot
> The js-output-type, library-path and external-library-path options are
probably not needed
I would get rid of -js-output-type. I assume that -targets takes
precedence, but just to be safe, you shouldn't use both. -js-output-type is
necessary for 0.7.0, but switch entirely to -targets with 0.8.0.
udes giving
you access to native browser APIs instead of Flash Player APIs. That's
going to be a really nice change, I think. Thanks for pointing out this
issue!
- Josh
On Thu, Jul 6, 2017 at 2:35 PM, Josh Tynjala wrote:
> > The js-output-type, library-path and external-library-path
ts will be merged and we'll keep the pairs of
SWCs for IDEs.
Thoughts?
-Alex
On 7/6/17, 4:12 PM, "Josh Tynjala" wrote:
>Okay, I figured out how to make VSCode switch to JS APIs instead of SWF
>APIs for completion and things. In the next version of the extension, when
>the
I wrote a simple test runner similar to FlexUnit for some of my projects.
I'm happy to donate this code to FlexJS or FlexUnit if it can help
bootstrap the testing efforts.
https://github.com/BowlerHatLLC/nextgenas-test
It supports [Test], [Before], and [After] metadata:
https://github.com/Bowler
In addition to MD5, the code the installer uses to unzip files can also
cause Error #1000.
I came up with a solution for that using PowerShell that I posted on the
mailing list:
http://mail-archives.apache.org/mod_mbox/flex-dev/201706.mbox/%3CCADZSWG4j-DwOFUbFGrJaOZsXTgU1FfwmE9fJUP5dnrgCGFkhLQ%40
I took a quick look and didn't understand how it
> reports errors that can be collected and reported. How does that work?
> Would it interface with Selenium?
>
> Thanks,
> -Alex
>
> On 7/7/17, 8:23 AM, "Josh Tynjala" wrote:
>
> >I wrote a simple t
because I was using a new API that wasn't available in the older version of
PowerShell.
- Josh
On Fri, Jul 7, 2017 at 11:08 AM, Nicholas Kwiatkowski <
nicholaskwiatkow...@gmail.com> wrote:
> I think that was the direction I was going to go. Thanks!
>
> On Fri, Jul 7, 2017 at 11
While I personally use === and !==, the vast, VAST majority of ActionScript
developers do not. I think it makes sense to turn that off for the default
profile. It's not considered best practice in the ActionScript community.
Probably because we encounter undefined significantly less than JS
develop
This behavior is because the native HTML classes aren't in a package. The
compiler treats everything that's not in a package the same as classes like
Number, Boolean, and String, which you don't need to import.
It seems potentially tricky to change this behavior, unless you have a
whitelist. You w
That sounds reasonable.
- Josh
On Mon, Jul 10, 2017 at 9:32 AM, Alex Harui
wrote:
> Well, the goal is to not have the framework code use the native Event.
> Maybe we should add a warning that we can turn on for our code but is off
> by default.
>
> -Alex
>
> On 7/10/17, 8
> I was not able to run build through VSCode: It constantly reported:
"Unknown compiler option: targets"
You probably have an old version of asconfigc installed on your system. Run
the following command to update:
npm install -g asconfigc
- Josh
On Mon, Jul 10, 2017 at 1:23 PM, piotrz wrote:
If you're having trouble with AIR, the Flash Player version installed
shouldn't matter.
Have you double checked your compiler options? You should make sure your
project isn't setting -debug=false somehow. I forgot that I had done that
once!
- Josh
On Jul 11, 2017 4:48 AM, "Fréderic Cox" wrote:
Inside the your SDK, the adl executable is used to debug AIR apps. (adl =
AIR debug launcher)
If nothing in your SDK changed, then it's probably related to compiler
arguments or something related to building the SWF.
- Josh
On Tue, Jul 11, 2017 at 8:11 AM, Fréderic Cox wrote:
> Thanks for the
That sounds like the proper way to handle this! We should be able to
reference constants in our ActionScript so that we can get compile-time
errors from typos, while the compiler makes sure that generated JavaScript
can be properly minified.
- Josh
On Tue, Jul 11, 2017 at 8:20 AM, Alex Harui
wro
You should include the dashes, and you should surround everything in
quotes. I think you put spaces between each option, but I've never used
more than one.
Here's a Closure option I've successfully used:
-js-compiler-option="--compilation_level SIMPLE_OPTIMIZATIONS"
- Josh
On Tue, Jul 11, 2017
One thing to keep in mind with stripping out trace() calls is that some
developers expect any modifications to variables that happen inside the
arguments to remain. I remember a while back someone at Adobe mentioning
that people complained when something like this was completely stripped out:
trac
Probably the same with function calls too:
trace(someFunction());
They wanted this to remain:
someFunction();
- Josh
On Wed, Jul 12, 2017 at 6:22 AM, Josh Tynjala wrote:
> One thing to keep in mind with stripping out trace() calls is that some
> developers expect any modificati
Thanks, Harbs!
This project is actually written in ActionScript and built with the Node.js
module support in FlexJS 0.8. Here's the source code on Github:
https://github.com/BowlerHatLLC/generator-flexjs
I even figured out how to make Travis CI compile with FlexJS (and Travis is
running Linux, b
>>>>>>>
> >>>>>>>>> I've noticed lots of advice on the internet to use feature
> >>>>>>>>> detection
> >>>>>>>>> instead of browser/runtime detection. Did you rule out doing
> >>&
Core?
>
> FWIW, I just tried setting targets to JSNode and global is still not
> recognized. node.swc does not seem to be used even when that’s the target.
> That does not seem right either.
>
> > On Jul 13, 2017, at 7:42 PM, Josh Tynjala wrote:
> >
> > I think the cor
t
> recognized. node.swc does not seem to be used even when that’s the target.
> That does not seem right either.
> >
> >> On Jul 13, 2017, at 7:42 PM, Josh Tynjala
> wrote:
> >>
> >> I think the correct solution is to add node.swc to the
> >> -e
With classic Flex, I believe IDEs would check if the [Inspectable] metadata
had an enumeration field and provide those values as suggestions when a
property is used in MXML.
I've been meaning to add that feature to the VSCode extension. I just added
an issue to remind myself:
https://github.com/B
I have an mm.cfg in my home directory, but it isn't empty. It contains the
following two lines, plus an empty line:
ErrorReportingEnable=1
TraceOutputFileEnable=1
- Josh
On Fri, Jul 14, 2017 at 1:17 AM, Fréderic Cox wrote:
> Hi,
>
> I have checked [1] but something does not seem right. It stat
According to the release notes for BlazeDS 4.7.3, classes must be
whitelisted in order to be deserialized by ClassDeserializationValidator.
Perhaps that is what you are encountering.
- Josh
On Jul 14, 2017 4:46 PM, "jaabax" wrote:
I am not being able to communicate with the server with the jar
If we change the behavior of id in MXML, there needs to be a way to force
the compiler to make id behave the old way. The compiler is used for more
than just compiling FlexJS. For instance, it is used in my VSCode
extension, where it provides code intelligence for MXML with the classic
Flex SDK and
The compiler needs to be modified to support the debugger statement.
Ideally, it would also force Flash to pause in the debugger.
- Josh
On Jul 16, 2017 2:07 AM, "Harbs" wrote:
I just added a debugging package to FlexJS. There are two things I don’t
know how to do:
1. The debugging functions
If it were a variable or function, it could be defined somewhere like that.
It's a statement, though, so it needs to be added to where Falcon creates
the AST from the ActionScript code. Then, it also needs to emit the
statement as JS in FalconJX. On the SWF side, it should be translated to
appropri
Additionally, the cloning results in extra objects that need to be garbage
collected, which can hurt performance and make effects/animations look bad.
Good call on avoiding it!
- Josh
On Tue, Jul 18, 2017 at 8:23 AM, Alex Harui
wrote:
> +1 to what Harbs said.
>
> Also, in FlexJS, we want very f
uctions in ABCGeneratingReducer. If I can
figure out how to generate bytecode to call enterDebugger() (or whatever
the function is called), the debugger statement will work in both SWF and
JS.
- Josh
On Sun, Jul 16, 2017 at 9:22 AM, Josh Tynjala wrote:
> If it were a variable or function, it could be defined s
; >generated JS so far.
> >
> >I'm not yet sure if I can make it work on the SWF side. I figured out
> >where
> >I can generate bytecode instructions in ABCGeneratingReducer. If I can
> >figure out how to generate bytecode to call enterDebugger() (or whatever
> >
be used as a "statement" for dependency
> management. CoreClasses.as, for example, has plenty of lines like:
>
>import org.apache.flex.core.IUIBase; IUIBase;
>
>
> HTH,
> -Alex
>
> On 7/19/17, 6:57 PM, "Josh Tynjala" wrote:
>
> >Yes,
We could consider something similar to COMPILE::JS and COMPILE::SWF where
they default to a value of auto, which the compiler knows to turn into true
or false. COMPILE::DEBUG could also default to a value of auto, and then
the compiler makes it true for a debug build and false for a release build.
confused. If you can use flash.system.System.pause() what
> custom byte code is needed?
>
> Are there other JS statements we need to support some day? Being able to
> add them to js.swc might be a better plan than having to change the
> compiler for each statement.
>
> -Alex
This type of issue used to get me all the time with the classic Flex SDK.
I'd have some subclass of Panel or something, but I'd have some kind of
selectedItem property on it that dispatched Event.CHANGE. If I had a child
that was a Slider or something, the slider's Event.CHANGE would bubble, and
I'
into develop, if there's interest.
- Josh
On Tue, Jul 18, 2017 at 5:05 PM, Josh Tynjala wrote:
> I'm working on adding support for the debugger statement to the compiler
> (FLEX-35343). I can successfully emit the debugger statement in the
> generated JS so far.
>
> I&#x
Okay, so PAYG can't have One True Definition. How you implement PAYG
depends on context.
I wonder if some kind of PAYG pattern cookbook would be helpful? I was
thinking that our situations with PAYG remind me of software design
patterns. Design patterns aren't really defined with an exact
implemen
If there are no objections in the next 24 hours, I plan to merge my
"feature/debugger-statement" branch that adds a "debugger" statement to
ActionScript similar to the one available in JS.
Use of the debugger statement is completely optional, but it's a useful way
to trigger the debugger from code
, 2017 at 5:46 PM, Alex Harui
wrote:
> I'm still trying to get the ok to use undocumented APIs without violating
> the Flash EULA which prohibits reverse-engineering. Could just make it
> JS-only for now.
>
> -Alex
>
> On 7/31/17, 3:01 PM, "Josh Tynjala" wrote:
&g
It looks like assert.as uses CONFIG::debug and CONFIG::release. Are those
defined in the compiler options for Maven?
- Josh
On Tue, Aug 1, 2017 at 12:59 AM, piotrz wrote:
> Hi Alex,
>
> I just tried and yes it's also failing for me in TLF [1]. But on Jenkins it
> look like it is failing at the
> Tree: http://git-wip-us.apache.org/repos/asf/flex-falcon/tree/c500b3fe
> > Diff: http://git-wip-us.apache.org/repos/asf/flex-falcon/diff/c500b3fe
> >
> > Branch: refs/heads/develop
> > Commit: c500b3fe52299272dbf201033723296057c79413
> > Parents: b04074b
> > Author: Josh Tynja
was simple
> enough, but I do agree with you that it’s currently broken.
>
> For now, we’re going to have to agree to disagree on initializing values.
> I’ve seen a lot of value in leaving them undefined. It makes it really
> clear while debugging whether the value has been set or not
on to that dilemma at the moment, but maybe we’ll come
> up with something...
>
> Harbs
>
> > On Aug 2, 2017, at 1:24 AM, Josh Tynjala wrote:
> >
> > Don't get me wrong. If you see value in it, then we definitely shouldn't
> > remove it as an option. Howe
on that supports
> >>the
> >> divergence from official actionscript language documentation elsewhere,
> >>and
> >> the hope that new users will read it as the authoritative source.
> >>
> >>
> >> On Wed, Aug 2, 2017 at 10:31 AM, Har
Good one! To avoid the overhead of the isNaN() function call, I frequently
rely on the fact that NaN != NaN.
- Josh
On Wed, Aug 2, 2017 at 3:32 PM, Harbs wrote:
> Thanks for the history lesson. :-)
>
> This does bring up another difference between an initialized value of NaN
> and undefined:
>
of app size. We just have to make it possible to shave off
> code to improve download size and performance if/when someone needs it.
>
> Regarding the list of nullable types, I agree there should be some
> wildcard for all instances.
>
> My 2 cents,
> -Alex
>
> On 8/2/
How does that work?
>> unknownNumOrNaN != NaN will always be true
>>
>>> On Aug 3, 2017, at 1:37 AM, Josh Tynjala wrote:
>>>
>>> Good one! To avoid the overhead of the isNaN() function call, I
>> frequently
>>> rely on the fact that NaN !=
ing cases in Flash to their JS
> >counterparts.
> >
> >BTW, I just ran into a case where booleans behave differently in JS than
> >AS where initialization would not help. I’ve started my document. I’ll
> >add this case. Once the doc starts coming together I’ll share on the
I'm guessing that you didn't update the compiler before building the SDK. I
think that fxg-base-class is a somewhat new compiler option.
- Josh
On Fri, Aug 4, 2017 at 8:42 AM, piotrz wrote:
> Hi,
>
> With Santanu we did build FlexJS SDK by Ant and tried to use this version
> to
> build simple e
I've considered the idea of extending the TypeScript compiler to understand
MXML, and elements would contain TypeScript instead of
ActionScript. Creating a new compiler for TypeScript would be a massive
effort (even considering the similarities between ActionScript and
TypeScript), so it would be
(copying from users)
PMC,
We should consider a 0.8.1 release with some of the recent bug fixes. The
IntelliJ IDEA fix [1], in particular, seems especially important,
considering this thread. Developers want to to try FlexJS in a familiar
IDE, and 0.8.0 makes that harder right now.
It's also like
d to step up
> > to be the RM and help fix the examples.
> >
> > Go for it,
> > -Alex
> >
> > On 8/8/17, 6:41 AM, "Josh Tynjala" joshtynj...@gmail.com>> wrote:
> >
> >> (copying from users)
> >>
> >> PMC,
> >>
&
I recommend including a review of basic MXML language features in the
getting started material. Things like binding, states, and even just how to
add children to containers, listen to events, and things like that. It's
good for people completely new to Flex/FlexJS, but I think it's also
important f
Browsers are definitely planning to remove all support for the Flash Player
plugin on or before 2020.
- Josh
On Aug 14, 2017 5:19 AM, "Deepak MS" wrote:
Let's say Adobe releases final version of flash player version 35 for
instance, by end of 2019, without further maintenance or development of
It's best to assume that Adobe is no longer going to provide security
updates for Flash Player in 2020. Do not fork any web browsers to try to
continue supporting Flash Player or other plugins. You will put the
security of your users at great risk. It's not worth it.
The age of browser plugins, an
Moonshine currently uses the 0.8.0 compiler for code intelligence. Nightly
builds of FlexJS specify a new fxg-base-class compiler option in
flex-config.xml, but this compiler option didn't exist in 0.8.0.
There is currently no way to force Moonshine to use the newer compiler for
code intelligence
Everything is compiled into a single "fat" JAR, so unfortunately no.
- Josh
On Wed, Aug 16, 2017 at 10:44 AM, Alex Harui
wrote:
> Bummer. There is no way to overwrite the compiler jars?
>
> -Alex
>
> On 8/16/17, 10:34 AM, "Josh Tynjala" wrote:
>
> >
Yes, if we release a new version of the compiler, then Moonshine can be
updated to use it.
Alternatively, Moonshine could be refactored to allow users to optionally
point to a different version of the compiler, similar to how the VSCode
extension provides the nextgenas.sdk.editor setting.
- Josh
I remember seeing that Alex updated to a newer version of Closure compiler
recently. I don't recall if he updated Closure library at the same time. As
I understand it, it's a good idea to keep them both in sync.
- Josh
On Aug 22, 2017 3:43 AM, "Harbs" wrote:
> I’ve been getting hundreds of warn
VSCode checks if an SDK contains two directories named "bin" and
"frameworks", and it requires either "flex-sdk-description.xml" or
"air-sdk-description.xml" in the root of the SDK.
One change that I could make is to allow "bin" to be missing if "js/bin"
exists instead.
The parts of Moonshine tha
1 - 100 of 790 matches
Mail list logo
