date:20170905

[FlexJS, AMF] Steps to make FlexJS / Java - RemoteObject / AMF sample work

2017-09-05 Thread Carlos Rovira

Hi,

to people interested in make AMF sample work here is what I did:

1.- Use the following branches:

   flex-falcon:develop
   flex-type-defs:feature/amf
   flex-asjs:feature/amf

build each one in that order with "mvn clean install" (you can add
-DskipTests to avoid run tests)

2.- Go to examples/flexjs/RemoteObjectAmfTest and build it with "mvn clean
install"
3.- Go to examples/ and build it with "mvn clean install"
4.- Go to examples/amf/SampleAmfWebApp and build it with "mvn clean install"
5.- In SampleAmfWebApp run "mvn spring-boot:run", this creates a jetty
instance in port 8080 and deploy "SampleAmfWwebApp"
6.- Go to "RemoteObjectAmfTest " and to "target/javascript/bin/js-debug/" Run
in a browser "index.html"

Now you can play with the interface and get a string or and Array of
objects.

Hope that helps, please try and report if you find some problem or
something that not works.

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [FlexJS] Re: Remote object for Flex JS

2017-09-05 Thread Carlos Rovira

That was the problem I have the test working! :)[image: Imágenes integradas
2]

2017-09-05 20:18 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> Try switching flex-falcon to the develop branch.  I think the RemoteClass
> handling is in the develop branch and not feature/amf.
>
> -Alex
>
> On 9/5/17, 10:56 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Alex,
> >
> >thanks, I know start to remember. That two scaffold projects was created
> >by
> >me in February and I left it incomplete and created based on PKumar and
> >Chris Dutz help. Is great that you get it to work! :)
> >
> >Know I'm trying to build with maven, so I put all 3 repos in brach
> >"feature/amf", update to latest commit and build the 3 repos with "maven
> >clean install". Then build "RemoteObjectAmfTest" and the java one
> >"SampleAmfWebApp".
> >
> >I then run "man spring-boot:run" on SampleAmfWebApp and that creates a
> >Jetty instance with that app deployed.
> >Then run RemoteObjectAmfTest and write something in first text input and
> >hit Button "send name to AMF"
> >
> >In my mac terminal console I get:
> >
> >2017-09-05 19:23:33.521  INFO 38753 --- [qtp651097767-13]
> >o.s.f.s.MessageBrokerHandlerAdapter
> >: Channel endpoint websocketAmf received request.
> >
> >But nothing on the browser. The same happened if I hit "Get Array OF Value
> >Objects"
> >
> >I think I didn't reach to get that console input when I left this test in
> >February, But did you get some result back to the browser? I understand by
> >you other emails that you get the String and the Array of VOs back to the
> >browser
> >
> >Thanks!
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira=02%7C01%7C%7C4d91abc1c98f408cf18f08d4f487
> 9012%7Cfa7b1b5
> >a7b34438794aed2c178decee1%7C0%7C0%7C636402310449668789&
> sdata=WZEVMHFKNQhgC
> >MK%2FoVvKgo9c5rQ2hJ59Tx5cj8RRvKU%3D=0
>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: FlexJS installation - Installer vs. npm

2017-09-05 Thread Alex Harui

Om,

That error implies that js.swc or playerglobal.swc/airglobal.swc isn't
being found.  See if NPM install is putting them in the right place.

Then, those SWCs have to be referenced by whatever -config.xml file in
being used, and there are sensitivities in 0.8.0 with dual mode about
whether you specify SWCs on library-path, js-library-path or
swf-library-path.  Same for external-library-path.  So the answer may be
more in the -config.xml files rather than which files if js/libs does in
fact hold the typedefs SWCs.

HTH,
-Alex

