Re: [FlexJS] IFlexInfo

2013-10-02 Thread OmPrakash Muppirala
On Wed, Oct 2, 2013 at 7:52 PM, Alex Harui wrote: > > > On 10/2/13 4:55 PM, "OmPrakash Muppirala" wrote: > > > >I am still trying to get the jQuery_Sample app to run. I added > >'implements > >IFlexInfo' to the jquery application class. > >at > >org.apache.flex.core::SimpleCSSValuesImpl/get

RE: Please welcome Tom Chiverton as our newest committer

2013-10-02 Thread Maurice Amsellem
Congratulations Tom. Maurice Amsellem SYSTAR R&D - BusinessBridgeFX -Message d'origine- De : aYo ~ [mailto:a...@binitie.com] Envoyé : jeudi 3 octobre 2013 07:08 À : dev@flex.apache.org Objet : Re: Please welcome Tom Chiverton as our newest committer Congratulations Tom and welcome aYo

Re: IntelliJ IDE installation instructions

2013-10-02 Thread OmPrakash Muppirala
On Wed, Oct 2, 2013 at 11:27 PM, Alexander Doroshko < alexander.doros...@jetbrains.com> wrote: > On 04.09.2013 21:31, Alexander Doroshko wrote: > >> I remember my promise to publish a blog post promoting Apache Flex SDK at >> JetBrains site. I confirm that I'll do it but a bit later. >> > > And he

Re: IntelliJ IDE installation instructions

2013-10-02 Thread Alexander Doroshko
On 04.09.2013 21:31, Alexander Doroshko wrote: I remember my promise to publish a blog post promoting Apache Flex SDK at JetBrains site. I confirm that I'll do it but a bit later. And here it is: http://blog.jetbrains.com/idea/2013/10/how-is-flex-doing-quick-start-guides-and-tutorials/

Re: Please welcome Tom Chiverton as our newest committer

2013-10-02 Thread aYo ~
Congratulations Tom and welcome aYo www.ayobinitie.com mrbinitie.blogspot.com On 3 Oct 2013 03:54, "Justin Mclean" wrote: > Hi, > > I am pleased to announce that the Project Management Committee (PMC) for > Apache Flex has invited Tom Chiverton to become a committer and he has > accepted. > > To

Please welcome Tom Chiverton as our newest committer

2013-10-02 Thread Justin Mclean
Hi, I am pleased to announce that the Project Management Committee (PMC) for Apache Flex has invited Tom Chiverton to become a committer and he has accepted. Tom has been active on the mailing lists over a long time and has helped out on numerous occasions on the user and dev lists and with the

Re: [FlexJS] IFlexInfo

