Re: [ApacheCon] Let's make it happen :-)

[piotrz]

Thank you Justin. I have found where to edit it. :) 



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/ApacheCon-Let-s-make-it-happen-tp58856p60362.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [ApacheCon] Let's make it happen :-)

[piotrz]

Justin,

You mean that profile when I was doing registration as a speaker? 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/ApacheCon-Let-s-make-it-happen-tp58856p60361.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Just need to vent...

[Alex Harui]

Ah crud.  Nevermind.  I didn't have remove-circulars in the failing case.

Still pondering...
-Alex

On 3/10/17, 4:17 PM, "Alex Harui"  wrote:

>For those keeping track, I think I have gathered enough evidence to
>conclude that it is a Java 6 vs 7 difference in the Hash iterators that is
>fooling the way we build the list of files for GCC.
>
>I will look into fixing that.
>
>-Alex
>
>On 3/10/17, 11:27 AM, "Alex Harui"  wrote:
>
>>
>>
>>On 3/9/17, 2:35 PM, "Harbs"  wrote:
>>
>>>It looks to me like the missing definitions are classes which are only
>>>used in static methods.
>>>
>>>Could it be that Falcon is not properly declaring dependencies in static
>>>methods?
>>
>>I think the issue is the order of files being passed to GCC.  I am
>>investigating.
>>
>>-Alex
>>
>

Re: [ApacheCon] Let's make it happen :-)

[Justin Mclean]

Hi,

> I saw that schedule was announced [1]

Yep we need to make some noise about that!

> but my photo is missed. Something was
> wrong with it in the end?

That’s a seperate system to what I’m doing I think it related to your Linux 
Foundation profile. I plan to get to the Flex JS submit site tomorrow.

Thanks,
Justin

Re: [ApacheCon] Let's make it happen :-)

[piotrz]

Hi Justin,

I saw that schedule was announced [1], but my photo is missed. Something was
wrong with it in the end?

[1]
http://events.linuxfoundation.org/events/apachecon-north-america/program/schedule

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/ApacheCon-Let-s-make-it-happen-tp58856p60358.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Nabble

[Yishay Weiss]

Everytime I start a session Nabble tells me my password is incorrect and I have 
to change it. Anyone else having that problem?

[GitHub] flex-blazeds pull request #2: Fixed bug with flushing messages to polling cl...

[peterjoel]

Github user peterjoel closed the pull request at:

https://github.com/apache/flex-blazeds/pull/2


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flex-blazeds issue #2: Fixed bug with flushing messages to polling client.

[peterjoel]

Github user peterjoel commented on the issue:

https://github.com/apache/flex-blazeds/pull/2
  
Closing this, as it was merged a long time ago in the main repository.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[4.16.0] # Apache Flex SDK 4.16.0 nightly build 255: Successful

[flex . ci . builds]

flex-sdk_release-candidate - Build #255 - Successful

Changes since last build:
No changes

For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/255/.

Re: Just need to vent...

[Alex Harui]

For those keeping track, I think I have gathered enough evidence to
conclude that it is a Java 6 vs 7 difference in the Hash iterators that is
fooling the way we build the list of files for GCC.

I will look into fixing that.

-Alex

On 3/10/17, 11:27 AM, "Alex Harui"  wrote:

>
>
>On 3/9/17, 2:35 PM, "Harbs"  wrote:
>
>>It looks to me like the missing definitions are classes which are only
>>used in static methods.
>>
>>Could it be that Falcon is not properly declaring dependencies in static
>>methods?
>
>I think the issue is the order of files being passed to GCC.  I am
>investigating.
>
>-Alex
>

Re: Flex SDK release

[Justin Mclean]

Hi,

> I've grabbed a few of these.  I'll work on them as soon as the binaries and
> source on up on the repos.

Much appreciated.

Looks like most of the mirrors will have them now [1] (towards the bottom) and 
if not by the end of the day.

Thanks,
Justin

1. https://www.apache.org/mirrors/

Re: Just need to vent...

[Alex Harui]

On 3/9/17, 2:35 PM, "Harbs"  wrote:

