Re: AW: AW: Updated Mavenizer

[piotr.zarzycki]

Just checked and everything is ok. :)
Thank you Christofer.



-
Flex/Air developer open to new job offers and challenges.
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Updated-Mavenizer-tp31841p31905.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: Updated Mavenizer

[christofer.d...@c-ware.de]

I'm just using Aether for deploying mavenized FDKs so it has nothing to do with 
the actual execution of FM. So there shouldn't be a Problem.

Chris


Von: Frédéric THOMAS [webdoubl...@hotmail.com]
Gesendet: Dienstag, 5. November 2013 00:38
An: dev@flex.apache.org
Betreff: RE: Updated Mavenizer

Thanks Chris, sounds good, I don't have the time at the moment to look at
the code because of my work and I'm between Paris and London but will check
it as soon as I can, just a question, are you aware there is an issue with
FM and Aether running FM with maven 3.1.1 ? Should I raise an issue
somewhere ?

-Fred

-Message d'origine-
De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de]
Envoyé : dimanche 3 novembre 2013 16:00
À : dev@flex.apache.org
Objet : Updated Mavenizer

Hi,

today I committed some changes to the Mavenizer Tool.

Change 1 made sure all SDKs (Flex and Air) are processed in the right order
regarding the versions of the SDKs.

Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to
deploy the Mavenized files as it uses Aether directly to deploy files
directly inside the VM, causing a dramatic speedup of the time needed to
deploy stuff as well as being able to execute without the reliance on an
already installed Maven system. This should make it easy to add the new
Deployer to any sort of installer.

Chris

Re: [FALCON/JX] guava dependencies in compiler AND closure

[Erik de Bruin]

I've updated the Falcon build scripts. A fresh build ('ant wipe-all
main') from the root now cleanly builds all the 'example' projects -
where 'cleanly' means no weird exceptions from the compiler code
itself ;-)

EdB



On Tue, Nov 5, 2013 at 6:10 AM, Alex Harui  wrote:
> Thanks Gordon!
>
> On 11/4/13 4:59 PM, "Gordon Smith"  wrote:
>
>>OK, the 'develop' branch of flex-falcon now has a compiler/lib/guava.jar
>>that is the current release, 15.0. All the tests run by Falcon's 'ant
>>main' still pass.
>>
>>- Gordon
>>
>>-Original Message-
>>From: Erik de Bruin [mailto:e...@ixsoftware.nl]
>>Sent: Sunday, November 03, 2013 9:00 PM
>>To: dev@flex.apache.org
>>Subject: Re: [FALCON/JX] guava dependencies in compiler AND closure
>>
>>Thank you, Gordon. Yes, I think it's best to go to the latest version and
>>keep updating.
>>
>>EdB
>>
>>
>>
>>On Monday, November 4, 2013, Gordon Smith wrote:
>>
>>> I can take a look at upgrading the version of Guava that Falcon uses.
>>> Do you want it to use the latest version, 15.0?
>>>
>>> - Gordon
>>>
>>> Sent from my iPad
>>>
>>> On Nov 1, 2013, at 3:24 PM, "Erik de Bruin"  wrote:
>>>
>>> > I've been away from Falcon(Jx) for a long time, coding wise. I had
>>> > to basically set up my dev env all new and this is what happened.
>>> >
>>> > I really wish we got get Gordon or Darrel or even Mike to take a
>>> > look at replacing the deprecated Guava API calls... Here's to hoping
>>> > one of them reads this and accepts the challenge!
>>> >
>>> > EdB
>>> >
>>> >
>>> >
>>> > On Fri, Nov 1, 2013 at 10:29 PM, Alex Harui  wrote:
>>> >> DataBindingTest is the one I use.  I never did figure out how old
>>> >> my Closure tools are.  And there is a chance I mucked with the
>>> >> Guava's on
>>> my
>>> >> system to "fix" this.
>>> >>
>>> >> Did the compilation work before you started making changes?  I
>>> >> think that's what I used to see.  The problem would go away for a
>>> >> long time, then I would make some change and start getting it, then
>>> >> some other
>>> change
>>> >> would make it go away.  But it never really made sense as to why
>>> >> some change would break it or fix it.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 11/1/13 2:21 PM, "Erik de Bruin"  wrote:
>>> >>
>>> >>> Which of the ASJS examples is working for you? I've tried the
>>>'again'
>>> >>> and 'binding' ones and both give me errors, although the resulting
>>> >>> 'release JS' seems to work (with bugs).
>>> >>>
>>> >>> EdB
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Fri, Nov 1, 2013 at 5:22 PM, Alex Harui  wrote:
>>>  But there must be another newer one on our computers that google
>>> closure
>>>  finds when it does work, right?
>>> 
>>>  I also have a vague recollection that this issue is somehow
>>>  related to hitting certain code paths in Falcon which may be why
>>>  it goes away
>>> for a
>>>  while.
>>> 
>>>  -Alex
>>> 
>>>  On 11/1/13 8:36 AM, "Erik de Bruin"  wrote:
>>> 
>>> > No, I wasn't clear. The only 'guava.jar' I can find is in the
>>> > 'compiler/lib' directory. I don't know Java all that well, and
>>> > certainly won't claim to know anything about project
>>> > dependencies,
>>> but
>>> > my guess is that the fact that the 'compiler.jx' project is
>>> > dependent on the 'compiler' project has something to do with
>>> > this. I figure
>>> that
>>> > when the CC runs, it 'uses' (links?) the guava.jar in the
>>>'compiler'
>>> > project and since that's not the version it's expecting, it balks.
>>> >
>>> > EdB
>>> >
>>> >
>>> >
>>> > On Fri, Nov 1, 2013 at 4:19 PM, Alex Harui 
>>>wrote:
>>> >> But you found a guava.jar in your google closure files somewhere?
>>> >> Where
>>> >> was that? I'm not seeing one in my google folders.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 11/1/13 8:16 AM, "Erik de Bruin"  wrote:
>>> >>
>>>  I'd rather not fiddle with my setup right now, but I've
>>>  definitely seen this error and somehow got it to go away for
>>>  long periods of time.
>>>  What
>>>  kinds of things did you tweak to get around it?  It's been so
>>>  long that I don't recall how I got around it.
>>> >>>
>>> >>> I've been switching versions of the CC and Guava around,
>>> >>> hoping to find a combination
>>
>>
>>
>>--
>>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: [FALCONJX] added support for 'as', 'int', 'is', 'trace' and 'uint' to FlexJS framework and compiler

[Erik de Bruin]

Ok, all should be fine now. I've committed an example that should show
the proper functioning of the code with some of the most common use
cases: LanguageTests.

EdB



On Mon, Nov 4, 2013 at 8:23 AM, Erik de Bruin  wrote:
> Note: when trying to build a project using the new "Language" class
> yesterday, I noticed that the implementation is not complete. Please
> hold off on implementing it in any components until I check in some
> changes to FalconJx and the framework.
>
> EdB
>
>
>
> On Fri, Nov 1, 2013 at 3:57 PM, Alex Harui  wrote:
>>
>>
>> On 11/1/13 7:48 AM, "Erik de Bruin"  wrote:
>>
 Will we end up doing metadata and describetype following this pattern?
>>>
>>>It certainly provides an extra tool towards that goal, but depending
>>>on the requirements for both features - can you elaborate your ideas a
>>>bit - there might be other things that we can do, e.g. Closure
>>>provides some introspection tools as well.
>> The next "big experiment" is trying to cross-compile an app that uses one
>> of the app frameworks like Swiz, Parsely, etc.  Someone pointed out that
>> they use metadata and and I assume they must use describetype to fetch
>> said metadata.
>>
>> My hope is to avoid use of describetype in the FlexJS classes we write or
>> consider a lighter weight implementation for the few things we might need
>> (I recently checked in a lightweight getQualifiedClassName for CSS
>> TypeSelector support in JS), but I think we need to see if we can support
>> the existing app frameworks.
>>
>> I'm not sure we'd need full describetype support, probably just enough to
>> get the metadata.
>>
>> -Alex
>>
>
>
>
> --
> 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

[FLEXJS] describeType

[Erik de Bruin]

Hi,

flash.utils.describeType has an XML return type. JavaScript doesn't
have anything like that and I'm sure we don't want to simulate it for
the purpose of this exercise.

I suggest we create a utility class
"org.apache.flex.utils.DescribeType" and put some static methods on it
that allow us to get tailored introspection... Maybe start with
'DescribeType.getMetaData(value:*)'?

What metadata are you thinking of, specifically?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

[FLEXLS]when Flex js release?

[Mark Shen]

Anyone know this? Thanks.

Mark

Re: [FLEXLS]when Flex js release?

[Erik de Bruin]

We're working steadily towards an alpha quality release. There are a
few issues that remain to be fixed (help is very welcome!) and some
features that we'd like to have are still missing.

Since this is a volunteer effort, and we currently have fewer
volunteers than we have eager (future) users, so things take some time
to get done.

