You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2013/12/03 23:12:08 UTC
Version 4.12 of Apache Flex
Hi,
A new release of Apache Flex is a few months away what JIRA issues would you like to see fixed and what new features or improvments would you like to see?
You can get an indication of progress by looking at the latest version of the release notes in GitHub.
https://github.com/apache/flex-sdk/blob/develop/RELEASE_NOTES
Thanks,
Justin
Re: Version 4.12 of Apache Flex
Posted by mo...@comcast.net.
Thanks for the heads-up Justin. I'm hoping someone can please, please, please try to fix this issue,
https://issues.apache.org/jira/browse/FLEX-33846
that I'm running into with spark datagrid. I think it should effect anyone using spark datagrids with mx:DividedBox.
----- Original Message -----
From: "Justin Mclean" <ju...@classsoftware.com>
To: dev@flex.apache.org, users@flex.apache.org
Sent: Tuesday, December 3, 2013 2:12:08 PM
Subject: Version 4.12 of Apache Flex
Hi,
A new release of Apache Flex is a few months away what JIRA issues would you like to see fixed and what new features or improvments would you like to see?
You can get an indication of progress by looking at the latest version of the release notes in GitHub.
https://github.com/apache/flex-sdk/blob/develop/RELEASE_NOTES
Thanks,
Justin
Re: Version 4.12 of Apache Flex
Posted by FlexForever <ma...@yahoo.com>.
Yes, I already filled bug reports for both issues. Would be really great if
somebody can look into them especially as they are very easy to reproduce
and these bugs are really hindering my development.
https://issues.apache.org/jira/browse/FLEX-33972
https://issues.apache.org/jira/browse/FLEX-33973
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Version-4-12-of-Apache-Flex-tp4073p4145.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Version 4.12 of Apache Flex
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Also, implement something like removeAllListeners to a base class such as
> UIComponent
Sadly not 100% possible without Flash Player changes.
Thanks,
Justin
Re: Version 4.12 of Apache Flex
Posted by jude <fl...@gmail.com>.
That's what I was referring to. So far, I've read three different use cases
for removeEventListeners and I'm adding a few more. In my case it would be
to remove handlers setup by framework code so that components that can be
added to the stage and dragged around the screen without all of their
interactions being dispatched all the time. For example, if you add a
image, button or text input to the stage and then enable drag and drop you
would also be seeing it's mouse over, out, up and down states change as you
interacted with it and have to prevent it's focus in and out events from
doing things like setting focus on sub components for text input or button
emphasis or the drawing of the focus rectangle.
If you were to track the event listeners you would also be to see what
listeners are currently added to an object for debugging purposes. This
would open up the possibly of being able to see the order they will be
dispatched in.
On Mon, Dec 9, 2013 at 6:27 AM, Kessler CTR Mark J <
mark.kessler.ctr@usmc.mil> wrote:
> Well you can add some redundant code to removeAllListeners if you would
> like, but we can't modify the flash player code. The dispatching
> ultimately gets handled by the player. I made an example[1] a while back
> on duplicating the tracking of the event listeners and ultimately it can
> remove them all. The last updated code for it should be [2] for now.
>
>
> [1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.swf
> [2]
> https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516324241c4bc9d734f16
>
> -----Original Message-----
> From: jude [mailto:flexcapacitor@gmail.com]
> Sent: Monday, December 09, 2013 5:47 AM
> To: users@flex.apache.org
> Subject: Re: Version 4.12 of Apache Flex
>
> +1 on the skin upgrades.
>
> Also, implement something like removeAllListeners to a base class such as
> UIComponent or possibly have a utility class that has the same effect. I
> saw a patch a while back but I don't think it was ever added.
>
Re: Version 4.12 of Apache Flex
Posted by Mark Kessler <ke...@gmail.com>.
Ok, thanks Alex.
-Mark
On Mon, Dec 9, 2013 at 5:40 PM, Alex Harui <ah...@adobe.com> wrote:
> True, but in the five minutes I've spent thinking about this, I'm thinking
> this is for listeners added by a developer's AS code, not by code
> generated by MXML or by the framework, and it will be up to the developer
> to be disciplined enough to use it.
>
> So, if instead of writing: foo.addEventListener("event", someHandler)
> you instead write: EventListenerTracker.addTrackedEventListener(foo,
> "event", someHandler)
> you can later call EventListenerTracker.removeAllEventListeners(foo,
> "event").
>
> And by using addTrackedEventListener and not calling the API
> addEventListener, it is easy for the developer to grep their code to make
> sure everybody is using it.
>
> Anyway, I'm not going to spend time on it, so good luck and have fun if
> you do.
>
> -Alex
>
> On 12/9/13 2:34 PM, "Mark Kessler" <ke...@gmail.com> wrote:
>
> >Just a side thought on your proxy idea. The only complication to it is
> >this... We could have one that can be enabled at anytime, but it would
> >only
> >have visibility over what has happened since it was enabled. I like the
> >idea, just need to find an angle that works and provides the functionality
> >as well.
> >
> >
> >
> >-Mark
>
>
Re: Version 4.12 of Apache Flex
Posted by "piotr.zarzycki" <pi...@gmail.com>.
Hi All :)
Similar mechanism to described by Alex is a part of Fabrication Framework.
"Events" in fabrication called "Reaction". Every view is managed by mediator
whitch contain methods: addReaction, removeReaction, disposeReactions and
hasReaction - such methods into some utility could be really useful.
Mark implementation of reactions you can find in FabricationMediator ->
http://bit.ly/18yfgcC
Maybe it helps you in some way.
Piotr
-----
Flex/Air developer open to new job offers and challenges.
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Version-4-12-of-Apache-Flex-tp4073p4132.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Version 4.12 of Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
True, but in the five minutes I've spent thinking about this, I'm thinking
this is for listeners added by a developer's AS code, not by code
generated by MXML or by the framework, and it will be up to the developer
to be disciplined enough to use it.
So, if instead of writing: foo.addEventListener("event", someHandler)
you instead write: EventListenerTracker.addTrackedEventListener(foo,
"event", someHandler)
you can later call EventListenerTracker.removeAllEventListeners(foo,
"event").
And by using addTrackedEventListener and not calling the API
addEventListener, it is easy for the developer to grep their code to make
sure everybody is using it.
Anyway, I'm not going to spend time on it, so good luck and have fun if
you do.
-Alex
On 12/9/13 2:34 PM, "Mark Kessler" <ke...@gmail.com> wrote:
>Just a side thought on your proxy idea. The only complication to it is
>this... We could have one that can be enabled at anytime, but it would
>only
>have visibility over what has happened since it was enabled. I like the
>idea, just need to find an angle that works and provides the functionality
>as well.
>
>
>
>-Mark
Re: Version 4.12 of Apache Flex
Posted by Mark Kessler <ke...@gmail.com>.
Just a side thought on your proxy idea. The only complication to it is
this... We could have one that can be enabled at anytime, but it would only
have visibility over what has happened since it was enabled. I like the
idea, just need to find an angle that works and provides the functionality
as well.
-Mark
RE: Version 4.12 of Apache Flex
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
I wouldn't mind looking into that. Maybe using Dictionary's/Map's to group the data better. But I like the idea to only have it enabled exactly where it's needed. My proof of concept code was a bit overkill to make feasibility testing easier.
More idea's for it would be great. I did make a runonce eventlistener that worked well. It removed itself after one run.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Monday, December 09, 2013 12:35 PM
To: users@flex.apache.org
Subject: Re: Version 4.12 of Apache Flex
But I just had a thought: maybe the goal of this feature isn't to solve
removing event listeners in the framework code, but in the application
developer's code. Maybe we can create a utility class that acts as the
proxy and tracks addEventListener calls. Then it is more pay-as-you-go.
Use it if you really need it but the framework isn't burdened by it.
Re: Version 4.12 of Apache Flex
Posted by Alex Harui <ah...@adobe.com>.
Yes, it cannot be done as fast as the player code. And also, it is often
backwards from what you want. The references pinning an object in memory
is not the calls to addEventListener on that object, but the
addEventListener calls that object made to other objects. Remember:
foo.addEventListener("event", bar.eventHandler) creates a reference from
foo to bar, not the other way around. Foo can still be garbage collected
without calling foo.removeEventListener("event", bar.eventHandler).
But I just had a thought: maybe the goal of this feature isn't to solve
removing event listeners in the framework code, but in the application
developer's code. Maybe we can create a utility class that acts as the
proxy and tracks addEventListener calls. Then it is more pay-as-you-go.
Use it if you really need it but the framework isn't burdened by it.
On 12/9/13 4:38 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>Starling uses their own, but I believe the agreed reason for us not doing
>it was a performance issue. The flash player is running native code at
>something like 40 times more efficient I believe... or at least that was
>what was stated in someone's tests.
>
>-Mark
>
>-----Original Message-----
>From: Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil]
>Sent: Monday, December 09, 2013 7:27 AM
>To: users@flex.apache.org
>Subject: RE: Version 4.12 of Apache Flex
>
>Well you can add some redundant code to removeAllListeners if you would
>like, but we can't modify the flash player code. The dispatching
>ultimately gets handled by the player. I made an example[1] a while back
>on duplicating the tracking of the event listeners and ultimately it can
>remove them all. The last updated code for it should be [2] for now.
>
>
>[1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.swf
>[2]
>https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516
>324241c4bc9d734f16
RE: Version 4.12 of Apache Flex
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Starling uses their own, but I believe the agreed reason for us not doing it was a performance issue. The flash player is running native code at something like 40 times more efficient I believe... or at least that was what was stated in someone's tests.
-Mark
-----Original Message-----
From: Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil]
Sent: Monday, December 09, 2013 7:27 AM
To: users@flex.apache.org
Subject: RE: Version 4.12 of Apache Flex
Well you can add some redundant code to removeAllListeners if you would like, but we can't modify the flash player code. The dispatching ultimately gets handled by the player. I made an example[1] a while back on duplicating the tracking of the event listeners and ultimately it can remove them all. The last updated code for it should be [2] for now.
[1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.swf
[2] https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516324241c4bc9d734f16
RE: Version 4.12 of Apache Flex
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Well you can add some redundant code to removeAllListeners if you would like, but we can't modify the flash player code. The dispatching ultimately gets handled by the player. I made an example[1] a while back on duplicating the tracking of the event listeners and ultimately it can remove them all. The last updated code for it should be [2] for now.
[1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.swf
[2] https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516324241c4bc9d734f16
-----Original Message-----
From: jude [mailto:flexcapacitor@gmail.com]
Sent: Monday, December 09, 2013 5:47 AM
To: users@flex.apache.org
Subject: Re: Version 4.12 of Apache Flex
+1 on the skin upgrades.
Also, implement something like removeAllListeners to a base class such as
UIComponent or possibly have a utility class that has the same effect. I
saw a patch a while back but I don't think it was ever added.
Re: Version 4.12 of Apache Flex
Posted by jude <fl...@gmail.com>.
+1 on the skin upgrades.
Also, implement something like removeAllListeners to a base class such as
UIComponent or possibly have a utility class that has the same effect. I
saw a patch a while back but I don't think it was ever added.
Re: Version 4.12 of Apache Flex
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> 1) Update some skins to be in line with Android 4.x and iOS 7 design (e.g.
> action/title bar, tab bar etc.)
Some work been done for android 4.x skins and I intend to do some more once I have a bit of time.
> 2) Most of my problems are with displaying foreign fonts, e.g.
> - spark textArea does not display Arabic correctly
> - spark Label does not display Korean correctly on Android 4.3/4.4
Do these two issue have JIRA entries?
> 3) Create some additional components, e.g. Toast messages
This has been discussed before on the list you might want to and a look at that discussion and revisit.
Thanks,
Justin
Re: Version 4.12 of Apache Flex
Posted by FlexForever <ma...@yahoo.com>.
This is my wishlist:
1) Update some skins to be in line with Android 4.x and iOS 7 design (e.g.
action/title bar, tab bar etc.)
2) Most of my problems are with displaying foreign fonts, e.g.
- spark textArea does not display Arabic correctly
- spark Label does not display Korean correctly on Android 4.3/4.4
3) Create some additional components, e.g. Toast messages
Thanks!
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Version-4-12-of-Apache-Flex-tp4073p4119.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Version 4.12 of Apache Flex
Posted by mspecht <mw...@googlemail.com>.
Hi,
we make heavy use of DataGrids. That why I want to vote for fixing drag and
drop handling on the spark DataGrid.
(https://issues.apache.org/jira/browse/FLEX-33866)
Currently we still use Alex's proposed solution:
http://blogs.adobe.com/aharui/2011/03/spark-checkbox-datagrid-with-drag-and-drop-support.html
Thanks,
Mario
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Version-4-12-of-Apache-Flex-tp4073p4081.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Version 4.12 of Apache Flex
Posted by Thiago Maia <a0...@a00s.com>.
Hello
Im interested in this bug, it crashes the browser when we try to
set a background collor.
https://issues.apache.org/jira/browse/FLEX-33922
thanks a lot
Thiago Maia
On 12/3/2013 2:12 PM, Justin Mclean wrote:
> Hi,
>
> A new release of Apache Flex is a few months away what JIRA issues would you like to see fixed and what new features or improvments would you like to see?
>
> You can get an indication of progress by looking at the latest version of the release notes in GitHub.
>
> https://github.com/apache/flex-sdk/blob/develop/RELEASE_NOTES
>
> Thanks,
> Justin
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Re: Version 4.12 of Apache Flex
Posted by mo...@comcast.net.
Thanks for the heads-up Justin. I'm hoping someone can please, please, please try to fix this issue,
https://issues.apache.org/jira/browse/FLEX-33846
that I'm running into with spark datagrid. I think it should effect anyone using spark datagrids with mx:DividedBox.
----- Original Message -----
From: "Justin Mclean" <ju...@classsoftware.com>
To: dev@flex.apache.org, users@flex.apache.org
Sent: Tuesday, December 3, 2013 2:12:08 PM
Subject: Version 4.12 of Apache Flex
Hi,
A new release of Apache Flex is a few months away what JIRA issues would you like to see fixed and what new features or improvments would you like to see?
You can get an indication of progress by looking at the latest version of the release notes in GitHub.
https://github.com/apache/flex-sdk/blob/develop/RELEASE_NOTES
Thanks,
Justin
Re: Version 4.12 of Apache Flex
Posted by Mihai Chira <mi...@gmail.com>.
Thanks for the work on it so far!
We're also running into problems with grids:
https://issues.apache.org/jira/browse/FLEX-33934.
Many thanks,
Mihai
On 3 December 2013 22:12, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
> A new release of Apache Flex is a few months away what JIRA issues would
> you like to see fixed and what new features or improvments would you like
> to see?
>
> You can get an indication of progress by looking at the latest version of
> the release notes in GitHub.
>
> https://github.com/apache/flex-sdk/blob/develop/RELEASE_NOTES
>
> Thanks,
> Justin