Re: [FLEXJS] inheritance/interfaces

2013-11-15 Thread Frank Wienberg
As far as I know, instanceof checks do *not* work with interfaces. That's
what is is for. is works for both classes and interfaces.

new B() instanceof A = true
new B() instanceof IA = false (or even compile error?)
new B() is A = true
new B() is IA = true


On Thu, Nov 14, 2013 at 7:18 PM, OmPrakash Muppirala
bigosma...@gmail.comwrote:

 This might be related to [1] as well.

 Thanks,
 Om

 [1] https://issues.apache.org/jira/browse/FLEX-33780


 On Thu, Nov 14, 2013 at 9:39 AM, Erik de Bruin e...@ixsoftware.nl wrote:

  Thanks. On it.
 
  EdB
 
 
 
  On Thu, Nov 14, 2013 at 6:37 PM, Michael A. Labriola
  labri...@digitalprimates.net wrote:
  If class B extends class A and class A implements interface IA, does
  class B also implement IA? In other words, in this scenario, does (B is
 IA)
  return true?
  
   Yep
  
  
 
 
 
  --
  Ix Multimedia Software
 
  Jan Luykenstraat 27
  3521 VB Utrecht
 
  T. 06-51952295
  I. www.ixsoftware.nl
 



Re: [OT} 360|Flex 2014

2013-11-15 Thread Jun Heider

On Nov 14, 2013, at 3:19 PM, Maurice Amsellem maurice.amsel...@systar.com 
wrote:

 Sorry, it was too short.
 I have read your blog and you speak about performance and FB Profiler.
 I thought Adobe Scout introduced a really new way of profiling apps, 
 especially on Mobile, so it might be interesting to speak about it as well.
 
 Maurice 
 
 
 -Message d'origine-
 De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] 
 Envoyé : jeudi 14 novembre 2013 23:17
 À : dev@flex.apache.org; us...@flex.apache.org
 Objet : RE: [OT} 360|Flex 2014
 
 Adobe Scout
 
 -Message d'origine-
 De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 14 novembre 2013 
 22:56 À : dev@flex.apache.org; us...@flex.apache.org Objet : [OT} 360|Flex 
 2014
 
 I'm trying to decide what to present on at 360|Flex in 2014.  I put a blog 
 post up on my blog [1] looking for ideas.  Feel free to comment there or 
 discuss ideas on this thread.
 
 Thanks,
 -Alex
 
 [1]
 http://flexcloset.wordpress.com/2013/11/14/what-should-i-talk-about-360flex
 -2014/
 

+1 to that! Alex, please! :)



Re: [FLEXJS] inheritance/interfaces

2013-11-15 Thread Erik de Bruin
 As far as I know, instanceof checks do *not* work with interfaces. That's
 what is is for. is works for both classes and interfaces.

Correct.

I've updated the 'org.apache.flex.utils.Language.is()' method to take
super class interface implementation into account. I also updated the
example 'LanguageTests' with more checks.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [OT] 360|Flex 2014

2013-11-15 Thread Erik de Bruin
I'm very likely attending, and I'd like a lab about fixing and
debugging the SDK, please :-)

Setting up your workspace, preparing the SDK, creating patches etc.

EdB



On Fri, Nov 15, 2013 at 3:52 AM, Justin Mclean jus...@classsoftware.com wrote:
 Hi,

 Alex already posted about this and ask what do you think he should speak on, 
 but I'll ask a more general question:

 What topics would you like see see talks or labs on at 360 Flex 2014?

 Thanks,
 Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


RE: [OT] 360|Flex 2014

2013-11-15 Thread Mark Line
Personally I'd like to see stuff based around large enterprise development
or mobile (as I think Flex is a great for both)

Performance testing/improvement
Testing Flex Unit etc
Perhaps some news about falcon? 

That said I'm just happy its back :-)

-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com] 
Sent: 15 November 2013 02:53
To: dev@flex.apache.org; us...@flex.apache.org
Subject: [OT] 360|Flex 2014

Hi,

Alex already posted about this and ask what do you think he should speak on,
but I'll ask a more general question:

What topics would you like see see talks or labs on at 360 Flex 2014?

Thanks,
Justin=



Re: Flex 4.9 and FB 4.0

2013-11-15 Thread Tom Chiverton

On 14/11/2013 16:10, Raj U. Shaikh wrote:

I am using Flash Builder 4.0.1
Really ? I don't think Adobe support that any more ? Even with the 
release before Apache Flex was created.