You can help out by downloading the artefacts and help us pinpoint
areas that need some TLC.

Thank you,

EdB



On Tue, Nov 5, 2013 at 3:42 PM, Mark Shen  wrote:
> Anyone know this? Thanks.
>
> Mark



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: video not working in full screen mode in windows 8/ IE 10 metro browser

[sébastien Paturel]

Hi
i also got this.
Short solution is: call OSMFSettings.enableStageVideo = false; at root 
of your app.
Or if you want use stage video, you need to be sure that nothing will be 
drawn in the display list because stage video is shown under display list.

and thus you need backgroundAlpha="0" for your App container.

i have put some explanations in the list, you can search for "Flex 4.11 
+ OSMF 2.0 => bug" title.


Regards,
Seb

Le 05/11/2013 08:18, krishna4960 a écrit :

Hello friends,

I am running my flex application in windows 8/IE 10 metro browser. The
application displays a video without any problem when it is in minimized
mode (like 200*300 size) but the moment i click on the full screen button to
view the video in full screen mode, the page turns into blank and i have to
hit escape button to return to the application. This problem is occurring in
IE 10 metro browser only. The video runs in full screen mode without any
problem in Win8 /IE 10 desktop browser.

i am using   'stage.displayState = StageDisplayState.FULL_SCREEN;' to open
the video in full screen mode.

I will be grateful if you guys can help me.




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/video-not-working-in-full-screen-mode-in-windows-8-IE-10-metro-browser-tp31903.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FLEXJS] describeType

[Alex Harui]

Apparently, there is a under-documented describeTypeJSON which I think the
application frameworks are using to get any and all metadata on a class
and its methods because it is much faster than regular describeType.
Maybe we should do that.

-Alex

On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:

>Hi,
>
>flash.utils.describeType has an XML return type. JavaScript doesn't
>have anything like that and I'm sure we don't want to simulate it for
>the purpose of this exercise.
>
>I suggest we create a utility class
>"org.apache.flex.utils.DescribeType" and put some static methods on it
>that allow us to get tailored introspection... Maybe start with
>'DescribeType.getMetaData(value:*)'?
>
>What metadata are you thinking of, specifically?
>
>EdB
>
>
>
>-- 
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl

Re: Build failed in Jenkins: flex-falcon #194

[Erik de Bruin]

Please note, the build machine (windows1) crashed this weekend, so all
Apache builds that depend on Windows (quite a lot, actually) are
backed up. So it may be a while before you see an "all is well again
with flex-falcon" message...

EdB



On Tue, Nov 5, 2013 at 6:35 PM, Erik de Bruin  wrote:
> I've already changed the Jenkins job to always "ant wipe-all all".
>
> EdB
>
>
>
> On Tue, Nov 5, 2013 at 5:08 PM, Alex Harui  wrote:
>> Can someone with knowledge of the build system go an delete lib/guava*.*?
>>
>> Thanks,
>> -Alex
>>
>> On 11/5/13 6:46 AM, "Apache Jenkins Server" 
>> wrote:
>>
>>>See 
>>>
>>>Changes:
>>>
>>>[gordonsmith] Falcon: Updated guava.jar to the current release, 15.0
>>>
>>>[erik] Fixed old TODO: handle parsing of 'rest' parameter.
>>>
>>>[erik] Removed an @Ignore and TODO, with documentation.
>>>
>>>[erik] Cleaned up some TODOs ;-)
>>>
>>>[erik] No longer needed, there is now a 'test case' example in the ASJS
>>>project.
>>>
>>>[erik] Build files now download latest version of Guava (15.0 at the time
>>>of writing) and Closure Compiler.
>>>
>>>[erik] Update tests with proper interface 'goog.require' statements
>>>
>>>[erik] Fetch and store all interface "imports" for use during the initial
>>>writing of the FlexJS classes
>>>
>>>[erik] Add missing 'instanceof' enumeration
>>>
>>>[erik] More changes to tests to match desired 'goog' JS output
>>>
>>>[erik] Added enumeration for the 'interfaces' array
>>>
>>>[erik] This is where all the magic happens ;-)
>>>
>>>--
>>>Started by timer
>>>Started by timer
>>>Started by an SCM change
>>>Started by an SCM change
>>>Building remotely on windows1 in workspace
>>>
>>>Checkout:flex-falcon /  -
>>>hudson.remoting.Channel@4aaf667f:windows1
>>>Using strategy: Default
>>>Last Built Revision: Revision 7297f41bd3a6fca342f5986e11798f5af275e82a
>>>(origin/develop)
>>>Fetching changes from 1 remote Git repository
>>>Fetching upstream changes from origin
>>>Commencing build of Revision 7020dcfaccf04007aa29a9e60dbf92fe0294f21b
>>>(origin/develop)
>>>Checking out Revision 7020dcfaccf04007aa29a9e60dbf92fe0294f21b
>>>(origin/develop)
>>>Deleting old artifacts from #192
>>>[flex-falcon] $ cmd.exe /C
>>>'"f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\
>>>bin\ant.bat -file jenkins.xml main && exit %%ERRORLEVEL%%"'
>>>Buildfile: 
>>>
>>>clean:
>>>   [delete] Deleting directory
>>>
>>>   [delete] Deleting directory
>>>
>>>
>>>init:
>>>[mkdir] Created dir:
>>>
>>>[mkdir] Created dir:
>>>
>>>
>>>jflex-download:
>>> [echo] Be patient. This takes a few minutes...
>>>  [get] Getting: http://jflex.de/jflex-1.4.3.zip
>>>  [get] To:
>>>
>>>[unzip] Expanding:
>>>
>>>into 
>>>
>>>main:
>>>
>>>BUILD SUCCESSFUL
>>>Total time: 4 seconds
>>>[flex-falcon] $ cmd.exe /C
>>>'"f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\
>>>bin\ant.bat -file build.xml all && exit %%ERRORLEVEL%%"'
>>>Buildfile: 
>>>
>>>sdk:
>>>
>>>checkenv:
>>> [echo] JFLEX_JAR is
>>>>>b/JFlex.jar>
>>>
>>>download:
>>>
>>>prepare:
>>>
>>>antlr-jar-check:
>>>
>>>antlr-jar:
>>>
>>>commons-cli-jar-check:
>>>
>>>commons-cli-jar:
>>>
>>>commons-io-jar-check:
>>>
>>>commons-io-jar:
>>>
>>>commons-jars:
>>>
>>>guava-jar-check:
>>>
>>>guava-jar:
>>>
>>>jburg-jar-check:
>>>
>>>jburg-jar:
>>>
>>>lzma-jar-check:
>>>
>>>lzma-jar:
>>>
>>>main:
>>>
>>>setup:
>>>
>>>set.raw.as.tokenizer.uptodate:
>>>
>>>raw.as.tokenizer:
>>>
>>>set.raw.asdoc.tokenizer.uptodate:
>>>
>>>raw.asdoc.tokenizer:
>>>
>>>set.raw.mxml.tokenizer.uptodate:
>>>
>>>raw.mxml.tokenizer:
>>>
>>>jflex:
>>>
>>>annotate.class:
>>>
>>>set.as.parser.uptodate:
>>>
>>>as.parser:
>>>
>>>set.metadata.parser.uptodate:
>>>
>>>metadata.parser:
>>>
>>>set.css.lexer.and.parser.uptodate:
>>>
>>>css.lexer.and.parser:
>>>
>>>set.css.tree.uptodate:
>>>
>>>css.tree:
>>>
>>>antlr:
>>>
>>>node.adapter:
>>>
>>>unknown.tree.pattern.input.output:
>>>
>>>set.unknown.tree.handler.patterns.uptodate:
>>>
>>>unknown.tree.handler.patterns:
>>>
>>>set.cmc.emitter.uptodate:
>>>
>>>cmc.emitter:
>>>
>>>set.css.emitter.uptodate:
>>>
>>>css.emitter:
>>>
>>>jburg:
>>>
>>>set.flex.config.xml.available:
>>>
>>>copy.sdk:
>>>

Re: [FLEXJS] describeType

[Erik de Bruin]

My FlashBuilder's autocomplete is not aware of such a method. Any
secret handshakes I should be aware of to activate it?

EdB



On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
> Apparently, there is a under-documented describeTypeJSON which I think the
> application frameworks are using to get any and all metadata on a class
> and its methods because it is much faster than regular describeType.
> Maybe we should do that.
>
> -Alex
>
> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
>
>>Hi,
>>
>>flash.utils.describeType has an XML return type. JavaScript doesn't
>>have anything like that and I'm sure we don't want to simulate it for
>>the purpose of this exercise.
>>
>>I suggest we create a utility class
>>"org.apache.flex.utils.DescribeType" and put some static methods on it
>>that allow us to get tailored introspection... Maybe start with
>>'DescribeType.getMetaData(value:*)'?
>>
>>What metadata are you thinking of, specifically?
>>
>>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

Re: Build failed in Jenkins: flex-falcon #194

[Erik de Bruin]

