Re: (flex-sdk) 04/05: build.properties: FP and AIR 32.0

are pointing folks towards Adobe URLs that are still valid (since many no longer work). Existing binary distributions should still work okay, and it's existing source distributions that folks might have trouble with. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Mon, Mar 4, 2024 at 1

Re: BlazeDS 4.8.0 - flex.messaging.services.xxx

that other BlazeDS features could be updated and released to fix other security vulnerabilities. However, we would be open to a community contribution that upgrades flex-messaging-proxy to use org.apache.httpcomponents.httpclient. The original source code can be found in the blazeds-4.7.3 tag

Re: BlazeDS -Jakarta Namespace Support

We have a jakartaee branch where I've started the migration from JavaEE to JakartaEE: https://github.com/apache/flex-blazeds/tree/jakartaee I still need to do further testing, but I think it's nearly ready. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Mon, Aug 21, 2023 at 2

Re: Flex BlazeDS Missing War and

e recently, and I mirrored it on my Github account, just in case anyone might want it. I included instructions for updating Tomcat and BlazeDS in the bundle. https://github.com/joshtynjala/blazeds-turnkey-archive https://github.com/joshtynjala/blazeds-turnkey-archive/releases/tag/v4.0.0.14931 -- Jo

Re: Flex BlazeDS Missing War and

it in the repository history recently, and I've been working on adding new Royale frontends to replace the original Flex/Flash frontends, and making sure everything can be built with Maven. This samples project will show how to build a .war file that you can deploy to Tomcat. -- Josh Tynjala Bowler Hat

[ANNOUNCE] Apache Flex BlazeDS 4.8.0 Released!

The Apache Flex community is pleased to announce the release of Apache Flex Blaze DS 4.8.0 Apache Flex BlazeDS is the server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Apache Flex, Apache