On 9/5/17, 11:22 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>I am trying to debug a problem with Visual Studio Code integration.  The
>FlexJS 0.8.0 SDK that I installed with `npm install flexjs -g` does not
>work with VSCode.  It fails with this error:
>Error: Missing builtin type Object (1,1)
>
>More details here:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2FBowlerHatLLC%2Fvscode-nextgenas%2Fissues%2F122=02%7C01%7C%7Cb320b
>ed7ea2d4c6cac7408d4f48b1ae3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>36402325663950518=uA6c%2BKgpD8QPp3OB1okhwi%2BaprFJfZPkALgsX9gunx0%3D
>=0
>
>Then I tried the same with the Installer installed version of FlexJS 0.8.0
>and it seems to work fine.
>
>Here is a folder diff of the two installations:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fibb.co%2F
>j2berv=02%7C01%7C%7Cb320bed7ea2d4c6cac7408d4f48b1ae3%7Cfa7b1b5a7b3443
>8794aed2c178decee1%7C0%7C0%7C636402325663950518=BjN9%2BmOgqjFtb2I4YE
>ZZURO9XESAYbXVIBXYCkgEoPY%3D=0
>
>Off the bat, I see that the Installer version has a flex-typedefs folder
>which is missing in the npm version.  Any idea when that was added?  It
>can't possibly be in the released artifact because they both seem to be
>getting it from the same binary package.
>
>Also, can anyone see anything obvious that could be causing this error?
>
>Thanks,
>Om

FlexJS installation - Installer vs. npm

2017-09-05 Thread OmPrakash Muppirala

I am trying to debug a problem with Visual Studio Code integration.  The
FlexJS 0.8.0 SDK that I installed with `npm install flexjs -g` does not
work with VSCode.  It fails with this error:
Error: Missing builtin type Object (1,1)

More details here:
https://github.com/BowlerHatLLC/vscode-nextgenas/issues/122

Then I tried the same with the Installer installed version of FlexJS 0.8.0
and it seems to work fine.

Here is a folder diff of the two installations:
https://ibb.co/j2berv

Off the bat, I see that the Installer version has a flex-typedefs folder
which is missing in the npm version.  Any idea when that was added?  It
can't possibly be in the released artifact because they both seem to be
getting it from the same binary package.

Also, can anyone see anything obvious that could be causing this error?

Thanks,
Om

Re: [FlexJS] Re: Remote object for Flex JS

2017-09-05 Thread Alex Harui

Hi Carlos,

Try switching flex-falcon to the develop branch.  I think the RemoteClass
handling is in the develop branch and not feature/amf.

-Alex

On 9/5/17, 10:56 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>thanks, I know start to remember. That two scaffold projects was created
>by
>me in February and I left it incomplete and created based on PKumar and
>Chris Dutz help. Is great that you get it to work! :)
>
>Know I'm trying to build with maven, so I put all 3 repos in brach
>"feature/amf", update to latest commit and build the 3 repos with "maven
>clean install". Then build "RemoteObjectAmfTest" and the java one
>"SampleAmfWebApp".
>
>I then run "man spring-boot:run" on SampleAmfWebApp and that creates a
>Jetty instance with that app deployed.
>Then run RemoteObjectAmfTest and write something in first text input and
>hit Button "send name to AMF"
>
>In my mac terminal console I get:
>
>2017-09-05 19:23:33.521  INFO 38753 --- [qtp651097767-13]
>o.s.f.s.MessageBrokerHandlerAdapter
>: Channel endpoint websocketAmf received request.
>
>But nothing on the browser. The same happened if I hit "Get Array OF Value
>Objects"
>
>I think I didn't reach to get that console input when I left this test in
>February, But did you get some result back to the browser? I understand by
>you other emails that you get the String and the Array of VOs back to the
>browser
>
>Thanks!
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira=02%7C01%7C%7C4d91abc1c98f408cf18f08d4f4879012%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636402310449668789=WZEVMHFKNQhgC
>MK%2FoVvKgo9c5rQ2hJ59Tx5cj8RRvKU%3D=0

Re: [FlexJS] Re: Remote object for Flex JS

2017-09-05 Thread Carlos Rovira

Hi Alex,

thanks, I know start to remember. That two scaffold projects was created by
me in February and I left it incomplete and created based on PKumar and
Chris Dutz help. Is great that you get it to work! :)

Know I'm trying to build with maven, so I put all 3 repos in brach
"feature/amf", update to latest commit and build the 3 repos with "maven
clean install". Then build "RemoteObjectAmfTest" and the java one
"SampleAmfWebApp".

I then run "man spring-boot:run" on SampleAmfWebApp and that creates a
Jetty instance with that app deployed.
Then run RemoteObjectAmfTest and write something in first text input and
hit Button "send name to AMF"

In my mac terminal console I get:

2017-09-05 19:23:33.521  INFO 38753 --- [qtp651097767-13]
o.s.f.s.MessageBrokerHandlerAdapter
: Channel endpoint websocketAmf received request.

But nothing on the browser. The same happened if I hit "Get Array OF Value
Objects"