Tom


Re: SDK 4.11 service pack ?

2013-11-15 Thread Tom Chiverton

On 14/11/2013 22:45, Mark Kessler wrote:

supposed to match the build number?
That's what 4.9.1 does if you install it with the installer (files and 
the XML agree).


Tom


Flex at Scotch on the Rocks next year

2013-11-15 Thread Tom Chiverton
I notice that next years Scotch on the Rocks (Scotland, EU :-) ) has 
it's call for speakers open. I know a few Flex users were there last year.

Has anyone submitted a Flex talk idea yet ?

Is anyone other than me here going to be attending ?
--
extravision Signature
*Tom Chiverton* | Lead Developer | Extravision
*T:* 0161 817 2922 | *W:* www.extravision.com 
http://www.extravision.com | *T:* twitter.com/extravision 
http://twitter.com/extravision | *E:* tchiver...@extravision.com 
mailto:tchiver...@extravision.com

.
.
 A fresh approach to email marketing

.
Registered in the UK at : 107 Timber Wharf, 33 Worsley Street, 
Manchester, M15 4LD. Registration number: 05017214 VAT: GB 824 5386 19


Disclaimer: This e-mail is intended solely for the person to whom it is 
addressed and may contain confidential or privileged information. If you 
have received it in error please notify us immediately and destroy this 
e-mail and any attachments. In addition, you must not disclose, copy, 
distribute or take any action in reliance on this e-mail or any 
attachments. Any views or opinions presented in this e-mail are solely 
of the author and do not necessarily represent those of Extravision Ltd. 
E-mail may be susceptible to data corruption, interception, unauthorised 
amendment, viruses and delays or the consequences thereof. Accordingly, 
this e-mail and any attachments are opened at your own risk.




Re: Build failed in Jenkins: flex-sdk_mustella #531

2013-11-15 Thread Alex Harui
I'll take a look this weekend.

On 11/14/13 11:17 PM, Justin Mclean jus...@classsoftware.com wrote:

Hi,

Sorry not had time to look at the issue, was hoping someone else might
help out. I'll revert and reopen the JIRA bug.

https://issues.apache.org/jira/browse/FLEX-33879

Perhaps someone else can look at it?

Thanks,
Justin



Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Erik de Bruin
Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin e...@ixsoftware.nl wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler doesn't
 resolve all dependencies accurately, the classes it misses are never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare for
 some interesting merges. If I find a solution, I'll publish it first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin e...@ixsoftware.nl wrote:
One thought is that we might store both the 'name' and the 'qName' in
the class metadata (where currently only the interfaces - if any -
live) and adopt the 'getValue' routines to search that instead of the
entire namespace chain. This would get rid of the need for the dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it to me.
 I don't think I'll have time in the next few days to work on this, and
 I don't want any details to get lost in the avalanche of emails on the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Flex and AIR 4.0

2013-11-15 Thread Nick Collins
The first Adobe AIR 4.0 beta was just published to Adobe Labs today (
http://labs.adobe.com/technologies/flashruntimes/air/ ). One aspect of it
that I believe may directly affect us is that as of 4.0, ASC 2.0 will be
retired as a separate download, and will now be the only compiler. How will
this affect us being able to overlay AIR with the Flex SDK going forward?

Nick


Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Erik de Bruin
Is there a particular reason there is a 'className' property which is
set on some, but not all classes and even has 'getter/setter' methods?

Unless the property is seriously misnamed, why would you want to be
able to SET a class' name? If anything is constant, it should be the
name of the class, shouldn't it?

It looks like a legacy thing. Would it be alright to remove it? The
information is now available in the metadata.

EdB



On Fri, Nov 15, 2013 at 6:12 PM, Alex Harui aha...@adobe.com wrote:
 Awesome!  Definitely looked like a lot of work.  Thanks for doing it.

 -Alex

 On 11/15/13 8:24 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler doesn't
 resolve all dependencies accurately, the classes it misses are never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare for
 some interesting merges. If I find a solution, I'll publish it first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
One thought is that we might store both the 'name' and the 'qName' in
the class metadata (where currently only the interfaces - if any -
live) and adopt the 'getValue' routines to search that instead of the
entire namespace chain. This would get rid of the need for the
dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it to me.
 I don't think I'll have time in the next few days to work on this, and
 I don't want any details to get lost in the avalanche of emails on the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [OT] 360|Flex 2014

2013-11-15 Thread Jun Heider

On Nov 15, 2013, at 2:17 AM, Mark Line markl...@gmail.com wrote:

 What topics would you like see see talks or labs on at 360 Flex 2014?

Figured I'd mention some tips, for those of you that are interested in this 
discussion or are thinking of going.

1. So far 6 Apache Flex team members are confirmed to speak about our beloved 
Flex:

- Harui
- Heider
- Houser
- Labriola
- Mclean
- Muppirala

2. If you register now as faithful the tickets are dirt cheap @ $350: 
http://www.360flex.com/

3. This year attendees are limited to 200 people. So I suggest registering 
sooner rather than later.

Hope to see you all at Apache Flex party 2014! :)

Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Alex Harui
Looks like it should be ok to replace with getQualifiedClassName().

