Re: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[Alex Harui]

Actually I just saw one thing:  It says "TECHNOLOGY, MOBILE".  Can we get
more categories (Web, Desktop)?

Thanks,
-Alex

On 2/8/16, 8:45 PM, "Alex Harui"  wrote:

>Om,
>
>Looks ok. Thanks for choosing a registration service.
>
>-Alex
>
>On 2/8/16, 6:20 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
> wrote:
>
>>Okay, looks like folks are able to register and/or follow the event.  I
>>am
>>going to go ahead and add more details before starting to publicize it
>>more
>>widely.  Please give me feedback on the page
>>https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area at
>>any time and I will make the appropriate changes.
>>
>>Thanks,
>>Om
>>
>>On Mon, Feb 8, 2016 at 11:24 AM, OmPrakash Muppirala
>>
>>wrote:
>>
>>> I quickly created an event here:
>>> https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area
>>>
>>> Can a couple of folks try to register (using LinkedIn, Twitter or
>>> Facebook) and let's tweak it as needed.
>>>
>>> Once we figure out registration details, I will go in add more details.
>>> Then we can start publicizing the event.
>>>
>>> Thanks,
>>> Om
>>>
>>> On Mon, Feb 8, 2016 at 11:07 AM, OmPrakash Muppirala
> > wrote:
>>>
 If no one has objections, I will set up a Conferize event where folks
can
 sign up.

 Thanks,
 Om

 On Mon, Feb 8, 2016 at 10:42 AM, Alex Harui  wrote:

> It's on!  The conference room is booked and I've got my plane
>tickets.
> Even if you already said you will attend, please reply again to
>confirm.
>
> The event will be held in the ATS Training Room at Adobe's San
>Francisco
> office located at 601 Townsend St.
>
> The current agenda is:
>  9:30am Doors Open
> 10:00am Introduction to FlexJS - Alex Harui
> 11:00am Writing JavaScript in ActionScript - Omprakash Muppirala
> 12:00pm - 5:00pm (or later) Hackathon/Hands-on Training/Open
>Discussion
>
> There will be lunch as part of the afternoon session.  Impromptu
> presentations on other aspects of FlexJS may be put together and
> presented
> in the afternoon as discussion topics arise.
>
> At the end of the morning sessions, you will have seen how FlexJS
>works
> and how you can use MXML and ActionScript to write applications that
>run
> in browser and as desktop and mobile apps with or without the
>Flash/AIR
> runtime.  And you will have an understanding of how ActionScript is
>being
> used to write JavaScript with greater developer productivity.  Did
>you
> know:  there are no longer any .js files in the FlexJS code base.
>All
> JavaScript we need is written in ActionScript and cross-compiled.  No
> more
> forgetting to type 'this.' or mis-typing a property name and finding
>out
> at run-time.
>
> At the end of the afternoon session, you will have installed the
>FlexJS
> SDK and written (at least) a simple application and, if interested,
>set
> up
> the FlexJS development environment so you can contribute to the
>future of
> Flex.
>
> Hope to see you there.
> -Alex
>
> PS:  If this event proves to be successful, we might stage other
>events
> in
> other regions during the year.  Seattle is certainly a possibility.
>
>

>>>
>

Re: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[Alex Harui]

Om,

Looks ok. Thanks for choosing a registration service.

-Alex

On 2/8/16, 6:20 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>Okay, looks like folks are able to register and/or follow the event.  I am
>going to go ahead and add more details before starting to publicize it
>more
>widely.  Please give me feedback on the page
>https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area at
>any time and I will make the appropriate changes.
>
>Thanks,
>Om
>
>On Mon, Feb 8, 2016 at 11:24 AM, OmPrakash Muppirala
>
>wrote:
>
>> I quickly created an event here:
>> https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area
>>
>> Can a couple of folks try to register (using LinkedIn, Twitter or
>> Facebook) and let's tweak it as needed.
>>
>> Once we figure out registration details, I will go in add more details.
>> Then we can start publicizing the event.
>>
>> Thanks,
>> Om
>>
>> On Mon, Feb 8, 2016 at 11:07 AM, OmPrakash Muppirala
>>> > wrote:
>>
>>> If no one has objections, I will set up a Conferize event where folks
>>>can
>>> sign up.
>>>
>>> Thanks,
>>> Om
>>>
>>> On Mon, Feb 8, 2016 at 10:42 AM, Alex Harui  wrote:
>>>
 It's on!  The conference room is booked and I've got my plane tickets.
 Even if you already said you will attend, please reply again to
confirm.

 The event will be held in the ATS Training Room at Adobe's San