No message, but the build machine shows that last build succeeded.

EdB



On Tue, Nov 5, 2013 at 6:38 PM, Erik de Bruin  wrote:
> Please note, the build machine (windows1) crashed this weekend, so all
> Apache builds that depend on Windows (quite a lot, actually) are
> backed up. So it may be a while before you see an "all is well again
> with flex-falcon" message...
>
> EdB
>
>
>
> On Tue, Nov 5, 2013 at 6:35 PM, Erik de Bruin  wrote:
>> I've already changed the Jenkins job to always "ant wipe-all all".
>>
>> EdB
>>
>>
>>
>> On Tue, Nov 5, 2013 at 5:08 PM, Alex Harui  wrote:
>>> Can someone with knowledge of the build system go an delete lib/guava*.*?
>>>
>>> Thanks,
>>> -Alex
>>>
>>> On 11/5/13 6:46 AM, "Apache Jenkins Server" 
>>> wrote:
>>>
See 

Changes:

[gordonsmith] Falcon: Updated guava.jar to the current release, 15.0

[erik] Fixed old TODO: handle parsing of 'rest' parameter.

[erik] Removed an @Ignore and TODO, with documentation.

[erik] Cleaned up some TODOs ;-)

[erik] No longer needed, there is now a 'test case' example in the ASJS
project.

[erik] Build files now download latest version of Guava (15.0 at the time
of writing) and Closure Compiler.

[erik] Update tests with proper interface 'goog.require' statements

[erik] Fetch and store all interface "imports" for use during the initial
writing of the FlexJS classes

[erik] Add missing 'instanceof' enumeration

[erik] More changes to tests to match desired 'goog' JS output

[erik] Added enumeration for the 'interfaces' array

[erik] This is where all the magic happens ;-)

--
Started by timer
Started by timer
Started by an SCM change
Started by an SCM change
Building remotely on windows1 in workspace

Checkout:flex-falcon /  -
hudson.remoting.Channel@4aaf667f:windows1
Using strategy: Default
Last Built Revision: Revision 7297f41bd3a6fca342f5986e11798f5af275e82a
(origin/develop)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision 7020dcfaccf04007aa29a9e60dbf92fe0294f21b
(origin/develop)
Checking out Revision 7020dcfaccf04007aa29a9e60dbf92fe0294f21b
(origin/develop)
Deleting old artifacts from #192
[flex-falcon] $ cmd.exe /C
'"f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\
bin\ant.bat -file jenkins.xml main && exit %%ERRORLEVEL%%"'
Buildfile: 

clean:
   [delete] Deleting directory

   [delete] Deleting directory


init:
[mkdir] Created dir:

[mkdir] Created dir:


jflex-download:
 [echo] Be patient. This takes a few minutes...
  [get] Getting: http://jflex.de/jflex-1.4.3.zip
  [get] To:

[unzip] Expanding:

into 

main:

BUILD SUCCESSFUL
Total time: 4 seconds
[flex-falcon] $ cmd.exe /C
'"f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\
bin\ant.bat -file build.xml all && exit %%ERRORLEVEL%%"'
Buildfile: 

sdk:

checkenv:
 [echo] JFLEX_JAR is


download:

prepare:

antlr-jar-check:

antlr-jar:

commons-cli-jar-check:

commons-cli-jar:

commons-io-jar-check:

commons-io-jar:

commons-jars:

guava-jar-check:

guava-jar:

jburg-jar-check:

jburg-jar:

lzma-jar-check:

lzma-jar:

main:

setup:

set.raw.as.tokenizer.uptodate:

raw.as.tokenizer:

set.raw.asdoc.tokenizer.uptodate:

raw.asdoc.tokenizer:

set.raw.mxml.tokenizer.uptodate:

raw.mxml.tokenizer:

jflex:

annotate.class:

set.as.parser.uptodate:

as.parser:

set.metadata.parser.uptodate:

metadata.parser:

set.css.lexer.and.parser.uptodate:

css.lexer.and.parser:

set.css.tree.uptodate:

css.tree:

antlr:

nod

RE: [FALCON/JX] guava dependencies in compiler AND closure

[Gordon Smith]

Oops, sorry I forgot that guava.jar gets downloaded rather than being under 
source control. I had replaced the copy in compiler/lib and didn't notice that 
git commit didn't commit it.

Thanks for fixing the build script, Erik.

- Gordon

-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl] 
Sent: Tuesday, November 05, 2013 4:57 AM
To: dev@flex.apache.org
Subject: Re: [FALCON/JX] guava dependencies in compiler AND closure

I've updated the Falcon build scripts. A fresh build ('ant wipe-all
main') from the root now cleanly builds all the 'example' projects - where 
'cleanly' means no weird exceptions from the compiler code itself ;-)

EdB



On Tue, Nov 5, 2013 at 6:10 AM, Alex Harui  wrote:
> Thanks Gordon!
>
> On 11/4/13 4:59 PM, "Gordon Smith"  wrote:
>
>>OK, the 'develop' branch of flex-falcon now has a 
>>compiler/lib/guava.jar that is the current release, 15.0. All the 
>>tests run by Falcon's 'ant main' still pass.
>>
>>- Gordon
>>
>>-Original Message-
>>From: Erik de Bruin [mailto:e...@ixsoftware.nl]
>>Sent: Sunday, November 03, 2013 9:00 PM
>>To: dev@flex.apache.org
>>Subject: Re: [FALCON/JX] guava dependencies in compiler AND closure
>>
>>Thank you, Gordon. Yes, I think it's best to go to the latest version 
>>and keep updating.
>>
>>EdB
>>
>>
>>
>>On Monday, November 4, 2013, Gordon Smith wrote:
>>
>>> I can take a look at upgrading the version of Guava that Falcon uses.
>>> Do you want it to use the latest version, 15.0?
>>>
>>> - Gordon
>>>
>>> Sent from my iPad
>>>
>>> On Nov 1, 2013, at 3:24 PM, "Erik de Bruin"  wrote:
>>>
>>> > I've been away from Falcon(Jx) for a long time, coding wise. I had 
>>> > to basically set up my dev env all new and this is what happened.
>>> >
>>> > I really wish we got get Gordon or Darrel or even Mike to take a 
>>> > look at replacing the deprecated Guava API calls... Here's to 
>>> > hoping one of them reads this and accepts the challenge!
>>> >
>>> > EdB
>>> >
>>> >
>>> >
>>> > On Fri, Nov 1, 2013 at 10:29 PM, Alex Harui  wrote:
>>> >> DataBindingTest is the one I use.  I never did figure out how old 
>>> >> my Closure tools are.  And there is a chance I mucked with the 
>>> >> Guava's on
>>> my
>>> >> system to "fix" this.
>>> >>
>>> >> Did the compilation work before you started making changes?  I 
>>> >> think that's what I used to see.  The problem would go away for a 
>>> >> long time, then I would make some change and start getting it, 
>>> >> then some other
>>> change
>>> >> would make it go away.  But it never really made sense as to why 
>>> >> some change would break it or fix it.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 11/1/13 2:21 PM, "Erik de Bruin"  wrote:
>>> >>
>>> >>> Which of the ASJS examples is working for you? I've tried the
>>>'again'
>>> >>> and 'binding' ones and both give me errors, although the 
>>> >>> resulting 'release JS' seems to work (with bugs).
>>> >>>
>>> >>> EdB
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Fri, Nov 1, 2013 at 5:22 PM, Alex Harui  wrote:
>>>  But there must be another newer one on our computers that 
>>>  google
>>> closure
>>>  finds when it does work, right?
>>> 
>>>  I also have a vague recollection that this issue is somehow 
>>>  related to hitting certain code paths in Falcon which may be 
>>>  why it goes away
>>> for a
>>>  while.
>>> 
>>>  -Alex
>>> 
>>>  On 11/1/13 8:36 AM, "Erik de Bruin"  wrote:
>>> 
>>> > No, I wasn't clear. The only 'guava.jar' I can find is in the 
>>> > 'compiler/lib' directory. I don't know Java all that well, and 
>>> > certainly won't claim to know anything about project 
>>> > dependencies,
>>> but
>>> > my guess is that the fact that the 'compiler.jx' project is 
>>> > dependent on the 'compiler' project has something to do with 
>>> > this. I figure
>>> that
>>> > when the CC runs, it 'uses' (links?) the guava.jar in the
>>>'compiler'
>>> > project and since that's not the version it's expecting, it balks.
>>> >
>>> > EdB
>>> >
>>> >
>>> >
>>> > On Fri, Nov 1, 2013 at 4:19 PM, Alex Harui 
>>>wrote:
>>> >> But you found a guava.jar in your google closure files somewhere?
>>> >> Where
>>> >> was that? I'm not seeing one in my google folders.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 11/1/13 8:16 AM, "Erik de Bruin"  wrote:
>>> >>
>>>  I'd rather not fiddle with my setup right now, but I've 
>>>  definitely seen this error and somehow got it to go away 
>>>  for long periods of time.
>>>  What
>>>  kinds of things did you tweak to get around it?  It's been 
>>>  so long that I don't recall how I got around it.
>>> >>>
>>> >>> I've been switching versions of the CC and Guava around, 
>>> >>> hoping to find a combination
>>
>>
>>
>>--
>>Ix Multimedia Software
>>
>>Jan Luykenstraat 27
>>3521 VB Utrecht
>>
>>T. 06-51952295
>>I. www.ixsoftware.nl
>



