Re: [FlexJS] Some things still missing ni FlexJS

2017-01-18 Thread Alex Harui
On 1/18/17, 5:11 AM, "Kessler CTR Mark J" wrote: > >Could we have a new namespace of AS components that are stripped down >that are 100% compatible to the FlexJS side? People could start >converting over existing apps slowly while still being able to deploy to >their current targets. Could al

RE: [FlexJS] Some things still missing ni FlexJS

2017-01-18 Thread Kessler CTR Mark J
ssage- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, January 17, 2017 4:29 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [FlexJS] Some things still missing ni FlexJS On 1/17/17, 3:43 AM, "Kessler CTR Mark J" wrote: >I do not use AMF for enterprise level

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-17 Thread Alex Harui
On 1/17/17, 3:43 AM, "Kessler CTR Mark J" wrote: >I do not use AMF for enterprise level applications. AMF falls short >of our requirements. But the bottom line for us for converting to FlexJS >would be seamless operation(look / feel / interaction) in all major >browsers (excluding IE) and

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-17 Thread Peter Ent
See comment in-line. ‹peter On 1/17/17, 9:11 AM, "yishayw" wrote: >Kessler CTR Mark J wrote >> the ability to compile it using our existing spark based projects >>without >> having to having to create hundreds of JS beads / customizations. >> Understandably heavier, but compatibility is more imp

RE: [FlexJS] Some things still missing ni FlexJS

2017-01-17 Thread yishayw
Kessler CTR Mark J wrote > the ability to compile it using our existing spark based projects without > having to having to create hundreds of JS beads / customizations. > Understandably heavier, but compatibility is more important. An effort is underway to create a component set that bakes in mor

RE: [FlexJS] Some things still missing ni FlexJS

