Re: Adobe bug / jira offline?
On 6/7/13 4:43 PM, Mark Kessler kesslerconsult...@gmail.com wrote: The new bugbase does not have any of the Adobe Flex tickets in it... or list that it was a product. Does this mean we can mark all those issues from 2007/2008 that have inaccessible (well at least right now) attachments from the Adobe bugs... as resolved / incomplete :P Yeah, I thought they were going to make a static copies of the bugs. I'll have to check into that. I have almost all of the attachments, but there is no easy way to re-import them into Apache JIRA. It is on my list to write a custom tool to try to create a new import file that retains all of the current state of Apache JIRA. -Mark On Fri, Jun 7, 2013 at 7:25 PM, Mark Kessler kesslerconsult...@gmail.comwrote: I can't login to that new one using my adobe account. The one that I could log into the old bugs.adobe.com with. It wont let me create a new account with that name, so it must have the ability see it already exists. Going to make the bugs links in our JIRA harder to follow now. On Fri, Jun 7, 2013 at 7:13 PM, Marcus Fritze marcus.fri...@googlemail.com wrote: I think this was the old issue management system. The new one is https://bugbase.adobe.com Marcus Am 08.06.2013 um 01:06 schrieb Mark Kessler kesslerconsult...@gmail.com : Is adobe bugs/jira [1] offline? [1] http://bugs.adobe.com -Mark
Re: Build failed in Jenkins: flex-sdk_mustella #144
Well, I fixed a bunch more issues. If you have time, sync up and kick off another run and let's see if we're closer. -Alex On 6/7/13 6:11 AM, Alex Harui aha...@adobe.com wrote: Not on purpose but doesn't matter. I have to rework some tests locally before trying again on the vm. Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Erik de Bruin e...@ixsoftware.nl wrote: Hi, I've just logged in to take a peek at the VM and it seems to have rebooted or something. Jenkins is started. Is that on purpose? EdB On Fri, Jun 7, 2013 at 12:06 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Is the job running? If yes, open the job click on the red x button next to the progress bar on top. If the job is not running, go into job configure and select the 'Disable build' button. On Thu, Jun 6, 2013 at 3:00 PM, Alex Harui aha...@adobe.com wrote: Jenkins or something keeps trying to open the FlashPlayer. How do I stop it? On the status window the disable project button looks clickable. Would that stop it? From: OmPrakash Muppirala bigosma...@gmail.com Date: Thursday, June 6, 2013 12:45 PM To: Alex Harui aha...@adobe.com Cc: dev@flex.apache.org dev@flex.apache.org, erikdebr...@apache.org erikdebr...@apache.org Subject: Re: Build failed in Jenkins: flex-sdk_mustella #144 I took a peek a while ago. The build was stopped and there was an exception window on the Flash Player. Please go ahead and take a look. Om On Thu, Jun 6, 2013 at 12:44 PM, Alex Harui aha...@adobe.com wrote: Is someone using the VM? I'd like to get back to looking at the failures. -Alex On 6/6/13 9:01 AM, Erik de Bruin e...@ixsoftware.nl wrote: Ok, I've stopped the run. Jenkins currently doesn't have a schedule attached, it'll run only when started manually. EdB On Thu, Jun 6, 2013 at 5:42 PM, Alex Harui aha...@adobe.com wrote: Usually it lists off a set of files that it will run. Don't worry about -failures. Just shutdown jenkins and let me know and I'll log in and run whatever I need. Thanks, -Alex On 6/6/13 8:33 AM, Erik de Bruin e...@ixsoftware.nl wrote: If you run a -failures, should the command line reflect that? What I'm seeing is: Skipping testcase check Doing a regular mini run Buildfile: C:\jenkins_slave\workspace\flex-sdk_mustella\mustella\build.xml Is that expected? How do I know if it picked up the -failures or not? EdB On Thu, Jun 6, 2013 at 5:23 PM, Erik de Bruin e...@ixsoftware.nl wrote: Just did that. Run's runnin' now ;-) E On Thu, Jun 6, 2013 at 9:40 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Ahh so close... 39 failures. Erik, can you please re-run the failures as Alex requested? You can probably just update jenkins.sh and check it in. I am not near a real computer right now. Thanks, Om On Jun 6, 2013 12:02 AM, flex.muste...@gmail.com wrote: See http://localhost:8080/job/flex-sdk_mustella/144/changes Changes: [bigosmallm] Mustella run on Jenkins now works. So enabling the full test suite. -- [...truncated 80889 lines...] [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_globalSelector_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_classSelector_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_IDSelector_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelecto r_te st er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelecto r_te st er NV_localStyle_typeSelector_ priority_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_inline_2_test5 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_invalid_null_test6 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_invalid_empty_script_test7 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester
Re: Build failed in Jenkins: flex-sdk_mustella #144
I just started a run. -Om On Fri, Jun 7, 2013 at 11:57 PM, Alex Harui aha...@adobe.com wrote: Well, I fixed a bunch more issues. If you have time, sync up and kick off another run and let's see if we're closer. -Alex On 6/7/13 6:11 AM, Alex Harui aha...@adobe.com wrote: Not on purpose but doesn't matter. I have to rework some tests locally before trying again on the vm. Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Erik de Bruin e...@ixsoftware.nl wrote: Hi, I've just logged in to take a peek at the VM and it seems to have rebooted or something. Jenkins is started. Is that on purpose? EdB On Fri, Jun 7, 2013 at 12:06 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Is the job running? If yes, open the job click on the red x button next to the progress bar on top. If the job is not running, go into job configure and select the 'Disable build' button. On Thu, Jun 6, 2013 at 3:00 PM, Alex Harui aha...@adobe.com wrote: Jenkins or something keeps trying to open the FlashPlayer. How do I stop it? On the status window the disable project button looks clickable. Would that stop it? From: OmPrakash Muppirala bigosma...@gmail.com Date: Thursday, June 6, 2013 12:45 PM To: Alex Harui aha...@adobe.com Cc: dev@flex.apache.org dev@flex.apache.org, erikdebr...@apache.org erikdebr...@apache.org Subject: Re: Build failed in Jenkins: flex-sdk_mustella #144 I took a peek a while ago. The build was stopped and there was an exception window on the Flash Player. Please go ahead and take a look. Om On Thu, Jun 6, 2013 at 12:44 PM, Alex Harui aha...@adobe.com wrote: Is someone using the VM? I'd like to get back to looking at the failures. -Alex On 6/6/13 9:01 AM, Erik de Bruin e...@ixsoftware.nl wrote: Ok, I've stopped the run. Jenkins currently doesn't have a schedule attached, it'll run only when started manually. EdB On Thu, Jun 6, 2013 at 5:42 PM, Alex Harui aha...@adobe.com wrote: Usually it lists off a set of files that it will run. Don't worry about -failures. Just shutdown jenkins and let me know and I'll log in and run whatever I need. Thanks, -Alex On 6/6/13 8:33 AM, Erik de Bruin e...@ixsoftware.nl wrote: If you run a -failures, should the command line reflect that? What I'm seeing is: Skipping testcase check Doing a regular mini run Buildfile: C:\jenkins_slave\workspace\flex-sdk_mustella\mustella\build.xml Is that expected? How do I know if it picked up the -failures or not? EdB On Thu, Jun 6, 2013 at 5:23 PM, Erik de Bruin e...@ixsoftware.nl wrote: Just did that. Run's runnin' now ;-) E On Thu, Jun 6, 2013 at 9:40 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Ahh so close... 39 failures. Erik, can you please re-run the failures as Alex requested? You can probably just update jenkins.sh and check it in. I am not near a real computer right now. Thanks, Om On Jun 6, 2013 12:02 AM, flex.muste...@gmail.com wrote: See http://localhost:8080/job/flex-sdk_mustella/144/changes Changes: [bigosmallm] Mustella run on Jenkins now works. So enabling the full test suite. -- [...truncated 80889 lines...] [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_globalSelector_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_classSelector_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_IDSelector_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelecto r_te st er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelecto r_te st er NV_localStyle_typeSelector_ priority_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_inline_2_test5 Passed [java]
Re: New Mustella Failures
Hi, 1) ADG mirroring. The failing bitmap shows the text flipped (as if viewed in a mirror). I think mirrored in Flex is supposed to flip everything but text widgets so the font glyphs themselves are not mirrored, just laid out RTL or LTR depending on the characters. I did ask about this a while back, the test bitmap is incorrect as far as I can see as it doesn't show the text as RTL. 2) These 3 are all related to a change in DividedBox. Should now be fixed. Thanks, Justin
Re: New Mustella Failures
Hi,
1) ADG mirroring. The failing bitmap shows the text flipped (as if viewed
in a mirror).
Look closer at the test it setting the layout direction RTL not the direction
so only the columns should be reverse order not the text.
Look like there's an issue with the test as the same code run in a browser
doesn't show the text mirrored.
here's the code:
?xml version=1.0 encoding=utf-8?
mx:Application layout=vertical height=700 width=850
xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
xmlns:mx=library://ns.adobe.com/flex/mx
initialize=init(event)
fx:Script
![CDATA[
import mx.events.FlexEvent;
import mx.collections.*;
import mx.controls.NumericStepper;
import mx.formatters.CurrencyFormatter;
import mx.styles.StyleManager;
import mx.controls.advancedDataGridClasses.*;
protected function init(event:FlexEvent):void
{
createColumnGroups();
groupedData();
mydatagrid.expandAll();
}
[Bindable]
private var ac:ArrayCollection = new
ArrayCollection();
public var companies:AdvancedDataGridColumn =
new AdvancedDataGridColumn(Company);
public var quarters:AdvancedDataGridColumn =
new AdvancedDataGridColumn(Quarter);
public var india:AdvancedDataGridColumn = new
AdvancedDataGridColumn(India);
public var veeranistan:AdvancedDataGridColumn
= new AdvancedDataGridColumn(Veeranistan);
public var pareestan:AdvancedDataGridColumn =
new AdvancedDataGridColumn(Pareestan);
public var licenses:AdvancedDataGridColumn =
new AdvancedDataGridColumn(Licenses);
public var
countries:AdvancedDataGridColumnGroup = new AdvancedDataGridColumnGroup();
public var toplevel:AdvancedDataGridColumnGroup
= new AdvancedDataGridColumnGroup();
[Bindable]
public var hierarch_data:Array = [
{ feature:ADG, children:[
{ feature:ADG, subFeature:Multi column
sorting, startDate:{day:Monday, Year:2007}, endDate:1/07/07 },
{ feature:ADG, subFeature:Custom rows,
startDate:{day:Monday, Year:2009}, endDate:01/18/07 },
{ feature:ADG, subFeature:Tree Views,
startDate:{day:Monday, Year:2006}, endDate:01/29/07 },
{ feature:ADG, subFeature:Collections,
startDate:{day:Monday, Year:2004}, endDate:04/25/07 }
] }
];
[Bindable]
private var mydata:ArrayCollection = new
ArrayCollection ([
{Company:Adobe, Quarter:1, India:2 million,
Veeranistan:2 million, Pareestan:3 million, Licenses:433764538},
{Company:IBM, Quarter:1, India:9 million,
Veeranistan:1 million, Pareestan:5 million, Licenses:456789002},
{Company:KaashifSoft, Quarter:1, India:99
million, Veeranistan:99 million, Pareestan:99 million, Licenses:456712340},
{Company:NisheetSoft, Quarter:1, India:0
million, Veeranistan:0 million, Pareestan:0 million, Licenses:456782313},
{Company:Microsoft, Quarter:1, India:6
million, Veeranistan:5 million, Pareestan:6 million, Licenses:354216789},
{Company:Satyam, Quarter:1, India:1
million, Veeranistan:3 million, Pareestan:2 million, Licenses:325146789},
{Company:Subex, Quarter:1, India:2 million,
Veeranistan:9 million, Pareestan:1 million, Licenses:321456978},
{Company:Infosys, Quarter:1, India:0.89
million, Veeranistan:12 million, Pareestan:4.5 million,
Licenses:321475689},
{Company:MCAfee, Quarter:1, India:3
million, Veeranistan:5.98 million, Pareestan:6.2 million,
Licenses:321467589},
{Company:MPhasis, Quarter:1, India:2
million, Veeranistan:1.5 million, Pareestan:6.7 million,
Licenses:123456789},
Re: Popups in Flex 4 / FlexJS
Hi Alex, I think is a good approach. PopUpManager should not be present unless application requeriments needed. As well a more advanced manager like an MDIManager would be required if application is MDI, something that we don't have in Flex 4 out-of-the-box. So maybe Managers could be added as beads at application level so you add as needed. I think popups should be parented by application by default but could be configured to be parented by some specific view. In this way when using MVC frameworks like Swiz with modules, popups can dispatch events easily that will be managed by application or by a module so beanproviders can break into parts and and each domain could handle its events. If there's no event to be managed at that level, it could continue bubbling so it can be handled by other parent and in the end by main application. I think z-order will be managed by the manager using the mark you sugested, and I think it should support grouping or something that could make easy to handle a discrete set of popups. Right now we have PopUpManagerChildList with just 3 preset spaces APPLICATION, POPUP and PARENT and although this could work since parent could be the root of a group, I remember to have many problems in the past (I should revise it since maybe it was due to some bugs that could be solved now that we are in Apache). Maybe someone more could add his point of views to this thread so we can complete more info about this? 2013/6/8 Alex Harui aha...@adobe.com Hi Carlos, Thanks for bringing this up. The plan is to change the popup implementation, but it isn't completely settled on how, so any input is welcome. In FlexJS, the Application is not a display object. That's because it encourages you to separate your views from other code, and because it didn't make sense to tie the JS Application to Body. So, generally, you will have a main View. It will not be the SWF root in AS, and it will probably be the Body in JS. My current thinking is that Popups will just get added to the main view via addToParent() but marked as a popup. That allows you to plug-in different popupmanagers that manage child order based on different strategies. Simple apps don't really need a popupmanager at all unless they have non-modal floating windows, and simple apps don't have to carry around all the MDI overlapping windows code either. So, I think the View will parent the popup and events will bubble up to the View. But this is not set in stone yet. Much more prototyping and input is needed. -Alex On 6/7/13 3:08 PM, Carlos Rovira carlosrov...@apache.org wrote: The thread opened by Peter about Alert, is very interesting since there's some question about underlying Popups in actual Flex 4 that I will like to see if can be enhanced in FlexJS. Maybe others could thing are ok with actual implementation, so for this reason is better to discuss a bit. One legacy thing about PopUps in Flex that I think should be discussed is the location in displaylist tree. Actualy we have sys manager as root and the Application and then 1..n popups as childrens. This make difficult sometimes to handle events since popups are separated from the application that usualy launch it. For example in MVC frameworks like Swiz this break general management of events (that use to bubble) since popups does not find the dispatcher necessary for your code to work. Other issue is that actualiy is more easy implement an MDI system in the Application layer domain that in Popups zone, but at the price that you loose activation/desactivation feature (and it's skin representation). So what do you think. A new implementation should be in the same tree structure pattern or you think this could be changed to other implementation? -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: UIComponent lifecycle and invalidation in FlexJS
I see the point. I think JS version could live without invalidation, as I think this was always its nature, but SWF version maybe not...as you said maybe it's better to see how far can we reach without this lifecycle. In Flex 4, for displaylist invalidation and components visuals redraw, users need less traditional techniques since we have skins and FXG. I mean, I need rarely to override updateDisplayList (but sometimes is needed, and it end happening at skin level...). I'm talking of desktop/browser flex since mobile is 100% programatic skinning. As you point measurement is even less rare and even component developers could get his work done without implement a measurement method in this component. The invalidating properties is needed since ordering is important and in component development 100% of times you need to make properties, and override commitProperties method to make things happen in the right time and in the right order. So in my experience, this should be needed. 2013/6/8 Alex Harui aha...@adobe.com On 6/7/13 3:15 PM, Carlos Rovira carlosrov...@apache.org wrote: I ask it some time ago and I think it was not taken into account, but I think it's important. Right now FlexJS brings lots of new concepts like strands and beads or new mxml on the fly but I don't see old but good techniques of legacy Flex 4. One legacy thing I like was UIComponent lifecycle and it's invalidation mechanism. I assume that maybe it's too soon and until now nobody tried to implement this. But I want to ask since maybe Alex, Peter and others does not want such lifecycle for UIComponents. I think we should discuss a bit about what we want in this section and if we could plan to have something in the line of what we already have in Flex or people are considering new approaches. Good topic as well. Right now, I want to see how far we can go in FlexJS without invalidation. That's because current Flex relies on frame events to pump validation and there is no such thing as frame events in HTML/JS and I'd rather not keep hooking up to setTimeout. But that is not set in stone either. In fact, Peter and I were discussing this topic in relation to the Alert classes he is building as he needed to measure some text. It turns out that the measuring phase in current Flex is not always useful and sometimes wasteful. Currently Flex measures every component on the display list from the bottom up, but quite often, layout is driven from the top by percentages and other constraints and the measurements are not needed up front. FlexJS is attempting to do more things on-demand so instead of measuring everything, we're going to see if we can get away with measuring only when we need to. Invalidation is good when changing a bunch of properties at once, especially when properties needed to be applied in a certain order. The question is whether that needs to be handled globally like a LayoutManager or some more internal callLater feature on a per-instance basis. Like I said, nothing is set in stone, so thoughts on this topic are welcome. -Alex -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: Adobe bug / jira offline?
I figured you would have a copy of the attachments so I wasn't worried. But it does make the old issues hard to take care of... even if they are so old, they are a low-priority lol. You probably don't have much time to write the tools atm either, you've been busy. Should we change the old Adobe imported ones so they don't show up as major / unassigned issues? -Mark On Sat, Jun 8, 2013 at 2:44 AM, Alex Harui aha...@adobe.com wrote: On 6/7/13 4:43 PM, Mark Kessler kesslerconsult...@gmail.com wrote: The new bugbase does not have any of the Adobe Flex tickets in it... or list that it was a product. Does this mean we can mark all those issues from 2007/2008 that have inaccessible (well at least right now) attachments from the Adobe bugs... as resolved / incomplete :P Yeah, I thought they were going to make a static copies of the bugs. I'll have to check into that. I have almost all of the attachments, but there is no easy way to re-import them into Apache JIRA. It is on my list to write a custom tool to try to create a new import file that retains all of the current state of Apache JIRA.
Build failed in Jenkins: flex-sdk #76
See https://builds.apache.org/job/flex-sdk/76/ -- Started by timer Building remotely on windows1 in workspace https://builds.apache.org/job/flex-sdk/ws/ Checkout:flex-sdk / https://builds.apache.org/job/flex-sdk/ws/ - hudson.remoting.Channel@69621882:windows1 Using strategy: Default Last Built Revision: Revision 051867db4ea16ecf58354705befd3f1ab49fbe13 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/flex-sdk.git ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command git fetch -t https://git-wip-us.apache.org/repos/asf/flex-sdk.git +refs/heads/*:refs/remotes/origin/* returned status code 128: stdout: stderr: error: Failed connect to git-wip-us.apache.org:443; No error while accessing https://git-wip-us.apache.org/repos/asf/flex-sdk.git/info/refs?service=git-upload-pack fatal: HTTP request failed at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:858) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:200) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1105) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:813) at hudson.plugins.git.GitSCM.access$100(GitSCM.java:72) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1018) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository hudson.plugins.git.GitException: Could not fetch from any repository at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1025) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source)
Re: [DISCUSS] Alerts and Dialogs in FlexJS
My immediate thought on the delegate pattern is that it feels a little awkward. As a flex dev, I feel the event flow would be more familiar, but I guess we need to ask ourselves whether these api's will be used by old flex hats or whether we're appealing to a new group of developers. Maybe you could show some code to illustrate how it would work, for those not familiar with objective c and ios dev. In the mxml implementation it would be good to include a declarative display control similar to what we have in popup-wrapper. Espen - Original Message - From: Peter Ent [mailto:p...@adobe.com] Sent: Friday, June 07, 2013 08:52 PM GMT Standard Time To: flex-...@incubator.apache.org flex-...@incubator.apache.org Subject: [DISCUSS] Alerts and Dialogs in FlexJS Hi, I'm currently working on the Alert dialog for FlexJS. Alex and I have been discussing options regarding event handling from the Alert dialog which could provide a pattern for future dialogs. We thought it would been good to get some opinions. In Flex you normally post an Alert dialog using Alert.show() and pass it a closeFunction. The returned Alert instance can be used to listen for events for whatever else you want to do with it. The closeFunction is optional as you can also listen for events. We thought of these possibilities: Events: make the FlexJS Alert work the same - create an Alert instance and then listen for events. Delegate pattern: register an object (probably the instance that is posting the Alert) as a delegate and implement one or more callbacks. This is how you would do it in iOS, for example. Declare in MXML, something like this: fx:Declarations basic:Alert id=foo title=Panic message=Yowza! ok=doSomething() cancel=doSomethingElse() / /fx:Declarations These are not mutually exclusive by any means. Thoughts? Preferences? Peter Ent Flex SDK Team Adobe Systems This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
Re: Adobe bug / jira offline?
Hi, You probably don't have much time to write the tools atm either, you've been busy. Should we change the old Adobe imported ones so they don't show up as major / unassigned issues? -1 Until we know that they are still not bugs that effects the current SDK I'd leave them open. Justin
Re: [DISCUSS] Alerts and Dialogs in FlexJS
2013/6/8 Alex Harui aha...@adobe.com Good point, we forgot about that. It might be possible to use includeIn to defer its instantiation or add some other attribute that works like that but isn't tied to states. So from your response seems you're thinking in a state implementation similar to what we have today in flex 4, isn't it? Regarding deferred implementation maybe the proposal could be something like a value object that holds all config properties of the alert dialog (this will be the example posted by Peter) and the show method will be the one that unchains the process of create the UI Object through a static method. So all alerts VOs will be only a proxy that are very light weight and only it will pay as you go when calling show through delegating the work to the class that generates the fat UI object.
Re: FlexUnit Wiki Status
Thanks Mike.. I'll have a look at it. Cyrill On Wed, Jun 5, 2013 at 7:57 AM, Michael A. Labriola labri...@digitalprimates.net wrote: .. you could add those files to https://issues.apache.org/jira/browse/FLEX-33490. If possible also html web content as a zip archive. So that we have got everything collected here at apache. For now I have added a comment to the issue with a download link. I wanted to get this off of my to-do list. Mike
Re: Adobe bug / jira offline?
On 6/8/13 7:07 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, You probably don't have much time to write the tools atm either, you've been busy. Should we change the old Adobe imported ones so they don't show up as major / unassigned issues? -1 Until we know that they are still not bugs that effects the current SDK I'd leave them open. If your goal is just to downgrade them from major to minor but leave them open, I guess I'm ok with that, but it would be better if you could check the vote count before you do that. I would argue if they had more than two or more votes they could still be considered major. The number of votes did not import from Adobe but should be in the comments as a text string. -Alex
Re: New Mustella Failures
IIRC, you added or removed a validateNow()? That could affect timing, so
the CompareBitmap may need or not need to WaitForLayoutManager. But if
waiting helps, consider that this could mean an app that's busy so the
frame rate slows might see a flicker.
On 6/8/13 2:34 AM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
1) ADG mirroring. The failing bitmap shows the text flipped (as if
viewed
in a mirror).
Look closer at the test it setting the layout direction RTL not the
direction so only the columns should be reverse order not the text.
Look like there's an issue with the test as the same code run in a
browser doesn't show the text mirrored.
here's the code:
?xml version=1.0 encoding=utf-8?
mx:Application layout=vertical height=700 width=850
xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
xmlns:mx=library://ns.adobe.com/flex/mx
initialize=init(event)
fx:Script
![CDATA[
import mx.events.FlexEvent;
import mx.collections.*;
import mx.controls.NumericStepper;
import mx.formatters.CurrencyFormatter;
import mx.styles.StyleManager;
import mx.controls.advancedDataGridClasses.*;
protected function init(event:FlexEvent):void
{
createColumnGroups();
groupedData();
mydatagrid.expandAll();
}
[Bindable]
private var ac:ArrayCollection = new
ArrayCollection();
public var companies:AdvancedDataGridColumn =
new
AdvancedDataGridColumn(Company);
public var quarters:AdvancedDataGridColumn =
new
AdvancedDataGridColumn(Quarter);
public var india:AdvancedDataGridColumn = new
AdvancedDataGridColumn(India);
public var veeranistan:AdvancedDataGridColumn
= new
AdvancedDataGridColumn(Veeranistan);
public var pareestan:AdvancedDataGridColumn =
new
AdvancedDataGridColumn(Pareestan);
public var licenses:AdvancedDataGridColumn =
new
AdvancedDataGridColumn(Licenses);
public var
countries:AdvancedDataGridColumnGroup = new
AdvancedDataGridColumnGroup();
public var toplevel:AdvancedDataGridColumnGroup
= new
AdvancedDataGridColumnGroup();
[Bindable]
public var hierarch_data:Array = [
{ feature:ADG, children:[
{ feature:ADG, subFeature:Multi column
sorting,
startDate:{day:Monday, Year:2007}, endDate:1/07/07 },
{ feature:ADG, subFeature:Custom rows,
startDate:{day:Monday,
Year:2009}, endDate:01/18/07 },
{ feature:ADG, subFeature:Tree Views,
startDate:{day:Monday,
Year:2006}, endDate:01/29/07 },
{ feature:ADG, subFeature:Collections,
startDate:{day:Monday,
Year:2004}, endDate:04/25/07 }
] }
];
[Bindable]
private var mydata:ArrayCollection = new
ArrayCollection ([
{Company:Adobe, Quarter:1, India:2 million,
Veeranistan:2
million, Pareestan:3 million, Licenses:433764538},
{Company:IBM, Quarter:1, India:9 million,
Veeranistan:1
million, Pareestan:5 million, Licenses:456789002},
{Company:KaashifSoft, Quarter:1, India:99
million,
Veeranistan:99 million, Pareestan:99 million, Licenses:456712340},
{Company:NisheetSoft, Quarter:1, India:0
million, Veeranistan:0
million, Pareestan:0 million, Licenses:456782313},
{Company:Microsoft, Quarter:1, India:6
million, Veeranistan:5
million, Pareestan:6 million, Licenses:354216789},
{Company:Satyam, Quarter:1, India:1
million, Veeranistan:3
million, Pareestan:2 million, Licenses:325146789},
{Company:Subex, Quarter:1, India:2 million,
Veeranistan:9
million, Pareestan:1 million, Licenses:321456978},
{Company:Infosys, Quarter:1, India:0.89
million, Veeranistan:12
million, Pareestan:4.5 million, Licenses:321475689},
{Company:MCAfee, Quarter:1,
Build failed in Jenkins: flex-sdk_mustella #146
See http://localhost:8080/job/flex-sdk_mustella/146/changes Changes: [aharui] Try to use XML diffs to be tolerant of small floating point differences [aharui] fix bugs in xmldiffer [aharui] fix bug in xmldiffer [jmclean] Fix file case issue. [jmclean] Fix file case issues [jmclean] Changed case a file [jmclean] Fix file case issues [aharui] fix timing problem in Alert test [aharui] attempt to fix mustella tests on the VM [bigosmallm] Added create-md5 target in build.xml. Will be useful when creating artifacts on the build server. [bigosmallm] Using algorithm=md5 when generating md5 checksum because .md5 != .MD5 [aharui] These tests didn't have fonts embedded correctly [aharui] expand tolerance on some tests -- [...truncated 80814 lines...] [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_star_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_arrow_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_colon_script_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_invalid_null_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_invalid_empty_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_bindingWithLocaleChange_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_bindingWithLocaleChange_script_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_star_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_semicolonstar_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_colon_script_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_priod_script_test20 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_minus_script_test21 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_illegalNumber_test22 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_getterWithoutLocale_test23 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_getterWithoutLocale_script_test23 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_setToNumber_test24 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_setToNumber_script_test25 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_defaultValue_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_setInlineValue_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_i_default_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_zh_TW_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_ar_JO_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_bn_BD_test6 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_en_US_test7 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_globalSelector_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_classSelector_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_IDSelector_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester
Re: New Mustella Failures
The validate now was being called multiple times - removing it significantly improved performance. Why is the text reversed in the bitmap only the columns should be in reverse order.
Re: Build failed in Jenkins: flex-sdk_mustella #146
This is progress! Down to 15 failures now. Om On Jun 8, 2013 9:15 AM, flex.muste...@gmail.com wrote: See http://localhost:8080/job/flex-sdk_mustella/146/changes Changes: [aharui] Try to use XML diffs to be tolerant of small floating point differences [aharui] fix bugs in xmldiffer [aharui] fix bug in xmldiffer [jmclean] Fix file case issue. [jmclean] Fix file case issues [jmclean] Changed case a file [jmclean] Fix file case issues [aharui] fix timing problem in Alert test [aharui] attempt to fix mustella tests on the VM [bigosmallm] Added create-md5 target in build.xml. Will be useful when creating artifacts on the build server. [bigosmallm] Using algorithm=md5 when generating md5 checksum because .md5 != .MD5 [aharui] These tests didn't have fonts embedded correctly [aharui] expand tolerance on some tests -- [...truncated 80814 lines...] [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_star_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_arrow_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_colon_script_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_invalid_null_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_invalid_empty_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_bindingWithLocaleChange_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_bindingWithLocaleChange_script_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_star_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_semicolonstar_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_colon_script_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_priod_script_test20 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_minus_script_test21 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_illegalNumber_test22 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_getterWithoutLocale_test23 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_getterWithoutLocale_script_test23 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_setToNumber_test24 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_setToNumber_script_test25 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_defaultValue_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_setInlineValue_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_i_default_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_zh_TW_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_ar_JO_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_bn_BD_test6 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_en_US_test7 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_globalSelector_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_classSelector_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_IDSelector_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_priority_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester NV_localStyle_typeSelector_TypeStyle_test1 Passed
Re: [DISCUSS] Alerts and Dialogs in FlexJS
@Carlos: Interesting idea. I had already created a Flex 4 implementation of PopUp / Alert that can be used in a declarative way (see https://github.com/RIAstar/SkinnablePopUpFx). I'll see if I can tweak it to leverage your idea; don't think it should be too hard. Max On Sat, Jun 8, 2013 at 4:30 PM, Carlos Rovira carlosrov...@apache.orgwrote: 2013/6/8 Alex Harui aha...@adobe.com Good point, we forgot about that. It might be possible to use includeIn to defer its instantiation or add some other attribute that works like that but isn't tied to states. So from your response seems you're thinking in a state implementation similar to what we have today in flex 4, isn't it? Regarding deferred implementation maybe the proposal could be something like a value object that holds all config properties of the alert dialog (this will be the example posted by Peter) and the show method will be the one that unchains the process of create the UI Object through a static method. So all alerts VOs will be only a proxy that are very light weight and only it will pay as you go when calling show through delegating the work to the class that generates the fat UI object.
Build failed in Jenkins: flex-sdk_asdoc #27
See https://builds.apache.org/job/flex-sdk_asdoc/27/ -- Started by timer Building remotely on windows1 in workspace https://builds.apache.org/job/flex-sdk_asdoc/ws/ Checkout:flex-sdk_asdoc / https://builds.apache.org/job/flex-sdk_asdoc/ws/ - hudson.remoting.Channel@69621882:windows1 Using strategy: Default Last Built Revision: Revision 2601af62943e24e32d4d8c90fe9fc20b30b8b50d (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/flex-sdk.git ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command git fetch -t https://git-wip-us.apache.org/repos/asf/flex-sdk.git +refs/heads/*:refs/remotes/origin/* returned status code 128: stdout: stderr: error: The requested URL returned error: 503 while accessing https://git-wip-us.apache.org/repos/asf/flex-sdk.git/info/refs?service=git-upload-pack fatal: HTTP request failed at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:858) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:200) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1105) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:813) at hudson.plugins.git.GitSCM.access$100(GitSCM.java:72) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1018) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository hudson.plugins.git.GitException: Could not fetch from any repository at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1025) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source)
Re: [DISCUSS] Alerts and Dialogs in FlexJS
Right, that turned out to be harder than I anticipated. To get this to work I had to do the following things: - redeclare all event metadata that is declared by the Alert component and its base classes (to be able to use mxml event handlers) - extend EvenDispatcher and relay all events dispatched by the Alert instance - redeclare all style metadata that is declared by the Alert component and its base classes (to be able to use mxml style attributes) - implement IStyleClient (same reason) - cache the styles and assign them to the instance once created - decorate all properties exposed by Alert and its base classes (to be able to use mxml properties) - cache the properties and assign them to the instance once created The resulting delegate class can be found here: https://github.com/RIAstar/SkinnablePopUpFx/blob/delegate/skinnable-popup-fx/src/main/actionscript/net/riastar/components/AlertDelegate.as You can play around with the compiled result here: http://riastar.github.io/SkinnablePopUpFx/ I didn't decorate all of the properties/styles/events (just the ones to get the demo working), but the resulting code is already bigger than the Alert class itself :( So I'm not so sure if it's still such a great idea. To be complete you'd have to wrap every property, style and event of SkinnableComponent and UIComponent, and there are a lot of them. And we're not even talking about methods: suppose someone wants to call `alert.addElement(someElement)`... Of course this is good old Flex 4; perhaps this can be solved another way in FlexJS? Max On Sat, Jun 8, 2013 at 9:13 PM, Maxime Cowez maxime.co...@gmail.com wrote: @Carlos: Interesting idea. I had already created a Flex 4 implementation of PopUp / Alert that can be used in a declarative way (see https://github.com/RIAstar/SkinnablePopUpFx). I'll see if I can tweak it to leverage your idea; don't think it should be too hard. Max On Sat, Jun 8, 2013 at 4:30 PM, Carlos Rovira carlosrov...@apache.orgwrote: 2013/6/8 Alex Harui aha...@adobe.com Good point, we forgot about that. It might be possible to use includeIn to defer its instantiation or add some other attribute that works like that but isn't tied to states. So from your response seems you're thinking in a state implementation similar to what we have today in flex 4, isn't it? Regarding deferred implementation maybe the proposal could be something like a value object that holds all config properties of the alert dialog (this will be the example posted by Peter) and the show method will be the one that unchains the process of create the UI Object through a static method. So all alerts VOs will be only a proxy that are very light weight and only it will pay as you go when calling show through delegating the work to the class that generates the fat UI object.
Re: Adobe bug / jira offline?
Well not sure what to do with them really. Wouldn't mind just knocking some of them out from time to time. But if you can't replicate them properly it would be nice at least downgrade them. -Mark On Sat, Jun 8, 2013 at 11:13 AM, Alex Harui aha...@adobe.com wrote: On 6/8/13 7:07 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, You probably don't have much time to write the tools atm either, you've been busy. Should we change the old Adobe imported ones so they don't show up as major / unassigned issues? -1 Until we know that they are still not bugs that effects the current SDK I'd leave them open. If your goal is just to downgrade them from major to minor but leave them open, I guess I'm ok with that, but it would be better if you could check the vote count before you do that. I would argue if they had more than two or more votes they could still be considered major. The number of votes did not import from Adobe but should be in the comments as a text string. -Alex
Re: Adobe bug / jira offline?
Not sure what you mean by properly. Because of the way JIRA databases work, it is a ton of work to migrate JIRA systems. You need to have the same user names in the destination system and/or map to new names which is impractical especially given that I believe a lot of the Adobe JIRA users are simply gone from the world of Flex. So, the best I think we can do is what we've done, except that we didn't get attachments and may have messed up some of the statuses, duplicated some issues and probably missed a few as well. On 6/8/13 7:56 PM, Mark Kessler kesslerconsult...@gmail.com wrote: Well not sure what to do with them really. Wouldn't mind just knocking some of them out from time to time. But if you can't replicate them properly it would be nice at least downgrade them. -Mark On Sat, Jun 8, 2013 at 11:13 AM, Alex Harui aha...@adobe.com wrote: On 6/8/13 7:07 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, You probably don't have much time to write the tools atm either, you've been busy. Should we change the old Adobe imported ones so they don't show up as major / unassigned issues? -1 Until we know that they are still not bugs that effects the current SDK I'd leave them open. If your goal is just to downgrade them from major to minor but leave them open, I guess I'm ok with that, but it would be better if you could check the vote count before you do that. I would argue if they had more than two or more votes they could still be considered major. The number of votes did not import from Adobe but should be in the comments as a text string. -Alex
Re: [DISCUSS] Alerts and Dialogs in FlexJS
Sounds interesting. If one of you can sketch out what the MXML would look like, it would help clarify what you're thinking. -Alex On 6/8/13 12:13 PM, Maxime Cowez maxime.co...@gmail.com wrote: @Carlos: Interesting idea. I had already created a Flex 4 implementation of PopUp / Alert that can be used in a declarative way (see https://github.com/RIAstar/SkinnablePopUpFx). I'll see if I can tweak it to leverage your idea; don't think it should be too hard. Max On Sat, Jun 8, 2013 at 4:30 PM, Carlos Rovira carlosrov...@apache.orgwrote: 2013/6/8 Alex Harui aha...@adobe.com Good point, we forgot about that. It might be possible to use includeIn to defer its instantiation or add some other attribute that works like that but isn't tied to states. So from your response seems you're thinking in a state implementation similar to what we have today in flex 4, isn't it? Regarding deferred implementation maybe the proposal could be something like a value object that holds all config properties of the alert dialog (this will be the example posted by Peter) and the show method will be the one that unchains the process of create the UI Object through a static method. So all alerts VOs will be only a proxy that are very light weight and only it will pay as you go when calling show through delegating the work to the class that generates the fat UI object.
Re: New Mustella Failures
On 6/8/13 11:15 AM, Justin Mclean jus...@classsoftware.com wrote: The validate now was being called multiple times - removing it significantly improved performance. Why is the text reversed in the bitmap only the columns should be in reverse order. Don't know OTOH. One possibility is that now that validateNow isn't being called it gets validated and the text is fixed on some later frame, which could be after compareBitmap does its thing. I can put this on my list of things to dig into after I get other mustella failures on the VM resolved. Let me know. -Alex
Re: Build failed in Jenkins: flex-sdk_mustella #146
Bummer. Was hoping for less than 6. Back to digging. From: OmPrakash Muppirala bigosma...@gmail.commailto:bigosma...@gmail.com Date: Saturday, June 8, 2013 11:56 AM To: dev@flex.apache.orgmailto:dev@flex.apache.org dev@flex.apache.orgmailto:dev@flex.apache.org Cc: erikdebr...@apache.orgmailto:erikdebr...@apache.org erikdebr...@apache.orgmailto:erikdebr...@apache.org, aha...@apache.orgmailto:aha...@apache.org aha...@apache.orgmailto:aha...@apache.org, jmcl...@apache.orgmailto:jmcl...@apache.org jmcl...@apache.orgmailto:jmcl...@apache.org Subject: Re: Build failed in Jenkins: flex-sdk_mustella #146 This is progress! Down to 15 failures now. Om On Jun 8, 2013 9:15 AM, flex.muste...@gmail.commailto:flex.muste...@gmail.com wrote: See http://localhost:8080/job/flex-sdk_mustella/146/changes Changes: [aharui] Try to use XML diffs to be tolerant of small floating point differences [aharui] fix bugs in xmldiffer [aharui] fix bug in xmldiffer [jmclean] Fix file case issue. [jmclean] Fix file case issues [jmclean] Changed case a file [jmclean] Fix file case issues [aharui] fix timing problem in Alert test [aharui] attempt to fix mustella tests on the VM [bigosmallm] Added create-md5 target in build.xml. Will be useful when creating artifacts on the build server. [bigosmallm] Using algorithm=md5 when generating md5 checksum because .md5 != .MD5 [aharui] These tests didn't have fonts embedded correctly [aharui] expand tolerance on some tests -- [...truncated 80814 lines...] [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_star_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_arrow_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_binding_colon_script_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_invalid_null_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_invalid_empty_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_bindingWithLocaleChange_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_bindingWithLocaleChange_script_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_star_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_semicolonstar_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_colon_script_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_priod_script_test20 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_minus_script_test21 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_function_illegalNumber_test22 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_getterWithoutLocale_test23 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_getterWithoutLocale_script_test23 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_setToNumber_test24 Passed [java] spark/validators/NumberValidator/Properties/NV_groupingSeparator_tester NV_groupingSeparator_setToNumber_script_test25 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_defaultValue_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_setInlineValue_test2 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_i_default_test3 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_zh_TW_test4 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_ar_JO_test5 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_bn_BD_test6 Passed [java] spark/validators/NumberValidator/Styles/NV_inline_style_tester NV_inline_style_useSetStyleMethod_en_US_test7 Passed [java] spark/validators/NumberValidator/Styles/NV_localCSSStyle_tester NV_localCSSStyle_globalSelector_test1 Passed [java]