Francisco
 office located at 601 Townsend St.

 The current agenda is:
  9:30am Doors Open
 10:00am Introduction to FlexJS - Alex Harui
 11:00am Writing JavaScript in ActionScript - Omprakash Muppirala
 12:00pm - 5:00pm (or later) Hackathon/Hands-on Training/Open
Discussion

 There will be lunch as part of the afternoon session.  Impromptu
 presentations on other aspects of FlexJS may be put together and
 presented
 in the afternoon as discussion topics arise.

 At the end of the morning sessions, you will have seen how FlexJS
works
 and how you can use MXML and ActionScript to write applications that
run
 in browser and as desktop and mobile apps with or without the
Flash/AIR
 runtime.  And you will have an understanding of how ActionScript is
being
 used to write JavaScript with greater developer productivity.  Did you
 know:  there are no longer any .js files in the FlexJS code base.  All
 JavaScript we need is written in ActionScript and cross-compiled.  No
 more
 forgetting to type 'this.' or mis-typing a property name and finding
out
 at run-time.

 At the end of the afternoon session, you will have installed the
FlexJS
 SDK and written (at least) a simple application and, if interested,
set
 up
 the FlexJS development environment so you can contribute to the
future of
 Flex.

 Hope to see you there.
 -Alex

 PS:  If this event proves to be successful, we might stage other
events
 in
 other regions during the year.  Seattle is certainly a possibility.


>>>
>>

Re: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[OmPrakash Muppirala]

Okay, looks like folks are able to register and/or follow the event.  I am
going to go ahead and add more details before starting to publicize it more
widely.  Please give me feedback on the page
https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area at
any time and I will make the appropriate changes.

Thanks,
Om

On Mon, Feb 8, 2016 at 11:24 AM, OmPrakash Muppirala 
wrote:

> I quickly created an event here:
> https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area
>
> Can a couple of folks try to register (using LinkedIn, Twitter or
> Facebook) and let's tweak it as needed.
>
> Once we figure out registration details, I will go in add more details.
> Then we can start publicizing the event.
>
> Thanks,
> Om
>
> On Mon, Feb 8, 2016 at 11:07 AM, OmPrakash Muppirala  > wrote:
>
>> If no one has objections, I will set up a Conferize event where folks can
>> sign up.
>>
>> Thanks,
>> Om
>>
>> On Mon, Feb 8, 2016 at 10:42 AM, Alex Harui  wrote:
>>
>>> It's on!  The conference room is booked and I've got my plane tickets.
>>> Even if you already said you will attend, please reply again to confirm.
>>>
>>> The event will be held in the ATS Training Room at Adobe's San Francisco
>>> office located at 601 Townsend St.
>>>
>>> The current agenda is:
>>>  9:30am Doors Open
>>> 10:00am Introduction to FlexJS - Alex Harui
>>> 11:00am Writing JavaScript in ActionScript - Omprakash Muppirala
>>> 12:00pm - 5:00pm (or later) Hackathon/Hands-on Training/Open Discussion
>>>
>>> There will be lunch as part of the afternoon session.  Impromptu
>>> presentations on other aspects of FlexJS may be put together and
>>> presented
>>> in the afternoon as discussion topics arise.
>>>
>>> At the end of the morning sessions, you will have seen how FlexJS works
>>> and how you can use MXML and ActionScript to write applications that run
>>> in browser and as desktop and mobile apps with or without the Flash/AIR
>>> runtime.  And you will have an understanding of how ActionScript is being
>>> used to write JavaScript with greater developer productivity.  Did you
>>> know:  there are no longer any .js files in the FlexJS code base.  All
>>> JavaScript we need is written in ActionScript and cross-compiled.  No
>>> more
>>> forgetting to type 'this.' or mis-typing a property name and finding out
>>> at run-time.
>>>
>>> At the end of the afternoon session, you will have installed the FlexJS
>>> SDK and written (at least) a simple application and, if interested, set
>>> up
>>> the FlexJS development environment so you can contribute to the future of
>>> Flex.
>>>
>>> Hope to see you there.
>>> -Alex
>>>
>>> PS:  If this event proves to be successful, we might stage other events
>>> in
>>> other regions during the year.  Seattle is certainly a possibility.
>>>
>>>
>>
>

Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Alex Harui]

OK, I looked at what is coded up so far on the compiler side and looked at
the spec some more.  We've taken the approach so far of making up public
method names that have a pretty close mapping to the internal methods.  It
seems to me that we should not try to obfuscate the method names.  So what
if there is a setChild() or filter() method on our JS version of XML.

One notable difference in the mapping is that the compiler has already
parsed the @ prefix for attributes into its own token, so it makes it
easier to call setAttribute() vs setChild() so the internal implementation
doesn't have to bother to determine what is being "put".

Here's what I came up with:

[[get]] maps to attribute() and child() methods.  I think we need to
handle someXML[x] where x is a numeric property name (0, 1, 2, 3, etc).
We could see if we know the key is an integer and output elements()[x].