I think I didn't reach to get that console input when I left this test in
February, But did you get some result back to the browser? I understand by
you other emails that you get the String and the Array of VOs back to the
browser

Thanks!

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

2017-09-05 Thread Harbs

Changing this made MouseTest run:

-   public static var renderer:IRenderer = new BaseRenderer;
+   private static var _renderer:IRenderer;
+   public static function get renderer():IRenderer
+   {
+   if(!_renderer)
+   _renderer = new BaseRenderer;
+   return _renderer;
+   }
+   public static function set renderer(value:IRenderer):void{
+   _renderer = value;
+   }

I don’t know well enough to know whether getters and setters are necessary. If 
leaving the var uninitialized and requiring it to be set by the client might be 
a more efficient solution.

> On Sep 5, 2017, at 8:27 PM, Harbs  wrote:
> 
> 0.8 was more capable of using constants of non-native types, but it had much 
> more difficulty with resolving circulars.
> 
> Static constants and non-lazy static vars should be used with only native 
> types. For non-native types you should use lazy initialization.
> 
> It’s a trade-off that I’ve found is very work-able.
> 
>> On Sep 5, 2017, at 1:03 PM, lizhi  wrote:
>> 
>> Thank you very much!
>> Well, I also know there's a setTimeout, but this setTimeout is only JS
>> built, so I don't care.
>> However, it seems that the new version of the flexjs compiler has problems
>> dealing with static classes. And flexjs0.8 doesn't have that problem.
>> 
>> 
>> 
>> -
>> spriteflexjs.com 
>> --
>> Sent from: http://apache-flex-development.247.n4.nabble.com/
>

[RESULT][VOTE] Fork FlexJS from Apache Flex

2017-09-05 Thread Alex Harui

Results are:

+1 - 16
+0 - 1
-1 - 2

I will post our proposal on board@ for their feedback and possible
inclusion on the September board meeting agenda.

Thanks,
-Alex

On 8/31/17, 11:28 PM, "Alex Harui"  wrote:

>Hi folks,
>
>Here is the vote thread.  Please vote on whether to submit the proposal
>below to the board.  Please use +1 for yes, -1 for no, and if you want,
>any number in-between per [1].  Only PMC member votes will be used to
>determine the results, but we are more than happy to hear from non-PMC
>members as well.
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apach
>e.org%2Ffoundation%2Fvoting.html%23expressing-votes-1-0-1-and-fr=02%7
>C01%7C%7C5a9a9e3e6a99464b30ab08d4f102a66a%7Cfa7b1b5a7b34438794aed2c178dece
>e1%7C0%7C0%7C636398441064819782=NIXiUWgnEkLRP%2BQSbG1dLC1YjEvRKOGxdE
>er%2BSE1QPA%3D=0
>actions
>
>Thanks,
>-Alex
>
> Proposal ---
>
>Apache FlexJS for Apache Top-Level Project
>
>Abstract
>
>Apache FlexJS is a new implementation of the principles of Apache Flex but
>designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
>Apache FlexJS was created and released as part of the Apache Flex project
>and the UI framework is a full rewrite and does not leverage the code
>bases donated by Adobe.  Only the FlexJS compiler source was donated by
>Adobe.
>
>Over time, the set of Apache Flex committers who are working on Apache
>Flex releases have become distinct from those working on FlexJS.  Add to
>that the Adobe announcement of the end-of-life for Flash in the browser,
>it makes sense to separate FlexJS from Flex so that followers of one side
>or the other don't have to filter out emails, bugs, web pages, etc, that
>they don't need.
>
>The proposal is to form an Apache FlexJS top-level project instead of
>creating a new Incubator Podling.   That is because all but one of the
>folks being proposed to the new Apache FlexJS PMC below have been on the
>Apache Flex PMC for months, if not years, and understand how to
>participate productively in an Apache project.  Plus, Apache FlexJS has
>already been released by the top-level Apache Flex project.
>
>Overview of FlexJS
>
>Apache FlexJS is designed to improve developer productivity in creating
>applications for wherever Javascript runs, including browsers as well as
>Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
>of folks creating IDEs for FlexJS, and some folks are at various points in
>the process of migrating existing Flex applications to FlexJS.
>
>Current Status
>
>Meritocracy
>
>Within Apache Flex, the FlexJS development has been conducted as a
>meritocracy.  No existing FlexJS developers came with the compiler code
>base donated by Adobe nor were they on the initial committers list for
>Apache Flex other than Alex Harui.  Everyone else has earned their way in
>by contributing and earning merit.
>
>Community
>
>Many FlexJS users are trying to migrate an existing Apache Flex app off of
>Adobe Flash.  As their migration progresses they will become less and less
>interested in Apache Flex releases and activity.  However, the Apache Flex
>JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
>base, and the team page for Flex makes it hard to determine which
>committers are active on FlexJS, and it is frequently hard to determine if
>a user's question is about regular Flex or FlexJS.   We are seeing an
>increase in user interest with the Flash end-of-life announcement and
>having separate mailing lists, web pages, and JIRA projects will help save
>everyone time and energy.
>
>Alignment
>
>Apache FlexJS is already being released by Apache.
>
>Known Risks
>
>Code Extraction
>
>The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
>be migrated to GitBox.  Other Apache Flex repos would be treated as
>external dependencies.  This includes flex-utilities and the Apache Flex
>Installer.
>
>Orphaned Projects
>
>Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
>help out just-in-case, but are already mostly inactive on the Flex code
>bases. However, there are at least 3 Apache Flex PMC members who have not
>contributed at all to FlexJS and participate in regular Flex releases, so
>the expectation is that Apache Flex will remain a viable project for some
>time to come.
>
>Inexperience with Open Source
>
>All of the initial team has been contributing to Apache Flex for months if
>not years.
>
>Homogenous Developers
>
>No company employs more than two of the members of the initial team.
>
>Reliance on Salaried Developers
>
>Until about a year ago, only 2 of the proposed PMC members were paid to
>work on FlexJS.  The rest contributed in their spare time.  Two more are
>now paid to migrate an existing application and thus contribute to add
>missing features and fix bugs.  By creating a separate project, we hope to
>attract more folks who may not want to be involved with the legacy Apache