2017-01-17 Thread Kessler CTR Mark J
rg Subject: [Non-DoD Source] Re: [FlexJS] Some things still missing ni FlexJS On 1/13/17, 12:44 AM, "Christofer Dutz" wrote: >Well from my point of view it was the whole “write once run everywhere” >thing. >I was totally annoyed of having to write UI things once and then pat

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-16 Thread Alex Harui
On 1/16/17, 12:45 AM, "Christofer Dutz" wrote: >I would strongly object to make the FlexJS Compiler directly utilize >Cordova. This would tightly couple the two. >Guess I just don’t understand quite what’s the difference between the >CordovaCameraExample which produces a Cordova project, which

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-16 Thread Carlos Rovira
+1 to Cordova FlexJS Project Archetype (without doubt) 2017-01-16 9:45 GMT+01:00 Christofer Dutz : > I would strongly object to make the FlexJS Compiler directly utilize > Cordova. This would tightly couple the two. > Guess I just don’t understand quite what’s the difference between the > Cordova

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-16 Thread Christofer Dutz
I would strongly object to make the FlexJS Compiler directly utilize Cordova. This would tightly couple the two. Guess I just don’t understand quite what’s the difference between the CordovaCameraExample which produces a Cordova project, which is then packaged using cordova in another step. I t

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-15 Thread Alex Harui
On 1/15/17, 9:12 AM, "Christofer Dutz" wrote: >What exactly are you talking about when mentioning “Cordova Support”? >Don’t we already have examples that are bundled with Cordova to valid >Mobile Apps? >What’s missing here? Not sure I understand you question, but in another thread I mentioned

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-15 Thread Christofer Dutz
What exactly are you talking about when mentioning “Cordova Support”? Don’t we already have examples that are bundled with Cordova to valid Mobile Apps? What’s missing here? Chris Am 15.01.17, 07:58 schrieb "Alex Harui" : On 1/14/17, 4:00 AM, "Vincent" wrote: >So what wo

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-15 Thread Vincent
Hi Alex, I wasn't thinking from a strategical point of view but only from a technical one. That make sense. Thank you. Vincent Le 15/01/2017 à 07:58, Alex Harui a écrit : On 1/14/17, 4:00 AM, "Vincent" wrote: So what would be the interest of choosing technologies like Cordova instead

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-14 Thread Alex Harui
On 1/14/17, 4:00 AM, "Vincent" wrote: >So what would be the interest of choosing technologies like Cordova >instead of AIR to generate cross platform mobile apps ? A goal of Apache projects is to do their best to be independent of corporate influence. Flex is at Apache because a corporation m

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-14 Thread Carlos Rovira
Hi Vicent, 2017-01-14 13:00 GMT+01:00 Vincent : > Hi, > > Regarding performance using standard display list, it is already possible > with Flex to develop mobile applications indistinguishable from native ones. > My understanding of FlexJS is that the framework is much lighter than flex > so the

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-14 Thread Vincent
Hi, Regarding performance using standard display list, it is already possible with Flex to develop mobile applications indistinguishable from native ones. My understanding of FlexJS is that the framework is much lighter than flex so the generated swf should logically perform even better. So

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Carlos Rovira
2017-01-13 20:01 GMT+01:00 Alex Harui : > > > why can't we call that our 1.0? What would be wrong with > calling that 1.0? > > As I said, for me 0.8, 1.0, 0.15 or 2.1 is not a problem. Things out there taught us that number version not really matters I'm more with the internal thinking that make

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Alex Harui
On 1/13/17, 11:13 AM, "piotrz" wrote: >I was working on Big Flex app where we were using SOAP/XML. - I think now >we >can consume XML in FlexJS. Yes. You can migrate today if you are using XML, only need to support one language and don't use modules. Regarding skinning, in theory your compan

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread piotrz
I was working on Big Flex app where we were using SOAP/XML. - I think now we can consume XML in FlexJS. Another thing which came up to my mind - Did we ever write any WIKI page to show people what actually option of data consuming we have ? I think if it will be pointed on WIKI and in Release no

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Alex Harui
On 1/13/17, 10:28 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >2017-01-13 19:11 GMT+01:00 Alex Harui : > >> >> >> IMO, there are at least some existing Flex apps that don't use AMF. Now >> it may turn out that we will have AMF shortly, but until it is done, >>those >> who d

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Carlos Rovira
2017-01-13 19:46 GMT+01:00 Peter Ent : > > > I wasn't thinking of FlexJS/Native as desire to dump SWF and JS-xcompile, > but FlexJS/Native as a new addition and option for folks who want to work > in ActionScript and layout their apps in MXML but want a native > application as the end result, rath

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Peter Ent
See in-line. ‹peter On 1/13/17, 1:35 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Peter, > >2017-01-13 19:22 GMT+01:00 Peter Ent : > >> I was speaking to a friend that has some JavaScript developers working >>for >> him. They use React and React/Native for their mobile app

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Carlos Rovira
Hi Peter, 2017-01-13 19:22 GMT+01:00 Peter Ent : > I was speaking to a friend that has some JavaScript developers working for > him. They use React and React/Native for their mobile apps. His feeling is > that web-centric apps (e.g. Amazon.com) are going to be replaced with > mobile apps since mo

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Carlos Rovira
2017-01-13 19:11 GMT+01:00 Alex Harui : > > > IMO, there are at least some existing Flex apps that don't use AMF. Now > it may turn out that we will have AMF shortly, but until it is done, those > who don't need it can start migrating their apps today. Some folks are > already migrating. I don

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Peter Ent
I was speaking to a friend that has some JavaScript developers working for him. They use React and React/Native for their mobile apps. His feeling is that web-centric apps (e.g. Amazon.com) are going to be replaced with mobile apps since mobile devices are cheaper than laptops. They are concentrati

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Carlos Rovira
The last time I saw webgl working was testing Unity 3D webgl. Unity invest much effort and they got it working, but mainly on desktop, and without great performance. In mobile devices, was not supported (that was about 6 month ago), and when playing on iPhone (for example) was really bad experience

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Alex Harui
On 1/13/17, 12:44 AM, "Christofer Dutz" wrote: >Well from my point of view it was the whole “write once run everywhere” >thing. >I was totally annoyed of having to write UI things once and then patch >and bugfix things for all the other Browsers. I would say that fits under the "Developer Pro

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Dev LFM
Actually it would be more easy, if adobe just convert their flashplayer to render on webgl and that would work for all... 2017-01-13 15:15 GMT+00:00 Dev LFM : > Hi all, > > For me, as I since 8 years constantly developed content editors for > printing labs (basically I would use a Canvas on FlexJ

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Dev LFM
Hi all, For me, as I since 8 years constantly developed content editors for printing labs (basically I would use a Canvas on FlexJS), it was the no crossbrowsing differences, one player that behaves the same on all targets (This is the key). My company currently relies on Flash to sell.. and html/

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Harbs
I agree with Chris that target #1 is developers migrating from Flash. But, #2 is a very close second with JS developers looking for better productivity. #2 is where we can have a real win in terms of adoption. I think the reason js developers seem to always flutter from framework to framework i

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-13 Thread Christofer Dutz
Well from my point of view it was the whole “write once run everywhere” thing. I was totally annoyed of having to write UI things once and then patch and bugfix things for all the other Browsers. But in general I think you (Alex) and I have one great difference in our assumption of who will pro

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-12 Thread Alex Harui
On 1/12/17, 12:46 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >We need some strategy, and we must think about what others are giving in >comparison with us. >In LTE I think our solution win, but right now is complicate convince >business to choose us over Angular/React, sinc

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-12 Thread Carlos Rovira
We need some strategy, and we must think about what others are giving in comparison with us. In LTE I think our solution win, but right now is complicate convince business to choose us over Angular/React, since is world trending. So I'm with Chris that we need to give things others doesn't have, f

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-12 Thread yishayw
OmPrakash Muppirala wrote > If folks feel comfortable with the ease of use, extensibility and > stability > of FlexJS, they will start showing interest. At that point, any missing > killer features can be talked about. Enterprise companies can join us in > the effort to add any features they thin

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread piotrz
Personally I really believe that I get a full time job where the task will be move from Flex to FlexJS. As long as I have such faith I will be contributing. It is all about attracting by this framework not only developers, but rather managers, PMs who decide abot technology in the company. In my

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Carlos Rovira
Hi Peter, is possible to expose the AMF services in JSON. For example, people in Java are using Jersey (https://jersey.java.net), but that's not the point. We can always do as many changes as we want...but we need to say to people "we have FlexJS with AMF support and you can migrate from Flex to F

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Carlos Rovira
mething else. Having distinguishable features is > > essential, from my point of view, to get people to try something. > > > > Chris > > > > > > > > Von meinem Samsung Galaxy Smartphone gesendet. > > > > > > Ursprüngliche Nachricht -

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Peter Ent
Thanks. I was just wondering if you had services that used both AMF and REST/JSON so that those Flex projects migrated to FlexJS could just use JSON instead. ‹peter On 1/11/17, 2:06 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Peter, > >There are new projects using React

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Carlos Rovira
Hi Peter, There are new projects using React with Rest and Json. Think that was started from scratch. I'm referring to migrate old systems that still are stuck in Flex SDK and we have the opportunity to change to FlexJS. Those projects was done with AMF (and as I said many others out there). If w

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread OmPrakash Muppirala
view, to get people to try something. > > Chris > > > > Von meinem Samsung Galaxy Smartphone gesendet. > > > Ursprüngliche Nachricht > Von: Alex Harui > Datum: 11.01.17 17:22 (GMT+01:00) > An: dev@flex.apache.org > Betreff: Re: [FlexJS] So

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Alex Harui
Excellent. Looking forward to it. On 1/11/17, 8:54 AM, "PKumar" wrote: >Alex, > >I have ported the following amfjs library in FlexjS and working fine with >BlazeDS. But due to busy schedule i could not further continue on class >mapping part. Currently i am getting the Object from BlazeDS with

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread PKumar
Alex, I have ported the following amfjs library in FlexjS and working fine with BlazeDS. But due to busy schedule i could not further continue on class mapping part. Currently i am getting the Object from BlazeDS with one "_explicitType" field. Now i need to map that Object to correct class. Hope

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Alex Harui
On 1/11/17, 1:43 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Alex, > >I think many people in this thread are saying "No, we'll not go to >production without AMF and basic module support". IMHO, it would be very >difficult to say we have 1.0 without that, since AMF/Remote

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Peter Ent
Question in-line below. Thanks, Peter On 1/11/17, 4:43 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Alex, > >I think many people in this thread are saying "No, we'll not go to >production without AMF and basic module support". IMHO, it would be very >difficult to say we h

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Christofer Dutz
I think parsley and similar should be able to run in FlexJS as they don’t rely on any UI stuff and as far as I understood it, the concepts they are based on should work with FlexJS. Haven’t tried that though ;-) Chris Am 11.01.17, 11:04 schrieb "Vincent" : Hi Carlos, I agree with

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Vincent
ncent<mailto:vinc...@after24.net> Sent: Wednesday, January 11, 2017 12:04 PM To: dev@flex.apache.org<mailto:dev@flex.apache.org> Subject: Re: [FlexJS] Some things still missing ni FlexJS Hi Carlos, I agree with you. AMF support is essential for us to start thinking porting our Flex apps

RE: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Yishay Weiss
We’re using PureMVC with FlexJS. From: Vincent<mailto:vinc...@after24.net> Sent: Wednesday, January 11, 2017 12:04 PM To: dev@flex.apache.org<mailto:dev@flex.apache.org> Subject: Re: [FlexJS] Some things still missing ni FlexJS Hi Carlos, I agree with you. AMF support is essenti

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Carlos Rovira
Hi Vincent, I think we don't have nothing yet like Parsely or Swiz. It's clear that we need many things to be in the same relation as Flex SDK, but my point is to isolate the problem, so if people want to change, at least make him to create a completely new interface that affects only to the clien

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Vincent
Hi Carlos, I agree with you. AMF support is essential for us to start thinking porting our Flex apps to FlexJS. I use MVC architecture with the support of Parsley 3 for : - Dependency Injection - Messaging - Managed command (synchronous and asynchronous) Is there an equivalent of this tools

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-11 Thread Carlos Rovira
Hi Alex, I think many people in this thread are saying "No, we'll not go to production without AMF and basic module support". IMHO, it would be very difficult to say we have 1.0 without that, since AMF/RemoteObject was in almost 99% of old Flex SDK, with some HTTPServices and almost no WebServices

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Alex Harui
In my mind, there is little doubt that someone will someday implement AMF and not-unloadable modules. The question is when? IMO, as soon as someone can tell us they've gone to production with the code we have, I'm willing to call that 1.0, and the people who wrote that app probably migrated a sin

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Dev LFM
+1 2017-01-10 14:09 GMT+00:00 Fréderic Cox : > AMF is also essential for us to take FlexJS serious as a replacement to > Flex > > On Tue, Jan 10, 2017 at 2:41 PM, Vincent wrote: > > > Hello, > > > > Same points than Christopher : AMF and modules. > > The first is essential for us. > > > > Vincen

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Fréderic Cox
AMF is also essential for us to take FlexJS serious as a replacement to Flex On Tue, Jan 10, 2017 at 2:41 PM, Vincent wrote: > Hello, > > Same points than Christopher : AMF and modules. > The first is essential for us. > > Vincent. > > > > Le 10/01/2017 à 13:07, Christofer Dutz a écrit : > >> +1

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Vincent
Hello, Same points than Christopher : AMF and modules. The first is essential for us. Vincent. Le 10/01/2017 à 13:07, Christofer Dutz a écrit : +1 for the AMF and +1 for not-unloadable modules. I see it the same way as Carlos. At the moment I see FlexJS as an opportunity for companies to ge

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Carlos Rovira
The problem with AMF could be what Alex mentioned some time ago. If there's some C++ code in Flash Player that was making the magic behind scenes for a super efficient protocol, and if we can super pass this problem in this era of "no-plugins". We'll need to know what's the effort behind AMF, If co

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Christofer Dutz
+1 for the AMF and +1 for not-unloadable modules. I see it the same way as Carlos. At the moment I see FlexJS as an opportunity for companies to get out of the dilemma of being stuck in a dead end with their existing Flex applications. Supporting things like modules and AMF will ease the migrati

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-10 Thread Carlos Rovira
"IMO, this has two halves: non-unloadable modules is relatively straight forward to do. Unloadable modules will be a ton of work. IIRC, Flex 1.0 and I think even Flex 2.x grew its customer base without unloadable modules." If non-unloadable modules is easy to implement, I think it should go ASA

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-08 Thread Harbs
I agree that skinning is harder than it should be. For one thing: There’s too many attributes which are set directly. More extensive use of CSS would make skinning easier. On Jan 8, 2017, at 10:49 AM, Christofer Dutz wrote: > From my side I’m missing skinnable components. I really loved the wa

RE: [FlexJS] Some things still missing ni FlexJS

2017-01-08 Thread Yishay Weiss
Two things that spring to my mind are intuitive layouts and stability. From: Harbs<mailto:harbs.li...@gmail.com> Sent: Sunday, January 8, 2017 10:18 AM To: dev@flex.apache.org<mailto:dev@flex.apache.org> Subject: Re: [FlexJS] Some things still missing ni FlexJS There’s one t

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-08 Thread Harbs
There’s one thing missing which was not really in the old Flex (or maybe yes with the history scripts), but I think is really important for any single page javascript application framework: Routing (or what was called “deep linking” in older terms). On Jan 7, 2017, at 5:58 PM, Carlos Rovira wr

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-07 Thread OmPrakash Muppirala
On Sat, Jan 7, 2017 at 10:47 AM, Carlos Rovira < carlos.rov...@codeoscopic.com> wrote: > Hi Om, > > about Yeoman, I didn't know about that, but it seems to me the same as a > Maven Arquetype to generate a project scaffold. > Right? If is this, we have already 3 of them (created by Chris, and we >

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-07 Thread Alex Harui
If someone has time, add some of these to JIRA. Which, if any, do folks think are 1.0 requirements? IMO, except for more doc and tutorials, the rest of the list is optional for 1.0, but volunteers are welcome to start now. Other opinions welcome. Some comments in-line... On 1/7/17, 9:39 PM, "o

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-07 Thread OmPrakash Muppirala
On Sat, Jan 7, 2017 at 9:42 AM, OmPrakash Muppirala wrote: > > > On Jan 7, 2017 7:59 AM, "Carlos Rovira" wrote: > > Hi, > > I want to list some things I miss from old Flex SDK in FlexJS. Hope others > could bring more if they want. Hope this thread could help us to know what > people things abou

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-07 Thread Carlos Rovira
Hi Om, about Yeoman, I didn't know about that, but it seems to me the same as a Maven Arquetype to generate a project scaffold. Right? If is this, we have already 3 of them (created by Chris, and we could make more) 2017-01-07 18:42 GMT+01:00 OmPrakash Muppirala : > On Jan 7, 2017 7:59 AM, "Carl

Re: [FlexJS] Some things still missing ni FlexJS

2017-01-07 Thread OmPrakash Muppirala
On Jan 7, 2017 7:59 AM, "Carlos Rovira" wrote: Hi, I want to list some things I miss from old Flex SDK in FlexJS. Hope others could bring more if they want. Hope this thread could help us to know what people things about it, if someone expect to implement it: * Modules (or how to make FlexJS lo