>It looks to me like the missing definitions are classes which are only
>used in static methods.
>
>Could it be that Falcon is not properly declaring dependencies in static
>methods?

I think the issue is the order of files being passed to GCC.  I am
investigating.

-Alex

Re: [FlexJS][FalconJX] Dual output Compilation

[PKumar]

Alex,

I downloaded the flexjs dual nightly build and it is working as expected
but one thing I want to point out here is that if I am not adding
"-compiler.target SWF" compiler option in FB 4.7 then I am getting compiler
error. If you want to check error screen shot, I can send you.

On 07-Mar-2017 7:01 AM, "Alex Harui [via Apache Flex Development]" <
ml-node+s247n60197...@n4.nabble.com> wrote:

> Hi,
>
> I think I finally have the dual branch operational enough for folks to
> poke at.  There is one issue with FB integration where it keeps starting a
> compile right after the previous compile finishes.  I'm looking into that
> today, but for now I just go to Project Properties and switch to another
> FlexJS SDK.
>
> One goal of the dual branch was to have one invocation of the compiler
> generate both SWF and JS output.  That way, if you are using an IDE like
> FlashBuilder and save your changes, the compiler will generate both SWF
> and JS and catch any differences in the underlying APIs.
>
> Another goal was to allow FlexJS classes to generate overrides of Flash
> classes but with FlexJS types.  This would give us better control over the
> APIs presented to FlexJS customers.  For example, in Flash, Sprite has a
> dispatchEvent method that takes a flash.events.Event.  We'd like to tell
> our users that UIBase has a dispatchEvent that takes an
> org.apache.flex.events.Event.  But if you write:
>
>   class UIBase extends Sprite
>   {
> override public function
> dispatchEvent(event:org.apache.flex.events.Event):Boolean
> {
> }
>   }
>
> The compiler normally returns an error since the base class has:
>
>   public function dispatchEvent(event:flash.events.Event):Boolean
>
>
> But now we can add metadata to our dispatchEvent override.
>
>   [SWFOverride(params="flash.events.Event",
> altparams="org.apache.flex.events.Event:org.apache.flex.events.MouseEvent")
>
> ]
>   override public function
> dispatchEvent(event:org.apache.flex.events.Event):Boolean
>
> And the FlexJS compiler will allow the override without an error.
> However, it will actually generate SWF code for event being a
> flash.events.Event since the runtime would otherwise throw an exception
> about illegal overrides. As long as org.apache.flex.events.Event extends
> flash.events.Event on the SWF side, then the code will operate normally in
> the player.
>
>
> The combination of these two goals make Flash Builder integration a bit
> more seamless.  Before, you would save your changes and compile a SWF,
> then go and run an Eclipse launch script that ran the cross-compiler.  And
> errors found during the cross-compile couldn't be clicked on in the
> problems pane.  But now, on each save you spend a bit more time compiling
> for both platforms, but you immediately see errors against the JS APIs and
> can examine them from the problems pane.  I found some missing APIs while
> testing this.
>
> In addition, the flex-config.xml and air-config.xml files have between
> tweaked to be JS-oriented.  IOW, the external-library-path and
> library-path in those files point to JS.swc and the FlexJS JS SWCs (like
> BasicJS.swc).  This means that code-hinting is oriented towards the JS API
> surface. That prevents a lot of Flash-only APIs from showing up in the
> code hinting.  We might want to figure out a way to hide APIs since some
> of the offerings don't have Flash support either.
>
> One cool outcome of this work is that we can now generate the JS output
> without playerglobal.swc or airglobal.swc.  I think they are needed for
> Flash Builder to think of the SDK as a Flex SDK, but if you are not using
> FB and just using Ant or Maven, it should be possible to create a release
> package for those Ant and Maven customers that have no Adobe dependencies!
>  Of course, that means that you won't get SWF output, which I think is
> still beneficial for many reasons, but if you think you don't need the SWF
> output, we could come up with a release package that is truly all ALv2
> compatible.
>
> I made changes to the Maven mojos to exercise this dual output code, but
> I'm waiting on Christofer and other maven experts to decide whether I've
> broken any Maven rules.   Maven doesn't really need these changes since
> you essentially dictate what outputs you want in the POM anyway.  The main
> benefit of dual output was for IDEs like Flash Builder.
>
> Anyway, you can try to use the Installer and install the FlexJS Dual build
> or build it from the repos.  If you use the repos, be sure to get both the
> flex-falcon and flex-asjs dual branches and build flex-falcon first.
>
> Let me know what you think.
> -Alex
>
>
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-FalconJX-Dual-
> output-Compilation-tp60197.html
> To start a new topic under Apache Flex Development, email
> ml-node+s247n1...@n4.nabble.com
> To 