--
Ix Multim

Re: [FLEXJS] describeType

[Alex Harui]

Told you it was under-documented ;-). The secret handshake is apparently
to ignore autocomplete and use google.  Looks like it is
avmplus.describeTypeJSON().  I've not used it, but there was a recent
thread about it.

On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:

>My FlashBuilder's autocomplete is not aware of such a method. Any
>secret handshakes I should be aware of to activate it?
>
>EdB
>
>
>
>On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
>> Apparently, there is a under-documented describeTypeJSON which I think
>>the
>> application frameworks are using to get any and all metadata on a class
>> and its methods because it is much faster than regular describeType.
>> Maybe we should do that.
>>
>> -Alex
>>
>> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
>>
>>>Hi,
>>>
>>>flash.utils.describeType has an XML return type. JavaScript doesn't
>>>have anything like that and I'm sure we don't want to simulate it for
>>>the purpose of this exercise.
>>>
>>>I suggest we create a utility class
>>>"org.apache.flex.utils.DescribeType" and put some static methods on it
>>>that allow us to get tailored introspection... Maybe start with
>>>'DescribeType.getMetaData(value:*)'?
>>>
>>>What metadata are you thinking of, specifically?
>>>
>>>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

RE: [FLEXJS] describeType

[Maurice Amsellem]

I confirm, it's avmplus.describeTypeJSON() 

This is a typical use:

  typeInfo = avmplus. describeTypeJSON (cls, avmplus.INCLUDE_BASES
   | avmplus.INCLUDE_INTERFACES
   | avmplus.INCLUDE_VARIABLES
   | avmplus.INCLUDE_ACCESSORS
   | avmplus.INCLUDE_METHODS
   | avmplus.INCLUDE_METADATA
   | avmplus.INCLUDE_CONSTRUCTOR
  |avmplus.INCLUDE_TRAITS);

And it will return an object with dynamic properties...

Maurice 

-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] 
Envoyé : mardi 5 novembre 2013 19:03
À : dev@flex.apache.org
Objet : Re: [FLEXJS] describeType

Told you it was under-documented ;-). The secret handshake is apparently to 
ignore autocomplete and use google.  Looks like it is 
avmplus.describeTypeJSON().  I've not used it, but there was a recent thread 
about it.

On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:

>My FlashBuilder's autocomplete is not aware of such a method. Any 
>secret handshakes I should be aware of to activate it?
>
>EdB
>
>
>
>On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
>> Apparently, there is a under-documented describeTypeJSON which I 
>>think the  application frameworks are using to get any and all 
>>metadata on a class  and its methods because it is much faster than 
>>regular describeType.
>> Maybe we should do that.
>>
>> -Alex
>>
>> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
>>
>>>Hi,
>>>
>>>flash.utils.describeType has an XML return type. JavaScript doesn't 
>>>have anything like that and I'm sure we don't want to simulate it for 
>>>the purpose of this exercise.
>>>
>>>I suggest we create a utility class
>>>"org.apache.flex.utils.DescribeType" and put some static methods on 
>>>it that allow us to get tailored introspection... Maybe start with 
>>>'DescribeType.getMetaData(value:*)'?
>>>
>>>What metadata are you thinking of, specifically?
>>>
>>>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

Re: [FLEXJS] describeType

[Roland Zwaga]

Or check out these as3-reflect classes:
https://code.google.com/p/as3-commons/source/browse/trunk/as3-commons-reflect/src/main/actionscript/org/as3commons/reflect/JSONTypeProvider.as
and
https://code.google.com/p/as3-commons/source/browse/trunk/as3-commons-lang/src/main/actionscript/org/as3commons/lang/typedescription/JSONTypeDescription.as
Both being used to create the as3-reflect types...

Roland


On 5 November 2013 19:05, Maurice Amsellem wrote:

> I confirm, it's avmplus.describeTypeJSON()
>
> This is a typical use:
>
>   typeInfo = avmplus. describeTypeJSON (cls, avmplus.INCLUDE_BASES
>| avmplus.INCLUDE_INTERFACES
>| avmplus.INCLUDE_VARIABLES
>| avmplus.INCLUDE_ACCESSORS
>| avmplus.INCLUDE_METHODS
>| avmplus.INCLUDE_METADATA
>| avmplus.INCLUDE_CONSTRUCTOR
>   |avmplus.INCLUDE_TRAITS);
>
> And it will return an object with dynamic properties...
>
> Maurice
>
> -Message d'origine-
> De : Alex Harui [mailto:aha...@adobe.com]
> Envoyé : mardi 5 novembre 2013 19:03
> À : dev@flex.apache.org
> Objet : Re: [FLEXJS] describeType
>
> Told you it was under-documented ;-). The secret handshake is apparently
> to ignore autocomplete and use google.  Looks like it is
> avmplus.describeTypeJSON().  I've not used it, but there was a recent
> thread about it.
>
> On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:
>
> >My FlashBuilder's autocomplete is not aware of such a method. Any
> >secret handshakes I should be aware of to activate it?
> >
> >EdB
> >
> >
> >
> >On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
> >> Apparently, there is a under-documented describeTypeJSON which I
> >>think the  application frameworks are using to get any and all
> >>metadata on a class  and its methods because it is much faster than
> >>regular describeType.
> >> Maybe we should do that.
> >>
> >> -Alex
> >>
> >> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
> >>
> >>>Hi,
> >>>
> >>>flash.utils.describeType has an XML return type. JavaScript doesn't
> >>>have anything like that and I'm sure we don't want to simulate it for
> >>>the purpose of this exercise.
> >>>
> >>>I suggest we create a utility class
> >>>"org.apache.flex.utils.DescribeType" and put some static methods on
> >>>it that allow us to get tailored introspection... Maybe start with
> >>>'DescribeType.getMetaData(value:*)'?
> >>>
> >>>What metadata are you thinking of, specifically?
> >>>
> >>>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
>
>


-- 
regards,
Roland

-- 
Roland Zwaga
Senior Consultant | Stack & Heap BVBA

+32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com

http://randoriframework.com
http://zwaga.blogspot.com
http://www.springactionscript.org
http://www.as3commons.org

ActionScript coding conventions

[Gordon Smith]

Didn't we used to have a coding conventions document for committers to follow? 
I can't find it anywhere on the site.

- Gordon

Re: ActionScript coding conventions

[Erik de Bruin]

I don't think we copied them over to Apache Flex yet... All I could
find was this:

http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/

EdB



On Tue, Nov 5, 2013 at 7:16 PM, Gordon Smith  wrote:
> Didn't we used to have a coding conventions document for committers to 
> follow? I can't find it anywhere on the site.
>
> - Gordon
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [FLEXJS] describeType

[Erik de Bruin]

Wow.

Getting this to work involves creating a wrapper class around an
undocumented method in playerglobal.swc, which is not under our
control.

That doesn't sound like a sustainable way forward :-(

EdB



On Tue, Nov 5, 2013 at 7:02 PM, Alex Harui  wrote:
> Told you it was under-documented ;-). The secret handshake is apparently
> to ignore autocomplete and use google.  Looks like it is
> avmplus.describeTypeJSON().  I've not used it, but there was a recent
> thread about it.
>
> On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:
>
>>My FlashBuilder's autocomplete is not aware of such a method. Any
>>secret handshakes I should be aware of to activate it?
>>
>>EdB
>>
>>
>>
>>On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
>>> Apparently, there is a under-documented describeTypeJSON which I think
>>>the
>>> application frameworks are using to get any and all metadata on a class
>>> and its methods because it is much faster than regular describeType.
>>> Maybe we should do that.
>>>
>>> -Alex
>>>
>>> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
>>>
Hi,

flash.utils.describeType has an XML return type. JavaScript doesn't
have anything like that and I'm sure we don't want to simulate it for
the purpose of this exercise.

I suggest we create a utility class
"org.apache.flex.utils.DescribeType" and put some static methods on it
that allow us to get tailored introspection... Maybe start with
'DescribeType.getMetaData(value:*)'?

What metadata are you thinking of, specifically?

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

Re: [FLEXJS] describeType

[Alex Harui]

Not sure I understand.  Lots of Flex wraps playerglobal.swc.  Is it just
the fact that it is undocumented?

At a higher level, goal is to try to see what it would take to support the
popular app frameworks like Parsley and Swiz in JS.  Maybe the first step
is to just try it and see what its dependencies are.

-Alex

On 11/5/13 11:22 AM, "Erik de Bruin"  wrote:

>Wow.
>
>Getting this to work involves creating a wrapper class around an
>undocumented method in playerglobal.swc, which is not under our
>control.
>
>That doesn't sound like a sustainable way forward :-(
>
>EdB
>
>
>
>On Tue, Nov 5, 2013 at 7:02 PM, Alex Harui  wrote:
>> Told you it was under-documented ;-). The secret handshake is apparently
>> to ignore autocomplete and use google.  Looks like it is
>> avmplus.describeTypeJSON().  I've not used it, but there was a recent
>> thread about it.
>>
>> On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:
>>
>>>My FlashBuilder's autocomplete is not aware of such a method. Any
>>>secret handshakes I should be aware of to activate it?
>>>
>>>EdB
>>>
>>>
>>>
>>>On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
 Apparently, there is a under-documented describeTypeJSON which I think
the
 application frameworks are using to get any and all metadata on a
class
 and its methods because it is much faster than regular describeType.
 Maybe we should do that.

 -Alex

 On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:

>Hi,
>
>flash.utils.describeType has an XML return type. JavaScript doesn't
>have anything like that and I'm sure we don't want to simulate it for
>the purpose of this exercise.
>
>I suggest we create a utility class
>"org.apache.flex.utils.DescribeType" and put some static methods on it
>that allow us to get tailored introspection... Maybe start with
>'DescribeType.getMetaData(value:*)'?
>
>What metadata are you thinking of, specifically?
>
>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

please UNSUBSCRIBE me

[Deborah Krikun]

THIS IS A TEXT EMAILDeborah Krikun
Associate Professor, Digital Arts
Westchester Community College, 
Center for the Digital Arts
Peekskill, NY
914-606-7300
Phone: 914.606.7359 (msg) 606-7300 (main)
Email: deborah.kri...@sunywcc.edu
Websites: www.sunywcc.edu/peekskill

Re: please UNSUBSCRIBE me

[Erik de Bruin]

Please send an email to 'dev-unsubscr...@flex.apache.org'.

EdB



On Tue, Nov 5, 2013 at 8:40 PM, Deborah Krikun  wrote:
> THIS IS A TEXT EMAIL
>
> Deborah Krikun
> Associate Professor, Digital Arts
> Westchester Community College,
> Center for the Digital Arts
> Peekskill, NY
> 914-606-7300
> Phone: 914.606.7359 (msg) 606-7300 (main)
> Email: deborah.kri...@sunywcc.edu
> Websites: www.sunywcc.edu/peekskill



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [FLEXLS]when Flex js release?

[Erik de Bruin]

https://cwiki.apache.org/confluence/display/FLEX/Using+FlexJS+with+Adobe+Flash+Builder

Have fun!

EdB



On Tue, Nov 5, 2013 at 8:45 PM, Mark Shen  wrote:
> how to download artefacrs?  what us the  url?
>
> Thanks Erik
>
> Mark
>
>
> On Tue, Nov 5, 2013 at 9:52 AM, Erik de Bruin  wrote:
>
>> We're working steadily towards an alpha quality release. There are a
>> few issues that remain to be fixed (help is very welcome!) and some
>> features that we'd like to have are still missing.
>>
>> Since this is a volunteer effort, and we currently have fewer
>> volunteers than we have eager (future) users, so things take some time
>> to get done.
>>
>> You can help out by downloading the artefacts and help us pinpoint
>> areas that need some TLC.
>>
>> Thank you,
>>
>> EdB
>>
>>
>>
>> On Tue, Nov 5, 2013 at 3:42 PM, Mark Shen  wrote:
>> > Anyone know this? Thanks.
>> >
>> > Mark
>>
>>
>>
>> --
>> 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: please UNSUBSCRIBE me

[OmPrakash Muppirala]

Deborah,

If you are using mail forwarding, then you might have to send the email to '
dev-unsubscr...@flex.apache.org'  from the original email id that is
subscribed.
If that does not work, let us know your email id, one of our moderators
will manually unsubscribe you.

Sorry for the inconvenience.

Thanks,
Om


On Tue, Nov 5, 2013 at 11:47 AM, Erik de Bruin  wrote:

> Please send an email to 'dev-unsubscr...@flex.apache.org'.
>
> EdB
>
>
>
> On Tue, Nov 5, 2013 at 8:40 PM, Deborah Krikun  wrote:
> > THIS IS A TEXT EMAIL
> >
> > Deborah Krikun
> > Associate Professor, Digital Arts
> > Westchester Community College,
> > Center for the Digital Arts
> > Peekskill, NY
> > 914-606-7300
> > Phone: 914.606.7359 (msg) 606-7300 (main)
> > Email: deborah.kri...@sunywcc.edu
> > Websites: www.sunywcc.edu/peekskill
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Re: [FLEXJS] describeType

[Erik de Bruin]

In my experience an 'undocumented' API means: liable to change without
notice in the next update.

At a higher level... I think we've got other things to do before we
even think about supporting AS frameworks that have low level hooks
into the original SDK.

EdB



On Tue, Nov 5, 2013 at 8:43 PM, Alex Harui  wrote:
> Not sure I understand.  Lots of Flex wraps playerglobal.swc.  Is it just
> the fact that it is undocumented?
>
> At a higher level, goal is to try to see what it would take to support the
> popular app frameworks like Parsley and Swiz in JS.  Maybe the first step
> is to just try it and see what its dependencies are.
>
> -Alex
>
> On 11/5/13 11:22 AM, "Erik de Bruin"  wrote:
>
>>Wow.
>>
>>Getting this to work involves creating a wrapper class around an
>>undocumented method in playerglobal.swc, which is not under our
>>control.
>>
>>That doesn't sound like a sustainable way forward :-(
>>
>>EdB
>>
>>
>>
>>On Tue, Nov 5, 2013 at 7:02 PM, Alex Harui  wrote:
>>> Told you it was under-documented ;-). The secret handshake is apparently
>>> to ignore autocomplete and use google.  Looks like it is
>>> avmplus.describeTypeJSON().  I've not used it, but there was a recent
>>> thread about it.
>>>
>>> On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:
>>>
My FlashBuilder's autocomplete is not aware of such a method. Any
secret handshakes I should be aware of to activate it?

EdB



On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
> Apparently, there is a under-documented describeTypeJSON which I think
>the
> application frameworks are using to get any and all metadata on a
>class
> and its methods because it is much faster than regular describeType.
> Maybe we should do that.
>
> -Alex
>
> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
>
>>Hi,
>>
>>flash.utils.describeType has an XML return type. JavaScript doesn't
>>have anything like that and I'm sure we don't want to simulate it for
>>the purpose of this exercise.
>>
>>I suggest we create a utility class
>>"org.apache.flex.utils.DescribeType" and put some static methods on it
>>that allow us to get tailored introspection... Maybe start with
>>'DescribeType.getMetaData(value:*)'?
>>
>>What metadata are you thinking of, specifically?
>>
>>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

Re: please UNSUBSCRIBE me

[Alex Harui]

Actually, she's tried that and failed.

Deborah, it appears you subscribed using a me.com email address and maybe
those emails are being forwarded to wherever you are reading this.  To
unsubscribe, you will need to send an email from the me.com address.

-Alex

On 11/5/13 11:47 AM, "Erik de Bruin"  wrote:

>Please send an email to 'dev-unsubscr...@flex.apache.org'.
>
>EdB
>
>
>
>On Tue, Nov 5, 2013 at 8:40 PM, Deborah Krikun  wrote:
>> THIS IS A TEXT EMAIL
>>
>> Deborah Krikun
>> Associate Professor, Digital Arts
>> Westchester Community College,
>> Center for the Digital Arts
>> Peekskill, NY
>> 914-606-7300
>> Phone: 914.606.7359 (msg) 606-7300 (main)
>> Email: deborah.kri...@sunywcc.edu
>> Websites: www.sunywcc.edu/peekskill
>
>
>
>-- 
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl

Re: [FLEXLS]when Flex js release?

[Mark Shen]

how to download artefacrs?  what us the  url?

Thanks Erik

Mark


On Tue, Nov 5, 2013 at 9:52 AM, Erik de Bruin  wrote:

> We're working steadily towards an alpha quality release. There are a
> few issues that remain to be fixed (help is very welcome!) and some
> features that we'd like to have are still missing.
>
> Since this is a volunteer effort, and we currently have fewer
> volunteers than we have eager (future) users, so things take some time
> to get done.
>
> You can help out by downloading the artefacts and help us pinpoint
> areas that need some TLC.
>
> Thank you,
>
> EdB
>
>
>
> On Tue, Nov 5, 2013 at 3:42 PM, Mark Shen  wrote:
> > Anyone know this? Thanks.
> >
> > Mark
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

RE: [FLEXJS] describeType

[Maurice Amsellem]

That's also the way it's implemented in Parsley, but the wrapper class can be 
very simple:

