Re: [TLF] merge 'tables' into 'develop'
Hi,
Good news: the test suite ('ant all') now runs to completion. This is
the summary:
[flexunit] Tests run: 381, Failures: 3, Errors: 11, Skipped: 39, Time
elapsed: 574.023 sec
Is that what you would expect? Or do you need more details?
EdB
On Thu, Nov 27, 2014 at 3:40 PM, piotrz wrote:
> Many Thanks Erik for Helping with this!
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/TLF-merge-tables-into-develop-tp42713p42803.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [TLF] merge 'tables' into 'develop'
I've merged everything from tables to develop branch. I've removed from tests one class OpeationTest which causes freeze of our test - Need to investigate why it's happened. Tests freezing in this class quite random. :( It's not good that any tests failed and these errors also worrying me. Reports for failed tests FloatTest [1], FlowModelTest [2], ContainerAttributeTest Because so many tests are failed I think something has to be broken in TLF or these tests are not suit to current changed code. [1] http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.FloatTest.xml [2] http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.FlowModelTest.xml [3] http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.ContainerAttributeTest.xml Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/TLF-merge-tables-into-develop-tp42713p42826.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Clean up remote branches in git
Hi, Would y'all please take a look at the remote branches in the SDK repo? It looks to me that the majority have already been merged back into 'develop' and don't serve any purpose anymore. Can you please remove any branches you created that have become obsolete? Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [TLF] merge 'tables' into 'develop'
I will investigate early next week why we’re getting failures. I’ll start with the FloatTests and see what I come up with. On Nov 28, 2014, at 10:16 AM, piotrz wrote: > I've merged everything from tables to develop branch. > I've removed from tests one class OpeationTest which causes freeze of our > test - Need to investigate why it's happened. Tests freezing in this class > quite random. :( > > It's not good that any tests failed and these errors also worrying me. > > Reports for failed tests FloatTest [1], FlowModelTest [2], > ContainerAttributeTest > > Because so many tests are failed I think something has to be broken in TLF > or these tests are not suit to current changed code. > > [1] > http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.FloatTest.xml > [2] > http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.FlowModelTest.xml > [3] > http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.ContainerAttributeTest.xml > > Piotr > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: > http://apache-flex-development.247.n4.nabble.com/TLF-merge-tables-into-develop-tp42713p42826.html > Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [TLF] merge 'tables' into 'develop'
I’m also pretty sure there’s a bug somewhere in at least some Operations. I’ll look at that as well… On Nov 28, 2014, at 11:05 AM, Harbs wrote: > I will investigate early next week why we’re getting failures. I’ll start > with the FloatTests and see what I come up with. > > On Nov 28, 2014, at 10:16 AM, piotrz wrote: > >> I've merged everything from tables to develop branch. >> I've removed from tests one class OpeationTest which causes freeze of our >> test - Need to investigate why it's happened. Tests freezing in this class >> quite random. :( >> >> It's not good that any tests failed and these errors also worrying me. >> >> Reports for failed tests FloatTest [1], FlowModelTest [2], >> ContainerAttributeTest >> >> Because so many tests are failed I think something has to be broken in TLF >> or these tests are not suit to current changed code. >> >> [1] >> http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.FloatTest.xml >> [2] >> http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.FlowModelTest.xml >> [3] >> http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/automation_apps/bin/TEST-UnitTest.Tests.ContainerAttributeTest.xml >> >> Piotr >> >> >> >> - >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: >> http://apache-flex-development.247.n4.nabble.com/TLF-merge-tables-into-develop-tp42713p42826.html >> Sent from the Apache Flex Development mailing list archive at Nabble.com. >
Re: [TLF] merge 'tables' into 'develop'
Thank you Harbs! Just remember if you would like to check any specific test class you have to add it to MinimalTestSuite.as and run minimal test mode. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/TLF-merge-tables-into-develop-tp42713p42830.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
AW: AW: Updated Flex-SDK to use apache-flex blazeds :-)
Hi Alex, unfortunatly I couldn't look into this prior to today :-( I just had a look ... the structure of the opt project is a little strange. It has one shared src directory which contains the java code for all opt packages. In the "opt/poms" directory there is a module for every target platform which consists of a pom. Inside these poms, all reference the source directory two steps up and tell the compiler which classes to use (Actually the same way the Ant build does it). The content you found in the samplewebapp/WEB-INF/lib/flex-messaging-opt.jar actually is identical to the jat produced by the baven build in the directory flex-blazeds/modules/opt/poms/tomcat6/target So I still don't get the problem :-( Chris Von: Alex Harui Gesendet: Montag, 24. November 2014 18:29 An: dev@flex.apache.org Betreff: Re: AW: Updated Flex-SDK to use apache-flex blazeds :-) On 11/24/14, 1:07 AM, "Christofer Dutz" wrote: >Then my assumption was correct. In the ant build they bundled the content >of the other modules into each opt module. I’m not sure I understand. The classes in flex-messaging-opt.jar are not in the other jars in the Ant build of BlazeDS, and the source for those classes is in the modules/opt folder. I would agree that it would be bad for a class to be in more than one jar and would be interested in figuring out a way to avoid such a situation, but I’m not seeing it here. Here’s what I see in the JAR. ~/apache-tomcat-6.0.41/webapps/samplewebapp/WEB-INF/lib$ jar -tf ~/flex-messaging-opt.jar META-INF/ META-INF/MANIFEST.MF flex/ flex/messaging/ flex/messaging/security/ flex/messaging/security/TomcatLogin.class flex/messaging/security/TomcatLoginCommand.class flex/messaging/security/TomcatLoginHolder.class flex/messaging/security/TomcatValve$TomcatLoginImpl.class flex/messaging/security/TomcatValve.class flex/messaging/vendors.properties META-INF/DEPENDENCIES META-INF/LICENSE META-INF/NOTICE META-INF/maven/ META-INF/maven/org.apache.flex.blazeds/ META-INF/maven/org.apache.flex.blazeds/flex-messaging-opt-tomcat6/ META-INF/maven/org.apache.flex.blazeds/flex-messaging-opt-tomcat6/pom.xml META-INF/maven/org.apache.flex.blazeds/flex-messaging-opt-tomcat6/pom.prope rties ~/git/flex/master/flex-blazeds$ find . -name Tom*.java ./modules/opt/src/tomcat/flex/messaging/security/Tomcat7Valve.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatLogin.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatLoginHolder.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatValve.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatValve4150.java -Alex
Re: [DISCUSSION] TourDeFlex 1.2 RC2
Hi, Please read my emails as RM I didn't carry over votes for a good reason. There's only 2 +1 votes on this RC and it requires one more +1 to be released. Or would the PMC rather I cancel the vote and make yet another RC to vote on? Thanks, Justin
Re: Tour de Flex Mobile
Great work :) I've done some testing and detected some bugs so far: *ButtonBarView.mxml* Bug: Select a Button then Unselect it Fix: validate buttonbar.selectedIndex before get buttonbar.selectedItem.label label.text = buttonbar.selectedIndex > -1 ? buttonbar.selectedItem.label + " Pressed." : "No Button Pressed"; *ButtonBarSkin* If you add more than 3 buttons the button separator will be thicker only between the middle buttons. *ButtonSkin* Try two buttons side to side one with width=45 and another width=450. The Button skin does not resizes correctly. On buttonUp the border on the right side is bigger. On button down the border is bigger top, down, left and right. best regards, Carlos Monteiro On 17 November 2014 at 19:38, quick6black wrote: > Hi Om, > > I created another pull request, this fixes a few bugs and an issue with the > lateral menu sliding out. I also added in a drag to close and a new view > for > some more native air features. I would like to create a better landing > page, > any ideas? > > thanks, > > Aaron > > > > -- > View this message in context: > http://apache-flex-development.247.n4.nabble.com/Tour-de-Flex-Mobile-tp41483p42431.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. >
Re: [VOTE] TourDeFlex 1.2 Release Candidate 2
+1 (binding) EdB On Sun, Nov 23, 2014 at 7:10 PM, Justin Mclean wrote: > Hi, > > This is a TourDeFlex 1.2 Release Candidate 2. Please see the RELEASE_NOTES > and the README. > > Changes since the last RC: > - Re added back in 3rd party examples > - Changes to NOTICE file > > The release candidate can be found here; > https://dist.apache.org/repos/dist/dev/flex/TourDeFlex/1.2/rc2/ > > Before voting please review the section,"What are the ASF requirements on > approving a release?", at: > http://www.apache.org/dev/release.html#approving-a-release > > Please vote to approve this release: > +1 Approve the release > -1 Veto the release (please provide specific comments to why) > > This vote will be open for at least 72 hours or as long as needed. > > The vote passes if there is: > - At least 3 +1 votes from the PMC > - More positive votes than negative votes > > People who are not in PMC or who are not an committer are also encouraged to > test out the release and vote, although their votes will not be binding. > > Please put all discussion about this release in the DISCUSS thread not this > VOTE thread. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Working on builds.apache.org
Hi, just wanted to tell you that I'm currently reviving some of the Jenkins jobs in order to get them up and running including tests on the Apache infra build. So if you got some build failure mails ... be sure to check what server they come from ;-) Currently even on my machine I get test failures on Falcon ... ist that normal or do I have to tweak yet another setting in order to have things green? I'm getting this: Running mxml.tags.MXMLHTTPServiceTagTests Error: Unable to resolve resource bundle 'styles' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'collections' Error: Unable to resolve resource bundle 'collections' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'core' Error: Unable to resolve resource bundle 'rpc' Error: Unable to resolve resource bundle 'collections' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'rpc' Error: Unable to resolve resource bundle 'rpc' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'rpc' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'rpc' Error: Unable to resolve resource bundle 'messaging' Error: Unable to resolve resource bundle 'collections' Error: Unable to resolve resource bundle 'logging' Error: Unable to resolve resource bundle 'logging' Error: Unable to resolve resource bundle 'messaging' Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1,241 sec /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/compiler.tests/build.xml:138: Tests failed at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.actOnTestResult(JUnitTask.java:2150) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:1101) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.oneJunitThread(JUnitTask.java:919) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.runTestsInThreads(JUnitTask.java:932) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:841) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.Main.start(Main.java:198) at org.apache.tools.ant.Main.main(Main.java:286) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.intellij.rt.ant.execution.AntMain2.main(AntMain2.java:30) /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/compiler.tests/build.xml:138: Tests failed at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.actOnTestResult(JUnitTask.java:2150) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:1101) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.oneJunitThread(JUnitTask.java:919) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.runTestsInThreads(JUnitTask.java:932) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUn
Jenkins builds and general structure of FlexJS/Falcon related project
Hi, today I worked on getting the Flex builds working on builds.apache.org. I changed the test runner in falcon to start the flashplayer with a timeout (currently set to 20 seconds as I asked someone of Infra to check what the flashplayer is complaining about ... but will set that back to 1 or 2 seconds as soon as that's done). Currently the entire tests had a timeout of 5 minutes after which the build just failled. I think this way individual tests will fail and we'll have the opportunity to check if any tests after that hanging one would pass. Second thing was that the flashplayer on builds.apache.org doesn't seem to be configured to dump the flashlog.txt, so I adjusted the build script only to copy this, if it exists. Now to my actual problem: I did get quite some of them running. But FlexJS is causing me a little headache. The problem is the build structure of the project in general. It contains Falcon as well as FlexJS, unfortunately FlexJS' tests need ASJS, which in turn needs Falcon. So we have sort of a "A --> B --> A" situation here. Is there any reason why we can't split up Falcon, FalconJX, FlexJS and VF2JS into 4 modules? Actually splitting up into Falcon and FalconJX should be enough, but I would really like to vote for completely separating FlexJS and VF2JS cause this could help find the placed where both are sharing static variables which is causing quite some pain for me in Flexmojos (The two buggers keep on overwriting their configs) ;-) If all were split up, we could create a build pipeline like this: - build flex-sdk - build falcon - build asjs - build falconjx ?Each would be a separate project for which jenkins is configured to execute in exactly this order. What do you think? Chris
Re: AW: AW: Updated Flex-SDK to use apache-flex blazeds :-)
On 11/28/14, 1:55 AM, "Christofer Dutz" wrote: >The content you found in the >samplewebapp/WEB-INF/lib/flex-messaging-opt.jar actually is identical to >the jat produced by the baven build in the directory >flex-blazeds/modules/opt/poms/tomcat6/target > >So I still don't get the problem :-( Ugh, my fault. That was the problem ;-). I didn’t realize there were more targets under modules/opt/poms. All of the other jars I needed were right under modules/xxx. I think we’re ok now. Sorry for the misunderstanding. Maybe the build could pull jars from out of the various places in the tree and flatten them all into one folder so Jenkins "Last Successful Artifacts” are easier to grab? -Alex
Re: Jenkins builds and general structure of FlexJS/Falcon related project
On 11/28/14, 8:29 AM, "Christofer Dutz" wrote: >I changed the test runner in falcon to start the flashplayer with a >timeout (currently set to 20 seconds as I asked someone of Infra to check >what the flashplayer is complaining about This is exactly why using builds.a.o for GUI tests is inefficient. You have to ask someone in Infra to tell you want is on the screen! There is a -Dis.jenkins=true option that I think will skip the GUI tests. That was my point in the other thread. If there is a way for the builds.a.o to trust what the built is good without running GUI tests you’ll probably save a lot of time and hassle. >The problem is the build structure of the project in general. > >It contains Falcon as well as FlexJS, unfortunately FlexJS' tests need >ASJS, which in turn needs Falcon. > >So we have sort of a "A --> B --> A" situation here. >If all were split up, we could create a build pipeline like this: > >- build flex-sdk > >- build falcon > >- build asjs > >- build falconjx > >?Each would be a separate project for which jenkins is configured to >execute in exactly this order. I’d like to solve the circularity as well, but ASJS will fail without FalconJX because it uses FalconJX for its tests. Basically, each one currently wants to test against the other. I’ll ponder this a bit more. -Alex
Re: Working on builds.apache.org
On 11/28/14, 5:20 AM, "Christofer Dutz" wrote: > >Currently even on my machine I get test failures on Falcon ... ist that >normal or do I have to tweak yet another setting in order to have things >green? > > >I'm getting this: > > >Running mxml.tags.MXMLHTTPServiceTagTests > >Error: Unable to resolve resource bundle 'styles' Those bundles come from flex-sdk. I think if you build the SDK bundles in en_US and compile the test in some other locale you can run into this sort of error. And vice-versa. -Alex
Re: Jenkins builds and general structure of FlexJS/Falcon related project
On 11/28/14, 8:54 AM, "Alex Harui" wrote: > > >On 11/28/14, 8:29 AM, "Christofer Dutz" wrote: >>The problem is the build structure of the project in general. >> >>It contains Falcon as well as FlexJS, unfortunately FlexJS' tests need >>ASJS, which in turn needs Falcon. >> >>So we have sort of a "A --> B --> A" situation here. >>If all were split up, we could create a build pipeline like this: >> >>- build flex-sdk >> >>- build falcon >> >>- build asjs >> >>- build falconjx >> >>?Each would be a separate project for which jenkins is configured to >>execute in exactly this order. > >I’d like to solve the circularity as well, but ASJS will fail without >FalconJX because it uses FalconJX for its tests. Basically, each one >currently wants to test against the other. > >I’ll ponder this a bit more. After pondering a bit, here’s my thinkings: I expect some contributors may only work in flex-asjs and not the compilers and vice-versa so having the build scripts in flex-asjs and flex-falcon each run tests that use the other project is desirable. But for CI, I think the important factor is that FlexJS not only uses FalconJX for testing, but also in the generation of one of its libraries. AS gets cross-compiled into JS. So maybe the answer is this: On the CI servers, they build the Falcon and FalconJX and run the their unit tests, and optionally flex-sdk integration/feature tests. Then build FlexJS and run its integration tests. Then run FalconJX’s integration/feature tests that require FlexJS. Thoughts? -Alex
AW: Jenkins builds and general structure of FlexJS/Falcon related project
Hi Alex, well I was simply assuming that something is generally not setup correctly and that one of them could simply check the reason for this and I was assuming that if we sort out the problem the tests could work fine. Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Freitag, 28. November 2014 17:55 An: dev@flex.apache.org Betreff: Re: Jenkins builds and general structure of FlexJS/Falcon related project On 11/28/14, 8:29 AM, "Christofer Dutz" wrote: >I changed the test runner in falcon to start the flashplayer with a >timeout (currently set to 20 seconds as I asked someone of Infra to >check what the flashplayer is complaining about This is exactly why using builds.a.o for GUI tests is inefficient. You have to ask someone in Infra to tell you want is on the screen! There is a -Dis.jenkins=true option that I think will skip the GUI tests. That was my point in the other thread. If there is a way for the builds.a.o to trust what the built is good without running GUI tests you’ll probably save a lot of time and hassle. >The problem is the build structure of the project in general. > >It contains Falcon as well as FlexJS, unfortunately FlexJS' tests need >ASJS, which in turn needs Falcon. > >So we have sort of a "A --> B --> A" situation here. >If all were split up, we could create a build pipeline like this: > >- build flex-sdk > >- build falcon > >- build asjs > >- build falconjx > >?Each would be a separate project for which jenkins is configured to >execute in exactly this order. I’d like to solve the circularity as well, but ASJS will fail without FalconJX because it uses FalconJX for its tests. Basically, each one currently wants to test against the other. I’ll ponder this a bit more. -Alex
Re: Tour de Flex Mobile
On Nov 28, 2014 2:17 AM, "Carlos Monteiro" wrote: > > Great work :) > I've done some testing and detected some bugs so far: > > *ButtonBarView.mxml* > Bug: Select a Button then Unselect it > Fix: validate buttonbar.selectedIndex before get > buttonbar.selectedItem.label > label.text = buttonbar.selectedIndex > -1 ? buttonbar.selectedItem.label + > " Pressed." : "No Button Pressed"; > > *ButtonBarSkin* > If you add more than 3 buttons the button separator will be thicker only > between the middle buttons. > > *ButtonSkin* > Try two buttons side to side one with width=45 and another width=450. > > The Button skin does not resizes correctly. > On buttonUp the border on the right side is bigger. > On button down the border is bigger top, down, left and right. > > best regards, > Carlos Monteiro Thanks for testing, Carlos! Would you be kind enough to add JIRA tickets for these issues, please? Thanks, Om > > > On 17 November 2014 at 19:38, quick6black wrote: > > > Hi Om, > > > > I created another pull request, this fixes a few bugs and an issue with the > > lateral menu sliding out. I also added in a drag to close and a new view > > for > > some more native air features. I would like to create a better landing > > page, > > any ideas? > > > > thanks, > > > > Aaron > > > > > > > > -- > > View this message in context: > > http://apache-flex-development.247.n4.nabble.com/Tour-de-Flex-Mobile-tp41483p42431.html > > Sent from the Apache Flex Development mailing list archive at Nabble.com. > >
Re: AW: Jenkins builds and general structure of FlexJS/Falcon related project
On 11/28/14, 1:12 PM, "Christofer Dutz" wrote: >Hi Alex, > >well I was simply assuming that something is generally not setup >correctly and that one of them could simply check the reason for this and >I was assuming that if we sort out the problem the tests could work fine. Yeah, well it is intentional, although I suppose you could argue it isn’t correct. Think of it this way: I think each version of Java comes with a compiler and some libraries, right? Do the Java compiler folks run tests where they compile the libraries? The library developers must run tests that require compilation. We have the same situation. I did not study how Java or Google Closure does it. If folks have learned from experience that the compiler folks shouldn’t have tests in the main target that compile the library, then maybe we shouldn’t either. -Alex
[RESULT][VOTE] TourDeFlex 1.2 Release Candidate 2
Hi, The vote passes with 3 +1 binding votes and no other votes. Justin
Draft Tour De Flex 1.2 announcement
Hi, To be sent out in 24 hours once the mirrors have caught up, and the web site pages updated. The Apache Flex community is pleased to announce the release of Apache Flex TourDeFlex 1.2. The Apache Flex Tour De Flex component explorer provides a sample set of working Apache Flex examples. This release now contains over 300 working examples and has several improvements and bug fixes from the previous release, including a consistent look and feels, support for 3rd party examples and Apache Flex Squiggly spelling engine examples. For your convenience the latest version has been compiled and placed upon on the Apache Flex web site: http://flex.apache.org/tourdeflex/ For a full list of changes from the previous version please go to: http://www.apache.org/dyn/closer.cgi/flex/tourdeflex/1.2/RELEASE_NOTES This application is based on work donated by Adobe and their component explorer and is expected to be updated over time. We welcome feedback and contributions to it from the wider Apache Flex community. The Apache Flex TourDeFlex is available in source form for you to compile from the following download page: http://www.apache.org/dyn/closer.cgi/flex/tourdeflex/1.2 When downloading from a mirror site, please remember to verify the downloads using signatures or MD5 hashes. For more information on Apache Flex, visit the project home page: http://flex.apache.org Thank you for using Apache Flex, The Apache Flex Community Thanks, Justin
