[jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.
[ https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676730#comment-13676730 ] Alex Harui commented on FLEX-33083: --- I was not able to reproduce the problem with the new zip. I attached swfutils.jar that might be needed to pair with the mxmlc.jar. If that doesn't work, try FlashBuilder again and see if you get the same stack trace in the log. Make sure you clean the project. Then check your location of flex-messaging-common.jar. It needs to be in libs/external/optional. There should be some other jars in there like flex-fontkit.jar. Flash builder report An internal build error has occurred. See the error log for more information. - Key: FLEX-33083 URL: https://issues.apache.org/jira/browse/FLEX-33083 Project: Apache Flex Issue Type: Bug Components: Project Management Environment: Flash builder 4.6 , sdk 4.8.0 Reporter: Alex Harui Assignee: Alex Harui Labels: easyfix Attachments: mxmlc.jar, swfutils.jar, weborb.codegen.test.zip 1. download the source kit from https://svn.apache.org/repos/asf/incubator/flex/trunk 2. run ant release 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. extract AIR Integration Kit.zip to folder 5 copy additional files for Flash Ide ( frameworks/libs\player\* and frameworks\*-config.xm) 6.create a simple project with reference to RemoteObject private var remote:RemoteObject; remote = new RemoteObject; flash builder log file : !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 !MESSAGE Uncaught exception in compiler !STACK 0 java.lang.NullPointerException at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730) at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538) at flex2.tools.oem.Application.compile(Application.java:1357) at flex2.tools.oem.Application.recompile(Application.java:1295) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: checkin tests filing on Linux
Interesting. There was so much work done to integrate the globalization classes that I'm surprised we didn't upgrade AC to use them. IMO, the results of Array.sort with the globalization classes is correct and localeCompare is doing a dumb sort. I haven't looked but maybe we documented how to use the globalization classes with AC and the sort test should be doing that. -Alex On 6/5/13 10:54 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Interesting. I expected them to match because I thought we'd wired up the AC sort behavior to use the flash.globalization classes. If you step through this on the Mac it goes into localeCompare? On OSX it's calling spark.collections.Sort:internalSort which is using mx.xollections.SortField:stringCompare which uses ObjectUtils.stringCompare which uses localeCompare to compare strings. So for AC it's not using the flash globalisation classes. Not that changing that will fix the test (it may improve performance) as it look to be an issue with Array.sort() on Linux. Thanks, Justin
Re: checkin tests filing on Linux
Hi, Interesting. There was so much work done to integrate the globalization classes that I'm surprised we didn't upgrade AC to use them. It wouldn't be too hard to change. IMO, the results of Array.sort with the globalization classes is correct And that's where the issue is as it returns a different order on Linux. There's no errors and en_US is being set correctly. Thanks, Justin
Re: Multidimensional States
On 6/5/13 9:00 PM, flexcapaci...@gmail.com flexcapaci...@gmail.com
wrote:
Thanks for this input as well.
Alex, what would currentState look like as a organizing property?
It would look like it does now. By organizing property I mean a
property that you assign semantics to to change the UI. Other properties
like isFocused and visible have well-defined semantics.
What does
conditional expressions look like?
Probably like binding expressions. Or maybe they will be binding
expressions.
And what are you doing here with isFocused,
s:Rect id=focusBorder includeIn={isFocused}
left={emphasized ? -1 : -2} /
I didn't know you could use bindings in an includeIn or is that a typo?
You can't today. I'm just imagining a world where any property can define
whether things are included/excluded or have a different value.
I like these:
currentState.mouse = up;
currentState = up-focused-nonDefault;
They look like something that can be done. In this case, maybe separate
with spaces to promote a more CSS type of syntax? This might be simplest
to
support since it could apply properties in a last declared wins situation.
I'm not sure I understood this section.
It might also be easier to solve if CSS in Flex supported defining
properties such as size and position?
FlexJS will support the CSS properties left, right, top, bottom.
Another concrete example to think about is the toggle button. It doubles
the amount of states as Button just with toggled vs normal.
I used to use ToggleButton as an example, but it doesn't have an
emphasized state and then I think the total number of states is the same.
Right now with mobile development we have a solution for fixed size in
either portrait and landscape states and set the applicationDPI. We also
solve this with constraints and percentage based values.
Can we or should we support responsive design can with states?
A long-ish term goal for FlexJS is to support W3C CSS. That's because the
browsers do already, and it is better to join them vs try to change their
behavior. The hard part is just emulating it in Flash/Actionscript. And
that includes a list of classNames and more media query parameters.
Will that help?
-Alex
Re: checkin tests filing on Linux
On 6/5/13 11:26 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Interesting. There was so much work done to integrate the globalization classes that I'm surprised we didn't upgrade AC to use them. It wouldn't be too hard to change. IMO, the results of Array.sort with the globalization classes is correct And that's where the issue is as it returns a different order on Linux. There's no errors and en_US is being set correctly. Different but valid? If you use some other language to sort that list on Linux that also claims to support globalized sorts, what order would it return? If changing the test to have the AC sort through the globalization classes allows that test to pass on all platforms, then I'd say that's the way to go. -Alex
Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_tester NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_inline_2_test5 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_null_test6 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_empty_script_test7 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_negative_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester
Re: TLF Modifications/Getting Involved
Hi all, IMHO. There are no much contributions to TLF only because of its closed nature. I also used TLF in my past projects. I felt very hard to modify the existing behavior, just because most of the classes are marked final, private, Excluded, internal, marked with custom namespace. I really welcomes Tony's interest. If we make the private/custom namespace methods to protected or public, we can see a lot of improvements/involvements in TLF also. +++1 for Tony's proposal. On Sat, Jun 1, 2013 at 5:05 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, This seems to already by an issue in Apache's Jira ( https://issues.apache.org/jira/browse/FLEX-21488) which is closed to be tracked by the Adobe Jira, but it seems the Adobe Jira has already been decommissioned. Perhaps we should open it back up-or maybe I'm missing something. I've reopened the JIRA issues. Are there any other classes other than these? public final class TextFlow public final class ParagraphElement public final class LinkElement To summarize things, I'd like to make the following general categories of changes to TLF: Remove many final classes, giving developers the ability to extend them. Attempt to make many hidden classes publicly visible so that they can be extended and use in the type of configuration described below. Make TLF more configurable, so that in places where TLF would create an instance of a TLF-type class, it instead accesses a user-configured factory for creating that type of class so that developers can inject their extended classes into their text with ease. (Probably in the Configuration class.) All sound like good ideas to me. Thanks, Justin -- * Regards, S. Jagan Langa*
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_tester NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_inline_2_test5 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_null_test6 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_empty_script_test7 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_negative_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester
Re: checkin tests filing on Linux
Hi, Different but valid? Looks invalid to me - basically they are left in the order they are passed in. cote, côte, coté, côté If changing the test to have the AC sort through the globalization classes allows that test to pass on all platforms, then I'd say that's the way to go. It doesn't fix the issue the ArrayCollection is sorted n the correct order on OSX/Linux The issue is with Array.sort() and the globalisation classes as I said before it look like a FP issue not a SDK issue. Thanks, Justin
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
After more than 72 hours, I'm closing the vote, refer to the next [Vote][Results] thread for the follow up Thanks to all for your vote and contribution Carlos Rovira 2013/6/4 Alex Harui aha...@adobe.com +1 binding On 6/4/13 9:02 AM, Jeff Tapper j...@spoon.as wrote: +1 binding -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, June 02, 2013 5:58 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote. -- 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: Multidimensional States
On Thu, Jun 6, 2013 at 1:33 AM, Alex Harui aha...@adobe.com wrote: I like these: currentState.mouse = up; currentState = up-focused-nonDefault; They look like something that can be done. In this case, maybe separate with spaces to promote a more CSS type of syntax? This might be simplest to support since it could apply properties in a last declared wins situation. I'm not sure I understood this section. I was describing a situation where if we have multiple states and you assign more than one state to the current state property and one state property assignment collides with another then the last one assigned wins. Its the same as CSS. For example, State name=blue/ State name=red/ State name=emphasized/ State name=focused/ Label color.blue=blue color.red=red color.emphasized=green/ and currentState = blue emphasized; then the label color would be green because blue and emphasized states both define a color. There wouldn't be any error thrown. It might also be easier to solve if CSS in Flex supported defining properties such as size and position? FlexJS will support the CSS properties left, right, top, bottom. Another concrete example to think about is the toggle button. It doubles the amount of states as Button just with toggled vs normal. I used to use ToggleButton as an example, but it doesn't have an emphasized state and then I think the total number of states is the same. Right now with mobile development we have a solution for fixed size in either portrait and landscape states and set the applicationDPI. We also solve this with constraints and percentage based values. Can we or should we support responsive design can with states? A long-ish term goal for FlexJS is to support W3C CSS. That's because the browsers do already, and it is better to join them vs try to change their behavior. The hard part is just emulating it in Flash/Actionscript. And that includes a list of classNames and more media query parameters.
[VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
Here we have the vote results: *+1 Binding* OmPrakash Muppirala Justin Mclean Erik de Bruin Frederic Thomas Sebastian Mohr Jeff Tapper Alex Harui *0 Binding* Jeffry Houser *-1 Binding* Igor Costa *+1 Non-Binding* Carlos Rovira Joao Fernandes Cyrill Zadra aYo Jose Barragan Arnoud Bos Margo Powell Sumudu Chinthaka Vicker Leung Mark Kessler Carlos Velasco The vote pass with 7 +1-Binding, 1 0-Binding, 1 -1-Binding and 11 Non-Binding votes Hope some PMC could give us the next steps. For me some of them should be: * Comunicate in swiz-framework mailing list that this vote results * Ask Chris Scott to write an email in this mailing list to express his desire of donation. * See If other swiz committers like Ben or Brian should sign as well. * I remember Alex said that some IIRC sign should be made for Chris. This could be pointed in response to Chris when he write his email to this list asking for the step he should do to complete donation. * Prepare repo to receive the donation. * ...other points to take into account provided by Mentors and PMCs? Thanks again to all for your contribution, discussion and votes and to make this happen. Best, Carlos 2013/6/6 Carlos Rovira carlos.rov...@codeoscopic.com After more than 72 hours, I'm closing the vote, refer to the next [Vote][Results] thread for the follow up Thanks to all for your vote and contribution Carlos Rovira 2013/6/4 Alex Harui aha...@adobe.com +1 binding On 6/4/13 9:02 AM, Jeff Tapper j...@spoon.as wrote: +1 binding -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, June 02, 2013 5:58 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote. -- 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 -- 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: Multidimensional States
Yeah. I like the state delegates. What if you took it one step further and
added inline states?
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
s:Group id=focusGroup
s:states
s:State name=nonFocused/
s:State name=focused/
/s:states
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect} alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:strokes:SolidColorStroke color=...//s:stroke
/s:Rect
/s:Group
On Thu, Jun 6, 2013 at 2:12 AM, Cosma Colanicchia cosma...@gmail.comwrote:
Multiple states using spaces (e.g. currentState=up default) looks nice to
the eyes.
I was thinking about impact on the transitions management - I'm not sure
that the current transition approach (fromState/toState) scales well once
we go this way.
A possible idea could be to support state delegates, i.e. allow to break
up the MXML component in subcomponents, and let each of these subcomponents
manage its own set of states and the related transitions.
Elaborating on the Bill approach, something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus stateDelegate=focusGroup
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
[...]
s:Group id=focusGroup
top=0 bottom=0 left=0 right=0
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect}
alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect
top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:stroke
s:SolidColorStroke color=.../
/s:stroke
/s:Rect
/s:Group
This would allow multiple transitions in each exclusive state group to be
managed indipendently, and make sense to me as well, because often each set
of these state groups only impacts a specific part of the component (or of
the skin): in the example, focus just add a glowing border on top of the
rest.
This allow to grab one or two set of states, and subtract them from the
cartesian multiplication (and also simplify the related transitions
management, isolating it from other states). When the stateDelegate is
not provided, it just means that the related states are managed by the top
MXML component.
In a sense, responding to Jude, this aims to bring the benefits of the
composition approach (versus the inheritance provided by basedOn states).
Re: Multidimensional States
Probably just a sintax choice: having them all toghether could be useful to
quickly have an outlook of the states stuff when you open an MXML document,
instead of searching for a number of sparse s:states blocks (they are the
state of the main MXML component, after all) - on the other hand, defining
them inline maybe feels right and the resulting code snippets are more
manageable.
2013/6/6 jude flexcapaci...@gmail.com
Yeah. I like the state delegates. What if you took it one step further and
added inline states?
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
s:Group id=focusGroup
s:states
s:State name=nonFocused/
s:State name=focused/
/s:states
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect} alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:strokes:SolidColorStroke color=...//s:stroke
/s:Rect
/s:Group
On Thu, Jun 6, 2013 at 2:12 AM, Cosma Colanicchia cosma...@gmail.com
wrote:
Multiple states using spaces (e.g. currentState=up default) looks nice
to
the eyes.
I was thinking about impact on the transitions management - I'm not sure
that the current transition approach (fromState/toState) scales well once
we go this way.
A possible idea could be to support state delegates, i.e. allow to
break
up the MXML component in subcomponents, and let each of these
subcomponents
manage its own set of states and the related transitions.
Elaborating on the Bill approach, something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus stateDelegate=focusGroup
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
[...]
s:Group id=focusGroup
top=0 bottom=0 left=0 right=0
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect}
alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect
top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:stroke
s:SolidColorStroke color=.../
/s:stroke
/s:Rect
/s:Group
This would allow multiple transitions in each exclusive state group to
be
managed indipendently, and make sense to me as well, because often each
set
of these state groups only impacts a specific part of the component (or
of
the skin): in the example, focus just add a glowing border on top of the
rest.
This allow to grab one or two set of states, and subtract them from the
cartesian multiplication (and also simplify the related transitions
management, isolating it from other states). When the stateDelegate is
not provided, it just means that the related states are managed by the
top
MXML component.
In a sense, responding to Jude, this aims to bring the benefits of the
composition approach (versus the inheritance provided by basedOn states).
Re: TLF Modifications/Getting Involved
I might have run into the same issues with List numbering. I had to do the same types of work around to modify anything because all of the classes were internal or final. I don't know if I solved the issue you were mentioning. If you describe it in more detail I can see if it's the same and share what I have. On Fri, May 31, 2013 at 9:36 AM, Compton, Tony anthony.ste.comp...@hp.comwrote: Hello, everyone. My name is Tony Compton, a developer for HP Exstream, a division of Hewlett-Packard, Inc. I've spent the last year working on a product that relies on Flex and TLF. I'm writing today because I work with TLF almost daily and I would like to help contribute to the project, but before I spend the time making the kinds of changes that I think will make TLF an easier framework to extend and develop using I wanted to make sure that they were welcome changes. There are a number of things about TLF that make it difficult to extend and otherwise alter its behavior. Please keep in mind that some of the changes I'm about to suggest stem from a personal design philosophy that if I, as a developer, attempt to extend via inheritance or otherwise alter the behavior of an object or class that works and it does not continue to work with my extensions then I am at fault-not the framework. Here are some improvements I would like to make: There are a few classes within TLF that are marked as final. This creates a unnecessary barrier to extension. One example of this is the InlineGraphicElement class. I would like to extend this class, but I cannot, so in order to add any additional behaviors or features to the class I am forced to do something like extend SubParagraphGroupElementBase (SubParagraphGroupElement is also marked final, which I feel is unnecessary, although I wasn't especially inconvenienced by that). This seems to already by an issue in Apache's Jira ( https://issues.apache.org/jira/browse/FLEX-21488) which is closed to be tracked by the Adobe Jira, but it seems the Adobe Jira has already been decommissioned. Perhaps we should open it back up-or maybe I'm missing something. There are many hidden classes sprinkled throughout TLF. Where I encountered particular hindrance is in attempting to extend TextFieldHtmlmporter to handle more advanced HTML pasting. While a the class is not marked final, there are still some areas I feel can be improved. For instance, if I wanted to inherit from TextFieldHtmlImporter and allow it to interpret a custom font-related attribute I can't simply inherit from the hidden FontImporter class and make my changes, then configure the TextFieldHtmlImporter to use my newly created class. I am forced to create a new class that does everything FontImporter does (plus my extra stuff) then create a class that extends TextFieldHtmlImporter and jump through the necessary hoops to make sure that my importer gets used instead of FontImporter (which, on its own is more difficult than I think it needs to be). I would like to see situations like this be more strategy-like pattern wherein I can supply the importer with a FontImporter to use and if I do not it will use the default, but make the default FontImporter publicly visible and therefore extendable. Similarly, I'd like to apply the same notion of using the strategy pattern to TLF's creation of TextLines/TextFlowLines and child TextLines for list numberings. Currently I've been unable to find a way to affect how TLF lays out its list markers. It's been a while since I looked at this problem, but if I recall correctly, somewhere in TLF it's calling a static factory method on a class by name, so there is no way for me to modify the behavior of TLF with regards to how it creates TextLines. It would be nice if there was a configurable property that I could set (that implements ITextFlowLineFactory or something like that) that TLF would then access and use to create TextFlowLines, thereby giving me at least some means of altering its behavior (although, as I said, it's been a while-so there may be some details of the current implementation that I'm not remembering quite right). (This type of customization may need to go in the Configuration class.) To summarize things, I'd like to make the following general categories of changes to TLF: Remove many final classes, giving developers the ability to extend them. Attempt to make many hidden classes publicly visible so that they can be extended and use in the type of configuration described below. Make TLF more configurable, so that in places where TLF would create an instance of a TLF-type class, it instead accesses a user-configured factory for creating that type of class so that developers can inject their extended classes into their text with ease. (Probably in the Configuration class.) I'd be interested in hearing your thoughts on these topics. Hopefully they are well received so that I can begin working on them. Thanks and
Re: checkin tests filing on Linux
On 6/6/13 12:49 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Different but valid? Looks invalid to me - basically they are left in the order they are passed in. cote, côte, coté, côté Ah, I didn't understand that the order was not changing. If you are sure of what the order should be, you could detect that you are on Linux and hardcode the array and not call sort(). But I will say that the order on Mac is different between OSX versions based on ever-changing standards, which is why I was wondering what a more native Linux sort would return. -Alex
Re: Multidimensional States
Good stuff.
Today, you can sort of do this with fx:Declarations/fx:Component, but it
isn't in-line, just in the same document. Do either of you have a skin or
component that could truly take advantage of that?
And still, you end up writing code to set currentState according to some
other set of properties, which is why I'm wondering why you guys would
rather manage the code that sets currentState vs just tying the visuals to
other properties.
-Alex
On 6/6/13 3:19 AM, Cosma Colanicchia cosma...@gmail.com wrote:
Probably just a sintax choice: having them all toghether could be useful
to
quickly have an outlook of the states stuff when you open an MXML
document,
instead of searching for a number of sparse s:states blocks (they are
the
state of the main MXML component, after all) - on the other hand, defining
them inline maybe feels right and the resulting code snippets are more
manageable.
2013/6/6 jude flexcapaci...@gmail.com
Yeah. I like the state delegates. What if you took it one step further
and
added inline states?
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
s:Group id=focusGroup
s:states
s:State name=nonFocused/
s:State name=focused/
/s:states
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect} alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:strokes:SolidColorStroke color=...//s:stroke
/s:Rect
/s:Group
On Thu, Jun 6, 2013 at 2:12 AM, Cosma Colanicchia cosma...@gmail.com
wrote:
Multiple states using spaces (e.g. currentState=up default) looks
nice
to
the eyes.
I was thinking about impact on the transitions management - I'm not
sure
that the current transition approach (fromState/toState) scales well
once
we go this way.
A possible idea could be to support state delegates, i.e. allow to
break
up the MXML component in subcomponents, and let each of these
subcomponents
manage its own set of states and the related transitions.
Elaborating on the Bill approach, something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus stateDelegate=focusGroup
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
[...]
s:Group id=focusGroup
top=0 bottom=0 left=0 right=0
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect}
alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect
top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:stroke
s:SolidColorStroke color=.../
/s:stroke
/s:Rect
/s:Group
This would allow multiple transitions in each exclusive state group
to
be
managed indipendently, and make sense to me as well, because often
each
set
of these state groups only impacts a specific part of the component
(or
of
the skin): in the example, focus just add a glowing border on top of
the
rest.
This allow to grab one or two set of states, and subtract them from
the
cartesian multiplication (and also simplify the related transitions
management, isolating it from other states). When the stateDelegate
is
not provided, it just means that the related states are managed by the
top
MXML component.
In a sense, responding to Jude, this aims to bring the benefits of the
composition approach (versus the inheritance provided by basedOn
states).
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_tester NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_inline_2_test5 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_null_test6 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_empty_script_test7 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_negative_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_function_large_test10 Passed [java]
Swiz Donation: Next Steps (was Re: [VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation)
Yes, Chris needs get on our email list and put it in writing that he wants to donate. I think we need some proof of ownership. Does he own the code or some corporation or business entity that he belongs to. I think he will need to sign an ICLA. -Alex
Re: Build failed in Jenkins: flex-sdk_mustella #144
OK. Can you shut down Jenkins when it is done so it doesn't kick off another run? Let me know when it's all done and I'll poke at the remaining failures. -Alex On 6/6/13 8:23 AM, 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_typeSelector_teste r NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_teste r 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_inline_2_test5 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_null_test6 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_empty_script_test7 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_tester NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_tester 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_inline_2_test5 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_null_test6 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_invalid_empty_script_test7 Passed [java]
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_test er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_test 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_100point12_test4 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_inline_2_test5 Passed [java]
Re: Swiz Donation: Next Steps (was Re: [VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation)
2013/6/6 Alex Harui aha...@adobe.com Ugh. I have to watch a video? What am I looking for in that video? hehe I only want to say that history is written in the internet so is easy to prove that Chris Scott is the author, but I see that he must prove it himself. better wait for his email to follow up :) Best, Carlos
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_test er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_test 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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_1_test3 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester
Auto fit list item height to it's content
hi guys i have being working on a flex mobile project and having some difficulties with my labelitemrenderer i have a list with a custom item renderer and inside the renderer i have a label that will populate with variable length data from the db. so i want to re size the row height of the list item to occupy those text please let me know the best way to accomplish this i have being looking around the web whole day could not find any reliable solution Beast Regards Sumudu
RE: [jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.
Ive also had this happen with builder 4.7 I actually assumed it was some problem of mine until reading this post I changed back to sdk 4.7 and all was fine again I will look into it my end -Original Message- From: Alex Harui (JIRA) [mailto:j...@apache.org] Sent: Wednesday, June 05, 2013 10:15 PM To: dev@flex.apache.org Subject: [jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information. [ https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676359#comment-13676359 ] Alex Harui commented on FLEX-33083: --- Well, technically, Flash Builder 4.5 isn't supported for Apache Flex, but it shouldn't be a factor for this scenario. I updated mxmlc to show more information for this exception. I've attached an updated mxmlc.jar which you can use to replace the one in the lib folder of your Apache Flex SDK. If you compile the app from the command line you should see a better error message. I couldn't find an easy way to get that better information into the console, log, or problems pane. When I compile your project from the command line, I now get: flex.messaging.config.ConfigurationException: channel not found for reference 'weborb-rtmp-messaging' in destination 'SampleRTMPDestination'. You didn't mention if you are using Blaze or DataServices and which version. I'm not sure why with Adobe Flex 4.6 you aren't seeing this same problem, but it could be that I still don't have your test case set up properly. I only set up to use Blaze 4, not DataServices or whatever Adobe calls it these days. Flash builder report An internal build error has occurred. See the error log for more information. -- --- Key: FLEX-33083 URL: https://issues.apache.org/jira/browse/FLEX-33083 Project: Apache Flex Issue Type: Bug Components: Project Management Environment: Flash builder 4.6 , sdk 4.8.0 Reporter: Alex Harui Assignee: Alex Harui Labels: easyfix Attachments: mxmlc.jar, weborb.codegen.test.zip 1. download the source kit from https://svn.apache.org/repos/asf/incubator/flex/trunk 2. run ant release 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. extract AIR Integration Kit.zip to folder 5 copy additional files for Flash Ide ( frameworks/libs\player\* and frameworks\*-config.xm) 6.create a simple project with reference to RemoteObject private var remote:RemoteObject; remote = new RemoteObject; flash builder log file : !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 !MESSAGE Uncaught exception in compiler !STACK 0 java.lang.NullPointerException at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730) at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538) at flex2.tools.oem.Application.compile(Application.java:1357) at flex2.tools.oem.Application.recompile(Application.java:1295) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at
Re: Multidimensional States
AFAIK:
- currently states also play a role in the skinning contract of a
skinnable component (skinStates)
- states are supported by transitions management
The first one maybe could be dropped, resulting in a relaxed skinning
contract: the button may have bindable model properties such as isFocused
or isDefault, and the skin could adjust its visuals looking at their values
(currently, MXML skin are enforced by the compiler to declare as states all
the skin states in the host component metadata - but if I remember
correctly AS skins don't have this restriction).
However, I don't know if a transition management like the current one could
be adapted to work without states.. the includeIn and property.state=...
MXML syntax allow to declare the final value of a property in a specified
state, but unlike a binding that would apply the value immediately, when a
transition is defined that value will only be applied at the and of the
entire transition, giving the effects a chance to provide smooth visual
changes in between. In other words, is a way to decuple the
focusGroup.alpha view property from the (ideal) hostComponent.isFocused
model property, thus allowing effects to play in between - a kind of
decoupling that could probably be achieved by defining a lot of
intermediate variables in the view layer, but the resulting code would be
ugly and hard to manage.
2013/6/6 Alex Harui aha...@adobe.com
Good stuff.
Today, you can sort of do this with fx:Declarations/fx:Component, but it
isn't in-line, just in the same document. Do either of you have a skin or
component that could truly take advantage of that?
And still, you end up writing code to set currentState according to some
other set of properties, which is why I'm wondering why you guys would
rather manage the code that sets currentState vs just tying the visuals to
other properties.
-Alex
On 6/6/13 3:19 AM, Cosma Colanicchia cosma...@gmail.com wrote:
Probably just a sintax choice: having them all toghether could be useful
to
quickly have an outlook of the states stuff when you open an MXML
document,
instead of searching for a number of sparse s:states blocks (they are
the
state of the main MXML component, after all) - on the other hand, defining
them inline maybe feels right and the resulting code snippets are more
manageable.
2013/6/6 jude flexcapaci...@gmail.com
Yeah. I like the state delegates. What if you took it one step further
and
added inline states?
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
s:Group id=focusGroup
s:states
s:State name=nonFocused/
s:State name=focused/
/s:states
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect} alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:strokes:SolidColorStroke color=...//s:stroke
/s:Rect
/s:Group
On Thu, Jun 6, 2013 at 2:12 AM, Cosma Colanicchia cosma...@gmail.com
wrote:
Multiple states using spaces (e.g. currentState=up default) looks
nice
to
the eyes.
I was thinking about impact on the transitions management - I'm not
sure
that the current transition approach (fromState/toState) scales well
once
we go this way.
A possible idea could be to support state delegates, i.e. allow to
break
up the MXML component in subcomponents, and let each of these
subcomponents
manage its own set of states and the related transitions.
Elaborating on the Bill approach, something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus stateDelegate=focusGroup
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
[...]
s:Group id=focusGroup
top=0 bottom=0 left=0 right=0
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect}
alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect
top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:stroke
s:SolidColorStroke color=.../
/s:stroke
/s:Rect
/s:Group
This would allow multiple transitions in each exclusive state group
to
be
managed indipendently, and make sense to me as well, because often
each
set
of these state groups only impacts a specific part of the component
(or
of
the skin): in the example, focus just add a glowing border on top of
the
rest.
This allow to grab one or two set of states, and subtract them from
the
cartesian multiplication (and
Re: Swiz Donation: Next Steps (was Re: [VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation)
On Thu, Jun 6, 2013 at 11:00 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: hehe I only want to say that history is written in the internet so is easy to prove that Chris Scott is the author, but I see that he must prove it himself. We could not in good conscience accept a donation without written, clear intentions from the author. I suspect it will require a software grant and the author will need to go through some legal paperwork to assent that he has ownership of the code and is willing to donate it to the ASF. I need to get more familiar with the details of what is required for the ASF to accept software donations, but it's a complicated subject and time is short. I do know that we want to be very sure we have all the details in order so we can be confident in saying that we have the right to continue to produce the software. Greg
Re: Auto fit list item height to it's content
Off the top of my head, i think you'll need to set variableRowHeight=true on the list and then override measure and layoutContents methods in your custom renderer as appropriate On 06/06/2013 17:05, Sumudu Chinthaka wrote: hi guys i have being working on a flex mobile project and having some difficulties with my labelitemrenderer i have a list with a custom item renderer and inside the renderer i have a label that will populate with variable length data from the db. so i want to re size the row height of the list item to occupy those text please let me know the best way to accomplish this i have being looking around the web whole day could not find any reliable solution Beast Regards Sumudu -- Lee Burrows ActionScripter
RE: Swiz Donation: Next Steps (was Re: [VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation)
We could not in good conscience accept a donation without written, clear intentions from the author. I suspect it will require a software grant and the author will need to go through some legal paperwork to assent that he has ownership of the code and is willing to donate it to the ASF. I need to get more familiar with the details of what is required for the ASF to accept software donations, but it's a complicated subject and time is short. I do know that we want to be very sure we have all the details in order so we can be confident in saying that we have the right to continue to produce the software. I can verify this from my experience with FlexUnit. It's a multistep process. This is what Bertrand provided me a while back and it's the starting point Chris must likely follow: http://incubator.apache.org/ip-clearance/index.html http://www.apache.org/licenses/software-grant.txt Mike
Re: Auto fit list item height to it's content
Hi, please post on us...@flex.apache.org, and include the code for your renderer. It's a bit confusing, but we're trying to use the dev@ list for issues regarding changes to the code in the SDK and other Apache Flex repos, and users@ is for questions regarding usage of that code, even though you are a developer. Thanks, -Alex On 6/6/13 9:05 AM, Sumudu Chinthaka csum...@gmail.com wrote: hi guys i have being working on a flex mobile project and having some difficulties with my labelitemrenderer i have a list with a custom item renderer and inside the renderer i have a label that will populate with variable length data from the db. so i want to re size the row height of the list item to occupy those text please let me know the best way to accomplish this i have being looking around the web whole day could not find any reliable solution Beast Regards Sumudu
Re: Multidimensional States
To be clear, I'm mainly concerned about how to implement this in FlexJS.
I'm not planning to try to upgrade or retrofit this into the current Flex
SDK, but someone else is certainly welcome to take that on.
My thoughts around effects in general is that, in FlexJS, you have
replaceable models. The models that will work with effects/transitions
will probably have a PROP_CHANGING/PROP_CHANGED event pair, where the
CHANGING is cancelable and would probably serve as the trigger.
On 6/6/13 9:13 AM, Cosma Colanicchia cosma...@gmail.com wrote:
AFAIK:
- currently states also play a role in the skinning contract of a
skinnable component (skinStates)
- states are supported by transitions management
The first one maybe could be dropped, resulting in a relaxed skinning
contract: the button may have bindable model properties such as
isFocused
or isDefault, and the skin could adjust its visuals looking at their
values
(currently, MXML skin are enforced by the compiler to declare as states
all
the skin states in the host component metadata - but if I remember
correctly AS skins don't have this restriction).
However, I don't know if a transition management like the current one
could
be adapted to work without states.. the includeIn and property.state=...
MXML syntax allow to declare the final value of a property in a
specified
state, but unlike a binding that would apply the value immediately, when a
transition is defined that value will only be applied at the and of the
entire transition, giving the effects a chance to provide smooth visual
changes in between. In other words, is a way to decuple the
focusGroup.alpha view property from the (ideal)
hostComponent.isFocused
model property, thus allowing effects to play in between - a kind of
decoupling that could probably be achieved by defining a lot of
intermediate variables in the view layer, but the resulting code would be
ugly and hard to manage.
2013/6/6 Alex Harui aha...@adobe.com
Good stuff.
Today, you can sort of do this with fx:Declarations/fx:Component, but it
isn't in-line, just in the same document. Do either of you have a skin
or
component that could truly take advantage of that?
And still, you end up writing code to set currentState according to some
other set of properties, which is why I'm wondering why you guys would
rather manage the code that sets currentState vs just tying the visuals
to
other properties.
-Alex
On 6/6/13 3:19 AM, Cosma Colanicchia cosma...@gmail.com wrote:
Probably just a sintax choice: having them all toghether could be
useful
to
quickly have an outlook of the states stuff when you open an MXML
document,
instead of searching for a number of sparse s:states blocks (they are
the
state of the main MXML component, after all) - on the other hand,
defining
them inline maybe feels right and the resulting code snippets are
more
manageable.
2013/6/6 jude flexcapaci...@gmail.com
Yeah. I like the state delegates. What if you took it one step
further
and
added inline states?
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
s:Group id=focusGroup
s:states
s:State name=nonFocused/
s:State name=focused/
/s:states
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect} alphaFrom=0
alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect top=0 bottom=0 left=0 right=0
alpha=0 alpha.default=1/
s:strokes:SolidColorStroke color=...//s:stroke
/s:Rect
/s:Group
On Thu, Jun 6, 2013 at 2:12 AM, Cosma Colanicchia cosma...@gmail.com
wrote:
Multiple states using spaces (e.g. currentState=up default) looks
nice
to
the eyes.
I was thinking about impact on the transitions management - I'm not
sure
that the current transition approach (fromState/toState) scales
well
once
we go this way.
A possible idea could be to support state delegates, i.e. allow
to
break
up the MXML component in subcomponents, and let each of these
subcomponents
manage its own set of states and the related transitions.
Elaborating on the Bill approach, something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus stateDelegate=focusGroup
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
[...]
s:Group id=focusGroup
top=0 bottom=0 left=0 right=0
s:transitions
s:Transition fromStatenonDefault toStatedefault
s:Fade target={focusRect}
alphaFrom=0 alphaTo=1/
s:/Transition
/s:transitions
s:Rect id=focusRect
top=0 bottom=0 left=0 right=0
alpha=0
Re: Swiz Donation: Next Steps (was Re: [VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation)
Thanks Mike, I'll forward to Chris so he can chek it. Best Carlos 2013/6/6 Michael A. Labriola labri...@digitalprimates.net We could not in good conscience accept a donation without written, clear intentions from the author. I suspect it will require a software grant and the author will need to go through some legal paperwork to assent that he has ownership of the code and is willing to donate it to the ASF. I need to get more familiar with the details of what is required for the ASF to accept software donations, but it's a complicated subject and time is short. I do know that we want to be very sure we have all the details in order so we can be confident in saying that we have the right to continue to produce the software. I can verify this from my experience with FlexUnit. It's a multistep process. This is what Bertrand provided me a while back and it's the starting point Chris must likely follow: http://incubator.apache.org/ip-clearance/index.html http://www.apache.org/licenses/software-grant.txt Mike -- 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: [DRAFT] Flex June Report
Any other comments before I file this report? - Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES Apache Flex SDK 4.9.1 was released on 2/28/13. Apache Flex Installer 2.5.4 was released on 4/11/13. The community is currently preparing its next release of both the SDK and Installer. ACTIVITY Activity in Apache Flex continues to be in two main areas: improvements to the existing Adobe Flash Platform-dependent code base, including the releases listed above, and prototyping ways to create a version of Flex that is independent from the Adobe Flash Platform. There is another group working on Maven-related tools for the existing code base. Just in the past 30 days, 130 JIRA issues were resolved. JIRA activity is so high, a vote is underway to split JIRA notifications off to its own mailing list (issues@flex.a.o) Getting used to Git was still a frequent topic in April and May. Because Git does not support partial checkouts, the community prototyped using GitHub for the whiteboards. GitHub notifications are sent to the commits@ list just like any other Apache Git commit. The PMC then voted to approve this workflow. And because we do our work in a branch and have trunk only have released sources, we had to ask Infra to update the mirrors to work from that branch. The owner of a popular application-framework that leverages the Flex SDK has offered to donate the code to the project. This has met with some opposition from those who use competing application-frameworks. The ensuing dicussion indicated that the PMC is in favor of accepting donations from the these other frameworks should they choose to donate, so we believe we are not endorsing or showing favoritism. COMMUNITY No new committers in the last 90 days. A vote is underway to promote a committer to the PMC. Latest analytics include over 4000 downloads since 4/11/2013, and an average of 3000 hits per day during weekdays. INFRASTRUCTURE * Infra attempted to resolve INFRA-4380 but ran into problems. I have approval to try to use the SOAP interface to pull the current state of JIRA issues, merge them with the original attachments and provide a new import file for INFRA. That task has been delayed by other issues like getting new releases out, but we will get to it eventually. BRANDING We have noted that Apache projects are forming that use code module names that are used in Apache Flex. Namely 'Falcon' and now 'Spark'. These two words are used often on the mailing lists when discussing the related code which then finds its way into the search engines. Is this an issue? --
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_te st er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_NEGATIVE_INFINITY_test19 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_test1 Passed [java] spark/validators/NumberValidator/Properties/NV_minValue_tester NV_minValue_default_script_test2 Passed [java]
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_typeSelector_te st er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_12_script_test14 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_32_script_test15 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MAX_VALUE_test16 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_POSITIVE_INFINITY_test17 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_MIN_VALUE_test18 Passed [java]
[jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.
[ https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677428#comment-13677428 ] Tim Baldwin commented on FLEX-33083: I had this issue, and realized when I installed the SDK I did not include the BlazeDS portion, because I use WebORB, not BlazeDS. When reinstalling the SDK including the BlazeDS portion, my project worked. Flash builder report An internal build error has occurred. See the error log for more information. - Key: FLEX-33083 URL: https://issues.apache.org/jira/browse/FLEX-33083 Project: Apache Flex Issue Type: Bug Components: Project Management Environment: Flash builder 4.6 , sdk 4.8.0 Reporter: Alex Harui Assignee: Alex Harui Labels: easyfix Attachments: mxmlc.jar, swfutils.jar, weborb.codegen.test.zip 1. download the source kit from https://svn.apache.org/repos/asf/incubator/flex/trunk 2. run ant release 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. extract AIR Integration Kit.zip to folder 5 copy additional files for Flash Ide ( frameworks/libs\player\* and frameworks\*-config.xm) 6.create a simple project with reference to RemoteObject private var remote:RemoteObject; remote = new RemoteObject; flash builder log file : !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 !MESSAGE Uncaught exception in compiler !STACK 0 java.lang.NullPointerException at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730) at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538) at flex2.tools.oem.Application.compile(Application.java:1357) at flex2.tools.oem.Application.recompile(Application.java:1295) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.
[ https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677444#comment-13677444 ] Mark Piller commented on FLEX-33083: I also confirm that it works IF the BlazeDS option is selected. I also strongly encourage a change in the installer to rename the BlazeDS option to Remoting Support. BlazeDS is not the only option on the market and by leaving the installation option to be called BlazeDS it would confuse anyone who is not using that product. There are multiple products which are alternatives to BlazeDS for various server-side environments: WebORB, AMFPHP, Red5, RubyAMF, PyAMF, etc. I believe it would be a very important change to provide a much better out of the box experience to everyone who is not using BlazeDS. Flash builder report An internal build error has occurred. See the error log for more information. - Key: FLEX-33083 URL: https://issues.apache.org/jira/browse/FLEX-33083 Project: Apache Flex Issue Type: Bug Components: Project Management Environment: Flash builder 4.6 , sdk 4.8.0 Reporter: Alex Harui Assignee: Alex Harui Labels: easyfix Attachments: mxmlc.jar, swfutils.jar, weborb.codegen.test.zip 1. download the source kit from https://svn.apache.org/repos/asf/incubator/flex/trunk 2. run ant release 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. extract AIR Integration Kit.zip to folder 5 copy additional files for Flash Ide ( frameworks/libs\player\* and frameworks\*-config.xm) 6.create a simple project with reference to RemoteObject private var remote:RemoteObject; remote = new RemoteObject; flash builder log file : !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 !MESSAGE Uncaught exception in compiler !STACK 0 java.lang.NullPointerException at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730) at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538) at flex2.tools.oem.Application.compile(Application.java:1357) at flex2.tools.oem.Application.recompile(Application.java:1295) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.
[ https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Piller updated FLEX-33083: --- Attachment: flex installer change.png The highlighted areas much change to reflect that it is the Remoting support rather than just BlazeDS support. Instead of BlazeDS, it should read Flex Remoting and Data Services Flash builder report An internal build error has occurred. See the error log for more information. - Key: FLEX-33083 URL: https://issues.apache.org/jira/browse/FLEX-33083 Project: Apache Flex Issue Type: Bug Components: Project Management Environment: Flash builder 4.6 , sdk 4.8.0 Reporter: Alex Harui Assignee: Alex Harui Labels: easyfix Attachments: flex installer change.png, mxmlc.jar, swfutils.jar, weborb.codegen.test.zip 1. download the source kit from https://svn.apache.org/repos/asf/incubator/flex/trunk 2. run ant release 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. extract AIR Integration Kit.zip to folder 5 copy additional files for Flash Ide ( frameworks/libs\player\* and frameworks\*-config.xm) 6.create a simple project with reference to RemoteObject private var remote:RemoteObject; remote = new RemoteObject; flash builder log file : !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 !MESSAGE Uncaught exception in compiler !STACK 0 java.lang.NullPointerException at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730) at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538) at flex2.tools.oem.Application.compile(Application.java:1357) at flex2.tools.oem.Application.recompile(Application.java:1295) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build failed in Jenkins: flex-sdk_mustella #144
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.commailto:bigosma...@gmail.com Date: Thursday, June 6, 2013 12:45 PM To: Alex Harui aha...@adobe.commailto:aha...@adobe.com Cc: dev@flex.apache.orgmailto:dev@flex.apache.org dev@flex.apache.orgmailto:dev@flex.apache.org, erikdebr...@apache.orgmailto:erikdebr...@apache.org erikdebr...@apache.orgmailto: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.commailto: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.nlmailto: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.commailto: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.nlmailto: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.nlmailto: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.commailto: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.commailto: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_typeSelector_te st er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_40_test13 Passed [java]
Re: Build failed in Jenkins: flex-sdk_mustella #144
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_typeSelector_te st er NV_localStyle_typeSelector_TypeStyle_test1 Passed [java] spark/validators/NumberValidator/Styles/NV_localStyle_typeSelector_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 NV_maxValue_invalid_nonNum_script_test8 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_small_test9 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_comma_large_test10 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_function_same_script_test11 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester NV_maxValue_binding_20_test12 Passed [java] spark/validators/NumberValidator/Properties/NV_maxValue_tester
Re: SDK Nightly builds?
In the interest of getting nightly builds of SDK available soon, asking this question again: Is there any way to generate a .MD5 hash of the artifacts after the release build is done? Or should we have a switch in the installer to disable MD5 checks for nightlies? Is that even a safe option? Any thoughts on this? Thanks, Om On Mon, Jun 3, 2013 at 1:34 PM, Erik de Bruin e...@ixsoftware.nl wrote: I love it when a plan comes together ;-) EdB On Mon, Jun 3, 2013 at 10:32 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: No I am not kidding. I used the url for build 27 in the Installer at which point I thought hmm... it would be good if I dint have to hardcode the build number and had a canonical url for the last build I started typing that in an email and I thought I would check if Jenkins indeed had a feature like that. That's when I saw the url for the last successful build. I dint realize that you had enabled it a few minutes back :-) On Mon, Jun 3, 2013 at 1:27 PM, Erik de Bruin e...@ixsoftware.nl wrote: I can't tell if you're kidding or not... As far as I can tell I just enabled that URL by adding the Archive the artifact Post-build Action this afternoon. EdB On Mon, Jun 3, 2013 at 9:49 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 12:47 PM, Erik de Bruin e...@ixsoftware.nl wrote: I took those links as examples and I spied on their settings to come to the URL I posted earlier. That URL doesn't simple point to the 'out' directories, it provides a permanent link to a continually update (on every build) archived version of the last successful build. A minor setting in the post build actions takes care of this archiving and makes the 'artifact' part of the URL available. Yes, I am using https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/apache-flex-sdk-4.10.0-bin for the installer config. Did you just enable this? :-) Thanks, Om EdB On Mon, Jun 3, 2013 at 9:28 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 3:38 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. Apache JMeter provides nightly builds by just pointing to the Jenkins out directories [1] Thanks, Om [1] http://jmeter.apache.org/nightly.html and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Build failed in Jenkins: flex-falcon #26
See https://builds.apache.org/job/flex-falcon/26/ -- [...truncated 1767 lines...] [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\framework.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\mobilecomponents\compile-config.xml (line: 29) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\mobilecomponents\compile-config.xml:29 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\spark.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\mobilecomponents\compile-config.xml (line: 29) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\mobilecomponents\compile-config.xml:29 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\textLayout.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\mobilecomponents\compile-config.xml (line: 29) [junit] /external-library-path [junit] [junit] [junit] Loading configuration: f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml:28 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\lib\player\11.1\playerglobal.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml (line: 28) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml:28 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\framework.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml (line: 28) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml:28 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\textLayout.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\rpc\compile-config.xml (line: 28) [junit] /external-library-path [junit] [junit] [junit] Loading configuration: f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml:31 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\lib\player\11.1\playerglobal.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml (line: 31) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml:31 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\framework.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml (line: 31) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml:31 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\spark.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml (line: 31) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml:31 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\mx\mx.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml (line: 31) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml:31 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\advancedgrids.swc'. [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml (line: 31) [junit] /external-library-path [junit] [junit] [junit] f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\projects\spark_dmv\compile-config.xml:31 [junit] Error: unable to open 'f:\hudson\hudson-slave\workspace\flex-sdk\frameworks\libs\textLayout.swc'. [junit]
Re: BlazeDS
What I like about BlazeDS is that it has the same basic architecture as LiveCycle DS, so you can pretty much swap them out 1:1 and just gain new functionality with LiveCycle. Granted, you do have to modify your code to take advantage of that functionality, but the changes are minimal. It has been several years since I looked at GraniteDS, but as I recall it leaned pretty heavily on the use of your Tide framework to be able to take advantage of any of the advanced functionality, which meant replacing a lot of my code. I'll take a look at where it is at now though before I pass judgement. I'm sure you have done a lot with it since then. Nick On Tue, Jun 4, 2013 at 3:33 AM, William Drai william.d...@graniteds.netwrote: Well we are currently helping many companies to switch from BlazeDS to GraniteDS and Spring/Parsley is one of the most frequent stacks we have to deal with, so yes it works perfectly. You can get some hints about how to switch herehttp://granitedataservices.com/migrating-from-blazeds-to-graniteds/, and usually the migration should not take more than a few days. William 2013/5/30 dude d...@atheist.com I know about GraniteDS and it's awesome (we already use Gas3). Unfort. it's not possible to migrate our current project to GraniteDS entirely within a reasonable amount of time, because we use technologies like Spring-Flex and Parsley which do not work combined with GraniteDS (or do they?). Am 30.05.2013 14:50, schrieb Franck Wolff: If you are looking for an efficient realtime messaging stack, you could have a look at GraniteDS http://www.graniteds.org/. Franck. 2013/5/30 dude d...@atheist.com Looking forward to that. Am 30.05.2013 12:36, schrieb christofer.d...@c-ware.de: As far as I know there are a lot of tutorials about creating NIO adapters for BlazeDS ... The ones out there make use of properitary Jetty features and I have not yet come across one generic servlet 3.0 spec endpoint. I would much more prefer to start working on such an endpoint. It's something I have on my todo list for quite some time now ;-) Chris -Ursprüngliche Nachricht- Von: Nick Collins [mailto:ndcoll...@gmail.com] Gesendet: Mittwoch, 29. Mai 2013 23:58 An: dev@flex.apache.org Betreff: Re: BlazeDS I may or may not have missed it, but does anyone know if there is any chance of the guys at Farata donating their extensions along with BlazeDS that add NIO support and such? That would make the Apache BlazeDS even more competitive against ADEP DS. Nick On Tue, May 28, 2013 at 10:47 PM, Alex Harui aha...@adobe.com wrote: I keep seeing signs that they are making slow progress toward getting it donated. On 5/28/13 7:48 PM, Justin Mclean jus...@classsoftware.com wrote: HI, A question just come up on the user list about BlazeDS. Alex do you know if it still likely to be donated? Thanks, Justin -- William Draï Granite Data Services 24, rue de l'Est 75020 Paris +33 (0)1 83 64 73 23 +33 (0)6 23 92 24 43 william.d...@graniteds.net
[jira] [Created] (FLEX-33584) Draging the mouse outside the window with the middle or right button will disable mouse over
Jean-Denis Boivin created FLEX-33584: Summary: Draging the mouse outside the window with the middle or right button will disable mouse over Key: FLEX-33584 URL: https://issues.apache.org/jira/browse/FLEX-33584 Project: Apache Flex Issue Type: Bug Components: MXML Components, Spark Components Affects Versions: Apache Flex 4.9.0 Environment: Any Reporter: Jean-Denis Boivin Problem Description: When targeting swf-version=16 or more, draging the mouse outside the window with the middle or right button will disable mouse over on flex components. Steps to Reproduce:Compile a swf with swf-version=16 or more, drag the mouse outside the window with the middle or right button down. Actual Result:When hovering any components, there is no over effect. Expected Result:Components should display a over effect. Any Workarounds: Click inside the SWF with the button you used on your mouse (right or middle), clicking with the left button won't resolve it. Using swf-version=13 does not have this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: SDK Nightly builds?
HI, Is there any way to generate a .MD5 hash of the artifacts after the release build is done? Should be straightforward. On OSX/Linux it's just md5 filename. On windows it may be more complex and you may need to use this: http://support.microsoft.com/kb/841290 Jenkins could be set up to run it as a last step. Thanks, Justin
[jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.
[ https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677830#comment-13677830 ] Justin Mclean commented on FLEX-33083: -- Changed license message to be more generic and checked into develop. Need other language translations. Flash builder report An internal build error has occurred. See the error log for more information. - Key: FLEX-33083 URL: https://issues.apache.org/jira/browse/FLEX-33083 Project: Apache Flex Issue Type: Bug Components: Project Management Environment: Flash builder 4.6 , sdk 4.8.0 Reporter: Alex Harui Assignee: Alex Harui Labels: easyfix Attachments: flex installer change.png, mxmlc.jar, swfutils.jar, weborb.codegen.test.zip 1. download the source kit from https://svn.apache.org/repos/asf/incubator/flex/trunk 2. run ant release 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. extract AIR Integration Kit.zip to folder 5 copy additional files for Flash Ide ( frameworks/libs\player\* and frameworks\*-config.xm) 6.create a simple project with reference to RemoteObject private var remote:RemoteObject; remote = new RemoteObject; flash builder log file : !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 !MESSAGE Uncaught exception in compiler !STACK 0 java.lang.NullPointerException at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730) at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538) at flex2.tools.oem.Application.compile(Application.java:1357) at flex2.tools.oem.Application.recompile(Application.java:1295) at flex2.tools.oem.Application.compile(Application.java:894) at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319) at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129) at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198) at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607) at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382) at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