[from parsley]
package avmplus {

public class DescribeTypeJSONAccessor {

public static function get functionRef () : Function {
try {
return describeTypeJSON;
}
catch (e:Error) {
}
return null;
}

But its really worth using  compared to describeType:
- faster
- much less memory
- can extract only the needed information, thanks to flags arguments

-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl] 
Envoyé : mardi 5 novembre 2013 20:22
À : dev@flex.apache.org
Objet : Re: [FLEXJS] describeType

Wow.

Getting this to work involves creating a wrapper class around an undocumented 
method in playerglobal.swc, which is not under our control.

That doesn't sound like a sustainable way forward :-(

EdB



On Tue, Nov 5, 2013 at 7:02 PM, Alex Harui  wrote:
> Told you it was under-documented ;-). The secret handshake is 
> apparently to ignore autocomplete and use google.  Looks like it is 
> avmplus.describeTypeJSON().  I've not used it, but there was a recent 
> thread about it.
>
> On 11/5/13 9:54 AM, "Erik de Bruin"  wrote:
>
>>My FlashBuilder's autocomplete is not aware of such a method. Any 
>>secret handshakes I should be aware of to activate it?
>>
>>EdB
>>
>>
>>
>>On Tue, Nov 5, 2013 at 6:32 PM, Alex Harui  wrote:
>>> Apparently, there is a under-documented describeTypeJSON which I 
>>>think the  application frameworks are using to get any and all 
>>>metadata on a class  and its methods because it is much faster than 
>>>regular describeType.
>>> Maybe we should do that.
>>>
>>> -Alex
>>>
>>> On 11/5/13 5:42 AM, "Erik de Bruin"  wrote:
>>>
Hi,

flash.utils.describeType has an XML return type. JavaScript doesn't 
have anything like that and I'm sure we don't want to simulate it 
for the purpose of this exercise.

I suggest we create a utility class
"org.apache.flex.utils.DescribeType" and put some static methods on 
it that allow us to get tailored introspection... Maybe start with 
'DescribeType.getMetaData(value:*)'?

What metadata are you thinking of, specifically?

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

Re: please UNSUBSCRIBE me

[Deborah Krikun]

ok will try from dkri...@me.comthank you so much for helping me - Deb KDeborah Krikun
Associate Professor, Digital Arts
Westchester Community College, 
Center for the Digital Arts
Peekskill, NY
914-606-7300
Phone: 914.606.7359 (msg) 606-7300 (main)
Email: deborah.kri...@sunywcc.edu
Websites: www.sunywcc.edu/peekskill
On Nov 05, 2013, at 02:54 PM, Alex Harui  wrote:Actually, she's tried that and failed.  Deborah, it appears you subscribed using a me.com email address and maybe those emails are being forwarded to wherever you are reading this. To unsubscribe, you will need to send an email from the me.com address.  -Alex  On 11/5/13 11:47 AM, "Erik de Bruin"  wrote: Please send an email to 'dev-unsubscr...@flex.apache.org'.EdBOn Tue, Nov 5, 2013 at 8:40 PM, Deborah Krikun  wrote:THIS IS A TEXT EMAILDeborah KrikunAssociate Professor, Digital ArtsWestchester Community College,Center for the Digital ArtsPeekskill, NY914-606-7300Phone: 914.606.7359 (msg) 606-7300 (main)Email: deborah.kri...@sunywcc.eduWebsites: www.sunywcc.edu/peekskill--Ix Multimedia SoftwareJan Luykenstraat 273521 VB UtrechtT. 06-51952295I. www.ixsoftware.nl

RE: ActionScript coding conventions

[Maurice Amsellem]

Is it legal to copy them to our Apache Flex wiki ?

I can do it, and also restore the formatting...

Maurice 

-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl] 
Envoyé : mardi 5 novembre 2013 19:25
À : dev@flex.apache.org
Objet : Re: ActionScript coding conventions

I don't think we copied them over to Apache Flex yet... All I could find was 
this:

http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/

EdB



On Tue, Nov 5, 2013 at 7:16 PM, Gordon Smith  wrote:
> Didn't we used to have a coding conventions document for committers to 
> follow? I can't find it anywhere on the site.
>
> - Gordon
>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: ActionScript coding conventions

[Alex Harui]

Yes because it is CC-BY-SA.  That is not universally true for other Adobe
content.

Even though there is no words about attribution with the license, it might
be smart to link to the adobe wiki and give some sort of attribution.

Also, be forewarned, you might be sparking a long discussion about whether
certain of these conventions should be adopted.  Folks are not in favor of
all of them.

Good luck,
-Alex

On 11/5/13 12:01 PM, "Maurice Amsellem" 
wrote:

>Is it legal to copy them to our Apache Flex wiki ?
>
>I can do it, and also restore the formatting...
>
>Maurice 
>
>-Message d'origine-
>De : Erik de Bruin [mailto:e...@ixsoftware.nl]
>Envoyé : mardi 5 novembre 2013 19:25
>À : dev@flex.apache.org
>Objet : Re: ActionScript coding conventions
>
>I don't think we copied them over to Apache Flex yet... All I could find
>was this:
>
>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/
>
>EdB
>
>
>
>On Tue, Nov 5, 2013 at 7:16 PM, Gordon Smith  wrote:
>> Didn't we used to have a coding conventions document for committers to
>>follow? I can't find it anywhere on the site.
>>
>> - Gordon
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl

[FlexJS] DataGrid

[Peter Ent]

Hi,

I've updated FlexJS with a DataGrid component. There is both an ActionScript 
and a JavaScript version. I also added an example application. I'll update some 
Wiki pages either today or tomorrow with an explanation of the component. This 
DataGrid is a basic shell that is a composed of a ButtonBar for the header and 
Lists for the columns and uses a simple itemRenderer for the cells.

In case you weren't aware, one of the key features of FlexJS is its use of 
styles to provide default component beads. For example, you can specify which 
bead to use to draw a button. This aspect of FlexJS was not present in the 
JavaScript side until recently when Alex Harui added that capability; before 
Alex's change the JavaScript version of a component had its beads hard-coded. 
While creating the DataGrid component I changed a few other components to 
extracting their beads from the style sheet which cleaned them up a quite a 
bit. There is still more work to do on that front but so far it works quite 
well.

Regards,
Peter Ent
Flex SDK Team
Adobe Systems

RE: ActionScript coding conventions

[Gordon Smith]

> it might be smart to link to the adobe wiki and give some sort of attribution.

If we simply link to 
http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then people 
will see wiki markup rather than the intended HTML.

> Also, be forewarned, you might be sparking a long discussion about whether 
> certain of these conventions should be adopted.  Folks are not in favor of 
> all of them.

The fact remains that most of the existing SDK code follows -- not exactly, but 
mostly -- these conventions. IMHO it doesn't make much sense to change the 
conventions unless someone is willing to also change the code so that the two 
things are in sync.

- Gordon


-Original Message-
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: Tuesday, November 05, 2013 12:10 PM
To: dev@flex.apache.org
Subject: Re: ActionScript coding conventions

Yes because it is CC-BY-SA.  That is not universally true for other Adobe 
content.

Even though there is no words about attribution with the license, it might be 
smart to link to the adobe wiki and give some sort of attribution.

Also, be forewarned, you might be sparking a long discussion about whether 
certain of these conventions should be adopted.  Folks are not in favor of all 
of them.

Good luck,
-Alex

On 11/5/13 12:01 PM, "Maurice Amsellem" 
wrote:

>Is it legal to copy them to our Apache Flex wiki ?
>
>I can do it, and also restore the formatting...
>
>Maurice
>
>-Message d'origine-
>De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 5 
>novembre 2013 19:25 À : dev@flex.apache.org Objet : Re: ActionScript 
>coding conventions
>
>I don't think we copied them over to Apache Flex yet... All I could 
>find was this:
>
>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/
>
>EdB
>
>
>
>On Tue, Nov 5, 2013 at 7:16 PM, Gordon Smith  wrote:
>> Didn't we used to have a coding conventions document for committers 
>>to follow? I can't find it anywhere on the site.
>>
>> - Gordon
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl

Re: ActionScript coding conventions

[Alex Harui]

On 11/5/13 1:05 PM, "Gordon Smith"  wrote:

>> it might be smart to link to the adobe wiki and give some sort of
>>attribution.
>
>If we simply link to
>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then
>people will see wiki markup rather than the intended HTML.
Sorry, wasn't clear.

We have our nice copy but somewhere in a footer mention that the original
is from Adobe and lives at sourceforge and here's the link to it.


-Alex

RE: ActionScript coding conventions

[Maurice Amsellem]

>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.
Yes, that's also what I understood.

Maurice

-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] 
Envoyé : mardi 5 novembre 2013 22:08
À : dev@flex.apache.org
Objet : Re: ActionScript coding conventions

On 11/5/13 1:05 PM, "Gordon Smith"  wrote:

>> it might be smart to link to the adobe wiki and give some sort of 
>>attribution.
>
>If we simply link to
>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then 
>people will see wiki markup rather than the intended HTML.
Sorry, wasn't clear.

We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.


-Alex

RE: ActionScript coding conventions

[Maurice Amsellem]