[[put]] maps to setAttribute() and setChild() methods.  The setAttribute()
and setChild() implementations should call [[deepCopy]] on the value.  I
don't think the compiler should call [[deepCopy]].

[[delete]] maps to removeChild().

[[deleteByIndex]] maps to removeChildAt() methods.  The implementation
probably needs to throw the TypeError if removeChildAt() is called on an
XML object.  For now, I think you'll get an NPE if there isn't a
removeChildAt() on XML.

[[defaultValue]] This is not currently implemented in the compiler.  We
should probably take this on when we get around to handling other
ActionScript automatic type conversions.

[[hasProperty]] This is not currently implemented in the compiler.

[[deepCopy]] I think the compiler doesn't need to do anything here and the
implementation will handle it.

[[descendants]] The compiler is mapping ".." to descendants() calls.

[[equals]] The compiler will have to look for "==" and call and equals()
method.

[[resolveValue]] I'm not quite sure what to do here.

[[insert]] I think the compiler doesn't need to do anything here and the
implementation will handle it.

[[replace]] I think the compiler doesn't need to do anything here and the
implementation will handle it.

[[addInScopeNamespaces]] I think the compiler doesn't need to do anything
here and the implementation will handle it.

[[append]] maps to concat()


Another area of work is handling things like:

-typeof

-instanceof

These are already caught and converted to calls to
org.apache.flex.utils.Language.  I think the Language implementation will
have to become smart about XML.

Thoughts?
-Alex


On 2/8/16, 8:30 AM, "Alex Harui"  wrote:

>
>
>On 2/8/16, 1:00 AM, "Harbs"  wrote:
>>However the spec does not specify bracket notation internally, so that’s
>>not very clear. It could just be I’m not very experienced at reading
>>specification documentation… ;-)
>
>I'm not good at reading specs, probably because I find it boring.  This
>spec [1] seems to describe some not-so-common notation like the double
>brackets in section 9.1.1.
>
>[1] 
>http://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/Ecm
>a
>-357.pdf
>
>
>>
>>I have implemented some of the internal methods/properties, but not all.
>>I’m not sure it makes sense to implement them all.
>
>Implementing the internal methods/properties does not seem to be required
>by the spec.  But which ones are you thinking of skipping?
>
>>
>>It could be it makes sense to modify things a bit, but right now my
>>priority is to get all this working. Apparently, some feel that the ECMA
>>spec has some problems with it which might have been patched[1], but I’m
>>not sure exactly which.
>
>There could certainly be bugs everywhere: in the spec, in the Flash
>implementation, in the Mozilla implementation which apparently isn't
>available anymore.
>
>>
>>Right now, I’m pretty close to having all the methods in place (after
>>quite a few rewrites). The only thing I have not even started on is
>>filtering. I have no actually tried to compile any of this, so that will
>>be a whole task in itself. (BTW, you can see what I currently have done
>>in the e4x branch.)
>
>I have not looked closely at what you committed, but I'm quite excited
>that you are making any sort of progress on this.
>
>>
>>So here’s my current plan:
>>1. Finish up the methods (minus filtering) in the next day or two.
>>2. Sync up XML with the current FlexJS folder structure and get rid of
>>some junk (like all the JXON classes).
>>3. Get this all to compile.
>>4. Figure out the whole filtering issue.
>>5. Create test cases.
>>
>>Once this is done (or mostly done), it probably makes sense to get a
>>sanity check and decide whether to rewrite some of what I’ve done.
>>
>>Makes sense?
>
>Sounds reasonable.  I spent more time skimming the spec this morning.  I
>think there are a lot more cases that the compiler doesn't handle.  You
>and I may need to coordinate on when to work on those things, not that I'm
>looking forward to having to do all that work.  The key to success looks
>like it will be how the compiler can or 

Re: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[Alex Harui]

On 2/8/16, 1:28 PM, "Petr Nemecek"  wrote:

>Good agenda, would love to go, but too far for me. I hope you could make
>one of next stops somewhere in Europe.

If there is an ApacheCon in Europe this fall, I think I will be able to go
and also have one or more of these Flex events on the same trip.

>
>Any chance to record whole day and publish it?

I'll think about a way to do that.  We might try an Adobe Connect hookup,
but not sure how the audio will work.

-Alex

RE: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[Petr Nemecek]

Good agenda, would love to go, but too far for me. I hope you could make one of 
next stops somewhere in Europe.

Any chance to record whole day and publish it?

Cheers,
 Petr

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: Monday, February 08, 2016 7:42 PM
To: dev@flex.apache.org
Subject: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

It's on!  The conference room is booked and I've got my plane tickets.
Even if you already said you will attend, please reply again to confirm.