2013-10-02 Thread Alex Harui
On 10/2/13 4:55 PM, "OmPrakash Muppirala" wrote: > >I am still trying to get the jQuery_Sample app to run. I added >'implements >IFlexInfo' to the jquery application class. >at >org.apache.flex.core::SimpleCSSValuesImpl/getValue()[C:\p\flex_os\workspac >e\flexroot\git\flex-asjs\frameworks\a

Re: [FlexJS] IFlexInfo

2013-10-02 Thread OmPrakash Muppirala
On Thu, Sep 26, 2013 at 6:17 AM, Alex Harui wrote: > > > On 9/25/13 11:57 PM, "OmPrakash Muppirala" wrote: > > >On Wed, Sep 25, 2013 at 8:41 PM, Alex Harui wrote: > > > >> Turns out there is a bug in the Falcon code that the search for > >>IFlexInfo > >> only is in the baseclass and not deeper.

Re: [FALCON] using coerce_a

2013-10-02 Thread Darrell Loverin
Yes, very strange. The AVM2 spec says the jump instruction does not change the stack either (as you would expect). On Wed, Oct 2, 2013 at 6:23 PM, Alex Harui wrote: > When I look at the output, the sequence of ABC instructions generated by > MXMLC should be: > > Constructprop > Coerce_a > Jump

Re: [FALCON] using coerce_a

2013-10-02 Thread Alex Harui
When I look at the output, the sequence of ABC instructions generated by MXMLC should be: Constructprop Coerce_a Jump SetProperty And for Falcon ConstructProp Jump Coerce_a SetProperty In x86 asm, a jump only moves the IP and doesn't change anything else. But for some reason, AIR (and not Flash

Re: Spark DateFieldSpinner

2013-10-02 Thread Sebastian Mohr
Hi again ... In the latest version of the Spark DateFieldSpinner [1] I have improved the locale related switching & I added a customised DateRangeValidator [2] extending DateValidator that validates if the user sets his data within the correct range. Hope this helps. [1] https://dl.dropboxusercont

Re: [FALCON] using coerce_a

2013-10-02 Thread Darrell Loverin
Nice job figuring this out! Does your change now generate the coerce_a code in the same positions as the MXML compiler? The only difference I saw in byte code with respect to coerce_a was a "jump L1" instruction after (Falcon) a coerce_a instead before (mxmlc). mxmlc > constructprop pri

Re: [FALCON] using coerce_a

2013-10-02 Thread Alex Harui
The reducer method now calls getAncestorOfType(IBinaryOperatorNode.class) and then checks if the operator is OoperatorType.ASSIGNMENT and further that the left node is a DynamicAccessNodel I think just checking parent isn't good enough for nested ternary expressions. Coerce is being called in a f

RE: [FALCON] using coerce_a

2013-10-02 Thread Gordon Smith
In the reducer method for the ternary expression, how do you know whether it going to be assigned to a foo[bar] expression? Do you look at the parent node of the ternary expression? I have a feeling that that isn't how JBurg is supposed to be used, but maybe you can get away with it. You should

Re: AW: AW: FlexMojos 6, Flex sdk 4.10.0.20130801, and getAdvancedTelemetry()

2013-10-02 Thread mscharp
I never got the warnings to go away, however testing hasn't shown any issues thus far. I'm operating under the idea that those warnings aren't important, just annoying (like many other warnings). I could switch over to the version of FM that I built against 4.10, but I feel more comfortable build

Re: [FALCON] using coerce_a

2013-10-02 Thread Alex Harui
The code only thinks about coercing if there is a bracket [] node. It gets the type of the left hand side via resolveType and compares the resolveType of the clause node and calls coerce if it doesn't match. So your example won't have a coerce_a in the ABC. -Alex On 10/2/13 11:19 AM, "Gordon Sm

Re: [FALCON] using coerce_a

2013-10-02 Thread Gordon Smith
Does that work for ternary expressions and left-hand-sides with other types, such as var i:int = true ? 1 : 2; ? - Gordon On 10/2/13 11:01 AM, "Alex Harui" wrote: >Update: Changing Falcon to generate the coerce_a in the ternary clauses >allowed it to work for AIR. The code change is only in

Re: [FALCON] using coerce_a

2013-10-02 Thread Alex Harui
Update: Changing Falcon to generate the coerce_a in the ternary clauses allowed it to work for AIR. The code change is only in ternary expression reduction so I think it won't hurt performance too much. -Alex On 10/1/13 10:09 PM, "Alex Harui" wrote: >So, I added code to add the coerce_a and i

Re: Spark DateFieldSpinner

2013-10-02 Thread Sebastian Mohr
Thanks Justin ... just gave it a try :) -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Wed, Oct 2, 2013 at 10:39 AM, Justin Mclean wrote: > Hi, > > > Maybe, I can use t

Re: [DISCUSS] Apache Flex Bylaws

2013-10-02 Thread Justin Mclean
Hi, > I'm not satisfied with the way the voting document [1] reads vs what folks > say is the "default". There seem to be a lot of assumed knowledge that doesn't match with the documentation. > I'm planning to push to get [1] updated so we and all other projects > and podlings don't have to go t

Re: Spark DateFieldSpinner

2013-10-02 Thread Justin Mclean
Hi, > Maybe, I can use the EGit plugin for Eclipse to commit my next changes. > But, for now, I use the GitHub.app. I found source tree[1] to be easier to use than the github app or the eclipse plugins. I don't have a design background. Thanks, Justin 1. http://www.sourcetreeapp.com

Re: Spark DateFieldSpinner

2013-10-02 Thread Sebastian Mohr
Thanks Om and Alex, @Om > Do you want to add this as a new component to the mobile library or to the default web/desktop library? Not only ... I would preferably also use this component outside of mobile projects. But, since there is a separation between mobile components and "normal" components,

Re: [DISCUSS] Apache Flex Bylaws

2013-10-02 Thread Tom Chiverton
On 01/10/2013 00:19, Justin Mclean wrote: 1. Voting procedure for committers a) lazy-majority (more +1s than -1s) I don't think this requires absolutely everyone to agree, if it doesn't work out it's easy enough to change. 2. Voting procedure for PMC members d) 2/3 majority (3 +1's and twice an