What is the "---" wiki on its own line?  Is it to underline the text above ?

-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] 
Envoyé : mardi 5 novembre 2013 22:30
À : dev@flex.apache.org
Objet : RE: ActionScript coding conventions

>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.
Yes, that's also what I understood.

Maurice

-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013 22:08 
À : dev@flex.apache.org Objet : Re: ActionScript coding conventions

On 11/5/13 1:05 PM, "Gordon Smith"  wrote:

>> it might be smart to link to the adobe wiki and give some sort of 
>>attribution.
>
>If we simply link to
>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then 
>people will see wiki markup rather than the intended HTML.
Sorry, wasn't clear.

We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.


-Alex

RE: ActionScript coding conventions

[Maurice Amsellem]

https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices

Can you please review.

Maurice 

-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] 
Envoyé : mardi 5 novembre 2013 22:47
À : dev@flex.apache.org
Objet : RE: ActionScript coding conventions

What is the "---" wiki on its own line?  Is it to underline the text above ?

-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 5 novembre 2013 22:30
À : dev@flex.apache.org
Objet : RE: ActionScript coding conventions

>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.
Yes, that's also what I understood.

Maurice

-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013 22:08 
À : dev@flex.apache.org Objet : Re: ActionScript coding conventions

On 11/5/13 1:05 PM, "Gordon Smith"  wrote:

>> it might be smart to link to the adobe wiki and give some sort of 
>>attribution.
>
>If we simply link to
>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then 
>people will see wiki markup rather than the intended HTML.
Sorry, wasn't clear.

We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.


-Alex

Re: ActionScript coding conventions

[Justin Mclean]

Hi,

> https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices

While the SDK generally follows most of these rules it's not 100% consistent, 
so probably should be noted that you should use local conventions in the case 
the SDK code varies from these rules.

Notice a couple of formatting issues on a quick look though - will details them 
later today when I have more time.

Thanks,
Justin

RE: ActionScript coding conventions

[Maurice Amsellem]

>While the SDK generally follows most of these rules it's not 100% consistent, 
>so probably should be noted that you should use local conventions in the case 
>the SDK code varies from >these rules.

There is something close to this statement in "Exceptions to formatting rules". 

 Is it enough ?

-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com] 
Envoyé : mercredi 6 novembre 2013 00:20
À : dev@flex.apache.org
Objet : Re: ActionScript coding conventions

Hi,

> https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices

While the SDK generally follows most of these rules it's not 100% consistent, 
so probably should be noted that you should use local conventions in the case 
the SDK code varies from these rules.

Notice a couple of formatting issues on a quick look though - will details them 
later today when I have more time.

Thanks,
Justin

RE: ActionScript coding conventions

[Gordon Smith]

It looks great, Maurice! The only thing I noticed in a quick lookover is that 
the major and minor section separators are supposed to look like this:



//--

//

//  Properties

//

//--



(columns 4 through 80)



//--

//  width

//--



(columns 4 through 40)



- Gordon



-Original Message-
From: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Sent: Tuesday, November 05, 2013 3:08 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions



https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices



Can you please review.



Maurice



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:47

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



What is the "---" wiki on its own line?  Is it to underline the text above ?



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:30

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.

Yes, that's also what I understood.



Maurice



-Message d'origine-

De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013 22:08 
À : dev@flex.apache.org Objet : Re: ActionScript 
coding conventions



On 11/5/13 1:05 PM, "Gordon Smith" 
mailto:gosm...@adobe.com>> wrote:



>> it might be smart to link to the adobe wiki and give some sort of

>>attribution.

>

>If we simply link to

>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then

>people will see wiki markup rather than the intended HTML.

Sorry, wasn't clear.



We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.





-Alex

RE: ActionScript coding conventions

[Maurice Amsellem]

Thanks for reviewing.
This is now fixed (was: hazardous global copy/replace :-) 

Maurice 

-Message d'origine-
De : Gordon Smith [mailto:gosm...@adobe.com] 
Envoyé : mercredi 6 novembre 2013 02:11
À : dev@flex.apache.org
Objet : RE: ActionScript coding conventions

It looks great, Maurice! The only thing I noticed in a quick lookover is that 
the major and minor section separators are supposed to look like this:



//--

//

//  Properties

//

//--



(columns 4 through 80)



//--

//  width

//--



(columns 4 through 40)



- Gordon



-Original Message-
From: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Sent: Tuesday, November 05, 2013 3:08 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions



https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices



Can you please review.



Maurice



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:47

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



What is the "---" wiki on its own line?  Is it to underline the text above ?



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:30

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.

Yes, that's also what I understood.



Maurice



-Message d'origine-

De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013 22:08 
À : dev@flex.apache.org Objet : Re: ActionScript 
coding conventions



On 11/5/13 1:05 PM, "Gordon Smith" 
mailto:gosm...@adobe.com>> wrote:



>> it might be smart to link to the adobe wiki and give some sort of

>>attribution.

>

>If we simply link to

>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then

>people will see wiki markup rather than the intended HTML.

Sorry, wasn't clear.



We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.





-Alex

RE: ActionScript coding conventions

[Gordon Smith]

Hmm... somewhere along the line extra blank lines are getting inserted by 
somebody's email system.

- Gordon

-Original Message-
From: Gordon Smith [mailto:gosm...@adobe.com] 
Sent: Tuesday, November 05, 2013 5:11 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions

It looks great, Maurice! The only thing I noticed in a quick lookover is that 
the major and minor section separators are supposed to look like this:



//--

//

//  Properties

//

//--



(columns 4 through 80)



//--

//  width

//--



(columns 4 through 40)



- Gordon



-Original Message-
From: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Sent: Tuesday, November 05, 2013 3:08 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions



https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices



Can you please review.



Maurice



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:47

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



What is the "---" wiki on its own line?  Is it to underline the text above ?



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:30

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.

Yes, that's also what I understood.



Maurice



-Message d'origine-

De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013 22:08 
À : dev@flex.apache.org Objet : Re: ActionScript 
coding conventions



On 11/5/13 1:05 PM, "Gordon Smith" 
mailto:gosm...@adobe.com>> wrote:



>> it might be smart to link to the adobe wiki and give some sort of

>>attribution.

>

>If we simply link to

>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then

>people will see wiki markup rather than the intended HTML.

Sorry, wasn't clear.



We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.





-Alex

RE: ActionScript coding conventions

[Gordon Smith]

BTW, the section separators under "Class metadata" also got shortened.

- Gordon

-Original Message-
From: Gordon Smith [mailto:gosm...@adobe.com] 
Sent: Tuesday, November 05, 2013 5:20 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions

Hmm... somewhere along the line extra blank lines are getting inserted by 
somebody's email system.

- Gordon

-Original Message-
From: Gordon Smith [mailto:gosm...@adobe.com] 
Sent: Tuesday, November 05, 2013 5:11 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions

It looks great, Maurice! The only thing I noticed in a quick lookover is that 
the major and minor section separators are supposed to look like this:



//--

//

//  Properties

//

//--



(columns 4 through 80)



//--

//  width

//--



(columns 4 through 40)



- Gordon



-Original Message-
From: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Sent: Tuesday, November 05, 2013 3:08 PM
To: dev@flex.apache.org
Subject: RE: ActionScript coding conventions



https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices



Can you please review.



Maurice



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:47

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



What is the "---" wiki on its own line?  Is it to underline the text above ?



-Message d'origine-

De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]

Envoyé : mardi 5 novembre 2013 22:30

À : dev@flex.apache.org

Objet : RE: ActionScript coding conventions



>We have our nice copy but somewhere in a footer mention that the original is 
>from Adobe and lives at sourceforge and here's the link to it.

Yes, that's also what I understood.



Maurice



-Message d'origine-

De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013 22:08 
À : dev@flex.apache.org Objet : Re: ActionScript 
coding conventions



On 11/5/13 1:05 PM, "Gordon Smith" 
mailto:gosm...@adobe.com>> wrote:



>> it might be smart to link to the adobe wiki and give some sort of

>>attribution.

>

>If we simply link to

>http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then

>people will see wiki markup rather than the intended HTML.

Sorry, wasn't clear.



We have our nice copy but somewhere in a footer mention that the original is 
from Adobe and lives at sourceforge and here's the link to it.





-Alex

Re: ActionScript coding conventions

[Mark Kessler]

That looks a lot better than the other formatting.  Good work.

-Mark


On Tue, Nov 5, 2013 at 6:08 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:

>
> https://cwiki.apache.org/confluence/display/FLEX/Flex+SDK+coding+conventions+and+best+practices
>
> Can you please review.
>
> Maurice
>
> -Message d'origine-
> De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
> Envoyé : mardi 5 novembre 2013 22:47
> À : dev@flex.apache.org
> Objet : RE: ActionScript coding conventions
>
> What is the "---" wiki on its own line?  Is it to underline the text above
> ?
>
> -Message d'origine-
> De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
> Envoyé : mardi 5 novembre 2013 22:30
> À : dev@flex.apache.org
> Objet : RE: ActionScript coding conventions
>
> >We have our nice copy but somewhere in a footer mention that the original
> is from Adobe and lives at sourceforge and here's the link to it.
> Yes, that's also what I understood.
>
> Maurice
>
> -Message d'origine-
> De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 5 novembre 2013
> 22:08 À : dev@flex.apache.org Objet : Re: ActionScript coding conventions
>
> On 11/5/13 1:05 PM, "Gordon Smith"  wrote:
>
> >> it might be smart to link to the adobe wiki and give some sort of
> >>attribution.
> >
> >If we simply link to
> >http://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/ then
> >people will see wiki markup rather than the intended HTML.
> Sorry, wasn't clear.
>
> We have our nice copy but somewhere in a footer mention that the original
> is from Adobe and lives at sourceforge and here's the link to it.
>
>
> -Alex
>
>

Project voting guidelines

[Justin Mclean]

Hi,

Despite Alex's efforts this seem to have stalled:
http://mail-archives.apache.org/mod_mbox/incubator-general/201310.mbox/%3cce743d6a.14a96%25aha...@adobe.com%3e

With a few voting issues coming up recently I think it time to consider having 
our own guidelines. 

Here some I put together from other Apache projects in combination how we have 
been working as a project:
https://cwiki.apache.org/confluence/display/FLEX/Draft+Guidelines

Recent changes include:
- removed any mention of what defines an "active" committer or PMC member as 
it's controversial and can be easily gamed
- put in some expected (but not required) committer responsibilities
- filled in what are the default the voting rules

There are some difference from the "default" Apache guidelines
- Committers can veto checkins (seems a better match to me - not that there 
have been many veto's)
- Release candidate votes can be carry over to the next RC by a release manager 
if they so desire
- I also put the length of the Chair as a year with the option of them to stand 
for another year as that to me seem the fairest way to share that 
responsibility.

Feedback is welcome.

Thanks,
Justin

Re: Project voting guidelines

[Mark Kessler]

Looks reasonable.  It's nice to have it all down in one place as well.

-Mark


On Tue, Nov 5, 2013 at 10:28 PM, Justin Mclean wrote:

> Hi,
>
> Despite Alex's efforts this seem to have stalled:
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201310.mbox/%3cce743d6a.14a96%25aha...@adobe.com%3e
>
> With a few voting issues coming up recently I think it time to consider
> having our own guidelines.
>
> Here some I put together from other Apache projects in combination how we
> have been working as a project:
> https://cwiki.apache.org/confluence/display/FLEX/Draft+Guidelines
>
> Recent changes include:
> - removed any mention of what defines an "active" committer or PMC member
> as it's controversial and can be easily gamed
> - put in some expected (but not required) committer responsibilities
> - filled in what are the default the voting rules
>
> There are some difference from the "default" Apache guidelines
> - Committers can veto checkins (seems a better match to me - not that
> there have been many veto's)
> - Release candidate votes can be carry over to the next RC by a release
> manager if they so desire
> - I also put the length of the Chair as a year with the option of them to
> stand for another year as that to me seem the fairest way to share that
> responsibility.
>
> Feedback is welcome.
>
> Thanks,
> Justin

Re: ActionScript coding conventions

[Justin Mclean]

Hi,

There's a minor formatting issue here I think.
Use '' only if the value can be 'undefined'. You should generally use 'Object' 
rather than '', with 'null' being the “object doesn't exist” value.

I assume it should be * inside the single quotes.

Thanks,
Justin

RE: [FlexJS] DataGrid

[Sugan Naicker]

Hi,

Thanks Peter!

Regards,

Sugan Naicker
South Africa

-Original Message-
From: Peter Ent [mailto:p...@adobe.com] 
Sent: 05 November 2013 10:20 PM
To: dev@flex.apache.org; us...@flex.apache.org
Subject: [FlexJS] DataGrid

Hi,

I've updated FlexJS with a DataGrid component. There is both an ActionScript
and a JavaScript version. I also added an example application. I'll update
some Wiki pages either today or tomorrow with an explanation of the
component. This DataGrid is a basic shell that is a composed of a ButtonBar
for the header and Lists for the columns and uses a simple itemRenderer for
the cells.

In case you weren't aware, one of the key features of FlexJS is its use of
styles to provide default component beads. For example, you can specify
which bead to use to draw a button. This aspect of FlexJS was not present in
the JavaScript side until recently when Alex Harui added that capability;
before Alex's change the JavaScript version of a component had its beads
hard-coded. While creating the DataGrid component I changed a few other
components to extracting their beads from the style sheet which cleaned them
up a quite a bit. There is still more work to do on that front but so far it
works quite well.

Regards,
Peter Ent
Flex SDK Team
Adobe Systems

Re: ActionScript coding conventions

[Justin Mclean]

Hi,

Also right towards the bottom there's "i < n; " instead of "i < n".  I can 
fix that if you want.

Thanks,
Justin

Re: Project voting guidelines

[Erik de Bruin]

Hi,

"- Release candidate votes can be carry over to the next RC by a
release manager if they so desire"

I would suggest that we add something like: "and if it's
uncontroversial to do so." Where uncontroversial means: no one
objects. Otherwise a release manager could conceivably get the votes
he needs for one RC, then cut another one with undesirable changes in
it and release with the votes from the first one...

EdB



On Wed, Nov 6, 2013 at 4:38 AM, Mark Kessler
 wrote:
> Looks reasonable.  It's nice to have it all down in one place as well.
>
> -Mark
>
>
> On Tue, Nov 5, 2013 at 10:28 PM, Justin Mclean 
> wrote:
>
>> Hi,
>>
>> Despite Alex's efforts this seem to have stalled:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201310.mbox/%3cce743d6a.14a96%25aha...@adobe.com%3e
>>
>> With a few voting issues coming up recently I think it time to consider
>> having our own guidelines.
>>
>> Here some I put together from other Apache projects in combination how we
>> have been working as a project:
>> https://cwiki.apache.org/confluence/display/FLEX/Draft+Guidelines
>>
>> Recent changes include:
>> - removed any mention of what defines an "active" committer or PMC member
>> as it's controversial and can be easily gamed
>> - put in some expected (but not required) committer responsibilities
>> - filled in what are the default the voting rules
>>
>> There are some difference from the "default" Apache guidelines
>> - Committers can veto checkins (seems a better match to me - not that
>> there have been many veto's)
>> - Release candidate votes can be carry over to the next RC by a release
>> manager if they so desire
>> - I also put the length of the Chair as a year with the option of them to
>> stand for another year as that to me seem the fairest way to share that
>> responsibility.
>>
>> Feedback is welcome.
>>
>> Thanks,
>> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: Project voting guidelines

[Justin Mclean]

Hi,

> I would suggest that we add something like: "and if it's
> uncontroversial to do so." Where uncontroversial means: no one
> objects. 
People could object by voting -1 right away but point taken. How about ading 
"when there is minimal changes between release candidates"?

Justin

Flex Application Demo.

[SHIVANG SANGHI]

Hi,

I have developed an Tshirt Designer Application using Flex 4.6 . If the
apache dev/user team want to submit this application as a demo then i will
definitely convert this application in Apache Flex 4.10/4.11 . Below is the
running application url.

http://www.inkfi.com/demo/wpflex/online-designer-tool/

Please give your feedbacks and comments also..
I feel myself very proud if anyone suggest me something or this project
will be included in Flex list.

*Regards,*

*SHIVANG SANGHI*
*09871198444,09548998118*
*shivangsan...@gmail.com ,shivangsan...@yahoo.com
*

Re: Project voting guidelines

[Erik de Bruin]

Yes, that captures the spirit without sounding too legalese ;-)

EdB



On Wed, Nov 6, 2013 at 6:15 AM, Justin Mclean  wrote:
> Hi,
>
>> I would suggest that we add something like: "and if it's
>> uncontroversial to do so." Where uncontroversial means: no one
>> objects.
> People could object by voting -1 right away but point taken. How about ading 
> "when there is minimal changes between release candidates"?
>
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

RE: ActionScript coding conventions

[Maurice Amsellem]

please

-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com] 
Envoyé : mercredi 6 novembre 2013 04:58
À : dev@flex.apache.org
Objet : Re: ActionScript coding conventions

Hi,

Also right towards the bottom there's "i < n; " instead of "i < n".  I can 
fix that if you want.

Thanks,
Justin

[FLEXJS] JS framework: gjslint

[Erik de Bruin]

Hi,

I would like to run the entire JS framework through the 'gjslint'
tool. This is the JS linter provided by Google to check code that is
to be processed by the Closure Compiler.

It has some very strict whitespace rules, that will result in changes
in most files (although we started out with a clean, gjslint approved
version a long while ago, when I implemented 'goog' event handling).

The main advantages are that all code will be consistently formatted
and that it will most likely catch some annotation and related
errors/omissions.

If no one (Alex, Peter) has commits pending, I am ready to go.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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