[FlexJS] Express vs Flex 4

[Peter Ent <pe...@adobe.com>]

Hi,

I've created a Flex 4 app that mimics the FlexJS Express example, DataBindingExample. You can look at the code here:
https://paste.apache.org/I6cM

If you compare the MXML section in the Flex 4 example to the FlexJS Express example you will see they are nearly the same - at least in number of MXML elements. The Express package bundles up common beads, such as the data-binding beads, into Express components, making it simpler to write Flex applications.

Note that the FlexJS DataBindingExample has model, view, and controller parts; this Flex 4 comparison is self-contained to a single file.

Regards,
Peter Ent
Adobe Systems/Apache Flex Project

Re: [FlexJS] Express vs Flex 4

[OmPrakash Muppirala <bi...@gmail.com>]

On Thu, Jan 5, 2017 at 3:10 PM, Alex Harui <ah...@adobe.com> wrote:

>
>
> On 1/5/17, 2:35 PM, "Harbs" <ha...@gmail.com> wrote:
>
> >Cool.
> >
> >Suggestion:
> >
> >Instead of using a long prefix for the express components (i.e.
> >express:TextInput), what about using something like jx instead (short for
> >javascript express), so it would be jx:TextInput instead. If that looks
> >to similar to js, maybe “ex”. or just “x” like the “s” prefix for spark.
>
> Actually, at some point any component from Basic that isn't "overridden"
> by an Express version should get mapped into the Express namespace via the
> manifest and "lookupOnly".  We are doing this already for the Flat
> components.
>
> Then all of the prefixes can be "js", but "js" can map to the Express
> namespace.
>
> What do folks think about packing the express version of
> DataBindingExample into one MXML file?
>

After seeing Peter's email, I was thinking about the same thing.  It would
be nice to put up (in a tweet or blog) comparing the Flex4 with FlexJS, so
having the app in one mxml file would be good.

Thanks,
Om


>
> Thoughts?
> -Alex
>
>

Re: [FlexJS] Express vs Flex 4

[Alex Harui <ah...@adobe.com>]

On 1/5/17, 2:35 PM, "Harbs" <ha...@gmail.com> wrote:

>Cool.
>
>Suggestion:
>
>Instead of using a long prefix for the express components (i.e.
>express:TextInput), what about using something like jx instead (short for
>javascript express), so it would be jx:TextInput instead. If that looks
>to similar to js, maybe “ex”. or just “x” like the “s” prefix for spark.

Actually, at some point any component from Basic that isn't "overridden"
by an Express version should get mapped into the Express namespace via the
manifest and "lookupOnly".  We are doing this already for the Flat
components.

Then all of the prefixes can be "js", but "js" can map to the Express
namespace.

What do folks think about packing the express version of
DataBindingExample into one MXML file?

Thoughts?
-Alex

Re: [FlexJS] Express vs Flex 4

[Harbs <ha...@gmail.com>]

Cool.

Suggestion:

Instead of using a long prefix for the express components (i.e. express:TextInput), what about using something like jx instead (short for javascript express), so it would be jx:TextInput instead. If that looks to similar to js, maybe “ex”. or just “x” like the “s” prefix for spark.

On Jan 6, 2017, at 12:02 AM, Peter Ent <pe...@adobe.com> wrote:

> Hi,
> 
> I've created a Flex 4 app that mimics the FlexJS Express example, DataBindingExample. You can look at the code here:
> https://paste.apache.org/I6cM
> 
> If you compare the MXML section in the Flex 4 example to the FlexJS Express example you will see they are nearly the same - at least in number of MXML elements. The Express package bundles up common beads, such as the data-binding beads, into Express components, making it simpler to write Flex applications.
> 
> Note that the FlexJS DataBindingExample has model, view, and controller parts; this Flex 4 comparison is self-contained to a single file.
> 
> Regards,
> Peter Ent
> Adobe Systems/Apache Flex Project
>