-Alex

On 11/15/13 9:56 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Is there a particular reason there is a 'className' property which is
set on some, but not all classes and even has 'getter/setter' methods?

Unless the property is seriously misnamed, why would you want to be
able to SET a class' name? If anything is constant, it should be the
name of the class, shouldn't it?

It looks like a legacy thing. Would it be alright to remove it? The
information is now available in the metadata.

EdB



On Fri, Nov 15, 2013 at 6:12 PM, Alex Harui aha...@adobe.com wrote:
 Awesome!  Definitely looked like a lot of work.  Thanks for doing it.

 -Alex

 On 11/15/13 8:24 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl
wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it
still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler doesn't
 resolve all dependencies accurately, the classes it misses are never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare for
 some interesting merges. If I find a solution, I'll publish it first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
One thought is that we might store both the 'name' and the 'qName'
in
the class metadata (where currently only the interfaces - if any -
live) and adopt the 'getValue' routines to search that instead of
the
entire namespace chain. This would get rid of the need for the
dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it to
me.
 I don't think I'll have time in the next few days to work on this,
and
 I don't want any details to get lost in the avalanche of emails on
the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl



Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Erik de Bruin
Or, since that has gone the way of the dodo, I can just feed it
'this.FLEXJS_CLASS_INFO.names[0].name' ;-)

EdB



On Fri, Nov 15, 2013 at 7:12 PM, Alex Harui aha...@adobe.com wrote:
 Looks like it should be ok to replace with getQualifiedClassName().

 -Alex

 On 11/15/13 9:56 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Is there a particular reason there is a 'className' property which is
set on some, but not all classes and even has 'getter/setter' methods?

Unless the property is seriously misnamed, why would you want to be
able to SET a class' name? If anything is constant, it should be the
name of the class, shouldn't it?

It looks like a legacy thing. Would it be alright to remove it? The
information is now available in the metadata.

EdB



On Fri, Nov 15, 2013 at 6:12 PM, Alex Harui aha...@adobe.com wrote:
 Awesome!  Definitely looked like a lot of work.  Thanks for doing it.

 -Alex

 On 11/15/13 8:24 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl
wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it
still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler doesn't
 resolve all dependencies accurately, the classes it misses are never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare for
 some interesting merges. If I find a solution, I'll publish it first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
One thought is that we might store both the 'name' and the 'qName'
in
the class metadata (where currently only the interfaces - if any -
live) and adopt the 'getValue' routines to search that instead of
the
entire namespace chain. This would get rid of the need for the
dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it to
me.
 I don't think I'll have time in the next few days to work on this,
and
 I don't want any details to get lost in the avalanche of emails on
the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Alex Harui
Hopefully, although I grep'd and think I saw two places where there was
some cheating going on.

-Alex

On 11/15/13 10:27 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Or, since that has gone the way of the dodo, I can just feed it
'this.FLEXJS_CLASS_INFO.names[0].name' ;-)

EdB



On Fri, Nov 15, 2013 at 7:12 PM, Alex Harui aha...@adobe.com wrote:
 Looks like it should be ok to replace with getQualifiedClassName().

 -Alex

 On 11/15/13 9:56 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Is there a particular reason there is a 'className' property which is
set on some, but not all classes and even has 'getter/setter' methods?

Unless the property is seriously misnamed, why would you want to be
able to SET a class' name? If anything is constant, it should be the
name of the class, shouldn't it?

It looks like a legacy thing. Would it be alright to remove it? The
information is now available in the metadata.

EdB



On Fri, Nov 15, 2013 at 6:12 PM, Alex Harui aha...@adobe.com wrote:
 Awesome!  Definitely looked like a lot of work.  Thanks for doing it.

 -Alex

 On 11/15/13 8:24 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl
wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode
are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it
still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler doesn't
 resolve all dependencies accurately, the classes it misses are
never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare for
 some interesting merges. If I find a solution, I'll publish it
first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
One thought is that we might store both the 'name' and the
'qName'
in
the class metadata (where currently only the interfaces - if any
-
live) and adopt the 'getValue' routines to search that instead of
the
entire namespace chain. This would get rid of the need for the
dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it to
me.
 I don't think I'll have time in the next few days to work on this,
and
 I don't want any details to get lost in the avalanche of emails on
the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl



Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Erik de Bruin
popup.className = 'popup' and this.titleLabel.element.className =
'TitleBarLabel'?

EdB



On Fri, Nov 15, 2013 at 7:33 PM, Alex Harui aha...@adobe.com wrote:
 Hopefully, although I grep'd and think I saw two places where there was
 some cheating going on.

 -Alex

 On 11/15/13 10:27 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Or, since that has gone the way of the dodo, I can just feed it
'this.FLEXJS_CLASS_INFO.names[0].name' ;-)

EdB



On Fri, Nov 15, 2013 at 7:12 PM, Alex Harui aha...@adobe.com wrote:
 Looks like it should be ok to replace with getQualifiedClassName().

 -Alex

 On 11/15/13 9:56 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Is there a particular reason there is a 'className' property which is
set on some, but not all classes and even has 'getter/setter' methods?

Unless the property is seriously misnamed, why would you want to be
able to SET a class' name? If anything is constant, it should be the
name of the class, shouldn't it?

It looks like a legacy thing. Would it be alright to remove it? The
information is now available in the metadata.

EdB



On Fri, Nov 15, 2013 at 6:12 PM, Alex Harui aha...@adobe.com wrote:
 Awesome!  Definitely looked like a lot of work.  Thanks for doing it.

 -Alex

 On 11/15/13 8:24 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl
wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode
are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it
still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler doesn't
 resolve all dependencies accurately, the classes it misses are
never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare for
 some interesting merges. If I find a solution, I'll publish it
first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin e...@ixsoftware.nl
wrote:
One thought is that we might store both the 'name' and the
'qName'
in
the class metadata (where currently only the interfaces - if any
-
live) and adopt the 'getValue' routines to search that instead of
the
entire namespace chain. This would get rid of the need for the
dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it to
me.
 I don't think I'll have time in the next few days to work on this,
and
 I don't want any details to get lost in the avalanche of emails on
the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [OT] 360|Flex 2014

2013-11-15 Thread Angelo Lazzari
Hi all guys!

It's really excitig see that 360flex is still up  running! 

I know that organize an event of that size is time, money and resources 
expensive and you have a lot to manage, organize and so on, but, i would ask 
just one thing: how about an european 360|flex event? 

I mean i don't know how big is the european flex comunity but i think it could 
be a great occasion to increase it or at least trying to stay closer to the 
european people!

Madrid, Geneve, London, Romedon't know...but would be great!

It's just an idea, thanks guys!
Angelo

Sent from my 

 El Nov 15, 2013, a las 19:03, Jun Heider j...@realeyes.com escribió:
 
 
 On Nov 15, 2013, at 2:17 AM, Mark Line markl...@gmail.com wrote:
 
 What topics would you like see see talks or labs on at 360 Flex 2014?
 
 Figured I'd mention some tips, for those of you that are interested in this 
 discussion or are thinking of going.
 
 1. So far 6 Apache Flex team members are confirmed to speak about our beloved 
 Flex:
 
 - Harui
 - Heider
 - Houser
 - Labriola
 - Mclean
 - Muppirala
 
 2. If you register now as faithful the tickets are dirt cheap @ $350: 
 http://www.360flex.com/
 
 3. This year attendees are limited to 200 people. So I suggest registering 
 sooner rather than later.
 
 Hope to see you all at Apache Flex party 2014! :)


Re: [FLEXJS] CSS value handling can't work in release code

2013-11-15 Thread Alex Harui
Actually, it was these two:
as/src/org/apache/flex/html/staticControls/TitleBar.as: 
_titleLabel.class
Name = className;
as/src/org/apache/flex/html/staticControls/TitleBar.as: 
_closeButton.clas
sName = className;

But popup might be an issue as well.


But you reminded me that on the JS side, element.className is ok.  It
is used to assign a class selector of options to an HTMLElement.

-Alex