The event will be held in the ATS Training Room at Adobe's San Francisco office 
located at 601 Townsend St.

The current agenda is:
 9:30am Doors Open
10:00am Introduction to FlexJS - Alex Harui 11:00am Writing JavaScript in 
ActionScript - Omprakash Muppirala 12:00pm - 5:00pm (or later) 
Hackathon/Hands-on Training/Open Discussion

There will be lunch as part of the afternoon session.  Impromptu presentations 
on other aspects of FlexJS may be put together and presented in the afternoon 
as discussion topics arise.

At the end of the morning sessions, you will have seen how FlexJS works and how 
you can use MXML and ActionScript to write applications that run in browser and 
as desktop and mobile apps with or without the Flash/AIR runtime.  And you will 
have an understanding of how ActionScript is being used to write JavaScript 
with greater developer productivity.  Did you
know:  there are no longer any .js files in the FlexJS code base.  All 
JavaScript we need is written in ActionScript and cross-compiled.  No more 
forgetting to type 'this.' or mis-typing a property name and finding out at 
run-time.

At the end of the afternoon session, you will have installed the FlexJS SDK and 
written (at least) a simple application and, if interested, set up the FlexJS 
development environment so you can contribute to the future of Flex.

Hope to see you there.
-Alex

PS:  If this event proves to be successful, we might stage other events in 
other regions during the year.  Seattle is certainly a possibility.

Re: AW: [ApacheCon NA] Whose going and what topics?

[Alex Harui]

I submitted my "FlexJS:  Apache's Structured Language, Cross-platform
Solution for Clients" session.

-Alex

On 2/8/16, 1:19 PM, "Christofer Dutz"  wrote:

>Ok ... so I just submitted two talks:
>
>- Building FlexJS applications with Maven
>- Controlling Cyborgs with Apache Flex
>
>Don't forgett to post yours :-)
>
>Chris
>
>
>-Ursprüngliche Nachricht-
>Von: Christofer Dutz [mailto:christofer.d...@c-ware.de]
>Gesendet: Freitag, 5. Februar 2016 00:34
>An: dev@flex.apache.org
>Betreff: AW: [ApacheCon NA] Whose going and what topics?
>
>Well I currently lay a lot of emphasis on the Ecmascript 4 factor.
>Current JavaScript being EcmaScript 3.0 or 3.1 (which was renamed to 5.0
>but has no real changes in it). Sort of "Write Ecmascript 4 without
>breaking the internet" cause this was the major reason for not going down
>the 4.0 road and that's exactly what we are doing now ... writing
>Ecmascript 4 code having it cross compiled to 3.1 alias 5.0. I think its
>worth mentioning this.
>
>Chris
>
>
>Von: Alex Harui 
>Gesendet: Donnerstag, 4. Februar 2016 19:24
>An: dev@flex.apache.org
>Betreff: Re: [ApacheCon NA] Whose going and what topics?
>
>On 2/4/16, 1:47 AM, "Justin Mclean"  wrote:
>>
>>The organiser it more likely to pick talks that are topical, dare I say
>>fashionable, and will attract an audience so it does matter somewhat.
>>They I believe make the final selection.
>
>What buzz words do we think are topical or fashionable?  Or maybe
>controversial?
>
>I'm thinking of changing the title of my talk to include "cross-platform".
> So maybe:
>"FlexJS:  Apache's Structured Language, Cross-platform Solution for
>Clients"
>
>
>Thoughts?
>-Alex
>

Re: [FlexJS] a little bit promotion for flexJS?

[Alex Harui]

Hi Marcus,

Good thinking here.  I was unable to quickly figure out how to get listed as a 
web application framework.  It looks like there is another list called "Front 
End JavaScript Frameworks" as well.  Interestingly, the "Web Application 
Framework" mentioned "server-side".  Anybody know how to get us listed?

-Alex

From: Marcus Fritze 
mailto:marcus.fri...@googlemail.com>>
Reply-To: "dev@flex.apache.org" 
mailto:dev@flex.apache.org>>
Date: Monday, February 8, 2016 at 12:53 PM
To: "dev@flex.apache.org" 
mailto:dev@flex.apache.org>>
Subject: [FlexJS] a little bit promotion for flexJS?

Hi,

last weekend I found the list „web application frameworks" on github [1]

I was wondering why FlexSDK or FlexJS is not on this list. Isn’t Flex a "web 
application framework"?

It seems that list is generated automatically by the star-ratings of every 
project hosted in github in that category.  FlexSDK [2] has 258 stars and the 
FlexJS [3] has 27. Is the acceptance really so low and a niche product compared 
to the first one - Meteor - on that list?

It seems that Meteor is the new way to go for a lot of developers who are 
starting a new project in 2016….