Re: [VOTE] Fork FlexJS from Apache Flex

2017-09-05 Thread Alex Harui

+1 from me.

On 8/31/17, 11:28 PM, "Alex Harui"  wrote:

>Hi folks,
>
>Here is the vote thread.  Please vote on whether to submit the proposal
>below to the board.  Please use +1 for yes, -1 for no, and if you want,
>any number in-between per [1].  Only PMC member votes will be used to
>determine the results, but we are more than happy to hear from non-PMC
>members as well.
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apach
>e.org%2Ffoundation%2Fvoting.html%23expressing-votes-1-0-1-and-fr=02%7
>C01%7C%7C5a9a9e3e6a99464b30ab08d4f102a66a%7Cfa7b1b5a7b34438794aed2c178dece
>e1%7C0%7C0%7C636398441064819782=NIXiUWgnEkLRP%2BQSbG1dLC1YjEvRKOGxdE
>er%2BSE1QPA%3D=0
>actions
>
>Thanks,
>-Alex
>
> Proposal ---
>
>Apache FlexJS for Apache Top-Level Project
>
>Abstract
>
>Apache FlexJS is a new implementation of the principles of Apache Flex but
>designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
>Apache FlexJS was created and released as part of the Apache Flex project
>and the UI framework is a full rewrite and does not leverage the code
>bases donated by Adobe.  Only the FlexJS compiler source was donated by
>Adobe.
>
>Over time, the set of Apache Flex committers who are working on Apache
>Flex releases have become distinct from those working on FlexJS.  Add to
>that the Adobe announcement of the end-of-life for Flash in the browser,
>it makes sense to separate FlexJS from Flex so that followers of one side
>or the other don't have to filter out emails, bugs, web pages, etc, that
>they don't need.
>
>The proposal is to form an Apache FlexJS top-level project instead of
>creating a new Incubator Podling.   That is because all but one of the
>folks being proposed to the new Apache FlexJS PMC below have been on the
>Apache Flex PMC for months, if not years, and understand how to
>participate productively in an Apache project.  Plus, Apache FlexJS has
>already been released by the top-level Apache Flex project.
>
>Overview of FlexJS
>
>Apache FlexJS is designed to improve developer productivity in creating
>applications for wherever Javascript runs, including browsers as well as
>Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
>of folks creating IDEs for FlexJS, and some folks are at various points in
>the process of migrating existing Flex applications to FlexJS.
>
>Current Status
>
>Meritocracy
>
>Within Apache Flex, the FlexJS development has been conducted as a
>meritocracy.  No existing FlexJS developers came with the compiler code
>base donated by Adobe nor were they on the initial committers list for
>Apache Flex other than Alex Harui.  Everyone else has earned their way in
>by contributing and earning merit.
>
>Community
>
>Many FlexJS users are trying to migrate an existing Apache Flex app off of
>Adobe Flash.  As their migration progresses they will become less and less
>interested in Apache Flex releases and activity.  However, the Apache Flex
>JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
>base, and the team page for Flex makes it hard to determine which
>committers are active on FlexJS, and it is frequently hard to determine if
>a user's question is about regular Flex or FlexJS.   We are seeing an
>increase in user interest with the Flash end-of-life announcement and
>having separate mailing lists, web pages, and JIRA projects will help save
>everyone time and energy.
>
>Alignment
>
>Apache FlexJS is already being released by Apache.
>
>Known Risks
>
>Code Extraction
>
>The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
>be migrated to GitBox.  Other Apache Flex repos would be treated as
>external dependencies.  This includes flex-utilities and the Apache Flex
>Installer.
>
>Orphaned Projects
>
>Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
>help out just-in-case, but are already mostly inactive on the Flex code
>bases. However, there are at least 3 Apache Flex PMC members who have not
>contributed at all to FlexJS and participate in regular Flex releases, so
>the expectation is that Apache Flex will remain a viable project for some
>time to come.
>
>Inexperience with Open Source
>
>All of the initial team has been contributing to Apache Flex for months if
>not years.
>
>Homogenous Developers
>
>No company employs more than two of the members of the initial team.
>
>Reliance on Salaried Developers
>
>Until about a year ago, only 2 of the proposed PMC members were paid to
>work on FlexJS.  The rest contributed in their spare time.  Two more are
>now paid to migrate an existing application and thus contribute to add
>missing features and fix bugs.  By creating a separate project, we hope to
>attract more folks who may not want to be involved with the legacy Apache
>Flex code.
>
>Relationship with Existing Apache Projects
>
>Apache FlexJS might use some releases from Apache Flex for some features
>or for an Installer

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