On 11/15/13 10:46 AM, Erik de Bruin e...@ixsoftware.nl wrote:

popup.className = 'popup' and this.titleLabel.element.className =
'TitleBarLabel'?

EdB



On Fri, Nov 15, 2013 at 7:33 PM, Alex Harui aha...@adobe.com wrote:
 Hopefully, although I grep'd and think I saw two places where there was
 some cheating going on.

 -Alex

 On 11/15/13 10:27 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Or, since that has gone the way of the dodo, I can just feed it
'this.FLEXJS_CLASS_INFO.names[0].name' ;-)

EdB



On Fri, Nov 15, 2013 at 7:12 PM, Alex Harui aha...@adobe.com wrote:
 Looks like it should be ok to replace with getQualifiedClassName().

 -Alex

 On 11/15/13 9:56 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Is there a particular reason there is a 'className' property which is
set on some, but not all classes and even has 'getter/setter' methods?

Unless the property is seriously misnamed, why would you want to be
able to SET a class' name? If anything is constant, it should be the
name of the class, shouldn't it?

It looks like a legacy thing. Would it be alright to remove it? The
information is now available in the metadata.

EdB



On Fri, Nov 15, 2013 at 6:12 PM, Alex Harui aha...@adobe.com wrote:
 Awesome!  Definitely looked like a lot of work.  Thanks for doing
it.

 -Alex

 On 11/15/13 8:24 AM, Erik de Bruin e...@ixsoftware.nl wrote:

Big update: fixed!

If you really want to know what needed to happen to make this work,
please read the commit messages. It wasn't a simple fix.

Note: the metadata property is now required on each class in the
framework. I've added it to all the classes in the FlexJS framework
that are under active development. Please read the source for
examples, and I've added a small section to the wiki for reference:

https://cwiki.apache.org/confluence/x/W5sTAg

This was fun, but has taken way too much time, so I'll have to catch
up on my regular work in the coming week(s) ;-)

EdB



On Fri, Nov 15, 2013 at 8:55 AM, Erik de Bruin e...@ixsoftware.nl
wrote:
 Ah, small update: a lot of the warnings remaining in 'strict' mode
are
 for the classes the compiler misses... That at least combines the
 issues, two birds with one stone and all ;-)

 EdB



 On Thu, Nov 14, 2013 at 10:25 PM, Erik de Bruin
e...@ixsoftware.nl
wrote:
 This may be worse than we thought...

 When I fixed the storage and retrieval of the CSS properties, it
still
 didn't work properly in release mode. Some classes are found and
 bound, others are not. Turns out that the Closure Compiler
doesn't
 resolve all dependencies accurately, the classes it misses are
never
 'considered' during compilation :-(

 I will look into the custom dependency algorithm in the Publisher
 next. Wish me luck ;-)

 Also, the fix will literally affect all JS classes, so prepare
for
 some interesting merges. If I find a solution, I'll publish it
first
 in a branch, so we can look at it together before we commit.

 EdB



 On Wed, Nov 13, 2013 at 8:12 PM, Erik de Bruin
e...@ixsoftware.nl
wrote:
One thought is that we might store both the 'name' and the
'qName'
in
the class metadata (where currently only the interfaces - if
any
-
live) and adopt the 'getValue' routines to search that instead
of
the
entire namespace chain. This would get rid of the need for the
dreaded
'__proto__'  as well...
 Sounds good.  We need to find the superclass somehow as well.

 Alex, can you please create a JIRA issue for this and assign it
to
me.
 I don't think I'll have time in the next few days to work on
this,
and
 I don't want any details to get lost in the avalanche of emails
on
the
 list.

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl



Re: [OT] 360|Flex 2014

2013-11-15 Thread OmPrakash Muppirala
On Fri, Nov 15, 2013 at 12:58 AM, Erik de Bruin e...@ixsoftware.nl wrote:

 I'm very likely attending, and I'd like a lab about fixing and
 debugging the SDK, please :-)

 Setting up your workspace, preparing the SDK, creating patches etc.


+1 to this idea.

Thanks,
Om



 EdB



 On Fri, Nov 15, 2013 at 3:52 AM, Justin Mclean jus...@classsoftware.com
 wrote:
  Hi,
 
  Alex already posted about this and ask what do you think he should speak
 on, but I'll ask a more general question:
 
  What topics would you like see see talks or labs on at 360 Flex 2014?
 
  Thanks,
  Justin



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. www.ixsoftware.nl



