Weird, not obvious why this fails but the bug test cases don't. Out of
time for tonight. Will dig tomorrow.
-Alex
On 10/11/13 10:42 PM, "Alex Harui" wrote:
>-1 for now because the mustella run was not clean. Probably due to that
>FocusManager patch. I'm going to take a quick look now.
>
>-A
On Fri, Oct 11, 2013 at 9:20 PM, Justin Mclean wrote:
> Hi,
>
> > I dont think it is a matter of PMC vs. non-PMC members. AFAIK, Windows
> > users need to use the Installer to test the SDKs with existing Flex
> > projects.
>
> What the issue with the constructFlexForIDE.bat or
> makeApacheFlexfor
Hi,
The mustella tests are not part of the source release so IMO it's actually not
hugely relevant unless it's a serious issue or causes a regression.
If we fixed 50 bugs and add new functionally I'd say that outweighs a minor
focus issue or an issue with one of the 30,000+ tests and that shoul
On Fri, Oct 11, 2013 at 10:32 PM, Alex Harui wrote:
> I am not in favor of having our customers unwittingly use untested
> configurations. We should do some testing before switching everyone.
>
>
How do you suggest we test?
Thanks,
Om
> -Alex
>
> From:
-1 for now because the mustella run was not clean. Probably due to that
FocusManager patch. I'm going to take a quick look now.
-Alex
From: Justin Mclean
[jus...@classsoftware.com]
Sent: Friday, October 11, 2013 5:16 PM
To:
dev@flex.apache.org
Subject: [
I am not in favor of having our customers unwittingly use untested
configurations. We should do some testing before switching everyone.
-Alex
From: omup...@gmail.com
[omup...@gmail.com] On Behalf Of OmPrakash Muppirala
[bigosma...@gmail.com]
Sent: Friday,
I discovered today that DropDownList.js was broken. I made some quick changes
to it to get it to work for the DataBindingTest demo. We'll take a harder look
at it next week. I think things got a bit mixed up as Peter was trying out the
itemrenderer capability.
Thanks for trying FlexJS,
-Ale
Hi,
> OK I'll change the config file to do that.
Looks like there's a case issue with it, means it might work on windows but
will break on OSX/Linux.
http://sourceforge.net/projects/osmf.adobe/files/OSMF%202.0%20Release%20%28final%20source%2C%20ASDocs%2C%20pdf%20guides%20and%20release%20notes%29
Hi,
> I would rather let it be downloaded for 4.10 and 4.9 as well. If we run
> into issues, we can always rollback the OSMF version to back where it was.
OK I'll change the config file to do that.
Thanks,
Justin
Hi,
> I dont think it is a matter of PMC vs. non-PMC members. AFAIK, Windows
> users need to use the Installer to test the SDKs with existing Flex
> projects.
What the issue with the constructFlexForIDE.bat or makeApacheFlexforIDE.bat
scripts?
> What are you testing then?
The release as defi
On Fri, Oct 11, 2013 at 8:10 PM, Justin Mclean wrote:
> Hi,
> >> 1. Update config to point to OSMF 2.0
> > It is. I assume you mean so that it uses 2.0 only for 4.11?
>
> Sorry I meant to say or rather can be - it's more if we want that also
> downloaded for 4.10 and 4.9?
>
>
I would rather let
On Fri, Oct 11, 2013 at 8:32 PM, Justin Mclean wrote:
> Hi,
>
> > I prefer the second option. This is how we tested previous releases.
> Not everyone tests it that way. It's certainly easier to do it that way if
> you don't have a complication environment set up, and it's certainly easier
> for n
Hi,
> I prefer the second option. This is how we tested previous releases.
Not everyone tests it that way. It's certainly easier to do it that way if you
don't have a complication environment set up, and it's certainly easier for non
PMC members to test it that way.
The official vote is on the
Hi,
>> 1. Update config to point to OSMF 2.0
> It is. I assume you mean so that it uses 2.0 only for 4.11?
Sorry I meant to say or rather can be - it's more if we want that also
downloaded for 4.10 and 4.9?
Thanks,
Justin
Hi,
> 1. Update config to point to OSMF 2.0
It is. I assume you mean so that it uses 2.0 only for 4.11?
> 2. Update config to point to FP 11.9/AIR 3.9 final release swcs
We can do 2 that without recompiling no issues.
I assume we would want to default to 11.8/3.8 for a few weeks - in case thes
On Fri, Oct 11, 2013 at 11:35 AM, OmPrakash Muppirala
wrote:
> Lets compile all the changes we want to make to the Installer to go with
> the Flex 4.11 release.
>
> 1. Update config to point to OSMF 2.0
> 2. Update config to point to FP 11.9/AIR 3.9 final release swcs
>
> Anything else we need t
On Fri, Oct 11, 2013 at 7:11 PM, Justin Mclean wrote:
> Hi,
>
> > I dont think it is a valid test of the RC if the Installer is downloading
> > the wrong OSMF swc.
> I only put it there as a convenience to people who can't compile the SDK.
> People who have binding votes shouldn't be using the ins
Hi,
> I dont think it is a valid test of the RC if the Installer is downloading
> the wrong OSMF swc.
I only put it there as a convenience to people who can't compile the SDK.
People who have binding votes shouldn't be using the installer :-)
> In that case, you should probably revert the chang
On Fri, Oct 11, 2013 at 6:55 PM, Justin Mclean wrote:
> Hi,
>
> > Did we have to make any code changes to make OSMF 2.0 work with the Flex
> > SDK?
> No but it certainly requires more testing. IMO I'd hold off on changing
> the installer, unless other people think otherwise.
>
>
I dont think it is
Hi,
> Did we have to make any code changes to make OSMF 2.0 work with the Flex
> SDK?
No but it certainly requires more testing. IMO I'd hold off on changing the
installer, unless other people think otherwise.
Thanks,
Justin
On Fri, Oct 11, 2013 at 6:39 PM, Justin Mclean wrote:
> Hi,
>
> > Should we update the Installer config to point to OSMF 2.0 swc for the
> RC1?
> Issue there is we really need older version for 4.9 and 4.10 instals and
> newer for 4.11. Not sure the installer can do that without a code change
> an
Hi,
> Should we update the Installer config to point to OSMF 2.0 swc for the RC1?
Issue there is we really need older version for 4.9 and 4.10 instals and newer
for 4.11. Not sure the installer can do that without a code change and a VOTE.
Justin
There's a problem. The SDK's downloads.xml was updated to OSMF 2.0. But
the Installer is still looking at the earlier version.
Should we update the Installer config to point to OSMF 2.0 swc for the RC1?
Thanks,
Om
On Fri, Oct 11, 2013 at 6:30 PM, OmPrakash Muppirala
wrote:
> On Fri, Oct 11,
On Fri, Oct 11, 2013 at 6:18 PM, Justin Mclean wrote:
> Hi,
>
> > Need a clarification about the voting process. Are we going to carry
> votes
> > across RCs as suggested in this thread [1] ?
>
> If the changes are relatively minor between RC I think we'll can carry
> votes over. IF this is the c
Hi,
> Need a clarification about the voting process. Are we going to carry votes
> across RCs as suggested in this thread [1] ?
If the changes are relatively minor between RC I think we'll can carry votes
over. IF this is the case I'll mention it in the VOTE for the RC, people can
then vote -1
Hi,
To make it easier for people to test who are unable to compile the SDK I've
added RC1 to as an option in the installer. Download and give it a go!
Thanks,
Justin
Need a clarification about the voting process. Are we going to carry votes
across RCs as suggested in this thread [1] ?
Thanks,
Om
[1]
http://apache-flex-development.247.n4.nabble.com/Ideas-for-dealing-with-less-VOTEs-per-RC-td29767.html
On Fri, Oct 11, 2013 at 5:16 PM, Justin Mclean wrote
Hi,
(Moving to new thread so as to not pollute the vote thread.)
> mx:AdvancedDataGrid and mx:DataGrid speed improvements.
>
> what exactly is the speed improvements about?
Depends on what your datagrid is doing and is more noticeable with large
datagrids., Selecting, scrolling(especially hori
in the release note,
mx:AdvancedDataGrid and mx:DataGrid speed improvements.
what exactly is the speed improvements about?
Thanks
Jack
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Friday, October 11, 2013 5:25 PM
To: dev@flex.apache.org
Subject: Re: [V
Hi,
The link of course is:
https://dist.apache.org/repos/dist/dev/flex/sdk/4.11.0/rc1/
Not the link to the 4.10 RC1.
Thanks
Justin
Hi,
Please place all discussion around the release candidate here and not in the
[VOTE] thread.
Thanks,
Justin
Hi,
This is a Apache Flex 4.11.0 release candidate 1. Please see the RELEASE_NOTES
and the README.
There are a few new things that would be nice for people to test out, including:
- New mobile datagrid
- New 120 and 640 dpi skins
- Many datagrid improvements
- OSF 2.0 support
- Minor ASDoc chan
I uploaded a new FlexJSOverlay.zip. It builds and runs the DataBindingTest and
JQuerySample.
I discovered that if you don't specify the compiler argument
-compiler.mxml.children-as-data you will also get the model error, but that
argument should be baked into the external tool configurations.
Ok, I will add it to .ignoreButKeepAnEyeOnIt file :-)
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 11 octobre 2013 23:29
À : dev@flex.apache.org
Objet : Re: ASDocs issue
Hi,
> Ah, OK sorry for that one. I will add it to my .gitignore.
I wou
Hi,
> Ah, OK sorry for that one. I will add it to my .gitignore.
I wouldn't do that, sometime it does need to change and if someone else changes
it you'll need to update it.
Justin
Started to look at FlexJS again, so let me try to understand what was intention
of implementation
ListBase should define the model & comboBox etc should set the dataprovider on
the model of their superclass
Is this what was intended but ListBase never added the model bead for whatever
reason
T
The new runtimes for 11.9 and 3.9 have been released to the public [1].
Also, we have been running our Mustella tests against the beta versions of
11.9 and 3.9 for the past few weeks without any problem.
I am planning to update the playerglogal.swc on the mustella VM with the
release to let it run
Lets compile all the changes we want to make to the Installer to go with
the Flex 4.11 release.
1. Update config to point to OSMF 2.0
2. Update config to point to FP 11.9/AIR 3.9 final release swcs
Anything else we need to add?
Fred, you have been doing some work around refacoring, speeding up
I think bubbling the event is the easiest way to do it. This way you can
catch the event where it makes the most sense to handle it. For example,
you can add the event handler to the List (or DataGrid or whatever) which
is up the display-list chain from the itemRenderer and have the function
be own
Understood. I will do that.
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : vendredi 11 octobre 2013 18:45
À : dev@flex.apache.org
Objet : Re: Need help on https://issues.apache.org/jira/browse/FLEX-33813
(DataGrid goes blank)
On 10/11/13 8:00 AM, "Maurice Am
Ok, thanks.
I should have noticed that the mustella report couldn't be that fast after the
commit :-)
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : vendredi 11 octobre 2013 18:49
À : dev@flex.apache.org
Objet : Re: Build failed in Jenkins: flex-sdk_mustella #4
The FTETextField errors are independent from SplitViewNavigator. This run
apparently started before I checked in the change to FTETextField. I
think your changes are clean.
On 10/11/13 9:17 AM, "Maurice Amsellem"
wrote:
>Last mustella failure report:
>
>Changes say "SplitNavigator", and Callou
The changes section is a report from git on what has changed since the
last run. This is normally, but not necessarily, an indication of what
may have caused the failures.
In this case, the actual failures have been left unattended for so
long, that the git reporting is out of sync with Mustella r
On 10/11/13 8:00 AM, "Maurice Amsellem"
wrote:
>Hi Alex, thanks for the help.
>
>I agree that validateNow() is a bad things and breaks the deferred
>validation.
>
>However everything else in updateCaretForDataProviderChange is done in
>"immediate" way
>And validateNow() is also called at other
On 10/11/13 12:34 AM, "Maurice Amsellem"
wrote:
>>Simplification tends to remove flexibility. Spark components are
>>supposed
>>to leave control of all visuals to the skin designer. For example, can
>>the custom skin designer swap out a messageDisplay that does plain text
>>with one that doe
Last mustella failure report:
Changes say "SplitNavigator", and CalloutSkin (by mamsellem)
But the errors seem more related to itemRenderers .
Any idea ?
-Message d'origine-
De : flex.muste...@gmail.com [mailto:flex.muste...@gmail.com]
Envoyé : vendredi 11 octobre 2013 17:20
À : comm..
ok ok, I get what you guys are saying.
Gotcha, thanks :)
On Fri, Oct 11, 2013 at 9:45 AM, Lee Burrows
wrote:
> Hi,
>
> i dispatch from itemrenderers to parent list like this:
>
> (owner as List).dispatchEvent(myEvent);
>
> handling custom events with mxml is more complicated. you could listen fo
Maxime,
>However some components will always be popups and are not intended to be used
>any other way. Some examples are Alert, Toaster, CallOut, and
>DropDownListBase's list.
I agree with you. Alert is a Popup on its own, and it's a "low level"
component, so it should not need a second tag to
Hi,
i dispatch from itemrenderers to parent list like this:
(owner as List).dispatchEvent(myEvent);
handling custom events with mxml is more complicated. you could listen
for the list creation complete event (in mxml) and then add listeners
for the itemrenderer events via AS3, eg:
functio
I absolutely agree about the code redundancy. However at this moment it is
already all over the place. Alert, SkinnablePopUpContainer, PopUpAnchor,
DropDownListBase and perhaps some other classes I'm not thinking of, all
have their own ways of displaying and positioning popups. And - as you
pointed
I think what Jeff proposed was something like this:
someList.addEventListener("someCustomEventString",someHandler);
and in your itemRenderer, you just dispatch
dispatchEvent(new CustomEvent("CustomEventString"),bubbles=true)
No need to add and remove eventListeners based on the items created. T
So - now, after attempting to add some event handlers here, I remember why
I did what I did.
How on earth do you dispatch events from itemrenderers, and successfully
add handlers dynamically to the view?
First off, the mxml for the list is such that you merely indicate the class
to be utilized as
Hi Alex, thanks for the help.
I agree that validateNow() is a bad things and breaks the deferred validation.
However everything else in updateCaretForDataProviderChange is done in
"immediate" way
And validateNow() is also called at other places in the same method:
- line 5418 : validateNow ()
Hi Maurice,
Thanks for digging into this. ValidateNow() can fix a lot of things, but
it can also cause inefficiencies if the things it validates were going to
get invalidated shortly after. I don't know if that is the case or not
here.
If it were me (and it isn't) I would change the collectionC
Hi, I would like your help on a fix for
https://issues.apache.org/jira/browse/FLEX-33813 (DataGrid goes blank when
scrolled and content is reset)
I managed to spot where the issue is:
Grid.as
line 850:
const gridViewLayout:GridViewLayout = centerGridView.gridViewLayout;
const gridMaxVSP:Numb
Ah, OK sorry for that one.
I will add it to my .gitignore.
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 11 octobre 2013 14:57
À : dev@flex.apache.org
Objet : Re: ASDocs issue
Hi,
> My configuration being a little tweaked (with .gi
Hi,
> My configuration being a little tweaked (with .gitignored files), can you
> please double check ...
You might want to not check in changes to flex-sdk-description.xml but other
than that all good from what I can see.
Thanks,
Justin
You're welcome.
My configuration being a little tweaked (with .gitignored files), can you
please double check ...
Maurice
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 11 octobre 2013 13:01
À : dev@flex.apache.org
Objet : Re: ASDocs issue
I definitely like the idea of declaring Popups in MXML instead of ActionScript.
However, there is a downside to your approach, because it induces some code
redundancy: the popup management (modal, parent, adding/removing to
PopupManager, centering, etc...)
must be pushed to the Popup component i
Hi,
> Status:
> - build is OK
> - asdoc build is OK (no error)
> - asdoc content looks good.
Much appreciated for sorting that out.
Thanks,
Justin
> What's the difference between you new SkinnablePopup and the existing
SkinnablePopupContainer ?
It's how SkinnableComponent compares to SkinnableContainer, but for popups.
So it allows you to create custom popups without having to wrap them in a
SkinnablePopUpContainer or a PopUpAnchor.
>From a
Committed to :
https://git-wip-us.apache.org/repos/asf?p=flex-sdk.git;a=commit;h=5ae5a847
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : vendredi 11 octobre 2013 12:10
À : dev@flex.apache.org
Objet : RE: ASDocs issue
> However, I noticed that asd
> However, I noticed that asdoc "experimental" disclaimer does not show anymore
> :-(
Fixed ( I forgot to rebuild the asdoc compiler jars).
Status:
- build is OK
- asdoc build is OK (no error)
- asdoc content looks good.
Committing/pushing now.
Maurice
-Message d'origine-
De : Mauric
BTW, I like the idea of the mxml based Alert (in addition to AS script API) :-)
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : vendredi 11 octobre 2013 11:31
À : dev@flex.apache.org
Objet : RE: FLEX-33806 and spark Alert implementation
H
Hi Maxime,
What's the difference between you new SkinnablePopup and the existing
SkinnablePopupContainer ?
Maurice
-Message d'origine-
De : Maxime Cowez [mailto:maxime.co...@gmail.com]
Envoyé : vendredi 11 octobre 2013 11:25
À : dev@flex.apache.org
Objet : Re: FLEX-33806 and spark Ale
I've been working on a Spark implementation of Alert, which I've discussed
on this list before (see
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Alerts-and-dialogs-in-Flex-4-x-Spark-was-Alerts-and-dialogs-in-FlexJS-td27595.html).
Unlike the current experimental implementation - whic
I have fixed the issue with AnimationTarget, and experimental manifest and now
Experimental.swc and asdoc are compiling ok.
Didn't commit yet.
However, I noticed that asdoc "experimental" disclaimer does not show anymore
:-(
I am going to dig into the history of diffs, as suggested by Tom, to
Thanks, I will do.
-Message d'origine-
De : Tom Chiverton [mailto:t...@extravision.com]
Envoyé : vendredi 11 octobre 2013 10:46
À : dev@flex.apache.org
Objet : Re: ASDocs issue
Check the web view of the branch e.g.
https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=s
Check the web view of the branch e.g.
https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=shortlog;h=refs/heads/develop
and or the tree
https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=tree;h=refs/heads/develop;hb=refs/heads/develop
and find the commitdi
This is because original spark AnimationTarget is marked as internal, and
that's probably why it was duplicated in experimental, to make it public.
Since the redundant class was removed from experimental, the original internal
class cannot be accessed anymore.
I has changed spark AnimationTarget
Actually , there is a general problem here, that a number of files that were
removed have reappeared, of changes that was made have been cancelled, after I
made a pull/merge.
I am not familiar enough with git to understand how this can happen.
Anyway I feel like it's not safe to just try to re
Actually, the problem comes from asdoc build.xml
It's referencing (line 150 and 168 the namespace "
library://ns.adobe.com/flex/spark-mobilecomponents" which does not exist)
As far as I know, mobile components are also in the regular spar namespace
(library://ns.adobe.com/flex/spark)
Since mobil
I have checked the asdoc build.xml and it's missing some of the changes I have
made before (and I am sure I have commited and pushed, on 10/6).
I have also noticed some of the classes I have removed in experimental
(CalloutDropDownController, CallOutSkin) have reappeared when I merged from
origi
I have run the asdoc build.xml and getting this error:
D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\mobiletheme\src\spark\skins\mobile\ViewMenuSkin.mxml:
Could not resolve to a component implementation.
mailto:aha...@adobe.com]
Envoyé : vendredi 11 octobre 2013 08:58
À
>Simplification tends to remove flexibility. Spark components are supposed
>to leave control of all visuals to the skin designer. For example, can
>the custom skin designer swap out a messageDisplay that does plain text with
>one that does rich text?
If you replace plain text with rich text, i
Hi Justin,
I have created a test subdirectory in asdoc containing this single file and
also build_test.xml so that I can quickly quickly changes to the asdoc compiler
or templates
Without having to run through the whole SDK classes asdocs (while I was
working on the experimental asdoc changes
Hi,
> Let me know if you get past this before you quit for
> the day otherwise I'll try to dig deeper.
Day is already over for me. Any help would be appreciated.
> OK, pushed and merged (I think).
Yep. looks good. Mind updating the RELEASE_NOTES?
Thanks,
Justin
77 matches
Mail list logo
