date:20130324

Re: Git Push Summary

2013-03-24 Thread Justin Mclean

Hi,

Nice to know what repo this was :-)

> Updated Branches:
>  refs/heads/develop [created] 5e461b06f


Justin

FXG -> SVG progress

2013-03-24 Thread Om

On Fri, Mar 22, 2013 at 6:48 AM, Alex Harui  wrote:

>
>
>
> On 3/22/13 12:36 AM, "Erik de Bruin"  wrote:
>
> > I think both the FlexJS as well as VanillaSDK frameworks can benefit
> > from this. So it should be available to both. I don't know much about
> > XSLT, but if it 'converts one into another', I think it should
> > ultimately go with that other thing that 'converts one into another',
> > FalconJx.
> >
> > But for now, as it is a work in progress, I think it's best place is
> > in ASJS, in the root, next to my 'publisher'. The publisher was also a
> > proof of concept, that has since been integrated into FalconJx.
> >
> > Clear as mud, right?
> >
> I hope to get a look at FalconJX shortly, but in theory, you haven't
> changed
> the FXG subcompiler and I think that's where this XSLT will eventually go.
>
>
I have checked in the first cut of the "FXG to SVG" XSLTfile here [1]

Here is a very simple Flex app with three Rectangles, one with a a
SolidColor fill and two with LinearGradient fills:

Flex version:
http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.html (right
click for source)

Using the XSLT file, I transformed it into its equivalent

SVG version:
http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.svg.html(right
click for source)

The SVG version uses  and inline CSS to style the different elements.

To my naked eye, they both look pretty much the same.  After this
experiment, I am halfway convinced that this is a viable approach to carry
over Flex's Spark based skins into the HTML5/SVG world.

I have identified a few problems that I will be tackling next:

1.  States
2.  Tackling the ILayoutElement interface usage (i.e. usage of left, right,
etc. constraints)
3.  Transform Other Shapes, etc.
4.  Get a Spark component's skin to work in HTML5/SVG

I have a few ideas that I will be trying out.  If anyone wants to take a
peek at the XSLT file and modify it  or has any ideas they would like to
see me implement, that would be great.

Thanks,
Om

[1]
https://git-wip-us.apache.org/repos/asf?p=flex-asjs.git;a=blob;f=fxg2svg/transform.xslt;h=df474c463f3fcc2701db063e691f3a4f29f217a6;hb=develop

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Justin Mclean

Hi,

> Would you mind if I wrote up a proposed alternate that doesn't use rebase and 
> eliminate fast forwards? Yes, it will mean there is an extra 'useless' 
> commit... which I don't actually always find useless, but I think it simpler. 
> Then let's just discuss.

+1 to at least considering this. 

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Erik de Bruin

+ 1 on starting out simple and keeping the message clear.

When needed, or as a suggested way to work for those who have a better
than "noob" level understanding of git, I think we should keep the
"rebase" workflow in the wiki. Furthermore, we should write up as much
of this discussion in the wiki as we can, for future reference.

EdB

On Sun, Mar 24, 2013 at 10:04 AM, Justin Mclean
 wrote:
> Hi,
>
>> Would you mind if I wrote up a proposed alternate that doesn't use rebase 
>> and eliminate fast forwards? Yes, it will mean there is an extra 'useless' 
>> commit... which I don't actually always find useless, but I think it 
>> simpler. Then let's just discuss.
>
> +1 to at least considering this.
>
> Justin

-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [4/4] git commit: Updated .gitignore

2013-03-24 Thread Erik de Bruin

Fred,

I'm afraid that with these generic terms in .gitignore, there is the
risk that at some point too much is excluded. Remember, most active
committers are noobs at git, and when someone want to actually add an
"out" directory to the project, he/she wouldn't see it in git because
it is automatically ignored.

I think that apart from the IDE specific files (and I'm not even sure
about those...), only the files that actually need to be ignored
should be ignored.

EdB



On Sat, Mar 23, 2013 at 11:08 AM, Frédéric THOMAS
 wrote:
> Erik,
>
> Why not let the generic build path targets [1] excluded ?
>
> -Fred
>
> [1]
> # building
> target
> [Bb]uild/
> null
> tmp
> temp
> dist
> test-output
> build.log
> release
> out
> gen
>
> -Message d'origine- From: erikdebr...@apache.org
> Sent: Saturday, March 23, 2013 10:15 AM
> To: comm...@flex.apache.org
> Subject: [4/4] git commit: Updated .gitignore
>
>
> Updated .gitignore
>
> Removed generic patterns from 'main' .gitignore, only left OS 'stuff' and
> IDE specific files.
>
> Added project specific patterns to all 5 new .gitignore files.
>
> Signed-off-by: Erik de Bruin 
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-falcon/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-falcon/commit/3a1e5354
> Tree: http://git-wip-us.apache.org/repos/asf/flex-falcon/tree/3a1e5354
> Diff: http://git-wip-us.apache.org/repos/asf/flex-falcon/diff/3a1e5354
>
> Branch: refs/heads/develop
> Commit: 3a1e5354fd09baa8fc88de6f2324d0cf57f3dec8
> Parents: 1fddafc
> Author: Erik de Bruin 
> Authored: Sat Mar 23 10:15:22 2013 +0100
> Committer: Erik de Bruin 
> Committed: Sat Mar 23 10:15:22 2013 +0100
>
> --
> .gitignore   |   99 +
> compiler.js/.gitignore   |5 ++
> compiler.jx.tests/.gitignore |3 +
> compiler.jx/.gitignore   |3 +
> compiler.tests/.gitignore|4 ++
> compiler/.gitignore  |2 +
> 6 files changed, 18 insertions(+), 98 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/.gitignore
> --
> diff --git a/.gitignore b/.gitignore
> index c0b59e3..ce08f0b 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -12,103 +12,6 @@
> *.ipr
> *.iws
>
> -# building
> -target
> -[Bb]uild/
> -null
> -tmp
> -temp
> -dist
> -test-output
> -build.log
> -release
> -out
> -gen
> -
> -#Apache Flex Projects
> -lib/
> -libs/
> -in/
> -swfobject/
> -ide/
> -flex2/
> -thirdparty/
> -META-INF/
> -3.0.33/
> -3.0.33
> -intermediates/
> -results/
> -generated/
> -
> -*.pbj
> -*.vms
> -*.ser
> -*.mxp
> -bundles.properties
> -empty.properties
> -css_*.properties
> -FXGException_*.properties
> -FXGLog_*.properties
> -FABridge.js
> -frameworks/projects/spark/manifest.xml
> -env.properties
> -local.properties
> -flex-sdk-description.xml
> -
> #OS junk files
> [Tt]humbs.db
> -*.DS_Store
> -
> -#Visual Studio files
> -*.[Oo]bj
> -*.user
> -*.aps
> -*.pch
> -*.vspscc
> -*.vssscc
> -*_i.c
> -*_p.c
> -*.ncb
> -*.suo
> -*.tlb
> -*.tlh
> -*.bak
> -*.[Cc]ache
> -*.ilk
> -*.log
> -*.lib
> -*.sbr
> -*.sdf
> -ipch/
> -obj/
> -[Bb]in
> -[Dd]ebug*/
> -[Rr]elease*/
> -Ankh.NoLoad
> -
> -#Tooling
> -_ReSharper*/
> -*.resharper
> -[Tt]est[Rr]esult*
> -
> -#CVS files
> -.svn
> -.git
> -
> -# Office Temp Files
> -~$*
> -
> -#Binaries
> -*.dll
> -*.bin
> -*.com
> -*.exe
> -*.class
> -*.jar
> -*.swf
> -*.swc
> -
> -#Compressed Files
> -*.zip
> -*.rar
> -*.tar
> \ No newline at end of file
> +*.DS_Store
> \ No newline at end of file
>
> http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/compiler.js/.gitignore
> --
> diff --git a/compiler.js/.gitignore b/compiler.js/.gitignore
> index 42e99b1..d3bc09e 100644
> --- a/compiler.js/.gitignore
> +++ b/compiler.js/.gitignore
> @@ -1 +1,6 @@
> # ignored files/directories for the 'compiler.js' project
> +/build
> +/classes
> +/in
> +/intermediates
> +/lib
> \ No newline at end of file
>
> http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/compiler.jx.tests/.gitignore
> --
> diff --git a/compiler.jx.tests/.gitignore b/compiler.jx.tests/.gitignore
> index 7dce427..f08a076 100644
> --- a/compiler.jx.tests/.gitignore
> +++ b/compiler.jx.tests/.gitignore
> @@ -1 +1,4 @@
> # ignored files/directories for the 'compiler.jx.tests' project
> +/classes
> +/lib
> +/results
> \ No newline at end of file
>
> http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/compiler.jx/.gitignore
> --
> diff --git a/compiler.jx/.gitignore b/compiler.jx/.gitignore
> index 283d397..32c8982 100644
> --- a/compiler.jx/.gitignore
> +++ b/