Re: Flex at Scotch on the Rocks next year

2013-11-15 Thread Justin Mclean
Hi,

I'll be there.

Go ahead and submit a Flex session but it may not be accepted.  I was on the 
content advisory board last year and help organised the schedule but there was 
no Flex content in the schedule.

Now Apache Flex has a few releases that may change.

Thanks,
Justin

Apache Flex 4.10/4.11 stats

2013-11-15 Thread Justin Mclean
Hi,

Now that 4.11 is out the installs of 4.10 are slowing (to about 10/day). 4.11 
is currently getting 100-150/installs a day

In less than 3 months we've had more than 10,000 installs of Apache Flex 4.10. 
In the 3 weeks since it has been released 4.11 has had over 3000 installs.

Not bad for a project run by volunteers in their spare time :-)

Thanks,
Justin

Re: Apache Flex 4.10/4.11 stats

2013-11-15 Thread OmPrakash Muppirala
On Fri, Nov 15, 2013 at 3:32 PM, Justin Mclean jus...@classsoftware.comwrote:

 Hi,

 Now that 4.11 is out the installs of 4.10 are slowing (to about 10/day).
 4.11 is currently getting 100-150/installs a day

 In less than 3 months we've had more than 10,000 installs of Apache Flex
 4.10. In the 3 weeks since it has been released 4.11 has had over 3000
 installs.

 Not bad for a project run by volunteers in their spare time :-)

 Thanks,
 Justin



Agreed!  I am constantly (pleasantly) surprised with the download
statistics.  Any chance we can compare it with other open source software
out there?

Thanks,
Om


Re: Apache Flex 4.10/4.11 stats

2013-11-15 Thread Mark Kessler
Oh good I'm not the only person geeking about stats.


-Mark


On Fri, Nov 15, 2013 at 6:35 PM, OmPrakash Muppirala
bigosma...@gmail.comwrote:

 On Fri, Nov 15, 2013 at 3:32 PM, Justin Mclean jus...@classsoftware.com
 wrote:

  Hi,
 
  Now that 4.11 is out the installs of 4.10 are slowing (to about 10/day).
  4.11 is currently getting 100-150/installs a day
 
  In less than 3 months we've had more than 10,000 installs of Apache Flex
  4.10. In the 3 weeks since it has been released 4.11 has had over 3000
  installs.
 
  Not bad for a project run by volunteers in their spare time :-)
 
  Thanks,
  Justin



 Agreed!  I am constantly (pleasantly) surprised with the download
 statistics.  Any chance we can compare it with other open source software
 out there?

 Thanks,
 Om



Re: Apache Flex 4.10/4.11 stats

2013-11-15 Thread Justin Mclean
Hi,

We're in the same ball park as Ralio.

http://www.getrailo.org/index.cfm/download/statistics/

They count downloads not installs, and our installer underreports the actually 
number of installs as it's not the only way to install it.

Thanks,
Justin

Re: Apache Flex 4.10/4.11 stats

2013-11-15 Thread Justin Mclean
Hi,

And there some interesting stats about Apache Flex here:
http://www.ohloh.net/p/ApacheFlex

Thanks,
Justin


Re: Apache Flex 4.10/4.11 stats

2013-11-15 Thread Deepak MS
Great stats :)
But I'm also quite curious to know what was the download\installation rate
when flex was with Adobe. So that could compare the numbers now and then. I
did try searching for it, but couldn't get it anywhere.


On Sat, Nov 16, 2013 at 5:28 AM, Justin Mclean jus...@classsoftware.comwrote:

 Hi,

 And there some interesting stats about Apache Flex here:
 http://www.ohloh.net/p/ApacheFlex

 Thanks,
 Justin



Re: Apache Flex 4.10/4.11 stats

2013-11-15 Thread OmPrakash Muppirala
On Nov 15, 2013 7:42 PM, Deepak MS megharajdee...@gmail.com wrote:

 Great stats :)
 But I'm also quite curious to know what was the download\installation rate
 when flex was with Adobe. So that could compare the numbers now and then.
I
 did try searching for it, but couldn't get it anywhere.

I doubt if those stats would ever be revealed :-)

Om



 On Sat, Nov 16, 2013 at 5:28 AM, Justin Mclean jus...@classsoftware.com
wrote:

  Hi,
 
  And there some interesting stats about Apache Flex here:
  http://www.ohloh.net/p/ApacheFlex
 
  Thanks,
  Justin