2017-09-05 Thread Alex Harui

Again, please try to find small test cases that reproduce these bugs.  As
Harbs showed, details matter.  The fact that you were trying to initialize
a static variable with a function might matter in these cases.

Thanks,
-Alex

On 9/5/17, 3:20 AM, "lizhi"  wrote:

>But I feel the spriteflexjs library has been wasted. Because a lot of test
>examples are wrong now.
>
>Uncaught TypeError: Cannot read property 'BaseRenderer' of undefined
>at SpriteFlexjs.js:91
>Language.js:238 power by SpriteFlexJS
>Graphics.js:442 Uncaught TypeError: Cannot read property 'createPath' of
>undefined
>at flash.display.Graphics.makePath (Graphics.js:442)
>at flash.display.Graphics.moveTo (Graphics.js:359)
>at flash.display.Graphics.drawRect (Graphics.js:249)
>at new TestMouseEvent (TestMouseEvent.js:92)
>at localhost/:135
>Stage.js:581 Uncaught TypeError: Cannot read property 'call' of undefined
>at flash.display.Stage.__update (Stage.js:581)
>TestMouseEvent.css Failed to load resource: the server responded with a
>status of 404 (Not Found)
>
>
>
>-
>spriteflexjs.com 
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2F=02%7C01%7C%7C41810d8107ec43320
>92708d4f447cfea%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364020366431
>58863=dUpacBL0j29OlajHIUGYBbB3feWlvXcY3Y7i3gredTU%3D=0

> 5000 video calls / day!

2017-09-05 Thread Erik de Bruin

Hi,

This morning my eye fell on this encouraging statistic: the splicers for
the first time had to process more than 5000 video calls a day last week.
This is up from < 2000 this time last year. Go Homewav!

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [VOTE] Fork FlexJS from Apache Flex

2017-09-05 Thread Tom Chiverton


+1

People being on/not on the project board can be resolved after the split.

Tom


On 01/09/17 09:43, Yishay Weiss wrote:

+1

From: Alex Harui
Sent: Friday, September 1, 2017 9:28 AM
To: dev@flex.apache.org
Subject: [VOTE] Fork FlexJS from Apache Flex

Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

 Proposal ---

Apache FlexJS for Apache Top-Level Project

Abstract

Apache FlexJS is a new implementation of the principles of Apache Flex but
designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
Apache FlexJS was created and released as part of the Apache Flex project
and the UI framework is a full rewrite and does not leverage the code
bases donated by Adobe.  Only the FlexJS compiler source was donated by
Adobe.