Re: [4/4] git commit: Updated .gitignore

2013-03-24 Thread Frédéric THOMAS


Hi Erik,

Just a suggestion as I don't use those repo:

The removed # building section was also IDE targets, actually, because we 
never know with what IDE the people will work, I guess it is better to keep 
them excluded, otherwise the people can be also confuse by the bunch of 
untracked files, if you want include \out just, do 
that :


#Exclude all out
out
#Except this one
!\out

Could be even documented in the wiki.

Thanks,
-Fred

-Message d'origine- 
From: Erik de Bruin

Sent: Sunday, March 24, 2013 11:54 AM
To: dev@flex.apache.org
Subject: Re: [4/4] git commit: Updated .gitignore

Fred,

I'm afraid that with these generic terms in .gitignore, there is the
risk that at some point too much is excluded. Remember, most active
committers are noobs at git, and when someone want to actually add an
"out" directory to the project, he/she wouldn't see it in git because
it is automatically ignored.

I think that apart from the IDE specific files (and I'm not even sure
about those...), only the files that actually need to be ignored
should be ignored.

EdB



On Sat, Mar 23, 2013 at 11:08 AM, Frédéric THOMAS
 wrote:

Erik,

Why not let the generic build path targets [1] excluded ?

-Fred

[1]
# building
target
[Bb]uild/
null
tmp
temp
dist
test-output
build.log
release
out
gen

-Message d'origine- From: erikdebr...@apache.org
Sent: Saturday, March 23, 2013 10:15 AM
To: comm...@flex.apache.org
Subject: [4/4] git commit: Updated .gitignore


Updated .gitignore

Removed generic patterns from 'main' .gitignore, only left OS 'stuff' and
IDE specific files.

Added project specific patterns to all 5 new .gitignore files.

Signed-off-by: Erik de Bruin 


Project: http://git-wip-us.apache.org/repos/asf/flex-falcon/repo
Commit: http://git-wip-us.apache.org/repos/asf/flex-falcon/commit/3a1e5354
Tree: http://git-wip-us.apache.org/repos/asf/flex-falcon/tree/3a1e5354
Diff: http://git-wip-us.apache.org/repos/asf/flex-falcon/diff/3a1e5354

Branch: refs/heads/develop
Commit: 3a1e5354fd09baa8fc88de6f2324d0cf57f3dec8
Parents: 1fddafc
Author: Erik de Bruin 
Authored: Sat Mar 23 10:15:22 2013 +0100
Committer: Erik de Bruin 
Committed: Sat Mar 23 10:15:22 2013 +0100

--
.gitignore   |   99 +
compiler.js/.gitignore   |5 ++
compiler.jx.tests/.gitignore |3 +
compiler.jx/.gitignore   |3 +
compiler.tests/.gitignore|4 ++
compiler/.gitignore  |2 +
6 files changed, 18 insertions(+), 98 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/.gitignore
--
diff --git a/.gitignore b/.gitignore
index c0b59e3..ce08f0b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,103 +12,6 @@
*.ipr
*.iws

-# building
-target
-[Bb]uild/
-null
-tmp
-temp
-dist
-test-output
-build.log
-release
-out
-gen
-
-#Apache Flex Projects
-lib/
-libs/
-in/
-swfobject/
-ide/
-flex2/
-thirdparty/
-META-INF/
-3.0.33/
-3.0.33
-intermediates/
-results/
-generated/
-
-*.pbj
-*.vms
-*.ser
-*.mxp
-bundles.properties
-empty.properties
-css_*.properties
-FXGException_*.properties
-FXGLog_*.properties
-FABridge.js
-frameworks/projects/spark/manifest.xml
-env.properties
-local.properties
-flex-sdk-description.xml
-
#OS junk files
[Tt]humbs.db
-*.DS_Store
-
-#Visual Studio files
-*.[Oo]bj
-*.user
-*.aps
-*.pch
-*.vspscc
-*.vssscc
-*_i.c
-*_p.c
-*.ncb
-*.suo
-*.tlb
-*.tlh
-*.bak
-*.[Cc]ache
-*.ilk
-*.log
-*.lib
-*.sbr
-*.sdf
-ipch/
-obj/
-[Bb]in
-[Dd]ebug*/
-[Rr]elease*/
-Ankh.NoLoad
-
-#Tooling
-_ReSharper*/
-*.resharper
-[Tt]est[Rr]esult*
-
-#CVS files
-.svn
-.git
-
-# Office Temp Files
-~$*
-
-#Binaries
-*.dll
-*.bin
-*.com
-*.exe
-*.class
-*.jar
-*.swf
-*.swc
-
-#Compressed Files
-*.zip
-*.rar
-*.tar
\ No newline at end of file
+*.DS_Store
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/compiler.js/.gitignore
--
diff --git a/compiler.js/.gitignore b/compiler.js/.gitignore
index 42e99b1..d3bc09e 100644
--- a/compiler.js/.gitignore
+++ b/compiler.js/.gitignore
@@ -1 +1,6 @@
# ignored files/directories for the 'compiler.js' project
+/build
+/classes
+/in
+/intermediates
+/lib
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/compiler.jx.tests/.gitignore
--
diff --git a/compiler.jx.tests/.gitignore b/compiler.jx.tests/.gitignore
index 7dce427..f08a076 100644
--- a/compiler.jx.tests/.gitignore
+++ b/compiler.jx.tests/.gitignore
@@ -1 +1,4 @@
# ignored files/directories for the 'compiler.jx.tests' project
+/classes
+/lib
+/results
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/flex-falcon/blob/3a1e5354/compiler.jx

[jira] [Commented] (FLEX-28967) PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access a property or method of a null object reference

2013-03-24 Thread Carlos Rovira (JIRA)


[ 
https://issues.apache.org/jira/browse/FLEX-28967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612071#comment-13612071
 ] 

Carlos Rovira commented on FLEX-28967:
--

The Fix by miroslav.havrlent was tested and work successfully. It was 
introduced in develop

> PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access 
> a property or method of a null object reference
> -
>
> Key: FLEX-28967
> URL: https://issues.apache.org/jira/browse/FLEX-28967
> Project: Apache Flex
>  Issue Type: Bug
>  Components: PopUp Manager
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Internet Explorer 8.x
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Carlos Rovira
>  Labels: EasyFix
>
> Steps to reproduce:
> 1. using PopUpManager
>  
> Error in the code:
> public function centerPopUp(popUp:IFlexDisplayObject):void
> {
> if (popUp is IInvalidating)
> IInvalidating(popUp).validateNow();
> const o:PopUpData = findPopupInfoByOwner(popUp);
> 
> // If we don't find the pop owner or if the owner's parent is not 
> specified or is not on the
> // stage, then center based on the popUp's current parent.
> var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
> o.parent : popUp.parent;
> if (popUpParent)
> {
> var systemManager:ISystemManager = o.systemManager;
> .
> .
> .
> .
> If const "o" is null, popUpParent is set to popUp.parent as stated by 
> condition above.
> However in next step you assume that const "o" exists because you're asking 
> for o.systemManager, but o is null.
> Therefore: TypeError: Error #1009: Cannot access a property or method of a 
> null object reference
> Fix:
> public function centerPopUp(popUp:IFlexDisplayObject):void
> {
> if (popUp is IInvalidating)
> IInvalidating(popUp).validateNow();
> const o:PopUpData = findPopupInfoByOwner(popUp);
> 
> var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
> o.parent : popUp.parent;
> if (popUpParent)
> {
>   var systemManager:ISystemManager;
>   if (o != null) {
>   systemManager = o.systemManager;
>   } else if (popUpParent.hasOwnProperty("systemManager")) 
> {
>   systemManager = popUpParent["systemManager"];
>   } else if (popUpParent is ISystemManager) {
>   systemManager = popUpParent as ISystemManager;
>   }
>   
>   if (!systemManager)
>   return; // or throw exception maybe ?
> .
> .
> .
> .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (FLEX-28967) PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access a property or method of a null object reference

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-28967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira reassigned FLEX-28967:


Assignee: Carlos Rovira

> PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access 
> a property or method of a null object reference
> -
>
> Key: FLEX-28967
> URL: https://issues.apache.org/jira/browse/FLEX-28967
> Project: Apache Flex
>  Issue Type: Bug
>  Components: PopUp Manager
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Internet Explorer 8.x
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Carlos Rovira
>  Labels: EasyFix
>
> Steps to reproduce:
> 1. using PopUpManager
>  
> Error in the code:
> public function centerPopUp(popUp:IFlexDisplayObject):void
> {
> if (popUp is IInvalidating)
> IInvalidating(popUp).validateNow();
> const o:PopUpData = findPopupInfoByOwner(popUp);
> 
> // If we don't find the pop owner or if the owner's parent is not 
> specified or is not on the
> // stage, then center based on the popUp's current parent.
> var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
> o.parent : popUp.parent;
> if (popUpParent)
> {
> var systemManager:ISystemManager = o.systemManager;
> .
> .
> .
> .
> If const "o" is null, popUpParent is set to popUp.parent as stated by 
> condition above.
> However in next step you assume that const "o" exists because you're asking 
> for o.systemManager, but o is null.
> Therefore: TypeError: Error #1009: Cannot access a property or method of a 
> null object reference
> Fix:
> public function centerPopUp(popUp:IFlexDisplayObject):void
> {
> if (popUp is IInvalidating)
> IInvalidating(popUp).validateNow();
> const o:PopUpData = findPopupInfoByOwner(popUp);
> 
> var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
> o.parent : popUp.parent;
> if (popUpParent)
> {
>   var systemManager:ISystemManager;
>   if (o != null) {
>   systemManager = o.systemManager;
>   } else if (popUpParent.hasOwnProperty("systemManager")) 
> {
>   systemManager = popUpParent["systemManager"];
>   } else if (popUpParent is ISystemManager) {
>   systemManager = popUpParent as ISystemManager;
>   }
>   
>   if (!systemManager)
>   return; // or throw exception maybe ?
> .
> .
> .
> .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: FXG -> SVG progress

2013-03-24 Thread Harbs

FYI:

The svg version does not render in Firefox (Mac 19.0.2).

In Safari and Chrome, the appearance is very close, but the svg version has a 
smoother gradient and the blue shape is missing the black stroke.

On Mar 24, 2013, at 11:01 AM, Om wrote:

> On Fri, Mar 22, 2013 at 6:48 AM, Alex Harui  wrote:
> 
>> 
>> 
>> 
>> On 3/22/13 12:36 AM, "Erik de Bruin"  wrote:
>> 
>>> I think both the FlexJS as well as VanillaSDK frameworks can benefit
>>> from this. So it should be available to both. I don't know much about
>>> XSLT, but if it 'converts one into another', I think it should
>>> ultimately go with that other thing that 'converts one into another',
>>> FalconJx.
>>> 
>>> But for now, as it is a work in progress, I think it's best place is
>>> in ASJS, in the root, next to my 'publisher'. The publisher was also a
>>> proof of concept, that has since been integrated into FalconJx.
>>> 
>>> Clear as mud, right?
>>> 
>> I hope to get a look at FalconJX shortly, but in theory, you haven't
>> changed
>> the FXG subcompiler and I think that's where this XSLT will eventually go.
>> 
>> 
> I have checked in the first cut of the "FXG to SVG" XSLTfile here [1]
> 
> Here is a very simple Flex app with three Rectangles, one with a a
> SolidColor fill and two with LinearGradient fills:
> 
> Flex version:
> http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.html (right
> click for source)
> 
> Using the XSLT file, I transformed it into its equivalent
> 
> SVG version:
> http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.svg.html(right
> click for source)
> 
> The SVG version uses  and inline CSS to style the different elements.
> 
> 
> To my naked eye, they both look pretty much the same.  After this
> experiment, I am halfway convinced that this is a viable approach to carry
> over Flex's Spark based skins into the HTML5/SVG world.
> 
> I have identified a few problems that I will be tackling next:
> 
> 1.  States
> 2.  Tackling the ILayoutElement interface usage (i.e. usage of left, right,
> etc. constraints)
> 3.  Transform Other Shapes, etc.
> 4.  Get a Spark component's skin to work in HTML5/SVG
> 
> I have a few ideas that I will be trying out.  If anyone wants to take a
> peek at the XSLT file and modify it  or has any ideas they would like to
> see me implement, that would be great.
> 
> Thanks,
> Om
> 
> 
> [1]
> https://git-wip-us.apache.org/repos/asf?p=flex-asjs.git;a=blob;f=fxg2svg/transform.xslt;h=df474c463f3fcc2701db063e691f3a4f29f217a6;hb=develop

[jira] [Resolved] (FLEX-28967) PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access a property or method of a null object reference

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-28967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira resolved FLEX-28967.
--

   Resolution: Fixed
Fix Version/s: Apache Flex Next

> PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access 
> a property or method of a null object reference
> -
>
> Key: FLEX-28967
> URL: https://issues.apache.org/jira/browse/FLEX-28967
> Project: Apache Flex
>  Issue Type: Bug
>  Components: PopUp Manager
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Internet Explorer 8.x
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Carlos Rovira
>  Labels: EasyFix
> Fix For: Apache Flex Next
>
>
> Steps to reproduce:
> 1. using PopUpManager
>  
> Error in the code:
> public function centerPopUp(popUp:IFlexDisplayObject):void
> {
> if (popUp is IInvalidating)
> IInvalidating(popUp).validateNow();
> const o:PopUpData = findPopupInfoByOwner(popUp);
> 
> // If we don't find the pop owner or if the owner's parent is not 
> specified or is not on the
> // stage, then center based on the popUp's current parent.
> var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
> o.parent : popUp.parent;
> if (popUpParent)
> {
> var systemManager:ISystemManager = o.systemManager;
> .
> .
> .
> .
> If const "o" is null, popUpParent is set to popUp.parent as stated by 
> condition above.
> However in next step you assume that const "o" exists because you're asking 
> for o.systemManager, but o is null.
> Therefore: TypeError: Error #1009: Cannot access a property or method of a 
> null object reference
> Fix:
> public function centerPopUp(popUp:IFlexDisplayObject):void
> {
> if (popUp is IInvalidating)
> IInvalidating(popUp).validateNow();
> const o:PopUpData = findPopupInfoByOwner(popUp);
> 
> var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
> o.parent : popUp.parent;
> if (popUpParent)
> {
>   var systemManager:ISystemManager;
>   if (o != null) {
>   systemManager = o.systemManager;
>   } else if (popUpParent.hasOwnProperty("systemManager")) 
> {
>   systemManager = popUpParent["systemManager"];
>   } else if (popUpParent is ISystemManager) {
>   systemManager = popUpParent as ISystemManager;
>   }
>   
>   if (!systemManager)
>   return; // or throw exception maybe ?
> .
> .
> .
> .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: FXG to SVG - working example

2013-03-24 Thread Harbs

I barely touch mobile (at the moment). If I did I would probably be interested. 
I'm hoping someone else picks up on this…

Harbs

On Mar 23, 2013, at 6:39 AM, Daniel Freeman wrote:

> I wrote one of those.  I wrote SVG -> AS3 graphics.  And extending that
> class, I wrote FXG -> AS3 graphics.
> 
> It wasn't a complete implementation of the SVG or FXG standards.  It didn't
> handle text, and complex gradients weren't perfect.  The FXG class was
> based on Adobe's first FXG definition.  But it worked pretty well.
> 
> This was one of the features of the applications I offered to donate.
> 
> Actually, if you go back to build r53 of extendedMadness.  SVG was in
> there.  I took it out, because I didn't think too may people would be
> interested - and to reduce the bloat.  (I didn't want my Framework getting
> like Flex - did I),
> 
> http://code.google.com/p/mad-components/source/detail?r=53#
> 
> See example here:
> http://code.google.com/p/mad-components/source/browse/trunk/MadComponentStuff/src/MadComponentsDesktop.as?spec=svn53&r=53
> 
> FXG isn't too different from SVG.
> 
> 
> ... I've mentioned this before, but I'd like to relinquish control a little
> over maintaining MadComponents, ExtendedMadness, and MC3D.  I've offered
> before to donate them to this Apache group.
> 
> Bear in mind that people aren't using Flex to build mobile apps.  They're
> using MadComponents (General Purpose / Enterprise) or Feathers (Game UI).
> In fact, I've had clients engage my freelance services because they tried
> to build a mobile app using bloated Flex - and regretted it.
> 
> http://madskool.wordpress.com/2012/01/23/why-developers-are-using-madcomponents/
> 
> Is there any interest in this group in MadComponents?
> 
> 
> On Sat, Mar 16, 2013 at 4:01 AM, Michael Schmalle
> wrote:
> 
>> 
>> Quoting Alex Harui :
>> 
>> In my simple mind, Falcon generates the AST then at some point in time the
>>> futures task for that compilation unit is asked for output.  Current
>>> Falcon
>>> code calls the BURM which eventually calls an emitter, I'm assuming
>>> FalconJX
>>> does an AST tree walk instead of calling the BURM.  There is no reduction,
>>> just emitting.  CSS for JS is probably just going emit text from the tree.
>>> 
>> 
>> Yes this is correct basically.
>> 
>> Each compilation unit implements its own handleASBRequest() that gets
>> called during a generator request. This request ONLY happens AFTER the
>> handle AST and Scope requests have been processed.
>> 
>> Its very complicated below that principle because of the future tasks and
>> outgoing dependency requests that trigger other files to be parsed, scopes
>> built etc.
>> 
>> THe framework is elegant. The only thing I wish I could tear out and
>> abstract is how they have SWF baked into ITarget and Target.
>> 
>> This really makes it hard to do what we are doing without all this
>> "baggage".
>> 
>> As I said, parsing is multithreaded right now in FalconJx, I can easily
>> get the source code generation multithreaded to now that I have learned how
>> the framework wheels move together.
>> 
>> I'm just not at the point to worry to much about it at the moment because
>> in a couple of my test projects, the compiler is wicked fast, I also have
>> an implementation that uses the Workspace and only loads config once, which
>> is using the framework like and IDE does...
>> 
>> Mike
>> 
>> 
>> 
>> 
>>> On 3/15/13 1:44 PM, "Michael Schmalle"  wrote:
>>> 
>>> BTW,
 
 I have not seen one thing that you are asking for that doesn't contain
 an AST and node framework in the Falcon package.
 
 If it was me, I would create all the emitters exactly the same way be
 parsing the file, handling the AST, traversing it while outputting to
 the target, then writing it in its file format.
 
 Its simple and I guess the FalconJx framework is mainly due to me
 dealing with inheritance and dependency madness with Flex components
 for years. I said all my future projects will use composition, this
 one does big time.
 
 Mike
 
 Quoting Michael Schmalle :
 
 
> Quoting Alex Harui :
> 
> 
>> 
>> 
>> On 3/15/13 1:14 PM, "Michael Schmalle" 
>> wrote:
>> 
>> The problem is, SWF is so
>>> interconnected in the generator packages that you might have a problem
>>> getting a polarity with using the BURM.
>>> 
>> Don't know what "polarity" meant, but hopefully it doesn't really
>> matter.
>> 
> 
> Bad word, I meant polarity in emitters as what the BURM generators
> offer right now with FalconJS, properties, css, as, mxml.
> 
> 
> On that note; This would take more study to fully understand, but at
>>> the moment I don't have time to investigate. I guess you will have to
>>> weigh the options or get a "feel" for the Falcon framework when your
>>> not under as much of a timeline/deadline?
>>> 
>>> That being said, the FalconJx

[jira] [Updated] (FLEX-28967) PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access a property or method of a null object reference

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-28967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira updated FLEX-28967:
-

Description: 
Steps to reproduce:


http://ns.adobe.com/mxml/2009"; 
   xmlns:s="library://ns.adobe.com/flex/spark" 
   xmlns:mx="library://ns.adobe.com/flex/mx" 
minWidth="955" minHeight="600">













1. using PopUpManager
 
Error in the code:
public function centerPopUp(popUp:IFlexDisplayObject):void
{
if (popUp is IInvalidating)
IInvalidating(popUp).validateNow();

const o:PopUpData = findPopupInfoByOwner(popUp);

// If we don't find the pop owner or if the owner's parent is not 
specified or is not on the
// stage, then center based on the popUp's current parent.
var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
o.parent : popUp.parent;
if (popUpParent)
{
var systemManager:ISystemManager = o.systemManager;
.
.
.
.

If const "o" is null, popUpParent is set to popUp.parent as stated by condition 
above.
However in next step you assume that const "o" exists because you're asking for 
o.systemManager, but o is null.
Therefore: TypeError: Error #1009: Cannot access a property or method of a null 
object reference


Fix:


public function centerPopUp(popUp:IFlexDisplayObject):void
{
if (popUp is IInvalidating)
IInvalidating(popUp).validateNow();

const o:PopUpData = findPopupInfoByOwner(popUp);

var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
o.parent : popUp.parent;
if (popUpParent)
{
var systemManager:ISystemManager;
if (o != null) {
systemManager = o.systemManager;
} else if (popUpParent.hasOwnProperty("systemManager")) 
{
systemManager = popUpParent["systemManager"];
} else if (popUpParent is ISystemManager) {
systemManager = popUpParent as ISystemManager;
}

if (!systemManager)
return; // or throw exception maybe ?
.
.
.
.

  was:
Steps to reproduce:
1. using PopUpManager
 
Error in the code:
public function centerPopUp(popUp:IFlexDisplayObject):void
{
if (popUp is IInvalidating)
IInvalidating(popUp).validateNow();

const o:PopUpData = findPopupInfoByOwner(popUp);

// If we don't find the pop owner or if the owner's parent is not 
specified or is not on the
// stage, then center based on the popUp's current parent.
var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
o.parent : popUp.parent;
if (popUpParent)
{
var systemManager:ISystemManager = o.systemManager;
.
.
.
.

If const "o" is null, popUpParent is set to popUp.parent as stated by condition 
above.
However in next step you assume that const "o" exists because you're asking for 
o.systemManager, but o is null.
Therefore: TypeError: Error #1009: Cannot access a property or method of a null 
object reference


Fix:


public function centerPopUp(popUp:IFlexDisplayObject):void
{
if (popUp is IInvalidating)
IInvalidating(popUp).validateNow();

const o:PopUpData = findPopupInfoByOwner(popUp);

var popUpParent:DisplayObject = (o && o.parent && o.parent.stage) ? 
o.parent : popUp.parent;
if (popUpParent)
{
var systemManager:ISystemManager;
if (o != null) {
systemManager = o.systemManager;
} else if (popUpParent.hasOwnProperty("systemManager")) 
{
systemManager = popUpParent["systemManager"];
} else if (popUpParent is ISystemManager) {
systemManager = popUpParent as ISystemManager;
}

if (!systemManager)
return; // or throw exception maybe ?
.
.
.
.


> PopUpManagerImpl - centerPopUp method - TypeError: Error #1009: Cannot access 
> a property or method of a null object reference
> -
>
> Key: FLEX-28967
> URL: https://issues.apache.org/jira/browse/FLEX-28967
> Project: Apache Flex
>  Issue Type: Bug
>  Components: PopUp Manager
>Affects Versions: Adobe Flex SDK Prev

[jira] [Assigned] (FLEX-33408) UIComponent#getVisibleRect() omitted from documentation

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-33408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira reassigned FLEX-33408:


Assignee: Carlos Rovira

> UIComponent#getVisibleRect() omitted from documentation
> ---
>
> Key: FLEX-33408
> URL: https://issues.apache.org/jira/browse/FLEX-33408
> Project: Apache Flex
>  Issue Type: Bug
>  Components: ASDoc Content
>Affects Versions: Apache Flex 4.9.0
>Reporter: JC Franco
>Assignee: Carlos Rovira
>  Labels: ASDoc, easyfix, missing, mx:UIComponent
> Attachments: FLEX-33408.patch
>
>
> UIComponent#getVisibleRect is a public function, but it is hidden from 
> documentation:
> /**
>  *  @private
>  *
>  *  Get the bounds of this object that are visible to the user
>  *  on the screen.
>  *
>  *  @param targetParent The parent to stop at when calculating the visible
>  *  bounds. If null, this object's system manager will be used as
>  *  the parent.
>  *
>  *  @return a Rectangle including the visible portion of the 
> this
>  *  object. The rectangle is in global coordinates.
>  */
> public function getVisibleRect(targetParent:DisplayObject = 
> null):Rectangle
> {
> ...
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FLEX-33408) UIComponent#getVisibleRect() omitted from documentation

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-33408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira resolved FLEX-33408.
--

   Resolution: Fixed
Fix Version/s: Apache Flex Next

> UIComponent#getVisibleRect() omitted from documentation
> ---
>
> Key: FLEX-33408
> URL: https://issues.apache.org/jira/browse/FLEX-33408
> Project: Apache Flex
>  Issue Type: Bug
>  Components: ASDoc Content
>Affects Versions: Apache Flex 4.9.0
>Reporter: JC Franco
>Assignee: Carlos Rovira
>  Labels: ASDoc, easyfix, missing, mx:UIComponent
> Fix For: Apache Flex Next
>
> Attachments: FLEX-33408.patch
>
>
> UIComponent#getVisibleRect is a public function, but it is hidden from 
> documentation:
> /**
>  *  @private
>  *
>  *  Get the bounds of this object that are visible to the user
>  *  on the screen.
>  *
>  *  @param targetParent The parent to stop at when calculating the visible
>  *  bounds. If null, this object's system manager will be used as
>  *  the parent.
>  *
>  *  @return a Rectangle including the visible portion of the 
> this
>  *  object. The rectangle is in global coordinates.
>  */
> public function getVisibleRect(targetParent:DisplayObject = 
> null):Rectangle
> {
> ...
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33408) UIComponent#getVisibleRect() omitted from documentation

2013-03-24 Thread Carlos Rovira (JIRA)


[ 
https://issues.apache.org/jira/browse/FLEX-33408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612087#comment-13612087
 ] 

Carlos Rovira commented on FLEX-33408:
--

Applied Patch by Mark Kessler.

Thanks Mark for the contribution.

> UIComponent#getVisibleRect() omitted from documentation
> ---
>
> Key: FLEX-33408
> URL: https://issues.apache.org/jira/browse/FLEX-33408
> Project: Apache Flex
>  Issue Type: Bug
>  Components: ASDoc Content
>Affects Versions: Apache Flex 4.9.0
>Reporter: JC Franco
>Assignee: Carlos Rovira
>  Labels: ASDoc, easyfix, missing, mx:UIComponent
> Attachments: FLEX-33408.patch
>
>
> UIComponent#getVisibleRect is a public function, but it is hidden from 
> documentation:
> /**
>  *  @private
>  *
>  *  Get the bounds of this object that are visible to the user
>  *  on the screen.
>  *
>  *  @param targetParent The parent to stop at when calculating the visible
>  *  bounds. If null, this object's system manager will be used as
>  *  the parent.
>  *
>  *  @return a Rectangle including the visible portion of the 
> this
>  *  object. The rectangle is in global coordinates.
>  */
> public function getVisibleRect(targetParent:DisplayObject = 
> null):Rectangle
> {
> ...
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS


Hi Guys,

Just to say I created a new page on the wiki [1] to demonstrate Good vs Bad 
scenarios / Git usage, I'll fill it with more complex scenarios over the 
time.

It can be reviewed too :)

Thanks,
-Fred

[1] https://cwiki.apache.org/confluence/display/FLEX/Good+vs+Bad+Git+usage

-Message d'origine- 
From: Erik de Bruin

Sent: Sunday, March 24, 2013 11:51 AM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

+ 1 on starting out simple and keeping the message clear.

When needed, or as a suggested way to work for those who have a better
than "noob" level understanding of git, I think we should keep the
"rebase" workflow in the wiki. Furthermore, we should write up as much
of this discussion in the wiki as we can, for future reference.

EdB



On Sun, Mar 24, 2013 at 10:04 AM, Justin Mclean
 wrote:

Hi,

Would you mind if I wrote up a proposed alternate that doesn't use rebase 
and eliminate fast forwards? Yes, it will mean there is an extra 
'useless' commit... which I don't actually always find useless, but I 
think it simpler. Then let's just discuss.


+1 to at least considering this.

Justin




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS


Folks,

During the review of [1] you'll probably do, I've got no doubts the 
explanation parts I wrote with my English will not be grammatically correct, 
I hope anyway, that will be understandable, feel free to make me some 
proposals to improve it, that will save headaches for the others.


Thanks,
-Fred

[1] https://cwiki.apache.org/confluence/display/FLEX/Good+vs+Bad+Git+usage
-Message d'origine- 
From: Frédéric THOMAS

Sent: Sunday, March 24, 2013 2:43 PM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi Guys,

Just to say I created a new page on the wiki [1] to demonstrate Good vs Bad
scenarios / Git usage, I'll fill it with more complex scenarios over the
time.
It can be reviewed too :)

Thanks,
-Fred

[1] https://cwiki.apache.org/confluence/display/FLEX/Good+vs+Bad+Git+usage

-Message d'origine- 
From: Erik de Bruin

Sent: Sunday, March 24, 2013 11:51 AM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

+ 1 on starting out simple and keeping the message clear.

When needed, or as a suggested way to work for those who have a better
than "noob" level understanding of git, I think we should keep the
"rebase" workflow in the wiki. Furthermore, we should write up as much
of this discussion in the wiki as we can, for future reference.

EdB



On Sun, Mar 24, 2013 at 10:04 AM, Justin Mclean
 wrote:

Hi,

Would you mind if I wrote up a proposed alternate that doesn't use rebase 
and eliminate fast forwards? Yes, it will mean there is an extra 
'useless' commit... which I don't actually always find useless, but I 
think it simpler. Then let's just discuss.


+1 to at least considering this.

Justin




--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

[MENTORS] Voting on code donations

2013-03-24 Thread Alex Harui

Hi Former Mentors,

We’ve had some generous offers of code donations.  I noticed that some projects 
have votes about whether to accept code donations, but we haven’t for any Adobe 
donations to Apache Flex.  Is voting optional?

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Unsubscribe

2013-03-24 Thread Adnan Doric


Wrong email, sorry :)

[jira] [Commented] (FLEX-29004) BitmapImage.scaleMode="zoom" does not always center vertically

2013-03-24 Thread Carlos Rovira (JIRA)


[ 
https://issues.apache.org/jira/browse/FLEX-29004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612149#comment-13612149
 ] 

Carlos Rovira commented on FLEX-29004:
--

Could not find a way to reproduce this issue. Some code an image could be 
provided to show the problem

> BitmapImage.scaleMode="zoom" does not always center vertically
> --
>
> Key: FLEX-29004
> URL: https://issues.apache.org/jira/browse/FLEX-29004
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Spark: Image
>Affects Versions: Adobe Flex SDK 4.6 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>  Labels: EasyFix
>
> Steps to reproduce:
> 1. Set scaleMode="zoom" and fillMode="scale" on a spark Image or BitmapImage
>  
>  Actual Results:
> Some images will not be centered vertically, even when verticalAlign="middle" 
> (the default) 
>  
>  Workaround (if any):
>  I believe the problem is in spark.primitives.BitmapImage updateDisplayList() 
> line #1202
>  if (isZoom)
>  {
>  if (cWidth > unscaledWidth)
>  translateX = translateX + ((unscaledWidth - cWidth) * 
> getHorizontalAlignValue());
>  else if (cHeight > unscaledHeight)
>  translateY = translateY + ((unscaledHeight - cHeight) * 
> getVerticalAlignValue());
>  }
> I believe the "else if" should be just an "if".  Because everywhere else in 
> the updateDisplayList() method where getHorizontalAlignValue() or 
> getVerticalAlignValue() is being called, it is always 2 if statements, never 
> a single if...else statement.
> On my image, these were the values when it would not vertically center 
> correctly:
> b.height = 239
> b.width = 225
> cHeight = 987.86668
> cWidth = 930.1
> unscaledWidth = 930
> unscaledHeight = 455

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (FLEX-21066) Make removeItem( item:Object) accessible in ArrayCollection

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira reassigned FLEX-21066:


Assignee: Carlos Rovira

> Make removeItem( item:Object) accessible in ArrayCollection
> ---
>
> Key: FLEX-21066
> URL: https://issues.apache.org/jira/browse/FLEX-21066
> Project: Apache Flex
>  Issue Type: Improvement
>  Components: Collections
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Carlos Rovira
>  Labels: easyfix
>
> Steps to reproduce:
> 1. try removing an item from an ArrayCollection
> 2. try to use removeItem( item:Object)-method
> 3. method does not exist
>  
>  Actual Results:
>  Compiler Error
>  
>  Expected Results:
>  Item should be removed
>  
>  Workaround (if any):
> Call ac.removeItemAt( ac.getItemIndex( item) ).
> The internal list used in ArrayCollection-class is an ArrayList that does 
> have a method removeItem( item:Object). Please make this method accessible 
> from ArrayCollection, for example by adding the following to 
> ListCollectionView.as
> public function removeItem( item:Object ):Boolean
> {
>return list.removeItem( item );
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Unsubscribe

2013-03-24 Thread Frédéric THOMAS


Hi,

Try to send an email here: dev-unsubscr...@flex.apache.org

Thanks,
-Fred

-Message d'origine- 
From: Adnan Doric 
Sent: Sunday, March 24, 2013 4:44 PM 
To: dev@flex.apache.org 
Subject: Re: Unsubscribe 


Wrong email, sorry :)

Re: FXG -> SVG progress

2013-03-24 Thread Om

Harbs,

On Sun, Mar 24, 2013 at 5:25 AM, Harbs  wrote:

> FYI:
>
> The svg version does not render in Firefox (Mac 19.0.2).
>
>
Thanks for catching the issue with Firefox.  Firefox needs the width/height
and the viewBox attributes to render the SVG.  Whereas Chrome seems to make
stuff up and render things as needed.  I have updated the XSLT to handle
this now.

Please check the page again:
http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.svg.html
It should work now.


> In Safari and Chrome, the appearance is very close, but the svg version
> has a smoother gradient and the blue shape is missing the black stroke.
>
>
I dont see the difference in the gradient's smoothness, but your eyes maybe
better than mide.  The blue rect does not have a black stroke, but I do see
why you think that is the case.  There is a slight difference in the
rendering of the radiusX and radiusY between the renderers.

I tested on IE9 and the SVG looks fine over there as well.  Android browser
looks fine as well.

Anyone tested the svg page on an iOS device?

Thanks,
Om





> On Mar 24, 2013, at 11:01 AM, Om wrote:
>
> > On Fri, Mar 22, 2013 at 6:48 AM, Alex Harui  wrote:
> >
> >>
> >>
> >>
> >> On 3/22/13 12:36 AM, "Erik de Bruin"  wrote:
> >>
> >>> I think both the FlexJS as well as VanillaSDK frameworks can benefit
> >>> from this. So it should be available to both. I don't know much about
> >>> XSLT, but if it 'converts one into another', I think it should
> >>> ultimately go with that other thing that 'converts one into another',
> >>> FalconJx.
> >>>
> >>> But for now, as it is a work in progress, I think it's best place is
> >>> in ASJS, in the root, next to my 'publisher'. The publisher was also a
> >>> proof of concept, that has since been integrated into FalconJx.
> >>>
> >>> Clear as mud, right?
> >>>
> >> I hope to get a look at FalconJX shortly, but in theory, you haven't
> >> changed
> >> the FXG subcompiler and I think that's where this XSLT will eventually
> go.
> >>
> >>
> > I have checked in the first cut of the "FXG to SVG" XSLTfile here [1]
> >
> > Here is a very simple Flex app with three Rectangles, one with a a
> > SolidColor fill and two with LinearGradient fills:
> >
> > Flex version:
> > http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.html(right
> > click for source)
> >
> > Using the XSLT file, I transformed it into its equivalent
> >
> > SVG version:
> >
> http://people.apache.org/~bigosmallm/fxg2svg/transform/SeeFXG.svg.html(right
> > click for source)
> >
> > The SVG version uses  and inline CSS to style the different
> elements.
> >
> >
> > To my naked eye, they both look pretty much the same.  After this
> > experiment, I am halfway convinced that this is a viable approach to
> carry
> > over Flex's Spark based skins into the HTML5/SVG world.
> >
> > I have identified a few problems that I will be tackling next:
> >
> > 1.  States
> > 2.  Tackling the ILayoutElement interface usage (i.e. usage of left,
> right,
> > etc. constraints)
> > 3.  Transform Other Shapes, etc.
> > 4.  Get a Spark component's skin to work in HTML5/SVG
> >
> > I have a few ideas that I will be trying out.  If anyone wants to take a
> > peek at the XSLT file and modify it  or has any ideas they would like to
> > see me implement, that would be great.
> >
> > Thanks,
> > Om
> >
> >
> > [1]
> >
> https://git-wip-us.apache.org/repos/asf?p=flex-asjs.git;a=blob;f=fxg2svg/transform.xslt;h=df474c463f3fcc2701db063e691f3a4f29f217a6;hb=develop
>
>

Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)

2013-03-24 Thread Dave Fisher

Hi,

Does the Apache Flex project intend to have a product called Apache Falcon?

If so then someone ought to say so on gene...@i.ao

Regards,
Dave

Sent from my iPhone

On Mar 24, 2013, at 12:18 PM, Vinod Kumar Vavilapalli  
wrote:

> +1 (non-binding)
> 
> Thanks,
> +Vinod Kumar Vavilapalli
> 
> On Mar 20, 2013, at 9:54 PM, Srikanth Sundarrajan wrote:
> 
>> Hi,
>> 
>> Thanks for participating in the proposal discussion on Falcon
>> (formerly Ivory). I'd like to call a VOTE for acceptance of Apache
>> Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST).
>> 
>> [ ]  +1 Accept Apache Falcon into the Incubator
>> [ ]  +0 Don't care.
>> [ ]  -1 Don't accept Apache Falcon into the Incubator because...
>> 
>> Full proposal is pasted at the bottom of this email, and the
>> corresponding wiki is http://wiki.apache.org/incubator/FalconProposal.
>> 
>> 
>> Only VOTEs from Incubator PMC members are binding, but all are welcome
>> to express their thoughts.
>> 
>> Thanks,
>> Srikanth Sundarrajan
>> = Falcon Proposal =
>> 
>> == Abstract ==
>> Falcon is a data processing and management solution for Hadoop
>> designed for data motion, coordination of data pipelines, lifecycle
>> management, and data discovery. Falcon enables end consumers to
>> quickly onboard their data and its associated processing and
>> management tasks on Hadoop clusters.
>> 
>> == Proposal ==
>> Falcon will enable easy data management via declarative mechanism for
>> Hadoop. Users of Falcon platform simply define infrastructure
>> endpoints, data sets and processing rules declaratively. These
>> declarative configurations are expressed in such a way that the
>> dependencies between these configured entities are explicitly
>> described. This information about inter-dependencies between various
>> entities allows Falcon to orchestrate and manage various data
>> management functions.
>> 
>> The key use cases that Falcon addresses are:
>> * Data Motion
>> * Process orchestration and scheduling
>> * Policy-based Lifecycle Management
>> * Data Discovery
>> * Operability/Usability
>> 
>> With these features it is possible for users to onboard their data
>> sets with a comprehensive and holistic understanding of how, when and
>> where their data is managed across its lifecycle. Complex functions
>> such as retrying failures, identifying possible SLA breaches or
>> automated handling of input data changes are now simple directives.
>> All the administrative functions and user level functions are
>> available via RESTful APIs. CLI is simply a wrapper over the RESTful
>> APIs.
>> 
>> == Background ==
>> Hadoop and its ecosystem of products have made storing and processing
>> massive amounts of data commonplace. This has enabled numerous
>> organizations to gain valuable insights that they never could have
>> achieved in the past. While it is easy to leverage Hadoop for
>> crunching large volumes of data, organizing data, managing life cycle
>> of data and processing data is fairly involved. This is solved
>> adequately well in a classic data platform involving data warehouses
>> and standard ETL (extract-transform-load) tools, but remains largely
>> unsolved today. In addition to data processing complexities, Hadoop
>> presents new sets of challenges and opportunities relating to
>> management of data.
>> 
>> Data Management on Hadoop encompasses data motion, process
>> orchestration, lifecycle management, data discovery, etc. among other
>> concerns that are beyond ETL. Falcon is a new data processing and
>> management platform for Hadoop that solves this problem and creates
>> additional opportunities by building on existing components within the
>> Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without
>> reinventing the wheel. Falcon has been in production at InMobi, going
>> on its second year and has been managing hundreds of feeds and
>> processes.
>> 
>> Falcon is being developed by engineers employed with InMobi and
>> Hortonworks. This platform addition will increase the adoption of
>> Apache Hadoop by driving data management tractable for end users. We
>> are therefore proposing to make Falcon an Apache open source project.
>> 
>> == Rationale ==
>> The Falcon project aims to improve the usability of Apache Hadoop. As
>> a result Apache Hadoop will grow its community of users by increasing
>> the places Hadoop can be utilized and the use cases it will solve. By
>> developing Falcon in Apache we hope to gather a diverse community of
>> contributors, helping to ensure that Falcon is deployable for a broad
>> range of scenarios. Members of the Hadoop development community will
>> be able to influence Falcon’s roadmap, and contribute to it. We
>> believe having Falcon as part of the Apache Hadoop ecosystem will be a
>> great benefit to all of Hadoop's users.
>> 
>> == Current Status ==
>> Falcon is widely deployed in production within InMobi and moving on to
>> its second year. A version with a valuable set of feat

Re: Air 3.7 in Apache Flex

2013-03-24 Thread Alexander Doroshko




My understanding is that the only problem is that:
- flex-config.xml, air-config.xml and airmobile-config.xml files do not
include Flex related stuff;
- mxmlc.bat (mxmlc on Mac) and compc.bat (compc on Mac) scripts point to ASC
2.0 jars instead of legacy jars.

It seems like this might be handles by some clever text manipulation
in the SDK build script(s), IF the legacy jars are still present in
the distribution... Can anyone confirm that?


Legacy jars are included in the Apache Flex SDK installation and they 
are not overwritten when AIR SDK (any kind of bundle) is overlaid on top 
of Flex SDK. So, yes, if installer performs AIR SDK overlay skipping 
several files - the problem would be solved.

RE: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Michael A. Labriola

>None of the above solutions suits me, my requirement would be (as it should 
>from the Git model), not only to have one repo per person but one per project 
>(people might have several projects in their whiteboard) 

Fred,

Out of curiosity, and I am sorry if this was discussed in another thread, is 
there anything from an infrastructure perspective that is stopping commiters 
from having forks of the main repo? Effectively the concept of a whiteboard is 
more or less redundant to me if people were using their own forks.

Mike

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS


Hi Mike,

I'm not sure what you mean talking about fork and repo, I might be wrong but 
that's more a GitHub concept to me but there's the concept of spare 
checkouts, it means, once you cloned the entirely repo, you can filter the 
directories you want to see which will make Git working easier, I mean with 
less memory.


Before I go further, is that what you're talking about ?

-Fred

-Message d'origine- 
From: Michael A. Labriola

Sent: Sunday, March 24, 2013 9:16 PM
To: dev@flex.apache.org
Subject: RE: [Git/Wiki] please review the proposed workflow and comment

None of the above solutions suits me, my requirement would be (as it should 
from the Git model), not only to have one repo per person but one per 
project (people might have several projects in their whiteboard)


Fred,

Out of curiosity, and I am sorry if this was discussed in another thread, is 
there anything from an infrastructure perspective that is stopping commiters 
from having forks of the main repo? Effectively the concept of a whiteboard 
is more or less redundant to me if people were using their own forks.


Mike

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS

Sorry, I meant "sparse checkouts" :P Me and my English...

-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Sunday, March 24, 2013 9:34 PM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi Mike,

I'm not sure what you mean talking about fork and repo, I might be wrong but
that's more a GitHub concept to me but there's the concept of spare
checkouts, it means, once you cloned the entirely repo, you can filter the
directories you want to see which will make Git working easier, I mean with
less memory.

Before I go further, is that what you're talking about ?

-Fred

-Message d'origine- 
From: Michael A. Labriola

Sent: Sunday, March 24, 2013 9:16 PM
To: dev@flex.apache.org
Subject: RE: [Git/Wiki] please review the proposed workflow and comment

None of the above solutions suits me, my requirement would be (as it should 
from the Git model), not only to have one repo per person but one per 
project (people might have several projects in their whiteboard)

Fred,

Out of curiosity, and I am sorry if this was discussed in another thread, is
there anything from an infrastructure perspective that is stopping commiters
from having forks of the main repo? Effectively the concept of a whiteboard
is more or less redundant to me if people were using their own forks.

Mike

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Justin Mclean

HI,

> Out of curiosity, and I am sorry if this was discussed in another thread, is 
> there anything from an infrastructure perspective that is stopping commiters 
> from having forks of the main repo? Effectively the concept of a whiteboard 
> is more or less redundant to me if people were using their own forks.

Issue here is that the whiteboard area is an unstructured playground, it may 
follow the structure of another repo or it may have it's own structure.

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Justin Mclean

Hi,

With 1.  what happens if you do a pull before the commit like so:

echo Create File1 > File1
git add File1
git pull
git commit -m "Added File1"
git push

Justin

Re: FXG -> SVG progress

2013-03-24 Thread Harbs

It looks good. (Better than on my laptop.) The gradients are very smooth.

On Mar 24, 2013, at 9:45 PM, Om wrote:

> Anyone tested the svg page on an iOS device?

[jira] [Resolved] (FLEX-21066) Make removeItem( item:Object) accessible in ArrayCollection

2013-03-24 Thread Carlos Rovira (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Rovira resolved FLEX-21066.
--

   Resolution: Implemented
Fix Version/s: Adobe Flex SDK Next

The added removeItem method was introduced in the IList interface and 
propagated to the rest of classes implementing IList (11 classes in total).

The implementation was tested in various sample apps with List and TabNavigator.

> Make removeItem( item:Object) accessible in ArrayCollection
> ---
>
> Key: FLEX-21066
> URL: https://issues.apache.org/jira/browse/FLEX-21066
> Project: Apache Flex
>  Issue Type: Improvement
>  Components: Collections
>Affects Versions: Adobe Flex SDK 4.1 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Carlos Rovira
>  Labels: easyfix
> Fix For: Adobe Flex SDK Next
>
>
> Steps to reproduce:
> 1. try removing an item from an ArrayCollection
> 2. try to use removeItem( item:Object)-method
> 3. method does not exist
>  
>  Actual Results:
>  Compiler Error
>  
>  Expected Results:
>  Item should be removed
>  
>  Workaround (if any):
> Call ac.removeItemAt( ac.getItemIndex( item) ).
> The internal list used in ArrayCollection-class is an ArrayList that does 
> have a method removeItem( item:Object). Please make this method accessible 
> from ArrayCollection, for example by adding the following to 
> ListCollectionView.as
> public function removeItem( item:Object ):Boolean
> {
>return list.removeItem( item );
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS


Hi Justin,

---
With 1.  what happens if you do a pull before the commit like so:

echo Create File1 > File1
git add File1
git pull
git commit -m "Added File1"
git push
---
Nothing in this case as nothing happened remotely.


Btw, I just did a git update + refacto that's the reason why I haven't see 
your post before.


-Fred

-Message d'origine- 
From: Justin Mclean

Sent: Sunday, March 24, 2013 11:18 PM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi,

With 1.  what happens if you do a pull before the commit like so:

echo Create File1 > File1
git add File1
git pull
git commit -m "Added File1"
git push

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS


I mean the pull does not anything.

-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Monday, March 25, 2013 12:50 AM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi Justin,

---
With 1.  what happens if you do a pull before the commit like so:

echo Create File1 > File1
git add File1
git pull
git commit -m "Added File1"
git push
---
Nothing in this case as nothing happened remotely.


Btw, I just did a git update + refacto that's the reason why I haven't see
your post before.

-Fred

-Message d'origine- 
From: Justin Mclean

Sent: Sunday, March 24, 2013 11:18 PM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi,

With 1.  what happens if you do a pull before the commit like so:

echo Create File1 > File1
git add File1
git pull
git commit -m "Added File1"
git push

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Justin Mclean

Hi,

> I mean the pull does not anything.

The pull would do a fetch and then merge in the README change wouldn't it?

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS

I guess you're talking about the really 1rst case ?
Then, yes but nothing changed remotely, so, it doesn't pull anything.

-Fred

-Message d'origine- 
From: Justin Mclean 
Sent: Monday, March 25, 2013 1:05 AM 
To: dev@flex.apache.org 
Subject: Re: [Git/Wiki] please review the proposed workflow and comment 

Hi,

I mean the pull does not anything.

The pull would do a fetch and then merge in the README change wouldn't it?

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS

Btw, even after the commit, it doesn't do anything and for the same reason, 
the point is as you used to do with Svn, you do an update before doing a 
commit, to check if there are conflicts.


-Fred

-Message d'origine- 
From: Frédéric THOMAS

Sent: Monday, March 25, 2013 1:09 AM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

I guess you're talking about the really 1rst case ?
Then, yes but nothing changed remotely, so, it doesn't pull anything.

-Fred

-Message d'origine- 
From: Justin Mclean

Sent: Monday, March 25, 2013 1:05 AM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi,


I mean the pull does not anything.


The pull would do a fetch and then merge in the README change wouldn't it?

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Justin Mclean

Hi,

> Btw, even after the commit, it doesn't do anything and for the same reason, 
> the point is as you used to do with Svn, you do an update before doing a 
> commit, to check if there are conflicts.
I assume you mean do a pull to merge any changes before you do a push? I don't 
see why you would want to do a pull before every local commit and in fact it 
may not be possible if you are offline.

Justin

Re: [Git/Wiki] please review the proposed workflow and comment

2013-03-24 Thread Frédéric THOMAS

You right, I meant a git push talking about svn commit.

-Fred

-Message d'origine- 
From: Justin Mclean

Sent: Monday, March 25, 2013 1:20 AM
To: dev@flex.apache.org
Subject: Re: [Git/Wiki] please review the proposed workflow and comment

Hi,

Btw, even after the commit, it doesn't do anything and for the same 
reason, the point is as you used to do with Svn, you do an update before 
doing a commit, to check if there are conflicts.
I assume you mean do a pull to merge any changes before you do a push? I 
don't see why you would want to do a pull before every local commit and in 
fact it may not be possible if you are offline.

Justin

Re: [1/4] git commit: add removeItem to IList and ListCollectionView

2013-03-24 Thread Alex Harui

Carlos,

Did you consider that this change will break all third-party IList
implementations?

I would prefer that you revert this change and create an IList2 interface.

Sorry,
-Alex

On 3/24/13 4:06 PM, "carlosrov...@apache.org" 
wrote:

> Updated Branches:
>   refs/heads/develop 251c9b717 -> 5f87fec9e
> 
> 
> add removeItem to IList and ListCollectionView
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/flex-sdk/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-sdk/commit/14e10d49
> Tree: http://git-wip-us.apache.org/repos/asf/flex-sdk/tree/14e10d49
> Diff: http://git-wip-us.apache.org/repos/asf/flex-sdk/diff/14e10d49
> 
> Branch: refs/heads/develop
> Commit: 14e10d49b65760eb2be9d89e464b21d2483145a8
> Parents: 251c9b7
> Author: Carlos Rovira 
> Authored: Sun Mar 24 20:12:05 2013 +0100
> Committer: Carlos Rovira 
> Committed: Sun Mar 24 20:12:05 2013 +0100
> 
> --
>  .../projects/framework/src/mx/collections/IList.as |   16 +++-
>  .../src/mx/collections/ListCollectionView.as   |   20 +-
>  2 files changed, 33 insertions(+), 3 deletions(-)
> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/flex-sdk/blob/14e10d49/frameworks/proje
> cts/framework/src/mx/collections/IList.as
> --
> diff --git a/frameworks/projects/framework/src/mx/collections/IList.as
> b/frameworks/projects/framework/src/mx/collections/IList.as
> index fb91742..e636a7d 100644
> --- a/frameworks/projects/framework/src/mx/collections/IList.as
> +++ b/frameworks/projects/framework/src/mx/collections/IList.as
> @@ -212,7 +212,21 @@ public interface IList extends IEventDispatcher
>   *  @productversion Flex 3
>   */
>  function removeAll():void;
> -
> + 
> + /**
> +  *  Removes the specified item from this list, should it exist.
> +  *  Relies on ArrayList implementation
> +  *
> +  *  @param  item Object reference to the item that should be removed.
> +  *  @return Boolean indicating if the item was removed.
> +  *  
> +  *  @langversion 3.0
> +  *  @playerversion Flash 9
> +  *  @playerversion AIR 1.1
> +  *  @productversion Apache Flex 4.10
> +  */
> + function removeItem( item:Object ):Boolean;
> +  
>  /**
>   *  Removes the item at the specified index and returns it.
>   *  Any items that were after this index are now one index earlier.
> 
> http://git-wip-us.apache.org/repos/asf/flex-sdk/blob/14e10d49/frameworks/proje
> cts/framework/src/mx/collections/ListCollectionView.as
> --
> diff --git 
> a/frameworks/projects/framework/src/mx/collections/ListCollectionView.as
> b/frameworks/projects/framework/src/mx/collections/ListCollectionView.as
> index af33268..afce033 100644
> --- a/frameworks/projects/framework/src/mx/collections/ListCollectionView.as
> +++ b/frameworks/projects/framework/src/mx/collections/ListCollectionView.as
> @@ -757,8 +757,24 @@ public class ListCollectionView extends Proxy
>  //turns out that there are no neighbors of item in the filtered
>  //list, so item is the 1st item
>  return 0;
> -} 
> -
> +}
> +
> +/**
> +  *  Removes the specified item from this list, should it exist.
> +  *  Relies on ArrayList implementation
> +  *
> +  *  @param  item Object reference to the item that should be removed.
> +  *  @return Boolean indicating if the item was removed.
> +  *  
> +  *  @langversion 3.0
> +  *  @playerversion Flash 9
> +  *  @playerversion AIR 1.1
> +  *  @productversion Apache Flex 4.10
> +  */
> + public function removeItem( item:Object ):Boolean
> + {
> +  return list.removeItem( item );
> + }
>  
>  /**
>   * @inheritDoc
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: [1/4] git commit: add removeItem to IList and ListCollectionView

2013-03-24 Thread Justin Mclean

Hi,

> Did you consider that this change will break all third-party IList
> implementations?
Just wondering how common that would be? Over the years I used it quit often 
but can't recall needing to implement it. The AS3 commons collections use there 
own (different) IList interface.

> I would prefer that you revert this change and create an IList2 interface.

That seems ugly. How about putting the interface in the Apache namespace and 
having the classes in question implement both IList interfaces? That way it's 
backwards compatible and new code can use if if need be.

Justin

Re: [1/4] git commit: add removeItem to IList and ListCollectionView

2013-03-24 Thread Alex Harui




On 3/24/13 9:20 PM, "Justin Mclean"  wrote:

> Hi,
> 
>> Did you consider that this change will break all third-party IList
>> implementations?
> Just wondering how common that would be? Over the years I used it quit often
> but can't recall needing to implement it. The AS3 commons collections use
> there own (different) IList interface.
Dunno, but that's why I didn't actually veto.  But I would not want to cause
someone who did implement it to not migrate to Apache Flex because of it.
> 
>> I would prefer that you revert this change and create an IList2 interface.
> 
> That seems ugly. How about putting the interface in the Apache namespace and
> having the classes in question implement both IList interfaces? That way it's
> backwards compatible and new code can use if if need be.
> 
If you call it org.apache.flex.collections.IList, you might have to fully
qualify IList in other places in the code.  I don't really care what we call
it or what package it goes in.  Could call it IListWithRemoveItem.  Carlos
will find out if he tries to do what you suggest because he'll find himself
fixing a bunch of files again or not.  The fact he had to change all of
those SDK files was a first clue that this could impact third-parties.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: [1/4] git commit: add removeItem to IList and ListCollectionView

2013-03-24 Thread Justin Mclean

Hi,

> The fact he had to change all of those SDK files was a first clue that this 
> could impact third-parties.
Another possibility (possibly a little less useful but 100% 3rd party 
compatible) is to leave the interface as it was before (perhaps with the new 
method commented out to indicate it exists) and keep the new methods?

Justin

Re: [1/4] git commit: add removeItem to IList and ListCollectionView

2013-03-24 Thread Alex Harui

On 3/24/13 9:42 PM, "Justin Mclean"  wrote:

> Hi,
> 
>> The fact he had to change all of those SDK files was a first clue that this
>> could impact third-parties.
> Another possibility (possibly a little less useful but 100% 3rd party
> compatible) is to leave the interface as it was before (perhaps with the new
> method commented out to indicate it exists) and keep the new methods?
That's a possibility, or create a utility class that implements that method.
I doubt there is significant performance gains by implementing it over and
over again in several places.

Really, the documentation for that method should come with a warning that it
does a linear search and that for large data sets, some other mechanism
should be used to remove items.  I don't write real applications like you
folks do, but I would first make sure that I absolutely needed a method like
this.  For example, if you are deleting an object selected from a List, you
already have the selectedIndex.  Or if you know something about the data and
its sort order, you can sometimes know to start at the end and work
backwards.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

[jira] [Closed] (FLEX-16875) Add 'justify' to TextStyles.as

2013-03-24 Thread Cyrill Zadra (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyrill Zadra closed FLEX-16875.
---

   Resolution: Later
Fix Version/s: Apache Flex Next

Before FLEX-385 isn't implemented there is no need in fixing this one.

> Add 'justify' to TextStyles.as
> --
>
> Key: FLEX-16875
> URL: https://issues.apache.org/jira/browse/FLEX-16875
> Project: Apache Flex
>  Issue Type: Improvement
>  Components: Styles
>Affects Versions: Adobe Flex SDK 3.2 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Safari
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Cyrill Zadra
>Priority: Minor
>  Labels: easyfix
> Fix For: Apache Flex Next
>
>
> Add 'justify' as a valid textAlign style.
> [Style(name="textAlign", type="String", 
> enumeration="left,center,justify,right", inherit="yes")]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [1/4] git commit: add removeItem to IList and ListCollectionView

2013-03-24 Thread Alex Harui




On 3/24/13 10:22 PM, "Alex Harui"  wrote:

> 
> 
> 
> On 3/24/13 9:42 PM, "Justin Mclean"  wrote:
> 
>> Hi,
>> 
>>> The fact he had to change all of those SDK files was a first clue that this
>>> could impact third-parties.
>> Another possibility (possibly a little less useful but 100% 3rd party
>> compatible) is to leave the interface as it was before (perhaps with the new
>> method commented out to indicate it exists) and keep the new methods?
And actually, your proposal is only 99.9% 3rd party compatible.  There
is a non-zero probability that someone implemented removeItem on a subclass
of ListCollectionView or any of the other modified classes and this will
bust them.

> That's a possibility, or create a utility class that implements that method.
> I doubt there is significant performance gains by implementing it over and
> over again in several places.
> 
> Really, the documentation for that method should come with a warning that it
> does a linear search and that for large data sets, some other mechanism
> should be used to remove items.  I don't write real applications like you
> folks do, but I would first make sure that I absolutely needed a method like
> this.  For example, if you are deleting an object selected from a List, you
> already have the selectedIndex.  Or if you know something about the data and
> its sort order, you can sometimes know to start at the end and work
> backwards.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

[jira] [Assigned] (FLEX-28946) MX DataGrid default column sort breaks on NULL complex fields

2013-03-24 Thread Cyrill Zadra (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLEX-28946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyrill Zadra reassigned FLEX-28946:
---

Assignee: Cyrill Zadra

> MX DataGrid default column sort breaks on NULL complex fields
> -
>
> Key: FLEX-28946
> URL: https://issues.apache.org/jira/browse/FLEX-28946
> Project: Apache Flex
>  Issue Type: Bug
>  Components: mx: DataGrid
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
>Assignee: Cyrill Zadra
>  Labels: EasyFix
> Attachments: FLEX-28946.patch
>
>
>   Steps to reproduce:
> 1.Create an mx:DataGrid with an ArrayCollection dataProvider populated with 
> Objects that have nested objects.
> 2.Set one of the properties of a nested object to null
> 3.Try sorting (by clicking on the header field) on a column that displays 
> that property (eg. "address.city")
>  
>  Actual Results:
>  TypeError: Error #1009: Cannot access a property or method of a null object 
> reference. 
>  thrown in DataGridColumn.complexColumnSortCompare
>  the code does not check if resulting value is null
>  Note: DataGridColumn.deriveComplexColumnData function also does not check if 
> any component of complex property path is null
>  
>  Expected Results:
>  Grid sorted on that column, nulls handled corretly (first in ascending order)
>  
>  Workaround (if any):
>  Creating a custom compare function
> Example MXML:
> 
> http://ns.adobe.com/mxml/2009"; 
>  xmlns:s="library://ns.adobe.com/flex/spark" 
>  xmlns:mx="library://ns.adobe.com/flex/mx" 
> minWidth="955" minHeight="600">
>   
>  >
>   
>   
>   
>   
>   
>   
>   
>dataField="address.city" />
>   
>   
> 
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

47 matches

Mail list logo