If Flex (SDK and JS) would be on that list, maybe more people - who are maybe 
not familiar with Flex - could use and maybe improve Flex. As I said in my 
subject, a little bit promotion for flexJS.

I don’t know the current user statistics of the flex homepage or the flex 
installer. Does it makes sense to add a github star button on the flex homepage 
or the installer? So everybody who likes Flex and visits the site or runs the 
installer, can give a star. So the more stars Flex has, the more popular will 
it get (according to that list). And I think more users will also result in 
more active contributors.

Ok, the current contributors per star quote is really really good. 37% for 
flexJS and 13% for flexSDK. For Meteor it’s 0,82%.

Best regards

Marcus

[1] https://github.com/showcases/web-application-frameworks
[2] https://github.com/apache/flex-sdk
[3] https://github.com/apache/flex-asjs

AW: [ApacheCon NA] Whose going and what topics?

[Christofer Dutz]

Ok ... so I just submitted two talks:

- Building FlexJS applications with Maven
- Controlling Cyborgs with Apache Flex

Don't forgett to post yours :-)

Chris


-Ursprüngliche Nachricht-
Von: Christofer Dutz [mailto:christofer.d...@c-ware.de] 
Gesendet: Freitag, 5. Februar 2016 00:34
An: dev@flex.apache.org
Betreff: AW: [ApacheCon NA] Whose going and what topics?

Well I currently lay a lot of emphasis on the Ecmascript 4 factor. Current 
JavaScript being EcmaScript 3.0 or 3.1 (which was renamed to 5.0 but has no 
real changes in it). Sort of "Write Ecmascript 4 without breaking the internet" 
cause this was the major reason for not going down the 4.0 road and that's 
exactly what we are doing now ... writing Ecmascript 4 code having it cross 
compiled to 3.1 alias 5.0. I think its worth mentioning this.

Chris


Von: Alex Harui 
Gesendet: Donnerstag, 4. Februar 2016 19:24
An: dev@flex.apache.org
Betreff: Re: [ApacheCon NA] Whose going and what topics?

On 2/4/16, 1:47 AM, "Justin Mclean"  wrote:
>
>The organiser it more likely to pick talks that are topical, dare I say 
>fashionable, and will attract an audience so it does matter somewhat.
>They I believe make the final selection.

What buzz words do we think are topical or fashionable?  Or maybe controversial?

I'm thinking of changing the title of my talk to include "cross-platform".
 So maybe:
"FlexJS:  Apache's Structured Language, Cross-platform Solution for Clients"


Thoughts?
-Alex

[FlexJS] a little bit promotion for flexJS?

[Marcus Fritze]

Hi,

last weekend I found the list „web application frameworks" on github [1]

I was wondering why FlexSDK or FlexJS is not on this list. Isn’t Flex a "web 
application framework"?

It seems that list is generated automatically by the star-ratings of every 
project hosted in github in that category.  FlexSDK [2] has 258 stars and the 
FlexJS [3] has 27. Is the acceptance really so low and a niche product compared 
to the first one - Meteor - on that list?

It seems that Meteor is the new way to go for a lot of developers who are 
starting a new project in 2016….

If Flex (SDK and JS) would be on that list, maybe more people - who are maybe 
not familiar with Flex - could use and maybe improve Flex. As I said in my 
subject, a little bit promotion for flexJS.

I don’t know the current user statistics of the flex homepage or the flex 
installer. Does it makes sense to add a github star button on the flex homepage 
or the installer? So everybody who likes Flex and visits the site or runs the 
installer, can give a star. So the more stars Flex has, the more popular will 
it get (according to that list). And I think more users will also result in 
more active contributors.

Ok, the current contributors per star quote is really really good. 37% for 
flexJS and 13% for flexSDK. For Meteor it’s 0,82%.

Best regards

Marcus

[1] https://github.com/showcases/web-application-frameworks 

[2] https://github.com/apache/flex-sdk 
[3] https://github.com/apache/flex-asjs 




signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[OmPrakash Muppirala]

I quickly created an event here:
https://www.conferize.com/conferences/flexjs-world-tour---sf-bay-area

Can a couple of folks try to register (using LinkedIn, Twitter or Facebook)
and let's tweak it as needed.

Once we figure out registration details, I will go in add more details.
Then we can start publicizing the event.

Thanks,
Om

On Mon, Feb 8, 2016 at 11:07 AM, OmPrakash Muppirala 
wrote:

> If no one has objections, I will set up a Conferize event where folks can
> sign up.
>
> Thanks,
> Om
>
> On Mon, Feb 8, 2016 at 10:42 AM, Alex Harui  wrote:
>
>> It's on!  The conference room is booked and I've got my plane tickets.
>> Even if you already said you will attend, please reply again to confirm.
>>
>> The event will be held in the ATS Training Room at Adobe's San Francisco
>> office located at 601 Townsend St.
>>
>> The current agenda is:
>>  9:30am Doors Open
>> 10:00am Introduction to FlexJS - Alex Harui
>> 11:00am Writing JavaScript in ActionScript - Omprakash Muppirala
>> 12:00pm - 5:00pm (or later) Hackathon/Hands-on Training/Open Discussion
>>
>> There will be lunch as part of the afternoon session.  Impromptu
>> presentations on other aspects of FlexJS may be put together and presented
>> in the afternoon as discussion topics arise.
>>
>> At the end of the morning sessions, you will have seen how FlexJS works
>> and how you can use MXML and ActionScript to write applications that run
>> in browser and as desktop and mobile apps with or without the Flash/AIR
>> runtime.  And you will have an understanding of how ActionScript is being
>> used to write JavaScript with greater developer productivity.  Did you
>> know:  there are no longer any .js files in the FlexJS code base.  All
>> JavaScript we need is written in ActionScript and cross-compiled.  No more
>> forgetting to type 'this.' or mis-typing a property name and finding out
>> at run-time.
>>
>> At the end of the afternoon session, you will have installed the FlexJS
>> SDK and written (at least) a simple application and, if interested, set up
>> the FlexJS development environment so you can contribute to the future of
>> Flex.
>>
>> Hope to see you there.
>> -Alex
>>
>> PS:  If this event proves to be successful, we might stage other events in
>> other regions during the year.  Seattle is certainly a possibility.
>>
>>
>

Re: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[OmPrakash Muppirala]

If no one has objections, I will set up a Conferize event where folks can
sign up.

Thanks,
Om

On Mon, Feb 8, 2016 at 10:42 AM, Alex Harui  wrote:

> It's on!  The conference room is booked and I've got my plane tickets.
> Even if you already said you will attend, please reply again to confirm.
>
> The event will be held in the ATS Training Room at Adobe's San Francisco
> office located at 601 Townsend St.
>
> The current agenda is:
>  9:30am Doors Open
> 10:00am Introduction to FlexJS - Alex Harui
> 11:00am Writing JavaScript in ActionScript - Omprakash Muppirala
> 12:00pm - 5:00pm (or later) Hackathon/Hands-on Training/Open Discussion
>
> There will be lunch as part of the afternoon session.  Impromptu
> presentations on other aspects of FlexJS may be put together and presented
> in the afternoon as discussion topics arise.
>
> At the end of the morning sessions, you will have seen how FlexJS works
> and how you can use MXML and ActionScript to write applications that run
> in browser and as desktop and mobile apps with or without the Flash/AIR
> runtime.  And you will have an understanding of how ActionScript is being
> used to write JavaScript with greater developer productivity.  Did you
> know:  there are no longer any .js files in the FlexJS code base.  All
> JavaScript we need is written in ActionScript and cross-compiled.  No more
> forgetting to type 'this.' or mis-typing a property name and finding out
> at run-time.
>
> At the end of the afternoon session, you will have installed the FlexJS
> SDK and written (at least) a simple application and, if interested, set up
> the FlexJS development environment so you can contribute to the future of
> Flex.
>
> Hope to see you there.
> -Alex
>
> PS:  If this event proves to be successful, we might stage other events in
> other regions during the year.  Seattle is certainly a possibility.
>
>

RE: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[Jason Taylor]