[RESULT] [VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

Vote passes with 3 binding +1 votes. Thank you, Josh On Wed, Mar 8, 2023 at 3:05 PM Josh Tynjala wrote: > Hi, > > This is the vote for the 4.8.0 release of Apache Flex BlazeDS. > > This release disables or removes certain modules that required third-party > dependencies

Re: [DISCUSS] Release Apache Flex BlazeDS 4.8.0 RC1

At least one more binding +1 vote needed, folks! -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Wed, Mar 8, 2023 at 3:01 PM Josh Tynjala wrote: > Hi, > > Please discuss the BlazeDS 4.8.0 release candidate here and not in the > vote thread. > > Thanks, > Josh >

Re: [VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

and Haxe, but they still use AIR's native AMF implementation, so they're testing what needs to be tested). For completeness, I also ensured that they work when built for JS and served from Tomcat. https://github.com/feathersui/feathersui-blazeds-turnkey-samples -- Josh Tynjala Bowler Hat LLC

Re: [DISCUSS] Release Apache Flex BlazeDS 4.8.0 RC1

Thanks for taking a look, Greg! -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Tue, Mar 14, 2023 at 12:09 PM Greg Dove wrote: > Hi Josh, > > Just a quick note to say that I will test and review the build this coming > weekend. Sorry I can't get there sooner. >

[VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

Hi, This is the vote for the 4.8.0 release of Apache Flex BlazeDS. This release disables or removes certain modules that required third-party dependencies that are no longer maintained, and it updates a number of other dependencies. The release candidate can be found here:

[DISCUSS] Release Apache Flex BlazeDS 4.8.0 RC1

Hi, Please discuss the BlazeDS 4.8.0 release candidate here and not in the vote thread. Thanks, Josh

[VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

Hi, This is the vote for the 4.8.0 release of Apache Flex BlazeDS. This release disables or removes certain modules that required third-party dependencies that are no longer maintained, and it updates a number of other dependencies. The release candidate can be found here:

[RESULT] [VOTE] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

Vote passes with 3 binding and 1 non-binding +1 votes. Thank you, Josh On Thu, Feb 2, 2023 at 3:15 PM Josh Tynjala wrote: > Hi, > > This is the vote for the 1.1.0 release of Apache > flex-sdk-converter-maven-extension. > > This release fixes an HTTP to HTTPS redirect

Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

Thanks for voting, folks. I'm on vacation this week without my computer, so I'll call the result and make the release officially when I get back next week. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Thu, Feb 2, 2023 at 1:15 PM Josh Tynjala wrote: > Hi, > >

Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

Thanks for pointing out the requirements in the README. I'll be sure to update that for the tests fix. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Mon, Feb 13, 2023 at 3:20 AM Yishay Weiss wrote: > This is actually stated in the README, sorry for missing that. If you do

Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

11 so that we don't need to do a new RC? If you're going to try it with royale-compiler, you can switch back to JDK 17 for that. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Wed, Feb 8, 2023 at 11:10 PM Yishay Weiss wrote: > I’m getting this: > > C:\dev\apache-fle

Re: [VOTE] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

+1 On Thu, Feb 2, 2023 at 3:15 PM Josh Tynjala wrote: > Hi, > > This is the vote for the 1.1.0 release of Apache > flex-sdk-converter-maven-extension. > > This release fixes an HTTP to HTTPS redirect issue that causes Mavenized > downloads to fail. > > The release

Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

Thanks, Greg! -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Mon, Feb 6, 2023 at 7:16 PM Greg Dove wrote: > Thanks for your work on this, Josh. I followed your guide in here, and > think I covered all the required testing, and added my vote in the vote > thread >

Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

-swf build passes, then the extension successfully installed playerglobal 32.0. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Thu, Feb 2, 2023 at 11:28 PM Harbs wrote: > What do I need to do to test this? > > > On Feb 3, 2023, at 1:15 AM, Josh Tynjala > wr

[DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

Hi, Please discuss the flex-sdk-converter-maven-extension 1.1.0 release candidate here and not in the vote thread. Thanks, Josh

[VOTE] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

Hi, This is the vote for the 1.1.0 release of Apache flex-sdk-converter-maven-extension. This release fixes an HTTP to HTTPS redirect issue that causes Mavenized downloads to fail. The release candidate can be found here:

RE: BlazeDS release

erform > > And the plc4x documentation describes what has to be done in the nexus repo > for staging and releasing the maven artifacts. > > From: Josh Tynjala<mailto:joshtynj...@apache.org> > Sent: Tuesday, January 10, 2023 2:03 AM > To: dev@flex.apache.org<mailto:dev@

Re: BlazeDS release

thrown when services-config.xml references HTTPProxyService. 3) Instructions on how to disable HTTPProxyService in services-config.xml. - Josh On 2023/01/10 00:03:04 Josh Tynjala wrote: > Okay, some updates on my progress with BlazeDS. > > - I made the necessary changes to remove the v

RE: BlazeDS release

ase should be: > > > > mvn release:prepare > > > > mvn elease:perform > > And the plc4x documentation describes what has to be done in the nexus repo > for staging and releasing the maven artifacts. > > From: Josh Tynjala<mailto:joshtynj...@apa

Re: Change default branch on Github to develop?

Just following up. The default branch has been now changed to develop on several Flex repos. - Josh On 2023/01/09 17:56:54 Josh Tynjala wrote: > I ended up creating an Infra ticket for this: > > https://issues.apache.org/jira/browse/INFRA-24073 > > - Josh > > On 202

Re: BlazeDS release

need help with one thing: Do we have release manager instructions/checklist for BlazeDS? Thanks! - Josh On 2023/01/04 20:59:29 Josh Tynjala wrote: > I'd like to spend some time this month finishing up the recent BlazeDS > stuff so that we can get it released. > > Can som

Re: Change default branch on Github to develop?

I ended up creating an Infra ticket for this: https://issues.apache.org/jira/browse/INFRA-24073 - Josh On 2023/01/06 20:09:15 Josh Tynjala wrote: > I see that Royale's repos are defaulting to the develop on Github, but > Flex's repos are defaulting to master. I'd like to change Flex's

Change default branch on Github to develop?

it from master to develop for me? Or do we need to send a request to Infra to have them do it? Thanks, -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev>

Re: BlazeDS release

On 2023/01/04 20:59:29 Josh Tynjala wrote: > I'd like to spend some time this month finishing up the recent BlazeDS > stuff so that we can get it released. > > Can someone confirm that the changes listed here are still what should be > done? It looks straightforward eno

BlazeDS release

And which branch should I commit to? security-updates? develop? master? Something else? Thanks, -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev>

Running Adobe Flex 2 on OpenFL and JS

enfl-flex3/ Github repo: https://github.com/joshtynjala/openfl-adobe-flex-poc More details on my blog: https://joshblog.net/2021/adobe-flex-2-running-on-openfl-in-javascript-instead-of-swf/ Happy Friday! -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev>

Re: [VOTE] Fork FlexJS from Apache Flex

ed Resources > > Mailing Lists > > -private@ > -dev@ > -commits@ > -users@ > -issues@ > > Version Control > > We would like to use GitBox if it is practical to convert the current git > repos listed above. We want to explore using GitHub's wiki and > documentat

Re: [Flex JS] Flex SDK Installer always get stuck at "Finish uncompressing"

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

Re: FlexJS Closure warnings

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

Re: [FlexJS] Failing build for simple example

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

Re: [FlexJS] Failing build for simple example

Everything is compiled into a single "fat" JAR, so unfortunately no. - Josh On Wed, Aug 16, 2017 at 10:44 AM, Alex Harui <aha...@adobe.com.invalid> wrote: > Bummer. There is no way to overwrite the compiler jars? > > -Alex > > On 8/16/17, 10:34 AM, "Josh Ty

Re: [FlexJS] Failing build for simple example

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

Re: Adobe has announced the end-of-life of the Flash Player

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,

Re: Adobe has announced the end-of-life of the Flash Player

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

Re: [FlexJS][Docs] Started with some docs using a github repo

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

Re: Flex 0.8.1 release?

acation. Other folks will need 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 joshtynj...@gmail.com>> wrote: > > > >> (copy

Flex 0.8.1 release?

(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

Re: FlexJS Random crazy thought

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

Re: [FlexJS] Failing build for simple example

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

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

g > >project to compare badly performing 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

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

7 at 6:20 PM, Harbs <harbs.li...@gmail.com> wrote: > >> I’m curious. How does that work? >> unknownNumOrNaN != NaN will always be true >> >>> On Aug 3, 2017, at 1:37 AM, Josh Tynjala <joshtynj...@gmail.com> wrote: >>> >>> Good one! To avoid th

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

ve first > impression 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, > -A

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

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

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

case then we need to have documentation that supports > >>the > >> divergence from official actionscript language documentation elsewhere, > >>and > >> the hope that new users will read it as the authoritative source. > >> > >> > >> O

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

ment, but maybe we’ll come > up with something... > > Harbs > > > On Aug 2, 2017, at 1:24 AM, Josh Tynjala <joshtynj...@gmail.com> wrote: > > > > Don't get me wrong. If you see value in it, then we definitely shouldn't > > remove it as an option. However, for

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

been set or not. > > Harbs > > > On Aug 2, 2017, at 12:54 AM, Josh Tynjala <joshtynj...@gmail.com> wrote: > > > > Maybe I'll convince others eventually. > >

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

it-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 > > Par

Re: [MAVEN-BUILD] FlexJS Framework (maven) - Build # 1129 - Still Failing

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 >

Re: Debugger statement

, 2017 at 5:46 PM, Alex Harui <aha...@adobe.com.invalid> 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 P

Debugger statement

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

Re: PAYG

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

Re: [FlexJS] Debugging package

if there's interest. - Josh On Tue, Jul 18, 2017 at 5:05 PM, Josh Tynjala <joshtynj...@gmail.com> 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. > >

Re: [FlexJS] findPopupHost issue

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

Re: [FlexJS] Debugging package

wrote: > I'm still 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. > >

Re: [FlexJS] Debugging package

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.

Re: [FlexJS] Debugging package

: > I think we allow classes to 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&quo

Re: [FlexJS] Debugging package

f that Adobe > documented it at one point in time? > > HTH, > -Alex > > On 7/18/17, 5:05 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: > > >I'm working on adding support for the debugger statement to the compiler > >(FLEX-35343). I can successfully emit

Re: [FlexJS] Debugging package

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 <joshtynj...@gmail.com> wrote: > If it were a variable or function,

Re: [FlexJS] technical debt

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. > >

Re: [FlexJS] Debugging package

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

Re: [FlexJS] Debugging package

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.

Re: FlexJS MXML ids and classNames - FLEX-35310

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

Re: BlazeDS 4.7.3 ISSUE: SerializationException: Creation validation for class "" failed.

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

Re: Flash Builder desktop debugging issue

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

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

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:

Re: [FlexJS] Use of typeof

etting 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 <joshtynj...@gmail.com> > wrote: > >> > >

Re: [FlexJS] Use of typeof

c to 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 <joshtynj...@gmail.com> wrote:

Re: [FlexJS] Use of typeof

t;>>> > >>>>>>>>> I've noticed lots of advice on the internet to use feature > >>>>>>>>> detection > >>>>>>>>> instead of browser/runtime detection. Did you rule out doing > >>>>

Re: FlexJS Yeoman generator

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,

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

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 <joshtynj...@gmail.com> wrote: > One thing to keep in mind with stripping out trace() calls is that some > developer

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

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:

Re: [FalconJX] Debugging minified code

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

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

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

Re: Flash Builder desktop debugging issue

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

Re: Flash Builder desktop debugging issue

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"

Re: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS

> 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

Re: [FlexJS] Question about Events/possible bugs

gt; -Alex > > On 7/10/17, 8:52 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: > > >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

Re: [FlexJS] Question about Events/possible bugs

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

Re: [FlexJS] technical debt

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

Re: 4.16.0 Install issues

it 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:30 A

Re: FlexJS Tests (was Re: [FlexJS] technical debt)

; Hi Josh, > > That could be good. 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" <joshtynj...@gm

Re: 4.16.0 Install issues

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:

Re: FlexJS Tests (was Re: [FlexJS] technical debt)

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:

Re: [FlexJS][VS Code] dual issues

t the Maven artifacts will be merged and we'll keep the pairs of SWCs for IDEs. Thoughts? -Alex On 7/6/17, 4:12 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >Okay, I figured out how to make VSCode switch to JS APIs instead of SWF >APIs for completion and things. In the

Re: [FlexJS][VS Code] dual issues

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 <joshtynj...@gmail.com> wrote: > > The js-output-type, library-path and

Re: [FlexJS][VS Code] dual issues

> 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

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

, 2017 1:47 PM, "Alex Harui" <aha...@adobe.com.invalid> 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, &quo

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

to 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 <joshtynj...@gmail.com> wrote: > The problem looks to be related to this line: > > compiler = COMPILER.getDeclaredConstructor

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

of issues that are not problems since the > switch to dual. Maybe that’s related as well? > > > On Jul 6, 2017, at 9:06 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: > > > > I don't see why -targets wouldn't work when it works elsewhere, but I > just > > tried -compiler.ta

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

. 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 <joshtynj...@gmail.com> wrote: > I'm trying

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

Maybe that’s related as well? > > > On Jul 6, 2017, at 9:06 PM, Josh Tynjala <joshtynj...@gmail.com> 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. > > > &g

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

fig.xml > > > 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" <joshtynj...@gmail

Re: [FlexJS] 0.8.0 not working in IntelliJ IDEA

ml, and thus no targets are being 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" <joshtynj...@gmail.com> wrote: > > >While full support for

Re: [FlexJS] Mobile Depends on Flash 11.4?

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

  1   2   3   4   5   6   7   8   >