[FlexJS] Presenting at the HTML5 Dev Conference

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

Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
been approved by the HTML5DevConf.  I will have the opportunity to talk
about FlexJS from the basics and hopefully show some good demos.

I will start working on my slides (based on Alex's previous presentations)
and send them out for review soon.  If folks have an idea of the things I
should cover, please let me know, I will try to squeeze it in.

The conference is at: Moscone Center, San Francisco on October 20 & 21,
2014.  Here are more details: http://html5devconf.com/

Thanks,
Om

Re: [FlexJS] Presenting at the HTML5 Dev Conference

[Oleg Konovalov <ol...@gmail.com>]

If you included GWT, include Vaadin too (it's better but used more in
Europe than in US).
I used it a few yrs ago and liked it a lot.


But maybe this time my vote would be for Dart  (AFTER FlexJS of course).


On Thu, Sep 11, 2014 at 4:50 PM, Alex Harui <ah...@adobe.com> wrote:

> Good questions.  My thoughts:
>
>
> On 9/11/14 1:03 PM, "Harbs" <ha...@gmail.com> wrote:
>
> >Some additional thoughts: (don¹t know if you can fit this in ‹ and I
> >don¹t have the answers to all these points)
> >
> >FlexJS vs. Dart vs. Haxe. It seems that all three of these have points
> >for strong typing.
> I definitely try to make sure it doesn't sound like we thought of the idea
> of using a higher-level language for generating JS.  I include GWT and TS
> in the list.  I try not to set it up as a competition, but rather, a
> validation that strong-typing is important in building big things.  We can
> all go down to the local lumber yard and hack together a dog house out of
> wood and nails, but folks who build skyscrapers use different tools and
> techniques.  No high-rise buildings are made of wood and nails.
>
> >
> >Is there an advantage of ActionScript over those? (not sure)
> For dog houses, and probably one and two-story houses, there isn't any
> advantage.  But eventually, as your application grows, and the team that
> is building it grows, the requirement most of these other languages have
> of needing all of the code in once place in order to type-check it becomes
> a practical limitation.  Yes, these languages let you promise that some
> external thing will have a particular contract, but the ActionScript VM
> will verify the contract at the point of integration.  The Dart VM might,
> I haven't checked, but the JS runtimes certainly won't.
>
> >Is there an advantage of MXML? (probably yes)
> I think HTML proved the advantages of declarative markup.
>
> >
> >Maybe some thoughts on the MXML approach vs. HTML/CSS approach?
> >advantages and challenges, etc.
> I could certainly see someone creating a way to generate HTML from MXML,
> so I don't see it as an either/or.  We are just starting with MXML because
> we have it, and it is extensible.  I'm still not clear what is happening
> with Web Components and HTML extensibility.  But for sure, we have a
> better chance of working in IE9.
>
> >
> >What about TypeScript? Do we have advantages over that? What?
> IMO, having a markup language gives us advantages over TS.
>
> While it would be awesome if FlexJS became the most popular way to write
> HTML/JS/CSS apps, I will be more than happy just to be popular among
> enterprise or some other smaller market of folks building really big apps.
>  The notion of having markup to basically have a diagram or schematic of
> your components, and better connectors in AS and the VM to ensure those
> components are connected properly, an IDE that understands all of that, a
> debugger that also understands that, and scalability up to really large
> applications whose source code cannot be gathered all in one place, and
> scaleability down to mobile apps so you can share business logic with the
> mobile companion apps should make us attractive to those who are thinking
> ahead.  Once the requirement comes out to put a fifth floor on your wooden
> house, or add an addition to your house built in another country, you will
> find yourself worrying about a lot more things if you aren't using FlexJS.
>
> -Alex
>
>


-- 
Thank you,
Oleg.

Re: [FlexJS] Presenting at the HTML5 Dev Conference

[Oleg Konovalov <ol...@gmail.com>]

If you included GWT, include Vaadin too (it's better but used more in
Europe than in US).
I used it a few yrs ago and liked it a lot.


But maybe this time my vote would be for Dart  (AFTER FlexJS of course).


On Thu, Sep 11, 2014 at 4:50 PM, Alex Harui <ah...@adobe.com> wrote:

> Good questions.  My thoughts:
>
>
> On 9/11/14 1:03 PM, "Harbs" <ha...@gmail.com> wrote:
>
> >Some additional thoughts: (don¹t know if you can fit this in ‹ and I
> >don¹t have the answers to all these points)
> >
> >FlexJS vs. Dart vs. Haxe. It seems that all three of these have points
> >for strong typing.
> I definitely try to make sure it doesn't sound like we thought of the idea
> of using a higher-level language for generating JS.  I include GWT and TS
> in the list.  I try not to set it up as a competition, but rather, a
> validation that strong-typing is important in building big things.  We can
> all go down to the local lumber yard and hack together a dog house out of
> wood and nails, but folks who build skyscrapers use different tools and
> techniques.  No high-rise buildings are made of wood and nails.
>
> >
> >Is there an advantage of ActionScript over those? (not sure)
> For dog houses, and probably one and two-story houses, there isn't any
> advantage.  But eventually, as your application grows, and the team that
> is building it grows, the requirement most of these other languages have
> of needing all of the code in once place in order to type-check it becomes
> a practical limitation.  Yes, these languages let you promise that some
> external thing will have a particular contract, but the ActionScript VM
> will verify the contract at the point of integration.  The Dart VM might,
> I haven't checked, but the JS runtimes certainly won't.
>
> >Is there an advantage of MXML? (probably yes)
> I think HTML proved the advantages of declarative markup.
>
> >
> >Maybe some thoughts on the MXML approach vs. HTML/CSS approach?
> >advantages and challenges, etc.
> I could certainly see someone creating a way to generate HTML from MXML,
> so I don't see it as an either/or.  We are just starting with MXML because
> we have it, and it is extensible.  I'm still not clear what is happening
> with Web Components and HTML extensibility.  But for sure, we have a
> better chance of working in IE9.
>
> >
> >What about TypeScript? Do we have advantages over that? What?
> IMO, having a markup language gives us advantages over TS.
>
> While it would be awesome if FlexJS became the most popular way to write
> HTML/JS/CSS apps, I will be more than happy just to be popular among
> enterprise or some other smaller market of folks building really big apps.
>  The notion of having markup to basically have a diagram or schematic of
> your components, and better connectors in AS and the VM to ensure those
> components are connected properly, an IDE that understands all of that, a
> debugger that also understands that, and scalability up to really large
> applications whose source code cannot be gathered all in one place, and
> scaleability down to mobile apps so you can share business logic with the
> mobile companion apps should make us attractive to those who are thinking
> ahead.  Once the requirement comes out to put a fifth floor on your wooden
> house, or add an addition to your house built in another country, you will
> find yourself worrying about a lot more things if you aren't using FlexJS.
>
> -Alex
>
>


-- 
Thank you,
Oleg.

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Good questions.  My thoughts:


On 9/11/14 1:03 PM, "Harbs" <ha...@gmail.com> wrote:

>Some additional thoughts: (don¹t know if you can fit this in ‹ and I
>don¹t have the answers to all these points)
>
>FlexJS vs. Dart vs. Haxe. It seems that all three of these have points
>for strong typing.
I definitely try to make sure it doesn't sound like we thought of the idea
of using a higher-level language for generating JS.  I include GWT and TS
in the list.  I try not to set it up as a competition, but rather, a
validation that strong-typing is important in building big things.  We can
all go down to the local lumber yard and hack together a dog house out of
wood and nails, but folks who build skyscrapers use different tools and
techniques.  No high-rise buildings are made of wood and nails.

>
>Is there an advantage of ActionScript over those? (not sure)
For dog houses, and probably one and two-story houses, there isn't any
advantage.  But eventually, as your application grows, and the team that
is building it grows, the requirement most of these other languages have
of needing all of the code in once place in order to type-check it becomes
a practical limitation.  Yes, these languages let you promise that some
external thing will have a particular contract, but the ActionScript VM
will verify the contract at the point of integration.  The Dart VM might,
I haven't checked, but the JS runtimes certainly won't.

>Is there an advantage of MXML? (probably yes)
I think HTML proved the advantages of declarative markup.

>
>Maybe some thoughts on the MXML approach vs. HTML/CSS approach?
>advantages and challenges, etc.
I could certainly see someone creating a way to generate HTML from MXML,
so I don't see it as an either/or.  We are just starting with MXML because
we have it, and it is extensible.  I'm still not clear what is happening
with Web Components and HTML extensibility.  But for sure, we have a
better chance of working in IE9.

>
>What about TypeScript? Do we have advantages over that? What?
IMO, having a markup language gives us advantages over TS.

While it would be awesome if FlexJS became the most popular way to write
HTML/JS/CSS apps, I will be more than happy just to be popular among
enterprise or some other smaller market of folks building really big apps.
 The notion of having markup to basically have a diagram or schematic of
your components, and better connectors in AS and the VM to ensure those
components are connected properly, an IDE that understands all of that, a
debugger that also understands that, and scalability up to really large
applications whose source code cannot be gathered all in one place, and
scaleability down to mobile apps so you can share business logic with the
mobile companion apps should make us attractive to those who are thinking
ahead.  Once the requirement comes out to put a fifth floor on your wooden
house, or add an addition to your house built in another country, you will
find yourself worrying about a lot more things if you aren't using FlexJS.

-Alex

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Good questions.  My thoughts:


On 9/11/14 1:03 PM, "Harbs" <ha...@gmail.com> wrote:

>Some additional thoughts: (don¹t know if you can fit this in ‹ and I
>don¹t have the answers to all these points)
>
>FlexJS vs. Dart vs. Haxe. It seems that all three of these have points
>for strong typing.
I definitely try to make sure it doesn't sound like we thought of the idea
of using a higher-level language for generating JS.  I include GWT and TS
in the list.  I try not to set it up as a competition, but rather, a
validation that strong-typing is important in building big things.  We can
all go down to the local lumber yard and hack together a dog house out of
wood and nails, but folks who build skyscrapers use different tools and
techniques.  No high-rise buildings are made of wood and nails.

>
>Is there an advantage of ActionScript over those? (not sure)
For dog houses, and probably one and two-story houses, there isn't any
advantage.  But eventually, as your application grows, and the team that
is building it grows, the requirement most of these other languages have
of needing all of the code in once place in order to type-check it becomes
a practical limitation.  Yes, these languages let you promise that some
external thing will have a particular contract, but the ActionScript VM
will verify the contract at the point of integration.  The Dart VM might,
I haven't checked, but the JS runtimes certainly won't.

>Is there an advantage of MXML? (probably yes)
I think HTML proved the advantages of declarative markup.

>
>Maybe some thoughts on the MXML approach vs. HTML/CSS approach?
>advantages and challenges, etc.
I could certainly see someone creating a way to generate HTML from MXML,
so I don't see it as an either/or.  We are just starting with MXML because
we have it, and it is extensible.  I'm still not clear what is happening
with Web Components and HTML extensibility.  But for sure, we have a
better chance of working in IE9.

>
>What about TypeScript? Do we have advantages over that? What?
IMO, having a markup language gives us advantages over TS.

While it would be awesome if FlexJS became the most popular way to write
HTML/JS/CSS apps, I will be more than happy just to be popular among
enterprise or some other smaller market of folks building really big apps.
 The notion of having markup to basically have a diagram or schematic of
your components, and better connectors in AS and the VM to ensure those
components are connected properly, an IDE that understands all of that, a
debugger that also understands that, and scalability up to really large
applications whose source code cannot be gathered all in one place, and
scaleability down to mobile apps so you can share business logic with the
mobile companion apps should make us attractive to those who are thinking
ahead.  Once the requirement comes out to put a fifth floor on your wooden
house, or add an addition to your house built in another country, you will
find yourself worrying about a lot more things if you aren't using FlexJS.

-Alex

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Some additional thoughts: (don’t know if you can fit this in — and I don’t have the answers to all these points)

FlexJS vs. Dart vs. Haxe. It seems that all three of these have points for strong typing.

Is there an advantage of ActionScript over those? (not sure)
Is there an advantage of MXML? (probably yes)

Maybe some thoughts on the MXML approach vs. HTML/CSS approach? advantages and challenges, etc.

What about TypeScript? Do we have advantages over that? What?

(and good luck!)
Harbs

On Sep 11, 2014, at 9:56 PM, OmPrakash Muppirala <bi...@gmail.com> wrote:

> Thanks Alex!
> 
> It would be great if other Apache Flex folks show up there as well.
> 
> Regarding my slides:
>> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
>> start with IE9.
>> 
> 
> Sounds good to me.
> 
> 
>> -The slides are heavily oriented towards existing Flex users.  I wouldn't
>> expect there to be that many at the conference,
> 
> 
> I am guessing that there would be a substantial number of folks who have
> worked or currently working on Flex applications.
> 
> 
>> so I hope you can
>> emphasize how we think the MXML + AS should provide better developer
>> productivity for new apps.
>> 
> 
> How about adding these points:
> 1.  Advantages of using ActionScript3 to build your applications
> 
>   - Full fledged object oriented inheritance model (not just prototype
>   based)
>   - Statically type code, dynamic optional.  So best of both worlds.
>   - Packages, classes, interfaces
>   - Use standard design patterns easily
>   - Easy to maintain
>   - Friendly for projects with medium to large teams
> 
> 2.  Use MXML to efficiently build your interface
> 
>   - Like HTML, MXML is XML markup language
>   - Declaratively lay out your interface (components, skins, layout,
>   effects, etc.)
>   - Declaratively define nonvisual aspects of the application (data
>   binding, webservices, etc.)
>   - Unlike HTML, you can extend MXML with custom components that you
>   reference as MXML tags
> 
> Anything else you would like to add?
> BTW, where can I get the latest copy of your presentation slides?
> 
> Thanks,
> Om
> 
> On Thu, Sep 4, 2014 at 12:35 PM, Alex Harui <ah...@adobe.com> wrote:
> 
>> Congratulations and good luck!
>> 
>> Regarding my slides:
>> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
>> start with IE9.
>> -The slides are heavily oriented towards existing Flex users.  I wouldn't
>> expect there to be that many at the conference, so I hope you can
>> emphasize how we think the MXML + AS should provide better developer
>> productivity for new apps.
>> 
>> Wish I could be there to cheer you on!
>> 
>> -Alex
>> 
>> On 9/4/14 12:22 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>> 
>>> Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
>>> been approved by the HTML5DevConf.  I will have the opportunity to talk
>>> about FlexJS from the basics and hopefully show some good demos.
>>> 
>>> I will start working on my slides (based on Alex's previous presentations)
>>> and send them out for review soon.  If folks have an idea of the things I
>>> should cover, please let me know, I will try to squeeze it in.
>>> 
>>> The conference is at: Moscone Center, San Francisco on October 20 & 21,
>>> 2014.  Here are more details: http://html5devconf.com/
>>> 
>>> Thanks,
>>> Om
>> 
>> 

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Some additional thoughts: (don’t know if you can fit this in — and I don’t have the answers to all these points)

FlexJS vs. Dart vs. Haxe. It seems that all three of these have points for strong typing.

Is there an advantage of ActionScript over those? (not sure)
Is there an advantage of MXML? (probably yes)

Maybe some thoughts on the MXML approach vs. HTML/CSS approach? advantages and challenges, etc.

What about TypeScript? Do we have advantages over that? What?

(and good luck!)
Harbs

On Sep 11, 2014, at 9:56 PM, OmPrakash Muppirala <bi...@gmail.com> wrote:

> Thanks Alex!
> 
> It would be great if other Apache Flex folks show up there as well.
> 
> Regarding my slides:
>> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
>> start with IE9.
>> 
> 
> Sounds good to me.
> 
> 
>> -The slides are heavily oriented towards existing Flex users.  I wouldn't
>> expect there to be that many at the conference,
> 
> 
> I am guessing that there would be a substantial number of folks who have
> worked or currently working on Flex applications.
> 
> 
>> so I hope you can
>> emphasize how we think the MXML + AS should provide better developer
>> productivity for new apps.
>> 
> 
> How about adding these points:
> 1.  Advantages of using ActionScript3 to build your applications
> 
>   - Full fledged object oriented inheritance model (not just prototype
>   based)
>   - Statically type code, dynamic optional.  So best of both worlds.
>   - Packages, classes, interfaces
>   - Use standard design patterns easily
>   - Easy to maintain
>   - Friendly for projects with medium to large teams
> 
> 2.  Use MXML to efficiently build your interface
> 
>   - Like HTML, MXML is XML markup language
>   - Declaratively lay out your interface (components, skins, layout,
>   effects, etc.)
>   - Declaratively define nonvisual aspects of the application (data
>   binding, webservices, etc.)
>   - Unlike HTML, you can extend MXML with custom components that you
>   reference as MXML tags
> 
> Anything else you would like to add?
> BTW, where can I get the latest copy of your presentation slides?
> 
> Thanks,
> Om
> 
> On Thu, Sep 4, 2014 at 12:35 PM, Alex Harui <ah...@adobe.com> wrote:
> 
>> Congratulations and good luck!
>> 
>> Regarding my slides:
>> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
>> start with IE9.
>> -The slides are heavily oriented towards existing Flex users.  I wouldn't
>> expect there to be that many at the conference, so I hope you can
>> emphasize how we think the MXML + AS should provide better developer
>> productivity for new apps.
>> 
>> Wish I could be there to cheer you on!
>> 
>> -Alex
>> 
>> On 9/4/14 12:22 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>> 
>>> Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
>>> been approved by the HTML5DevConf.  I will have the opportunity to talk
>>> about FlexJS from the basics and hopefully show some good demos.
>>> 
>>> I will start working on my slides (based on Alex's previous presentations)
>>> and send them out for review soon.  If folks have an idea of the things I
>>> should cover, please let me know, I will try to squeeze it in.
>>> 
>>> The conference is at: Moscone Center, San Francisco on October 20 & 21,
>>> 2014.  Here are more details: http://html5devconf.com/
>>> 
>>> Thanks,
>>> Om
>> 
>> 

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

On 9/11/14 11:56 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>-The slides are heavily oriented towards existing Flex users.  I wouldn't
>> expect there to be that many at the conference,
>
>
>I am guessing that there would be a substantial number of folks who have
>worked or currently working on Flex applications.
OK, I could certainly be wrong about the demographics.

>
>
>> so I hope you can
>> emphasize how we think the MXML + AS should provide better developer
>> productivity for new apps.
>>
>
>How about adding these points:
>1.  Advantages of using ActionScript3 to build your applications
>
>   - Full fledged object oriented inheritance model (not just prototype
>   based)
>   - Statically type code, dynamic optional.  So best of both worlds.
>   - Packages, classes, interfaces
>   - Use standard design patterns easily
>   - Easy to maintain
>   - Friendly for projects with medium to large teams
>
>2.  Use MXML to efficiently build your interface
>
>   - Like HTML, MXML is XML markup language
>   - Declaratively lay out your interface (components, skins, layout,
>   effects, etc.)
>   - Declaratively define nonvisual aspects of the application (data
>   binding, webservices, etc.)
>   - Unlike HTML, you can extend MXML with custom components that you
>   reference as MXML tags
>
>Anything else you would like to add?
Looks great!

>BTW, where can I get the latest copy of your presentation slides?
I think this is it:
http://people.apache.org/~aharui/360Flex/FlexJS%20360%7cFlex%202014.pptx

-Alex

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

On 9/11/14 11:56 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>-The slides are heavily oriented towards existing Flex users.  I wouldn't
>> expect there to be that many at the conference,
>
>
>I am guessing that there would be a substantial number of folks who have
>worked or currently working on Flex applications.
OK, I could certainly be wrong about the demographics.

>
>
>> so I hope you can
>> emphasize how we think the MXML + AS should provide better developer
>> productivity for new apps.
>>
>
>How about adding these points:
>1.  Advantages of using ActionScript3 to build your applications
>
>   - Full fledged object oriented inheritance model (not just prototype
>   based)
>   - Statically type code, dynamic optional.  So best of both worlds.
>   - Packages, classes, interfaces
>   - Use standard design patterns easily
>   - Easy to maintain
>   - Friendly for projects with medium to large teams
>
>2.  Use MXML to efficiently build your interface
>
>   - Like HTML, MXML is XML markup language
>   - Declaratively lay out your interface (components, skins, layout,
>   effects, etc.)
>   - Declaratively define nonvisual aspects of the application (data
>   binding, webservices, etc.)
>   - Unlike HTML, you can extend MXML with custom components that you
>   reference as MXML tags
>
>Anything else you would like to add?
Looks great!

>BTW, where can I get the latest copy of your presentation slides?
I think this is it:
http://people.apache.org/~aharui/360Flex/FlexJS%20360%7cFlex%202014.pptx

-Alex

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Thanks Alex!

It would be great if other Apache Flex folks show up there as well.

Regarding my slides:
> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
> start with IE9.
>

Sounds good to me.


> -The slides are heavily oriented towards existing Flex users.  I wouldn't
> expect there to be that many at the conference,


I am guessing that there would be a substantial number of folks who have
worked or currently working on Flex applications.


> so I hope you can
> emphasize how we think the MXML + AS should provide better developer
> productivity for new apps.
>

How about adding these points:
1.  Advantages of using ActionScript3 to build your applications

   - Full fledged object oriented inheritance model (not just prototype
   based)
   - Statically type code, dynamic optional.  So best of both worlds.
   - Packages, classes, interfaces
   - Use standard design patterns easily
   - Easy to maintain
   - Friendly for projects with medium to large teams

2.  Use MXML to efficiently build your interface

   - Like HTML, MXML is XML markup language
   - Declaratively lay out your interface (components, skins, layout,
   effects, etc.)
   - Declaratively define nonvisual aspects of the application (data
   binding, webservices, etc.)
   - Unlike HTML, you can extend MXML with custom components that you
   reference as MXML tags

Anything else you would like to add?
BTW, where can I get the latest copy of your presentation slides?

Thanks,
Om

On Thu, Sep 4, 2014 at 12:35 PM, Alex Harui <ah...@adobe.com> wrote:

> Congratulations and good luck!
>
> Regarding my slides:
> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
> start with IE9.
> -The slides are heavily oriented towards existing Flex users.  I wouldn't
> expect there to be that many at the conference, so I hope you can
> emphasize how we think the MXML + AS should provide better developer
> productivity for new apps.
>
> Wish I could be there to cheer you on!
>
> -Alex
>
> On 9/4/14 12:22 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
> >been approved by the HTML5DevConf.  I will have the opportunity to talk
> >about FlexJS from the basics and hopefully show some good demos.
> >
> >I will start working on my slides (based on Alex's previous presentations)
> >and send them out for review soon.  If folks have an idea of the things I
> >should cover, please let me know, I will try to squeeze it in.
> >
> >The conference is at: Moscone Center, San Francisco on October 20 & 21,
> >2014.  Here are more details: http://html5devconf.com/
> >
> >Thanks,
> >Om
>
>

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Thanks Alex!

It would be great if other Apache Flex folks show up there as well.

Regarding my slides:
> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
> start with IE9.
>

Sounds good to me.


> -The slides are heavily oriented towards existing Flex users.  I wouldn't
> expect there to be that many at the conference,


I am guessing that there would be a substantial number of folks who have
worked or currently working on Flex applications.


> so I hope you can
> emphasize how we think the MXML + AS should provide better developer
> productivity for new apps.
>

How about adding these points:
1.  Advantages of using ActionScript3 to build your applications

   - Full fledged object oriented inheritance model (not just prototype
   based)
   - Statically type code, dynamic optional.  So best of both worlds.
   - Packages, classes, interfaces
   - Use standard design patterns easily
   - Easy to maintain
   - Friendly for projects with medium to large teams

2.  Use MXML to efficiently build your interface

   - Like HTML, MXML is XML markup language
   - Declaratively lay out your interface (components, skins, layout,
   effects, etc.)
   - Declaratively define nonvisual aspects of the application (data
   binding, webservices, etc.)
   - Unlike HTML, you can extend MXML with custom components that you
   reference as MXML tags

Anything else you would like to add?
BTW, where can I get the latest copy of your presentation slides?

Thanks,
Om

On Thu, Sep 4, 2014 at 12:35 PM, Alex Harui <ah...@adobe.com> wrote:

> Congratulations and good luck!
>
> Regarding my slides:
> -I think we're ready to abandon IE8 support for FlexJS.  I think we'll
> start with IE9.
> -The slides are heavily oriented towards existing Flex users.  I wouldn't
> expect there to be that many at the conference, so I hope you can
> emphasize how we think the MXML + AS should provide better developer
> productivity for new apps.
>
> Wish I could be there to cheer you on!
>
> -Alex
>
> On 9/4/14 12:22 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
> >been approved by the HTML5DevConf.  I will have the opportunity to talk
> >about FlexJS from the basics and hopefully show some good demos.
> >
> >I will start working on my slides (based on Alex's previous presentations)
> >and send them out for review soon.  If folks have an idea of the things I
> >should cover, please let me know, I will try to squeeze it in.
> >
> >The conference is at: Moscone Center, San Francisco on October 20 & 21,
> >2014.  Here are more details: http://html5devconf.com/
> >
> >Thanks,
> >Om
>
>

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Congratulations and good luck!

Regarding my slides:
-I think we're ready to abandon IE8 support for FlexJS.  I think we'll
start with IE9.
-The slides are heavily oriented towards existing Flex users.  I wouldn't
expect there to be that many at the conference, so I hope you can
emphasize how we think the MXML + AS should provide better developer
productivity for new apps.

Wish I could be there to cheer you on!

-Alex

On 9/4/14 12:22 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:

>Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
>been approved by the HTML5DevConf.  I will have the opportunity to talk
>about FlexJS from the basics and hopefully show some good demos.
>
>I will start working on my slides (based on Alex's previous presentations)
>and send them out for review soon.  If folks have an idea of the things I
>should cover, please let me know, I will try to squeeze it in.
>
>The conference is at: Moscone Center, San Francisco on October 20 & 21,
>2014.  Here are more details: http://html5devconf.com/
>
>Thanks,
>Om

Re: [FlexJS] Presenting at the HTML5 Dev Conference

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

Congratulations and good luck!

Regarding my slides:
-I think we're ready to abandon IE8 support for FlexJS.  I think we'll
start with IE9.
-The slides are heavily oriented towards existing Flex users.  I wouldn't
expect there to be that many at the conference, so I hope you can
emphasize how we think the MXML + AS should provide better developer
productivity for new apps.

Wish I could be there to cheer you on!

-Alex

On 9/4/14 12:22 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:

>Exciting news!  My proposal to speak about "FlexJS - An Introduction" has
>been approved by the HTML5DevConf.  I will have the opportunity to talk
>about FlexJS from the basics and hopefully show some good demos.
>
>I will start working on my slides (based on Alex's previous presentations)
>and send them out for review soon.  If folks have an idea of the things I
>should cover, please let me know, I will try to squeeze it in.
>
>The conference is at: Moscone Center, San Francisco on October 20 & 21,
>2014.  Here are more details: http://html5devconf.com/
>
>Thanks,
>Om