where do we register?

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: Monday, February 08, 2016 10:42 AM
To: dev@flex.apache.org
Subject: [FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

It's on!  The conference room is booked and I've got my plane tickets.
Even if you already said you will attend, please reply again to confirm.

The event will be held in the ATS Training Room at Adobe's San Francisco office 
located at 601 Townsend St.

The current agenda is:
 9:30am Doors Open
10:00am Introduction to FlexJS - Alex Harui 11:00am Writing JavaScript in 
ActionScript - Omprakash Muppirala 12:00pm - 5:00pm (or later) 
Hackathon/Hands-on Training/Open Discussion

There will be lunch as part of the afternoon session.  Impromptu presentations 
on other aspects of FlexJS may be put together and presented in the afternoon 
as discussion topics arise.

At the end of the morning sessions, you will have seen how FlexJS works and how 
you can use MXML and ActionScript to write applications that run in browser and 
as desktop and mobile apps with or without the Flash/AIR runtime.  And you will 
have an understanding of how ActionScript is being used to write JavaScript 
with greater developer productivity.  Did you
know:  there are no longer any .js files in the FlexJS code base.  All 
JavaScript we need is written in ActionScript and cross-compiled.  No more 
forgetting to type 'this.' or mis-typing a property name and finding out at 
run-time.

At the end of the afternoon session, you will have installed the FlexJS SDK and 
written (at least) a simple application and, if interested, set up the FlexJS 
development environment so you can contribute to the future of Flex.

Hope to see you there.
-Alex

PS:  If this event proves to be successful, we might stage other events in 
other regions during the year.  Seattle is certainly a possibility.

[FLEXJS] FlexJS Event: Monday April 4, 2016 in San Francisco

[Alex Harui]

It's on!  The conference room is booked and I've got my plane tickets.
Even if you already said you will attend, please reply again to confirm.

The event will be held in the ATS Training Room at Adobe's San Francisco
office located at 601 Townsend St.

The current agenda is:
 9:30am Doors Open
10:00am Introduction to FlexJS - Alex Harui
11:00am Writing JavaScript in ActionScript - Omprakash Muppirala
12:00pm - 5:00pm (or later) Hackathon/Hands-on Training/Open Discussion

There will be lunch as part of the afternoon session.  Impromptu
presentations on other aspects of FlexJS may be put together and presented
in the afternoon as discussion topics arise.

At the end of the morning sessions, you will have seen how FlexJS works
and how you can use MXML and ActionScript to write applications that run
in browser and as desktop and mobile apps with or without the Flash/AIR
runtime.  And you will have an understanding of how ActionScript is being
used to write JavaScript with greater developer productivity.  Did you
know:  there are no longer any .js files in the FlexJS code base.  All
JavaScript we need is written in ActionScript and cross-compiled.  No more
forgetting to type 'this.' or mis-typing a property name and finding out
at run-time.

At the end of the afternoon session, you will have installed the FlexJS
SDK and written (at least) a simple application and, if interested, set up
the FlexJS development environment so you can contribute to the future of
Flex.

Hope to see you there.
-Alex

PS:  If this event proves to be successful, we might stage other events in
other regions during the year.  Seattle is certainly a possibility.

Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Alex Harui]

On 2/8/16, 1:00 AM, "Harbs"  wrote:
>However the spec does not specify bracket notation internally, so that’s
>not very clear. It could just be I’m not very experienced at reading
>specification documentation… ;-)

I'm not good at reading specs, probably because I find it boring.  This
spec [1] seems to describe some not-so-common notation like the double
brackets in section 9.1.1.

[1] 
http://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/Ecma
-357.pdf


>
>I have implemented some of the internal methods/properties, but not all.
>I’m not sure it makes sense to implement them all.

Implementing the internal methods/properties does not seem to be required
by the spec.  But which ones are you thinking of skipping?

>
>It could be it makes sense to modify things a bit, but right now my
>priority is to get all this working. Apparently, some feel that the ECMA
>spec has some problems with it which might have been patched[1], but I’m
>not sure exactly which.

There could certainly be bugs everywhere: in the spec, in the Flash
implementation, in the Mozilla implementation which apparently isn't
available anymore.

>
>Right now, I’m pretty close to having all the methods in place (after
>quite a few rewrites). The only thing I have not even started on is
>filtering. I have no actually tried to compile any of this, so that will
>be a whole task in itself. (BTW, you can see what I currently have done
>in the e4x branch.)

I have not looked closely at what you committed, but I'm quite excited
that you are making any sort of progress on this.

>
>So here’s my current plan:
>1. Finish up the methods (minus filtering) in the next day or two.
>2. Sync up XML with the current FlexJS folder structure and get rid of
>some junk (like all the JXON classes).
>3. Get this all to compile.
>4. Figure out the whole filtering issue.
>5. Create test cases.
>
>Once this is done (or mostly done), it probably makes sense to get a
>sanity check and decide whether to rewrite some of what I’ve done.
>
>Makes sense?

Sounds reasonable.  I spent more time skimming the spec this morning.  I
think there are a lot more cases that the compiler doesn't handle.  You
and I may need to coordinate on when to work on those things, not that I'm
looking forward to having to do all that work.  The key to success looks
like it will be how the compiler can or can't know the resolved type of
something.  The spec is about how to change the runtime, but we can't
change the runtime and need to detect when an object is XML and generate
different code.  I have some concerns about whether that will start to
affect compiler performance, but I guess we'll just have to see, or maybe
I'll put XML checking in some conditional so you can opt in.

The link you posted didn't seem to point to any particular bug in E4X, but
it was an interesting discussion in how the JS runtimes don't want to take
on the complexity of E4X.  It would be interesting if there is a
functional subset of E4X that we could implement that would draw in the
E4X folks, especially the Node folks that appear to be stuck with handling
XML documents for legacy support reasons.

>
>[1]https://bugs.chromium.org/p/v8/issues/detail?id=235#c75

-Alex

[GitHub] flex-sdk pull request: Update build.xml

[blackjyn]

GitHub user blackjyn opened a pull request:

https://github.com/apache/flex-sdk/pull/42

Update build.xml

change "asdoc" to "bundles" for :
  







since there is no "asdoc" folder inside the respective dirs.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/blackjyn/flex-sdk patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flex-sdk/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit 387a3a89660c896ee8646c9c23586c32f06de6bf
Author: ZVHR El Ekhsaan 
Date:   2016-02-08T14:08:47Z

Update build.xml

change "asdoc" to "bundles" for :
  







since there is no "asdoc" folder inside the respective dirs




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

RE: unsubscribe

[Kessler CTR Mark J]

You can unsubscribe by sending an email to [1] and there are other mailing list 
options at [2].  The commits mailing list is a bit rough if you're not 
expecting that volume of emails.

[1] commits-unsubscr...@flex.apache.org
[2] http://flex.apache.org/community-mailinglists.html

-Mark

-Original Message-
From: Sumudu Chinthaka [mailto:csum...@gmail.com]
Sent: Sunday, February 07, 2016 8:33 PM
To: comm...@flex.apache.org
Subject: unsubscribe

Re: [FALCONJX][FLEXJS] XML handling (was Re: [FlexJS] Back port)

[Harbs]

Yes.

The internal methods are definitely different than the public APIs. For 
example, there is both a [[Replace]] internal method as well as a replace() 
API. The two do very different things. I also just realized that there is both 
[[InScopeNamespaces]] and inScopeNamespaces().

You are right that I was confused by [[Length]] which does refer to the length 
of the internal list of properties and not the length(). However the spec does 
not specify bracket notation internally, so that’s not very clear. It could 
just be I’m not very experienced at reading specification documentation… ;-)

I have implemented some of the internal methods/properties, but not all. I’m 
not sure it makes sense to implement them all.

It could be it makes sense to modify things a bit, but right now my priority is 
to get all this working. Apparently, some feel that the ECMA spec has some 
problems with it which might have been patched[1], but I’m not sure exactly 
which.

Right now, I’m pretty close to having all the methods in place (after quite a 
few rewrites). The only thing I have not even started on is filtering. I have 
no actually tried to compile any of this, so that will be a whole task in 
itself. (BTW, you can see what I currently have done in the e4x branch.)

So here’s my current plan:
1. Finish up the methods (minus filtering) in the next day or two.
2. Sync up XML with the current FlexJS folder structure and get rid of some 
junk (like all the JXON classes).
3. Get this all to compile.
4. Figure out the whole filtering issue.
5. Create test cases.

Once this is done (or mostly done), it probably makes sense to get a sanity 
check and decide whether to rewrite some of what I’ve done.

Makes sense?

[1]https://bugs.chromium.org/p/v8/issues/detail?id=235#c75

On Feb 8, 2016, at 7:09 AM, Alex Harui  wrote:

> Harbs,
> 
> Is it possible you are being tricked by the difference between the XML
> length() method and the Object length property?  The following outputs 1
> for me:
> 
> var xml:XML = ;
>   trace(xml.length());
> 
> 
> AFAICT, the spec is recommending an internal implementation that is not
> quite a 1:1 mapping to the public API.  It suggests keeping an ordered
> list of child nodes based upon how the Insert function got called so that
> if there is a "get" with a numeric property name, there is a specific
> behavior (conversion to XMLList and subsequent access of the correct
> child).  It does not seem to specify that there are properties like [0],
> [1], [2] on the XML object itself.  Rather, the get function is called
> with a numeric property name.
> 
> I really hadn't looked at the spec in any great detail until tonight, but
> it made me wonder if FalconJX should be outputting calls to insert,
> replace, put, get, etc.  We would add some sort of prefix and/or suffix to
> the internal methods so they don't really appear in the public API.
> 
> Thoughts?
> -Alex
> 
> On 2/7/16, 9:38 AM, "Harbs"  wrote:
> 
>> Yeah. Except an XML object always has a length of 0… AFAIK, xmlObj[1]
>> always returns undefined. The only valid index on an XML object is 0
>> which returns the XML object (to blur the distinction between XMLList and
>> XML). I think xmlList[0] is the same as xmlList[0][0][0][0]...
>> 
>> I think I’m just going to ignore this part of the spec because I’m
>> storing everything in a _children array and dealing with that.
>> 
>> On Feb 7, 2016, at 6:59 PM, Andy Dufilie  wrote:
>> 
>>> The insert code looks fine to me, assuming children of XML are stored as
>>> properties "0", "1", "2", ...
>>> It's shifting all children with index >= i and saving P starting at
>>> child
>>> index i.
>>> 
>>> [[Put]] is overwriting a child at a given index, and
>>> insertChildBefore/insertChildAfter/prependChild should be doing the same
>>> type of operation as insert.
>> 
>