You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by OmPrakash Muppirala <bi...@gmail.com> on 2015/06/15 22:06:21 UTC
[FlexJS] FlexJS vs. AngularJS 2.0
Here is a rundown of how to do things with AngularJS 2.0:
http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/
As I walk through the details, I see the twists and turns they are going
through to do seemingly simple things. The single biggest reason for that
is that there is no MXML like malleable way to declaratively create the UI
and to wire things up.
I am interested in seeing a step by step comparison of doing things the
FlexJS way vs. AngularJS2.0 way. Here are a few things we can concentrate
on:
1. Module loading
2. Classes
4. Components
5. Design Patterns
6. Events
7. Calling webservices
8. Skinning
...
Anyone wants to volunteer to help write this document? This would involve
understanding and writing FlexJS code samples. This would also involve
understanding AngularJS2.0 as well. Which is a benefit on its own.
Volunteers?
Thanks,
Om
RE: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by piotrz <pi...@gmail.com>.
Heh Mark - I have started my short adventure with AngularJS from exactly same
tutorial. Really good. :)
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-FlexJS-vs-AngularJS-2-0-tp47827p47899.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
On a side note, I remember fiddling with angular a while back. I bumped into this free training for it [1] that gave a good start up understanding of how some of the things work in it.
[1] http://campus.codeschool.com/courses/shaping-up-with-angular-js/intro
-Mark
-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash Muppirala
Sent: Monday, June 15, 2015 4:06 PM
To: dev@flex.apache.org
Subject: [FlexJS] FlexJS vs. AngularJS 2.0
Here is a rundown of how to do things with AngularJS 2.0:
http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/
As I walk through the details, I see the twists and turns they are going
through to do seemingly simple things. The single biggest reason for that
is that there is no MXML like malleable way to declaratively create the UI
and to wire things up.
I am interested in seeing a step by step comparison of doing things the
FlexJS way vs. AngularJS2.0 way. Here are a few things we can concentrate
on:
1. Module loading
2. Classes
4. Components
5. Design Patterns
6. Events
7. Calling webservices
8. Skinning
...
Anyone wants to volunteer to help write this document? This would involve
understanding and writing FlexJS code samples. This would also involve
understanding AngularJS2.0 as well. Which is a benefit on its own.
Volunteers?
Thanks,
Om
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by ro...@gmail.com.
I think a comparison to polymer would be interesting as well.
Richard Oren
714-916-2102
> On 15 Jun 2015, at 1:06 pm, OmPrakash Muppirala <bi...@gmail.com> wrote:
>
> Here is a rundown of how to do things with AngularJS 2.0:
> http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/
>
> As I walk through the details, I see the twists and turns they are going
> through to do seemingly simple things. The single biggest reason for that
> is that there is no MXML like malleable way to declaratively create the UI
> and to wire things up.
>
> I am interested in seeing a step by step comparison of doing things the
> FlexJS way vs. AngularJS2.0 way. Here are a few things we can concentrate
> on:
>
> 1. Module loading
> 2. Classes
> 4. Components
> 5. Design Patterns
> 6. Events
> 7. Calling webservices
> 8. Skinning
> ...
>
> Anyone wants to volunteer to help write this document? This would involve
> understanding and writing FlexJS code samples. This would also involve
> understanding AngularJS2.0 as well. Which is a benefit on its own.
>
> Volunteers?
>
> Thanks,
> Om
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by Carlos Rovira <ca...@codeoscopic.com>.
It's sure that Angular or React has more things right now (and many devs
right now enrolling their rows), but FlexJS is not comparable right now.
Looking at the way and speed things are happening here, I should expect
FlexJS to be a great technology
in the next 6 or 12 months, with many thinks others can't even dream due to
the nature of the technology itself.
So yes, this year probably the "framework of the year" could be maybe
React?....but in 2017? or 2018?
I think FlexJS has the opportunity to overpass all the cumbersome things
many of us see when making some angular or react programming.
2016-07-07 16:56 GMT+02:00 Alex Harui <ah...@adobe.com>:
> Probably true, but that's why we need volunteers to help us. Lots of
> small contributions can really add up. And Apache projects are not
> controlled by commercial entities so your contributions can have more
> impact.
>
> Thanks,
> -Alex
>
> On 7/7/16, 2:00 AM, "anshumanpradippatil1506"
> <an...@gmail.com> wrote:
>
> >I have worked lot with Flex and also now days working with angular2. One
> >thing I am sure about is FlexJS is far away from angular2, This is not
> >only
> >about component(UI) creation there are many other thing which angular2
> >provides such as DI, Routing, documentation ..........etc a long list
> >
> >
> >
> >--
> >View this message in context:
> >
> http://apache-flex-development.2333347.n4.nabble.com/FlexJS-FlexJS-vs-Angu
> >larJS-2-0-tp47827p53748.html
> >Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
>
--
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es
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] FlexJS vs. AngularJS 2.0
Posted by Alex Harui <ah...@adobe.com>.
Probably true, but that's why we need volunteers to help us. Lots of
small contributions can really add up. And Apache projects are not
controlled by commercial entities so your contributions can have more
impact.
Thanks,
-Alex
On 7/7/16, 2:00 AM, "anshumanpradippatil1506"
<an...@gmail.com> wrote:
>I have worked lot with Flex and also now days working with angular2. One
>thing I am sure about is FlexJS is far away from angular2, This is not
>only
>about component(UI) creation there are many other thing which angular2
>provides such as DI, Routing, documentation ..........etc a long list
>
>
>
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/FlexJS-FlexJS-vs-Angu
>larJS-2-0-tp47827p53748.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by anshumanpradippatil1506 <an...@gmail.com>.
I have worked lot with Flex and also now days working with angular2. One
thing I am sure about is FlexJS is far away from angular2, This is not only
about component(UI) creation there are many other thing which angular2
provides such as DI, Routing, documentation ..........etc a long list
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-FlexJS-vs-AngularJS-2-0-tp47827p53748.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by Michael Schmalle <te...@gmail.com>.
Well I understand your point but, in this day and age, the success of a
framework will come down to how well it integrates with other frameworks
and now even languages. Just like our world with it's diverse ethnic and
cultural backgrounds, a truly successful framework can integrate things
created by others many hours of work that applies to the same use case.
I only brought up web components because I have seen some great examples of
them with like polymer.
It's the same reason I wrote the EXTERNC compiler for js shims. Creating
adapters is a good thing IMHO, I was speaking of creating adapters for Web
Components not spitting them out of MXML perse.
Mike
On Mon, Jun 15, 2015 at 4:22 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
> The problem with webcomponents is that it is not yet widely supported.
> Only Chrome supports anything related to ShadowDOM, etc.
> http://caniuse.com/#feat=shadowdom
>
> The way I see this is that webcomponents is a way to make developers reuse
> code easily and has no real runtime advantages. So, the approach of FlexJS
> to let users define, compose and inherit components via MXML is more than
> sufficient. I don't see a real need to spit out webcomponent based HTML as
> the output of the FlexJS compilation step. What we are doing should work
> perfectly.
>
> Thanks,
> Om
>
> On Mon, Jun 15, 2015 at 1:13 PM, Michael Schmalle <
> teotigraphixllc@gmail.com
> > wrote:
>
> > Hi Om,
> >
> > I really have no idea as I am more down in the mud right now witht he
> > compiler but, I know one thing on the horizon that we should integrate
> and
> > maybe even try with MXML or something and that is Web Components. I still
> > need to do more research but now that is seems like we are making headway
> > with AS and the DOM, I might spend some time reading.
> >
> > I also wonder if one side of this discussion could be if Apache Flex can
> > augment the development of Angular, don't know, just talking.
> >
> > I tried a couple of the Hello World examples and the TODO app about a
> month
> > ago and totally hated add crap to HTML tags but, I did like the concept
> of
> > binding and stuff but, then again, MXML has been doing this for ages and
> is
> > Type strict. :)
> >
> > Mike
> >
> > On Mon, Jun 15, 2015 at 4:06 PM, OmPrakash Muppirala <
> bigosmallm@gmail.com
> > >
> > wrote:
> >
> > > Here is a rundown of how to do things with AngularJS 2.0:
> > > http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/
> > >
> > > As I walk through the details, I see the twists and turns they are
> going
> > > through to do seemingly simple things. The single biggest reason for
> > that
> > > is that there is no MXML like malleable way to declaratively create the
> > UI
> > > and to wire things up.
> > >
> > > I am interested in seeing a step by step comparison of doing things the
> > > FlexJS way vs. AngularJS2.0 way. Here are a few things we can
> > concentrate
> > > on:
> > >
> > > 1. Module loading
> > > 2. Classes
> > > 4. Components
> > > 5. Design Patterns
> > > 6. Events
> > > 7. Calling webservices
> > > 8. Skinning
> > > ...
> > >
> > > Anyone wants to volunteer to help write this document? This would
> > involve
> > > understanding and writing FlexJS code samples. This would also involve
> > > understanding AngularJS2.0 as well. Which is a benefit on its own.
> > >
> > > Volunteers?
> > >
> > > Thanks,
> > > Om
> > >
> >
>
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by piotrz <pi...@gmail.com>.
In my company colleagues did some internal project using webcomponents and
when I saw it for the first time I thought hey! We already have such things
in Flex - We can build such components really easy - This is nothing new. :)
Now in FlexJS it is also possible - maybe it's not so sophisticated as in
Flex yet, but it will be.
Just my two cents on this. :)
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-FlexJS-vs-AngularJS-2-0-tp47827p47835.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by OmPrakash Muppirala <bi...@gmail.com>.
The problem with webcomponents is that it is not yet widely supported.
Only Chrome supports anything related to ShadowDOM, etc.
http://caniuse.com/#feat=shadowdom
The way I see this is that webcomponents is a way to make developers reuse
code easily and has no real runtime advantages. So, the approach of FlexJS
to let users define, compose and inherit components via MXML is more than
sufficient. I don't see a real need to spit out webcomponent based HTML as
the output of the FlexJS compilation step. What we are doing should work
perfectly.
Thanks,
Om
On Mon, Jun 15, 2015 at 1:13 PM, Michael Schmalle <teotigraphixllc@gmail.com
> wrote:
> Hi Om,
>
> I really have no idea as I am more down in the mud right now witht he
> compiler but, I know one thing on the horizon that we should integrate and
> maybe even try with MXML or something and that is Web Components. I still
> need to do more research but now that is seems like we are making headway
> with AS and the DOM, I might spend some time reading.
>
> I also wonder if one side of this discussion could be if Apache Flex can
> augment the development of Angular, don't know, just talking.
>
> I tried a couple of the Hello World examples and the TODO app about a month
> ago and totally hated add crap to HTML tags but, I did like the concept of
> binding and stuff but, then again, MXML has been doing this for ages and is
> Type strict. :)
>
> Mike
>
> On Mon, Jun 15, 2015 at 4:06 PM, OmPrakash Muppirala <bigosmallm@gmail.com
> >
> wrote:
>
> > Here is a rundown of how to do things with AngularJS 2.0:
> > http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/
> >
> > As I walk through the details, I see the twists and turns they are going
> > through to do seemingly simple things. The single biggest reason for
> that
> > is that there is no MXML like malleable way to declaratively create the
> UI
> > and to wire things up.
> >
> > I am interested in seeing a step by step comparison of doing things the
> > FlexJS way vs. AngularJS2.0 way. Here are a few things we can
> concentrate
> > on:
> >
> > 1. Module loading
> > 2. Classes
> > 4. Components
> > 5. Design Patterns
> > 6. Events
> > 7. Calling webservices
> > 8. Skinning
> > ...
> >
> > Anyone wants to volunteer to help write this document? This would
> involve
> > understanding and writing FlexJS code samples. This would also involve
> > understanding AngularJS2.0 as well. Which is a benefit on its own.
> >
> > Volunteers?
> >
> > Thanks,
> > Om
> >
>
Re: [FlexJS] FlexJS vs. AngularJS 2.0
Posted by Michael Schmalle <te...@gmail.com>.
Hi Om,
I really have no idea as I am more down in the mud right now witht he
compiler but, I know one thing on the horizon that we should integrate and
maybe even try with MXML or something and that is Web Components. I still
need to do more research but now that is seems like we are making headway
with AS and the DOM, I might spend some time reading.
I also wonder if one side of this discussion could be if Apache Flex can
augment the development of Angular, don't know, just talking.
I tried a couple of the Hello World examples and the TODO app about a month
ago and totally hated add crap to HTML tags but, I did like the concept of
binding and stuff but, then again, MXML has been doing this for ages and is
Type strict. :)
Mike
On Mon, Jun 15, 2015 at 4:06 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
> Here is a rundown of how to do things with AngularJS 2.0:
> http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/
>
> As I walk through the details, I see the twists and turns they are going
> through to do seemingly simple things. The single biggest reason for that
> is that there is no MXML like malleable way to declaratively create the UI
> and to wire things up.
>
> I am interested in seeing a step by step comparison of doing things the
> FlexJS way vs. AngularJS2.0 way. Here are a few things we can concentrate
> on:
>
> 1. Module loading
> 2. Classes
> 4. Components
> 5. Design Patterns
> 6. Events
> 7. Calling webservices
> 8. Skinning
> ...
>
> Anyone wants to volunteer to help write this document? This would involve
> understanding and writing FlexJS code samples. This would also involve
> understanding AngularJS2.0 as well. Which is a benefit on its own.
>
> Volunteers?
>
> Thanks,
> Om
>