Re: Flex SDK release

[Nicholas Kwiatkowski]

I've grabbed a few of these.  I'll work on them as soon as the binaries and
source on up on the repos.

-Nick

On Fri, Mar 10, 2017 at 1:38 AM, Justin Mclean 
wrote:

> Hi,
>
> Can any one help out with these activities as part of the Flex SDK release
> [1][2][3]. They are updating the installer script, update the web site and
> the AS docs.
>
> Thanks,
> Justin
>
> PS looks like JIRA may of just gone off the air so these links may not
> work.
>
> 1. https://issues.apache.org/jira/browse/FLEX-35156
> 2. https://issues.apache.org/jira/browse/FLEX-35157
> 3. https://issues.apache.org/jira/browse/FLEX-35158

Re: [4.16.0] # Apache Flex SDK 4.16.0 nightly build 254: Successful

[OmPrakash Muppirala]

Has this build been turned off, now that 4.16 is out the door?

Thanks,
Om

On Thu, Mar 9, 2017 at 4:48 PM,  wrote:

> flex-sdk_release-candidate - Build #254 - Successful
>
> Changes since last build:
> No changes
>
> For more information, check the console output at http://apacheflexbuild.
> cloudapp.net:8080/job/flex-sdk_release-candidate/254/.

Re: [FlexJS][Maven] New Upstream Dependency (was Re: git commit: [flex-asjs] [refs/heads/develop] - Added Shader files (with compiler argument)

[yishayw]

Christofer Dutz wrote
> Ok … so that’s a Flash-Only bead?

Yes, in HTML you just set the CSS and it works (not in IE and Edge however)
so no need for an HTML bead.

Thanks for taking care of it.




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Maven-New-Upstream-Dependency-was-Re-git-commit-flex-asjs-refs-heads-develop-Added-Shader-fil-tp60260p60346.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: draft announcement for 4.16.0

[Mihai Chira]

I see that we're duplicating links. Is it for some specific email readers?

Also made some small changes (in-line).

On 12 February 2017 at 00:30, Justin Mclean  wrote:
> The Apache Flex community is pleased to announce the release of Apache
> Flex SDK 4.16.0
>
> The Apache Flex SDK is a highly productive, open source application
> framework for building and maintaining expressive applications that deploy
> consistently on all major browsers, desktops and devices (including
> smartphones, tablets and tv).
>
> Apache Flex SDK 4.16.0 is an update to Apache Flex SDK 4.15.0 that
> adds support for the latest Flash Player and AIR runtimes and many bug fixes.
>
> For more details, see the release notes at:
> http://www.apache.org/dist/flex/4.16.0/RELEASE_NOTES 
> 
>
> It's recommended you install the Apache Flex SDK by using the Apache Flex
> IDE installer:
> http://flex.apache.org/installer.html 
>
> The Apache Flex SDK is available in source form from the following
> download page:
> http://flex.apache.org/download-source.html 
> 
>
> When downloading from a mirror site, please remember to verify the
> downloads using signatures or MD5 hashes.
>
> For more information on Apache Flex, visit the project home page:
> http://flex.apache.org 
>
> Thank you for using Apache Flex,
> The Apache Flex Community

Re: [FlexJS] Dual branch

[Alex Harui]

On 3/10/17, 7:17 AM, "Christofer Dutz"  wrote:

>Hi Alex,
>
>So I adjusted the native examples poms in your dual branch … now it seems
>to build successfully with maven.

Great!  Thanks.  Have you looked over the changes I made to the mojos?
I'd like to merge this branch soon.

Thanks,
-Alex

Re: [FlexJS][Maven] New Upstream Dependency (was Re: git commit: [flex-asjs] [refs/heads/develop] - Added Shader files (with compiler argument)

[Alex Harui]

Yay!  Thanks.

On 3/10/17, 1:06 AM, "Christofer Dutz"  wrote:

>Ok …
>
>So, the Maven build works again ☺
>
>I download the zip, unpack it, copy the pbj files to another directory
>and add that to the source-path.
>Had to tweak the EmbedObject code a little though. But it seems to work
>now ☺
>
>Chris
>
>
>
>Am 10.03.17, 08:52 schrieb "Christofer Dutz" :
>
>Hi Alex,
>
>So looking at the download.xml it seems the ant build downloads:
>
>http://www.apache.org/dyn/mirrors/mirrors.cgi/flex/pixelbender/1.0/binarie
>s/apache-flex-sdk-pixel-bender-1.0.0-bin.zip
>
>That should be easy to integrate … I’ll look into that.
>
>Chris
>
>Am 10.03.17, 08:44 schrieb "Alex Harui" :
>
>
>
>On 3/9/17, 11:31 PM, "Christofer Dutz"
> wrote:
>
>>Ok … so that’s a Flash-Only bead?
>
>I expect there will be a JS version, but it won't use the PBJ
>files.
>
>>If the pbj files ar “sources”, I would add them to FlexJS. If
>they have
>>to be simply read as pbj files, they belong into
>src/main/resources, If
>>something compiles them to something else, then it belongs into
>>src/main/flex …
>>But I’ll have a look at that right away.
>
>PBJ files are compiled PBK sources.  Because they are compiled
>output and
>FlexJS is an Apache release, they cannot be placed in the repo
>and release
>packages.  They have to be downloaded.  They could be generated
>by the
>build script by compiling the PBK sources, but the PBK->PBJ
>compiler is an
>Adobe tool and enough folks complained about setting it up that
>we decided
>to create a separate release for it, so the flex-sdk could use
>the PBJ
>files from the binary convenience package and not have to deal
>with the
>Adobe tool.
>
>The FlexJS Ant script has been adjusted to download the PBJ.  Now
>we need
>to find a way to adjust Maven.  I'm now guessing that we should do
>something like we did for the externs in compiler-build-tools to
>download
>and place the PBJ files.
>
>Thoughts?
>-Alex
>
>
>
>
>

Re: [FlexJS] Dual branch

[Christofer Dutz]

Hi Alex,

So I adjusted the native examples poms in your dual branch … now it seems to 
build successfully with maven.

Chris


Am 07.03.17, 17:29 schrieb "Alex Harui" :



On 3/7/17, 4:36 AM, "Christofer Dutz"  wrote:

>Hi guys and especially Alex,
>
>I would like to ask you to give a short summary at what you changed in
>the dual branch. I don’t quite know as to what I should be looking for to
>make Maven support to match.
>
>Could you please summarize what new compiler options/arguments, which
>new/changed/obsolete compilation runs and how the packaging should have
>changed?
>Right now, I still see swc and js-swc as output of the compilation. I
>would expect one single swc to come out and this to contain two
>catalog.xml … ist that correct?

The goal of dual was just to get two "stacks" of SWCs (one for SWF, one
for JS) to work in the compiler.  Merging the two swcs into one and
renaming catalog.xml and library.swf is for later.  Getting two "stacks"
to work sets the foundation for merging later by first proving that we can
in fact produce runnable SWFs and JS from separate stacks and that having
two stacks allows us to find platform dependencies in our code.

So, there are still two SWCs produced from each frameworks/projects
folder.  However, instead of calling the JS oriented one a "typedefs" SWC,
I changed it to be a "js" classifier because the JS swc is now used to
build the JS app.  Before, the JS-oriented SWC was primarily used to
generate downstream JS-oriented SWCs so the "typedefs" classifier made
more sense.

The default SWC is the same as before.  It contains a library.swf compiled
with COMPILE::SWF,true and thus the code inside is used for linking into
SWFs.  It contains the cross-complled JS output like before which was
compiled with COMPILE::JS,true.  And it contains any defaults.css like
before.

The "js" SWC is a bit different.  It contains a library.swf compiled with
COMPILE::JS,true just like before, but now it also contains the
cross-compiled JS output (with COMPILE::JS, true) and any defaults.css.
So it is more of a peer of the main SWC, it just has a different
library.swf.

In order to do this, I still use CompileASMojo to build the default SWC.
I think the main changes there are that I switched the name of
compile-as-config.xml to compile-swf-config.xml, but more importantly, I
switched the mojo to use the FlexJS version of compc because the compc
from compiler-jx now can produce both SWF and JS output (by calling the
compc from the compiler folder for SWF output).  So, CompileASMojo also
learned how to filter artifacts and sort the js ones into js slots in the
-config.xml file.

The CompileJSMojo also now uses the compc from compiler-ix and filters
artifacts a bit differently to produce the "js" swc.

Then, once the framework is built, the CompileAppMojo now only needs one
default execution since it now calls the compiler-ix version of MXMLC
(MXMLJSC) which also now knows how to build both a SWF and JS output in
one execution.  So I took the second execution that had
outputJavaScript=true out of the pom.xml.

The main new compiler option is -compiler.targets which takes a set of
strings like "SWF, "JSFlex", "JS", "JSNode".  You can set compiler.targets
to one or more of these to dictate what output you want.  Then in order to
support that, lots of existing options got platform-specific options so
there is now a js-external-library-path and swf-external-library-path as
well as the old external-library-path option.  That way you can specify
one -config.xml file for all output targets.

I have essential obsoleted the -js-output-type parameter.  Folks should
use -compiler.targets instead for building SWCs and apps. Js-output-type
is still used by ASDoc though.

I think that's about it, although I'm sure I forgot to mention something.
I won't be too surprised if I did something that isn't with the Maven
philosophy.  My main goal was to get MXMLJSC to output both SWF and JS so
it would work better with most IDEs since most IDEs only know how to
launch one compiler.  And that has nothing to do with Maven.  But once I
got that working I decided that maybe Maven would prefer to have both
outputs from one execution as well.

HTH,
-Alex


>
>Thanks in advance,
>  Chris

Re: [FlexJS][Maven] New Upstream Dependency (was Re: git commit: [flex-asjs] [refs/heads/develop] - Added Shader files (with compiler argument)

[Christofer Dutz]

Ok …

So, the Maven build works again ☺

I download the zip, unpack it, copy the pbj files to another directory and add 
that to the source-path.
Had to tweak the EmbedObject code a little though. But it seems to work now ☺

Chris



Am 10.03.17, 08:52 schrieb "Christofer Dutz" :

Hi Alex,

So looking at the download.xml it seems the ant build downloads:

http://www.apache.org/dyn/mirrors/mirrors.cgi/flex/pixelbender/1.0/binaries/apache-flex-sdk-pixel-bender-1.0.0-bin.zip

That should be easy to integrate … I’ll look into that.

Chris

Am 10.03.17, 08:44 schrieb "Alex Harui" :



On 3/9/17, 11:31 PM, "Christofer Dutz"  
wrote:

>Ok … so that’s a Flash-Only bead?

I expect there will be a JS version, but it won't use the PBJ files.

>If the pbj files ar “sources”, I would add them to FlexJS. If they have
>to be simply read as pbj files, they belong into src/main/resources, If
>something compiles them to something else, then it belongs into
>src/main/flex …
>But I’ll have a look at that right away.

PBJ files are compiled PBK sources.  Because they are compiled output 
and
FlexJS is an Apache release, they cannot be placed in the repo and 
release
packages.  They have to be downloaded.  They could be generated by the
build script by compiling the PBK sources, but the PBK->PBJ compiler is 
an
Adobe tool and enough folks complained about setting it up that we 
decided
to create a separate release for it, so the flex-sdk could use the PBJ
files from the binary convenience package and not have to deal with the
Adobe tool.

The FlexJS Ant script has been adjusted to download the PBJ.  Now we 
need
to find a way to adjust Maven.  I'm now guessing that we should do
something like we did for the externs in compiler-build-tools to 
download
and place the PBJ files.

Thoughts?
-Alex