Over time, the set of Apache Flex committers who are working on Apache
Flex releases have become distinct from those working on FlexJS.  Add to
that the Adobe announcement of the end-of-life for Flash in the browser,
it makes sense to separate FlexJS from Flex so that followers of one side
or the other don't have to filter out emails, bugs, web pages, etc, that
they don't need.

The proposal is to form an Apache FlexJS top-level project instead of
creating a new Incubator Podling.   That is because all but one of the
folks being proposed to the new Apache FlexJS PMC below have been on the
Apache Flex PMC for months, if not years, and understand how to
participate productively in an Apache project.  Plus, Apache FlexJS has
already been released by the top-level Apache Flex project.

Overview of FlexJS

Apache FlexJS is designed to improve developer productivity in creating
applications for wherever Javascript runs, including browsers as well as
Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
of folks creating IDEs for FlexJS, and some folks are at various points in
the process of migrating existing Flex applications to FlexJS.

Current Status

Meritocracy

Within Apache Flex, the FlexJS development has been conducted as a
meritocracy.  No existing FlexJS developers came with the compiler code
base donated by Adobe nor were they on the initial committers list for
Apache Flex other than Alex Harui.  Everyone else has earned their way in
by contributing and earning merit.

Community

Many FlexJS users are trying to migrate an existing Apache Flex app off of
Adobe Flash.  As their migration progresses they will become less and less
interested in Apache Flex releases and activity.  However, the Apache Flex
JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
base, and the team page for Flex makes it hard to determine which
committers are active on FlexJS, and it is frequently hard to determine if
a user's question is about regular Flex or FlexJS.   We are seeing an
increase in user interest with the Flash end-of-life announcement and
having separate mailing lists, web pages, and JIRA projects will help save
everyone time and energy.

Alignment

Apache FlexJS is already being released by Apache.

Known Risks

Code Extraction

The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
be migrated to GitBox.  Other Apache Flex repos would be treated as
external dependencies.  This includes flex-utilities and the Apache Flex
Installer.

Orphaned Projects

Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
help out just-in-case, but are already mostly inactive on the Flex code
bases. However, there are at least 3 Apache Flex PMC members who have not
contributed at all to FlexJS and participate in regular Flex releases, so
the expectation is that Apache Flex will remain a viable project for some
time to come.

Inexperience with Open Source

All of the initial team has been contributing to Apache Flex for months if
not years.

Homogenous Developers

No company employs more than two of the members of the initial team.

Reliance on Salaried Developers

Until about a year ago, only 2 of the proposed PMC members were paid to
work on FlexJS.  The rest contributed in their spare time.  Two more are
now paid to migrate an existing application and thus contribute to add
missing features and fix bugs.  By creating a separate project, we hope to
attract more folks who may not want to be involved with the legacy Apache
Flex code.

Relationship with Existing Apache Projects

Apache FlexJS might use some releases from Apache Flex for some features
or for an Installer app.  FlexJS can be used to create Apache Cordova
applications and we hope to find time to make the Cordova community

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

2017-09-05 Thread lizhi

Thank you very much!
Well, I also know there's a setTimeout, but this setTimeout is only JS
built, so I don't care.
However, it seems that the new version of the flexjs compiler has problems
dealing with static classes. And flexjs0.8 doesn't have that problem.



-
spriteflexjs.com 
--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

2017-09-05 Thread Harbs

BTW, The problem is probably related to the fact that you have a static var 
referencing the top level function.

I found the problem by searching the JS files to “setTimeout”. SpriteFlexjs.js 
was the only file which had it listed in the dependency list.

HTH,
Harbs

> On Sep 5, 2017, at 12:33 PM, Harbs  wrote:
> 
> Lizhi,
> 
> Your problem is in SpriteFlexjs where you have the following output:
> 
> /* FlexJS Static Dependency List: flash.__native.BaseRenderer,setTimeout*/
> 
> The compiler thinks there’s a dependency on a setTimeout class.
> 
> That’s caused by this code:
> 
>   public static var requestAnimationFrame:Function =
>   window["requestAnimationFrame"]   ||
>   window["webkitRequestAnimationFrame"] ||
>   window["mozRequestAnimationFrame"]||
>   window["oRequestAnimationFrame"] ||
>   window["msRequestAnimationFrame"] ||
>   function(callback):void {
>   setTimeout(callback, 1000 / 60);
>   };
> 
> Changing it to the following fixes your error:
> 
>   public static var requestAnimationFrame:Function =
>   window["requestAnimationFrame"]   ||
>   window["webkitRequestAnimationFrame"] ||
>   window["mozRequestAnimationFrame"]||
>   window["oRequestAnimationFrame"] ||
>   window["msRequestAnimationFrame"] ||
>   function(callback):void {
>   window["setTimeout"](callback, 1000 / 60);
>   };
> 
> Harbs
> 
>> On Sep 5, 2017, at 11:27 AM, lizhi  wrote:
>> 
>> no error too.
>> 
>> package 
>> {
>>  import flash.utils.setTimeout;
>>  public class TestBug 
>>  {
>>  
>>  public function TestBug() 
>>  {
>>  new TestBug2();
>>  setTimeout(function():void{trace("se")}, 100);
>>  trace(1);
>>  }
>>  
>>  }
>> 
>> }
>> 
>> 
>> package 
>> {
>>  public class TestBug2 
>>  {
>>  
>>  public function TestBug2() 
>>  {
>>  
>>  setTimeout(function():void{trace("se")}, 100);
>>  }
>>  
>>  }
>> 
>> }
>> 
>> 
>> 
>> 
>> -
>> spriteflexjs.com 
>> --
>> Sent from: http://apache-flex-development.247.n4.nabble.com/
>

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

2017-09-05 Thread Harbs

Lizhi,

Your problem is in SpriteFlexjs where you have the following output:

/* FlexJS Static Dependency List: flash.__native.BaseRenderer,setTimeout*/

The compiler thinks there’s a dependency on a setTimeout class.

That’s caused by this code:

public static var requestAnimationFrame:Function =
window["requestAnimationFrame"]   ||
window["webkitRequestAnimationFrame"] ||
window["mozRequestAnimationFrame"]||
window["oRequestAnimationFrame"] ||
window["msRequestAnimationFrame"] ||
function(callback):void {
setTimeout(callback, 1000 / 60);
};

Changing it to the following fixes your error:

public static var requestAnimationFrame:Function =
window["requestAnimationFrame"]   ||
window["webkitRequestAnimationFrame"] ||
window["mozRequestAnimationFrame"]||
window["oRequestAnimationFrame"] ||
window["msRequestAnimationFrame"] ||
function(callback):void {
window["setTimeout"](callback, 1000 / 60);
};

Harbs

> On Sep 5, 2017, at 11:27 AM, lizhi  wrote:
> 
> no error too.
> 
> package 
> {
>   import flash.utils.setTimeout;
>   public class TestBug 
>   {
>   
>   public function TestBug() 
>   {
>   new TestBug2();
>   setTimeout(function():void{trace("se")}, 100);
>   trace(1);
>   }
>   
>   }
> 
> }
> 
> 
> package 
> {
>   public class TestBug2 
>   {
>   
>   public function TestBug2() 
>   {
>   
>   setTimeout(function():void{trace("se")}, 100);
>   }
>   
>   }
> 
> }
> 
> 
> 
> 
> -
> spriteflexjs.com 
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

2017-09-05 Thread lizhi

no error too.

package 
{
import flash.utils.setTimeout;
public class TestBug 
{

public function TestBug() 
{
new TestBug2();
setTimeout(function():void{trace("se")}, 100);
trace(1);
}

}

}


package 
{
public class TestBug2 
{

public function TestBug2() 
{

setTimeout(function():void{trace("se")}, 100);
}

}

}




-
spriteflexjs.com 
--
Sent from: http://apache-flex-development.247.n4.nabble.com/

[FlexJS, AMF] Steps to make FlexJS / Java - RemoteObject / AMF sample work

Re: [FlexJS] Re: Remote object for Flex JS

Re: FlexJS installation - Installer vs. npm

FlexJS installation - Installer vs. npm

Re: [FlexJS] Re: Remote object for Flex JS

Re: [FlexJS] Re: Remote object for Flex JS

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

[RESULT][VOTE] Fork FlexJS from Apache Flex

Re: [VOTE] Fork FlexJS from Apache Flex

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

> 5000 video calls / day!

Re: [VOTE] Fork FlexJS from Apache Flex

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

Re: Kotlinjs has solved the circular dependency problem. Flexjs, do you have any plans?

16 matches

Site Navigation

Mail list logo

Footer information