RE: [ANNOUNCE] Welcome Tom Chiverton as the newest PMC member
Congrats Tom Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : jeudi 18 septembre 2014 10:03 À : dev@flex.apache.org Objet : [ANNOUNCE] Welcome Tom Chiverton as the newest PMC member Hi, For all his hard work and recent contributions to Apache Flex the Apache Flex PMC has voted Tom Chiverton in as a fellow member. Tom, let me be the first to welcome you and wish you good luck in your new role: congratulations! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
BlazeDS released version
Hi A colleague of mine told me of the following: BlazeDS Latest Releases to the bottom of the page http://flex.apache.org/ says BlazeDS: 4.6.0 (Nov 2011) and points to http://sourceforge.net/adobe/blazeds/wiki/Home/ However, the latest released (not the nightly builds) version of BlazeDS seems to be 4.0.0.14931, released on I am going to fix the label, unless somebody objects. Maurice
RE: [VOTE} Accept FlatSpark Theme Donation
+1 (binding) -Message d'origine- De : lluuccaa1 [mailto:lluucc...@gmail.com] Envoyé : mardi 9 septembre 2014 12:09 À : dev@flex.apache.org Objet : Re: [VOTE} Accept FlatSpark Theme Donation +1 On 9 September 2014 11:16, Frédéric THOMAS webdoubl...@hotmail.com wrote: +1 (binding)Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: [VOTE} Accept FlatSpark Theme Donation Date: Mon, 8 Sep 2014 16:50:50 + Didn't see any objection in the discuss thread, so time for the official vote. I saw a note on an Apache incubator page saying that donation votes really shouldn't be lazy so PMC members please reply with votes. The creators of the FlatSpark theme (https://github.com/akamud/FlatSpark ) have generously offered to donate the theme to Apache Flex. Please vote to accept the donation. Thanks, -Alex
RE: [POLL] Accept Radii8 Code Donation
+1 -Message d'origine- De : Chris Martin [mailto:windo...@gmail.com] Envoyé : mardi 19 août 2014 18:03 À : dev@flex.apache.org Objet : Re: [POLL] Accept Radii8 Code Donation +1 On Mon, Aug 18, 2014 at 11:36 PM, Frédéric THOMAS webdoubl...@hotmail.com wrote: And that's a +1 indeed Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: [POLL] Accept Radii8 Code Donation Date: Tue, 19 Aug 2014 07:19:56 +0100 Thanks for the clarification and for this donation Jude, I'm happy to see you contribute and spend time on this useful tool. Frédéric THOMAS Date: Mon, 18 Aug 2014 21:32:23 -0500 Subject: Re: [POLL] Accept Radii8 Code Donation From: flexcapaci...@gmail.com To: dev@flex.apache.org On Monday, August 18, 2014, Justin Mclean jus...@classsoftware.com wrote: HI, Doesn't matter. So I'd take that as it currently doesn't work or compile? I feel like I missed giving some of the details on this project. As Alex and I have been going through it I've tried to keep compileable as long as I could. When it came to the icons I reused mostly all Eclipse icons since that is open source. We decided after some discussion that we (the community) should or could recreate the icons later. To keep the project compilable I decided to blacken out the images rather than remove them and have the compiler complain. If someone so chooses they can look at the runtime demo at radii8.com/demo until we get replacements. Remarkably we haven't had to remove too many classes. But where we have removed functionality I will document those cases and we can rewrite or work on getting permission after donation. I will document those cases so we know where and what was removed or doesn't work. Alex is well aware of these cases and that's partially why we didn't want to liter the list with these details until later. We were planning to provide all this information at some point and it's astute of you to notice and get more info. We just need to get the donation secured first IMHO and then go back and work on these issues after. The idea among a few ideas was to create a Flex Explorer / Design view online so people can try Flex and see the generated code. At the same time it's also in my opinion to create a design time canvas / design view we can use for our projects where we dint have to create something from scratch. We tell our client we can create a furniture layout designer that customers can use and that it will take 6 months but really we will use this, add some furniture components and then drink margaritas on the beach for 5 months. Somewhat joking but that's the plan. The other plan is to create awesome layouts that export Flex MXML but also HTML for mobile sites bc we all agree imho that we would rather do something else than code HTML layouts. I get the feeling no one on this dev list doesn't know how to do this but me personally. Once it's all committed we will work on getting it going, listing what works, what doesn't, what direction / needs / services people on the community want or need or would just like to see. Do we have any idea on how much work may be required to get this into a releasable state? While not required, a list of what needs to be done/what''s missing would be useful. Thanks, Justin
RE: Please welcome Chris Martin as an Apache Flex committer
Welcome on board, Chris. -Message d'origine- De : Jose Barragan [mailto:jose.barra...@codeoscopic.com] Envoyé : dimanche 17 août 2014 13:02 À : dev@flex.apache.org Objet : Re: Please welcome Chris Martin as an Apache Flex committer Welcome!! :) __ Jose Barragan Senior Software Engineer On 15 Aug 2014, at 19:36, Carlos Rovira carlos.rov...@codeoscopic.com wrote: Welcome Chris! :) 2014-08-13 20:54 GMT+02:00 Erik de Bruin e...@ixsoftware.nl: Chris, great to have you! Now, go forth and multiply your contributions ;-) EdB On Wednesday, August 13, 2014, Chris Martin windo...@gmail.com wrote: Thanks everyone! :D Tis great to be here :) Chris On Wed, Aug 13, 2014 at 4:27 AM, Christofer Dutz christofer.d...@c-ware.de javascript:; wrote: Welcome :-) Von: Kessler CTR Mark J mark.kessler@usmc.mil javascript:; Gesendet: Mittwoch, 13. August 2014 11:48 An: dev@flex.apache.org javascript:; Betreff: RE: Please welcome Chris Martin as an Apache Flex committer Congratulations :) -Mark -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com javascript:;] Sent: Tuesday, August 12, 2014 8:22 PM To: dev@flex.apache.org javascript:; Subject: Please welcome Chris Martin as an Apache Flex committer Hi, I am pleased to announce that the Project Management Committee (PMC) for Apache Flex has invited Chris Martin to become a committer and he has accepted. Chris has been active on the mailing lists and raised several important JIRA issues with patches and tests. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Carlos Rovira M: +34 607 22 60 05 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
RE: Please welcome Darkstone as an Apache Flex committer
Welcome Darkstone. -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : mercredi 13 août 2014 02:15 À : dev@flex.apache.org Objet : Please welcome Darkstone as an Apache Flex committer Hi, Sorry for being a little late in announcing this. I am pleased to announce that the Project Management Committee (PMC) for Apache Flex has invited Darkstone to become a committer and he has accepted. Darkstone has been active on the mailing lists and helped out with several JIRA issues, helped test multiple release candidates, as well as helping out with Chinese translations for the installer and SDK. Thanks, Justin
RE: [LAZY] Accept Radii8 Code Donation
+1 (binding) -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 28 juillet 2014 06:34 À : dev@flex.apache.org Objet : [LAZY] Accept Radii8 Code Donation Hi Folks, This is the official vote thread. It is Lazy consensus so you only need to raise objections although I'm not expecting any based on the earlier poll. Judah Frangipane (a long time Flex user) has been busy helping Harbs with TLF Tables, but has also developed a Flex=oriented IDE called Radii8. The GitHub project is here: https://github.com/monkeypunch3/Radii8 Judah is proposing to donate Radii8 to Apache Flex. Here's a quote from Judah about Radii8: What my main focus has been is to be able to design something that then generates a web site or an application with a lot of hooks and tools to do our job (web, mobile and desktop). Why not use Photoshop or Ai to accomplish that? I could! That will work for some projects but I'm trying to support the full Flex framework. And there's projects I'd like to do that would require it's own environment. Also, code editing or text editing might better be handled in things like FDT, FB, or IntelliJ. We'll close the vote after 72 hours. Thanks, -Alex
RE: [LAZY] Enabling Github pull requests in Apache Flex
Is this a vote thread? If so +1 for me -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : vendredi 25 juillet 2014 02:35 À : dev@flex.apache.org Objet : [LAZY] Enabling Github pull requests in Apache Flex The INFRA team has started supporting [1] pull requests from github. If no one has objections, I will open a ticket with INFRA to enable this feature for Apache Flex. In particular, these are the benefits we get from opting in for the tighter GitHub integration - Any Pull Request that gets opened, closed, reopened or commented on now gets recorded on the project's mailing list - If a project has a JIRA instance, any PRs or comments on PRs that include a JIRA ticket ID will trigger an update on that specific ticket - Replying to a GitHub comment on the dev@ mailing list will trigger a comment being placed on GitHub (yes, it works both ways!) - GitHub activity can now be relayed to IRC channels on the Freenode network. This means that we can actually accept pull requests from GitHub going forward. Thanks, Om [1] https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
RE: Regression issue from 4.12.0
Hi Justin, I will fix it in the coming days. Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 18 juillet 2014 02:01 À : dev@flex.apache.org Objet : Regression issue from 4.12.0 Hi, Just been informed on twitter this is a regression issue in 4.13.0 https://issues.apache.org/jira/browse/FLEX-34405 Justin
RE:[POLL] Accept Radii8 Code Donation
Thank you Jude for the comprehensive answer. It's much clearer now. I will try the mxml import. Btw, I am surprised that you say Form does not have a visual representation. Maybe we are not talking of the same thing. http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/spark/components/Form.html Maurice De : jude [flexcapaci...@gmail.com] Envoyé : vendredi 18 juillet 2014 09:29 À : dev Objet : Re: [POLL] Accept Radii8 Code Donation Comments inline... On Thu, Jul 17, 2014 at 3:20 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Nice piece of work and clean UI. I have some questions to Judah that I didn't ask when he first announced Radii8 some time ago: How is this going to be used in an real application development workflow ? I see a couple of scenarios. In *one* case, you would use this to get a quick mockup or layout for your Flex project. For example, I had a form with two inputs and a submit button. I opened Radiate and dragged an HGroup, two labels and two inputs to the stage along with a submit button. I set some properties and styles to get the look I was going for. I then opened the code panel and copied the MXML code to my main Flex project. I then closed Radiate without saving the document (or just closed the document). I later received a new mockup from the client asking for an updated form. I repeat the same process as before or import the code back in but this time I saved the document and I can open it in Radiate later. If I have a lot of panels or forms I could keep them saved and go back and modify or retrieve them as needed. Sort of used as a library of visual layouts. Right now, we can't use Flash Builders design view with Flex 4.13. And to me, in some cases it may be more efficient to visually create the mockup or layout than to write the code, run debug, and confirm all this is not always the case. There's a basic MXML importer in it now. It's not robust but you can pass in MXML and it will build the UI from it. So for people that want to type code it wouldn't be difficult to make it render live as you type. This is the *second* case, for example, there is a panel or view that has a code editor that shows the generated code. For MXML if you type in that text area right now nothing happens. It could be wired up to render the MXML live in the design view as you type. FYI It does render the code live when HTML code is active and you are showing a preview. In the code view are three tabs for MXML, HTML and Android XML. In the HTML code, if you click the preview button it will create an iframe behind the scenes and pass the generated HTML into it. This will give you the preview obviously. BTW there is a Show Background Image option that shows a snapshot of the actual design in the background of the HTML preview. Anyway, if you type in the code editor (text area) it will update the HTML preview live. The HTML should be a pixel perfect representation of the Flex rendition but because HTML is the spawn of satan and it may not look the same across browsers. So that is why you are able to modify the HTML on the fly. You may find you need to add CSS style or property exceptions, overrides or additions. The purpose of that panel would allow you to modify the generated CSS. But we are talking about MXML. So to get back on track, you would be able to type MXML or copy and paste it into the code editor and have it render. That's the second use case. The *third* is to have a desktop version that points to an actual Flex project application. You would have Flash Builder or another editor open. It would pull in the project and list the applications or MXML documents. When you clicked on the MXML file it would import it. You could then modified the layout and saved the changes. Flash Builder would prompt you to reopen the latest version of the file. In the same situation you could setup sections that are the only places that can be edited. Similar to Dreamweaver regions, you would delimit a section of MXML layout that can be edited. All other code would remain unchanged. So something like this: !--- DESIGN AREA: DO NOT EDIT BELOW THIS LINE-- s:Group id=areas:Graphic .../s:Graphic/s:Group !--- DESIGN AREA: DO NOT EDIT ABOVE THIS LINE-- The *forth* is to be able to pull in a SWF, live or in the debug or release folder of a project, make changes to the layout and then create an edit decision list from the changes. For example, I post a SWF online. A designer views the SWF and sees there are changes that need to be made. She opens Radiate desktop or online and the SWF is loaded into the program. She changes the font size, the color and moves some images around. What seems like a few small changes but actually maybe 30 different actual steps. She has no access to the project MXML or needs to. After she's made modifications she exports or emails the EDL to the developer. It contains a list of only the final changes: moved
RE: [POLL] Accept Radii8 Code Donation
Nice piece of work and clean UI. I have some questions to Judah that I didn't ask when he first announced Radii8 some time ago: How is this going to be used in an real application development workflow ? 1) consider I have created my first UI using Radii8 and exported the MXML code to Flex, I will then probably manually add some custom code (bindings, inline scripts, etc...). Then how do I get back to Radii8 to make a change ? 2) the component palette seem to include only a subset of Flex SDK components. Some key components/containers are missing: From, FormItem, DataGrid, Panel ,TitleWindow, ... And some components don't even exist (s:LinkButton ?) Is there a plan to support them ? 3) what is the purpose of the HTML / Android export ? who is going to use it ? Regards, Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 17 juillet 2014 07:23 À : dev@flex.apache.org Objet : Re: [POLL] Accept Radii8 Code Donation Hi, Looks good and a useful think to have. A few questions - which probably only Judah can answer: - Is Judah willing to fill in the paperwork to get the donation done? (We've had a least one donation that's stuck in limbo because paperwork was not done.) - Has he signed an ICLA? And I assume for something this large would require a software grant. - Have there been any other contributors to the code? - How was he employed when developing this? Does he or perhaps an employer own the rights to the code? - Once donated to Apache is he willing to continue working on and and/or support it? Thanks, Justin
RE: IOS 7 and Android 4.3 Skinning
Thanks om -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : mardi 8 juillet 2014 03:16 À : dev@flex.apache.org Objet : Re: IOS 7 and Android 4.3 Skinning The current BusyIndicator has its visuals baked into the component itself. That is not a very good idea. So, I created a new component MobileBusyIndicator [1] and created an android specific skin for it [2] Once I start working on the iOS7+ theme, I will move the current visualization into a new iOS7 specific skin. Next up: DateSpinner Thanks, Om [1] https://github.com/apache/flex-sdk/blob/new_android_skins/frameworks/projects/mobilecomponents/src/spark/components/MobileBusyIndicator.as [2] https://github.com/apache/flex-sdk/blob/new_android_skins/frameworks/projects/mobiletheme/src/spark/skins/android4/BusyIndicatorSkin.as On Sun, Jul 6, 2014 at 4:24 PM, Mark Kessler kesslerconsult...@gmail.com wrote: I like the table. Organized -Mark On Wed, Jul 2, 2014 at 8:01 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: Thanks to Aaron Nash, we now have skins for Android 4.3 - TextArea and TextInput. In the meantime, I have completed the Callout and related skins. I have updated the wiki page here: https://cwiki.apache.org/confluence/display/FLEX/Progress+info+for+And roid+4.x+skins BusyIndicator is next on my plate. Anyone else working on any skins? Thanks, Om On Mon, Jun 16, 2014 at 2:35 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: https://cwiki.apache.org/confluence/display/FLEX/Progress+info+for+And roid+4.x+skins has been updated with the latest progress. Thanks, Om On Mon, Jun 16, 2014 at 2:32 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Aaron, I have fixed the SpinnerList and SpinnerListContainer skins to make them work with all supported DPIs. Please feel free to review the code and let me know if something looks wrong. Thanks, Om On Fri, Jun 13, 2014 at 11:41 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Jun 13, 2014 11:13 AM, quick6black anas...@gmail.com wrote: I see where I messed up on the spinner lists, do you want me to fix and resubmit? it really gets wonky when you change the resolution Actually, I got this one. You can concentrate on the TextInput skins. Can you also update the wiki page to indicate what skins you are working on? Thanks, Om -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Re-IOS-7-and-Andr oid-4-3-Skinning-tp37835p38281.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE:Apache Flex committer invite
If you are new to git, I suggest you use GUI git client, like sourcetree or another one. It helped me a lot. Maurice De : Mihai Chira [mihai.ch...@gmail.com] Envoyé : vendredi 4 juillet 2014 20:22 À : dev@flex.apache.org Objet : Re: Apache Flex committer invite That's awesome! Thanks, Nicholas. I'll try it tomorrow. On 4 July 2014 18:26, Nicholas Kwiatkowski nicho...@spoon.as wrote: Mihai, We actually switched from SVN to GIT a while ago. Our SVN repo is in read only mode (except for the website, which is still pushed via SVN). You should be able to pull down our repos as in: http://flex.apache.org/dev-sourcecode.html , and push changes back via your new apache ID and password. -Nick On Fri, Jul 4, 2014 at 12:21 PM, Mihai Chira mihai.ch...@gmail.com wrote: Hi all, I just tried to make my first svn commit, and got the error below. I read the Apache Source Code Repository page[1] and I couldn't find this error there. The closest was If you still get 403 Forbidden errors, ask your PMC to double-check the authz file and LDAP/Unix group membership. Another clue was this stackoverflow page [2], but my working copy seems to be correctly capitalised. And the final seemingly useful piece of information I found was this thread[3], which suggests that it might be an apache server configuration issue. But I think it's more likely that I'm doing something wrong :) PS: my username and password are correct, as I tested them on the apache website. [1] http://www.apache.org/dev/version-control.html [2] http://stackoverflow.com/questions/57137/403-forbidden-error-using-subversion [3] http://serverfault.com/questions/256307/svn-put-403-forbidden-on-commit Commit failed (details follow): Changing file 'C:\Users\mihaichira\workspaceFlex\flex\sdk\trunk\frameworks\projects\framework\src\mx\core\UIComponent.as' is forbidden by the server Access to '/repos/asf/!svn/txr/1607803-z8a6/flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as' forbidden Additional errors: PUT of '/repos/asf/!svn/txr/1607803-z8a6/flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as': 403 Forbidden Thanks, Mihai
RE: [FlexJS] Designers needed for default theme
It's beautiful and very clean. I love it. PS: I didn't see scrollbars in the gallery. Maurice -Message d'origine- De : akamud [mailto:mudd...@gmail.com] Envoyé : vendredi 23 mai 2014 15:51 À : dev@flex.apache.org Objet : Re: [FlexJS] Designers needed for default theme I am one of the authors of FlatSpark and we are very happy with the community feedback over the theme. We saw this post and we were got VERY excited, of course we have TOTAL INTEREST IN CONTRIBUITING AND DONATING THE SKIN to FlexJS, if there is interest in doing this, we can talk about this right now. Besides that, we have an excelent suggestion for the Flex contest. After we started FlatSpark, we found out about BootFlat (http://bootflat.github.io/documentation.html), which is a little bit different and more friendly for enterprise UI's (we think so, hehe), so we planned to start another project based on BootFlat's styles. Because of this thread we will probably have a preview at the weekend specially for you. But please, we would like to know, what is your opinion about BootFlat? Another interesting point is that BootFlat is also open-source, under MIT license, so it would be possible to use it to create a new theme. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Designers-needed-for-default-theme-tp37656p37715.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [FlexJS] Use FlatSpark as theme for FlexJS
See other thread on users list called IOS 7 and Android 4.3 Skinning. [1] https://github.com/apache/flex-sdk/tree/new_android_skins/frameworks/projects/mobiletheme/src/spark/skins/android4 -Message d'origine- De : brunopacola [mailto:brunopac...@gmail.com] Envoyé : vendredi 23 mai 2014 18:07 À : dev@flex.apache.org Objet : RE: [FlexJS] Use FlatSpark as theme for FlexJS Hi Maurice, I'm not familiar with this iOS7+Android theme made by Om. Where can I find more information about this? Thank you! - Bruno Pacola FlatSpark Skin: http://akamud.github.io/FlatSpark -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Use-FlatSpark-as-theme-for-FlexJS-tp37721p37728.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [FlexJS] Use FlatSpark as theme for FlexJS
Why is that? Seems like we could just have more choices for folks. Of course. Sorry I didn't use the right word. By merge, I meant that since iOS7+Android are also skins, and iOS7 is also flat design, then we should consider all these skinning work as a whole, and not as separate initiatives and maybe share some work or thoughts. Makes sense ? - would it replace current spark default theme, or come as an option ? I would vote for 'option' OK Regarding the FlexJS + Flex sharing the same theme, I was rather on the design and artwork level, rather than the implementation. But maybe there is something to do at the implementation level too, or even the compiler. I thing we will see when starting working on it . Thank you for the answers. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 23 mai 2014 18:35 À : dev@flex.apache.org Objet : Re: [FlexJS] Use FlatSpark as theme for FlexJS On 5/23/14 8:45 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Also, it would need to be merged with the current work done on iOS7+Android by Om. Why is that? Seems like we could just have more choices for folks. Questions: - would it replace current spark default theme, or come as an option ? I would vote for 'option' - are you ok with FlexJS and Flex sharing the same theme? It would be interesting to see if the theme can be designed for both. We do want to know what we can use from existing themes as-is. The first concern that pops into my head is all of the Spark class dependencies in the MXML Skins. Not sure what the impact would be of having those definitions around when compiling/linking a FlexJS app. Theoretically it should work. Or maybe we'll modify Falcon so it does work. Some themes in current Flex do not appear to be SWCs full of MXML skins. I've never bothered to look to see how those work, but that might make it easier to have the theme work for both Flex and FlexJS. -Alex
RE: [OT] Looking for Flex work
I wish you good luck, Justin. Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 23 mai 2014 21:52 À : dev@flex.apache.org; us...@flex.apache.org Objet : [OT] Looking for Flex work Hi, My current work situation has changed and I'm looking for some new work. I'm based in Sydney Australia but am currently travelling in the US and UK for the next month. Just in case you don't know me, I've a Flex committer and board member and been the release manager for Apache Flex and Flex Unit and fixed 100's of bugs in the Apache Flex SDK. I've been working on commercial Flex applications for many years (since version 1.5) and have over 25 years of programming experience with a wide set of skills. I'm a regular user group and conference speaker and also run training courses on Flex and other technologies. I run the local Internet of Things meetup group and have published a book on Android application development. Please contact me off list at jus...@classsoftware.com if you have something you think may interest me or want more detail on my skills and experience. Thanks, Justin
RE: [FlexJS] Designers needed for default theme
+1 -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mercredi 21 mai 2014 01:42 À : dev@flex.apache.org Objet : Re: [FlexJS] Designers needed for default theme On 5/20/14 3:56 PM, Frédéric THOMAS webdoubl...@hotmail.com wrote: There is already this one, someone talked about on the list and twitter recently https://github.com/akamud/FlatSpark The author would have to donate it to Apache, but if folks like it, we can ask. -Alex
RE: Please welcome Mihai Chira as the newest Apache Flex committer
Congratulations and welcome on board Mihai. Maurice -Message d'origine- De : piotrz [mailto:piotrzarzyck...@gmail.com] Envoyé : lundi 19 mai 2014 21:15 À : dev@flex.apache.org Objet : Re: Please welcome Mihai Chira as the newest Apache Flex committer Hi Mihai!!! :) Welcome on board! :) Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Please-welcome-Mihai-Chira-as-the-newest-Apache-Flex-committer-tp37598p37602.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE:[ANNOUNCE] Apache Flex 4.12.1 released
Thanks Alex of taking care of this release. Maurice De : Alex Harui [aha...@adobe.com] Envoyé : samedi 3 mai 2014 07:39 À : us...@flex.apache.org; dev@flex.apache.org Objet : [ANNOUNCE] Apache Flex 4.12.1 released The Apache Flex community is pleased to announce the release of Apache Flex 4.12.1 Apache Flex is a highly productive, open source application framework for building and maintaining expressive applications that deploy consistently on all major browsers, desktops and devices (including smartphones, tablets and tv). Apache Flex 4.12.1 is a update to Apache Flex 4.12.0 that adds support for the latest Flash Player and AIR runtimes, improved mobile media query support, and over 20 bug fixes. Additional information can be found here: https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+4.12.1+Release +Notes Apache Flex is available in source form from the following download page: http://flex.apache.org/download-source.html It's recommended you install Apache Flex by using the Apache Flex IDE installer: http://flex.apache.org/installer.html When downloading from a mirror site, please remember to verify the downloads using signatures or MD5 hashes. For more information on Apache Flex, visit the project home page: http://flex.apache.org Thank you for using Apache Flex, The Apache Flex Community
RE: Updating documentation about the scrolling stage text issue
Hi, I just created an JIRA request to get write access to the blog: https://issues.apache.org/jira/browse/INFRA-7669 Is there anything else needed ? Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : mercredi 16 avril 2014 20:13 À : dev@flex.apache.org Objet : Updating documentation about the scrolling stage text issue (Moving to dev) On Apr 16, 2014 10:37 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I really wish there was a way to remove the stale information on that page. I agree. Flex is in a sort of schizophrenic situation. So let's take the good side of it, and be happy that at least this kind of documentation exists, even if it's not 100% accurate. PS: even if this was possible, how long and how much people would it take to review all the doc/blogs on Flex and make sure everything is up to date with SDK 4.12 ;-) Maurice The problem is that this issue was always seen as a major one. The fact that this has been fixed needs to be widely published. Would you mind doing a blog post on the ASF Flex blog about this? You can give an overview of the issue and describe how it has been fixed now. We can highlight the fact that the info in the link in question [1] is stale. Thanks, Om [1] http://help.adobe.com/en_US/flex/mobileapps/WS82181550ec4a666a39bafe0312d9a274c00-8000.html#WSc71dc4a5c6f1e0e0-1ee7fed313283418436-7ffe
RE: [DRAFT] 4.12.1 announcement
Maybe include a link to the release notes: https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+4.12.1+Release+Notes Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 2 mai 2014 18:59 À : dev@flex.apache.org Objet : [DRAFT] 4.12.1 announcement Hi, I'll send this out in about 12 hours or so. Do we need to announce on the official Apache announce list? -- start draft announcement -- The Apache Flex community is pleased to announce the release of Apache Flex 4.12.1 Apache Flex is a highly productive, open source application framework for building and maintaining expressive applications that deploy consistently on all major browsers, desktops and devices (including smartphones, tablets and tv). Apache Flex 4.12.1 is a update to Apache Flex 4.12.0 that adds support for the latest Flash Player and AIR runtimes, improved mobile media query support, and over 20 bug fixes. Apache Flex is available in source form from the following download page: http://flex.apache.org/download-source.html It's recommended you install Apache Flex by using the Apache Flex IDE installer: http://flex.apache.org/installer.html When downloading from a mirror site, please remember to verify the downloads using signatures or MD5 hashes. For more information on Apache Flex, visit the project home page: http://flex.apache.org http://flex.apache.org/ Thank you for using Apache Flex, The Apache Flex Community -- end draft announcement -- Thanks, -Alex
RE: [DRAFT] Installer 3.0 Announcement
ok -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 2 mai 2014 19:14 À : dev@flex.apache.org Objet : [DRAFT] Installer 3.0 Announcement Hi, I'll send this out after the 4.12.1 announcement. -- start draft announcement -- The Apache Flex community is pleased to announce the release of Apache Flex SDK Installer 3.0 Apache Flex is a highly productive, open source application framework for building and maintaining expressive applications that deploy consistently on all major browsers, desktops and devices (including smartphones, tablets and tv). Apache Flex SDK Installer 3.0 is an update to Apache Flex SDK Installer 2.7. It provides the ability to install other SDKs like the FlexJS SDK. Apache Flex SDK Installer is available in source form from the following download page: http://flex.apache.org/download-source.html Executables for Windows and Mac are available here: http://flex.apache.org/installer.html Executables for Linux are no longer provided as all recent Flex and FlexJS SDKs can be installed by running the installer.xml Ant script in the release packages. When downloading from a mirror site, please remember to verify the downloads using signatures or MD5 hashes. For more information on Apache Flex, visit the project home page: http://flex.apache.org Thank you for using Apache Flex, The Apache Flex Community -- end draft announcement -- Thanks, -Alex
RE:[DISCUSS] Discuss Apache Flex 4.12.1 RC2
No, it won't. So go ahead De : Alex Harui [aha...@adobe.com] Envoyé : jeudi 1 mai 2014 18:08 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 Working on it now. If your wiki page isn't ready right away I don't think it will matter that much. On 5/1/14 9:06 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: When do you intend to make the announcement on 4.12.1, so you I can have the wiki page ready ? De : Alex Harui [aha...@adobe.com] Envoyé : jeudi 1 mai 2014 17:35 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 On 4/30/14 1:41 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: (copied from wrong VOTE thread): One minor issue in the release notes: FLEX-33948 Add touch behaviour to spark DropDownList classes = the ticket is still open. implementation attempts were not satisfactory, and have not been committed. I accepted the patch in 4a13999192e5ebb8ab9d435069e226f6b9f30759 but forgot to update the bug. Also, I find that the release notes do not describe accurately enough what's in the release (eg. extended queries), and going to JIRA to understand what was done isn't better. I suggest that we add a page (either in the web site or in the wiki) to describe in detail the various features. What do you think? Feel free to add a wiki page. -Alex
RE:[DISCUSS] Discuss Apache Flex 4.12.1 RC2
When do you intend to make the announcement on 4.12.1, so you I can have the wiki page ready ? De : Alex Harui [aha...@adobe.com] Envoyé : jeudi 1 mai 2014 17:35 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 On 4/30/14 1:41 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: (copied from wrong VOTE thread): One minor issue in the release notes: FLEX-33948 Add touch behaviour to spark DropDownList classes = the ticket is still open. implementation attempts were not satisfactory, and have not been committed. I accepted the patch in 4a13999192e5ebb8ab9d435069e226f6b9f30759 but forgot to update the bug. Also, I find that the release notes do not describe accurately enough what's in the release (eg. extended queries), and going to JIRA to understand what was done isn't better. I suggest that we add a page (either in the web site or in the wiki) to describe in detail the various features. What do you think? Feel free to add a wiki page. -Alex
RE: [DISCUSS] Discuss Apache Flex 4.12.1 RC2
Here you are: https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+4.12.1+Release+Notes Feel free to make additions/changes. -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 1 mai 2014 18:15 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 Actually the announcement won't go out for another 24 hours so the mirrors can pick up the new bits. On 5/1/14 9:10 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: No, it won't. So go ahead De : Alex Harui [aha...@adobe.com] Envoyé : jeudi 1 mai 2014 18:08 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 Working on it now. If your wiki page isn't ready right away I don't think it will matter that much. On 5/1/14 9:06 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: When do you intend to make the announcement on 4.12.1, so you I can have the wiki page ready ? De : Alex Harui [aha...@adobe.com] Envoyé : jeudi 1 mai 2014 17:35 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 On 4/30/14 1:41 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: (copied from wrong VOTE thread): One minor issue in the release notes: FLEX-33948 Add touch behaviour to spark DropDownList classes = the ticket is still open. implementation attempts were not satisfactory, and have not been committed. I accepted the patch in 4a13999192e5ebb8ab9d435069e226f6b9f30759 but forgot to update the bug. Also, I find that the release notes do not describe accurately enough what's in the release (eg. extended queries), and going to JIRA to understand what was done isn't better. I suggest that we add a page (either in the web site or in the wiki) to describe in detail the various features. What do you think? Feel free to add a wiki page. -Alex
RE: [DISCUSS] Discuss Apache Flex 4.12.1 RC2
(copied from wrong VOTE thread): One minor issue in the release notes: FLEX-33948 Add touch behaviour to spark DropDownList classes = the ticket is still open. implementation attempts were not satisfactory, and have not been committed. Also, I find that the release notes do not describe accurately enough what's in the release (eg. extended queries), and going to JIRA to understand what was done isn't better. I suggest that we add a page (either in the web site or in the wiki) to describe in detail the various features. What do you think? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : mardi 29 avril 2014 04:33 À : dev@flex.apache.org Objet : Re: [DISCUSS] Discuss Apache Flex 4.12.1 RC2 Hi, Is it possible that between 4.11 and 4.12 we switched from OSX Java 6 to Java 7 and that caused this problem? Possibly. IMO, this is not a blocker since folks have not noticed this with 4.12. No didn't think it was a blocker - just an inconvenience when trying to make a release. Justin
RE: Adobe AIR app installs cross a billion
Thanks for sharing. Chinese in just after English with 11.4% ;-) Maurice -Message d'origine- De : DarkStone [mailto:darkst...@163.com] Envoyé : mercredi 30 avril 2014 14:00 À : dev@flex.apache.org Objet : Adobe AIR app installs cross a billion http://blogs.adobe.com/flashplayer/2014/04/air-app-installs-cross-a-billion.html -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Adobe-AIR-app-installs-cross-a-billion-tp37350.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [VOTE] Apache Flex SDK 4.12.1 RC2
+1 (Binding) Win7 64 - FR - Java 1.6 Checked MD5 = OK Manual build of SDK from source = OK ( rsls are ok) Tested SDK in FB 4.7 on large desktop Flex app = OK Tested SDK in IDEA 13.1 on small mobile AIR app = OK __ One minor issue in the release notes: FLEX-33948 Add touch behaviour to spark DropDownList classes = the ticket is still open. implementation attempts were not satisfactory, and have not been committed. Also, I find that the release notes do not describe accurately enough what's in the release (eg. extended queries), and going to JIRA to understand what was done isn't better. I suggest that we add a page (either in the web site or in the wiki) to describe in detail the various features. What do you think? Maurice On Mon, Apr 28, 2014 at 3:41 AM, Alex Harui aha...@adobe.com wrote: Hi, This is a Apache Flex 4.12.1 release candidate 2. Please see the RELEASE_NOTES and the README. There is a known bug in Adobe Flash Builder 4.6 and 4.7 that causes a issue when creating new applications. Adobe has provided a work around for FB 4.7 but not for 4.6. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/flex/sdk/4.12.1/rc1/ Before voting please review the section,What are the ASF requirements on approving a release?, at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - MD5 and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - That you can compile from source package - That the SDK can be used in your IDE of choice - That the SDK can be used to make a mobile, desktop and browser application When testing please check the md5 and asc files and make sure that the source can be compiled. Please vote to approve this release: +1 Approve the release -1 Veto the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes If you find an issue with the release that's a show stopper please don't hold off voting -1. If someone votes -1 please continue testing we want to try and catch as many issues as we can and cut down on the number of release candidates. Remember existing voters can change their vote during the voting process. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested the SDK with. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Alex
RE: Color me confused
Look for the following line in FlowElement: Line 574: // // Begin TLFFormat Related code // include ../formats/TextLayoutFormatInc.as Maurice -Message d'origine- De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : lundi 28 avril 2014 13:47 À : dev Objet : Color me confused I'm trying to add some properties to TextLayoutFormat for tables. I added the properties to ITextLayoutFormat and TextLayoutFormat. Great. Problem is, I get errors that the properties are not implemented in FlowElement and all its subclasses. Okay. That makes sense, because FlowElement implements ITextLayoutFormat. The odd thing, is that there's a whole slew of properties that FlowElement does NOT implement. (such as columnBreakBefore, columnBreakAfter, containerBreakBefore, color, etc. etc.) Why is there no compile error for almost all the TLF properties? Harbs
RE: Next Donation from Adobe
Thanks Alex (and Adobe). Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : samedi 26 avril 2014 06:28 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : samedi 26 avril 2014 21:39 À : dev@flex.apache.org Objet : RE: Next Donation from Adobe Another point, at the moment I'm integrating it to make it work with our compiler and the fixes I pushed before but the donated version uses the Flacon AST Classes to evaluate expresions, so, I wonder, once Flacon will be completed we could switch back to its classes or we don't need to wait ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right
RE: Next Donation from Adobe
Understood. In this case, it would be nice to get the license to use the improved ASDOC tools ( the ones that generate searchable classes etc...) Like in: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/ Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : samedi 26 avril 2014 23:51 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe On 4/26/14 12:45 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? It is the term we use for 'granting a license to Apache'. -Alex
RE: [DISCUSS] Release Apache Flex SDK 4.12.1 RC1
Thanks Alex for this release I will test it this week-end. -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 25 avril 2014 15:17 À : dev@flex.apache.org Objet : [DISCUSS] Release Apache Flex SDK 4.12.1 RC1 This is the discussion thread. If you are going to use the Installer to test the binaries, please use the Installer 3.0 RC at: https://dist.apache.org/repos/dist/dev/flex/installer/3.0/rc7/binaries/ Thanks, -Alex
RE: Question about mobile StageText pool
Thanks Alex for looking into it. The only thing I wondered is if savedStageText is guaranteed to get cleaned up. Yes it is. savedStageText will be disposed by the timer-based shrinkPool if the pool exceeds its reserve limit, so its OS native resources are freed, and it will be removed from the pool. However, the StageText empty instance will still be referenced by its ScrollableStageText owner, and will be GC'ed with it. I don't think this is an issue, as the StageText object is small compared to SST ( ST=240 bytes per instance, SST=1300 bytes per instance). Plus, mobile Flex default behavior enforces re-allocation of Views (to save memory), so this should not happen too often. We could fix this by storing savedStageText in a single-entry weak dictionary, but is it worth it ? Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 24 avril 2014 08:59 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool I looked a quick look at the commit email. I'll take a look with a real diff tool tomorrow. The only thing I wondered is if savedStageText is guaranteed to get cleaned up. If this holds up and the builds machine is working, I'll get that drop down list patch in, sync up the release branch and cut an RC. -Alex On 4/23/14 4:45 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I have just committed a fix for this issue, based on the alternative option: - removed both StageText = ScrollableStageText and ScrollableStageText = StageText maps from StageTextPool - SST maintains a reference to its latest StageText , so the maps are not needed anymore - added some sanity checks so that savedStageText cannot be used if it has been disposed by the cyclical purge, or reused by another TextInput. I did two tests with both persistent TI container (same instance added/removed), and non-persistent. In both cases, GC is done properly (in the profiler) CheckinTests and Mustella Mobile/TextInput test pass. So it's looking good to me. Can someone please review the changes, in case I missed something: Diff: http://git-wip-us.apache.org/repos/asf/flex-sdk/diff/36cece0d Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mercredi 23 avril 2014 02:12 À : dev@flex.apache.org Objet : RE: Question about mobile StageText pool I'm surprised that each skin instance doesn't have its own ScrollableStageText. I would think only the StageText instances are pooled. Actually, this is the case: only StageText are cached. SST acts as a *key* in the reverse dictionary (SST = ST). Stage text is released (and put into the cache) when SST is removed from the stage. If the same SST is added back to the stage, and it's ST is still in the cache, then it gets the same ST instance. That's why a map SST to ST is needed. I think you also have the option of making the back referencing pool a weak reference dictionary. It's already using weak keys: private var map_StyleableStageText_to_StageText:Dictionary = new Dictionary(true); private var map_StageText_to_StyleableStageText:Dictionary = new Dictionary(true); It's worse than what I thought: I replaced all the event listeners to use weak references, still does not work. This is because each SST instance that is used as a key in the pool reverse map is still referencing: - TextInputSkin (in styleName, parent, owner, automationParent, automationOwner) - TitleWindowSkin (in document, parentDocument)... - probably other referenced I didn't see ... So it's locking them (TextInputSkin and TitleWindowSkin) in memory. I tried nulling the references when the SST is removed from stage, does not work. I also tried to disable the pool, = the instances are correctly released, so at least we know where the problem is, but this is not an option. I thought about another possibility would be to use the SST itself as a map, instead of a static map (SST = ST) . This could be done as follows: - each SST will have a savedStageText variable, which contains the last StageText instance, when the SST is not on the stage - whenever the SST is put back to stage, if it has a 'savedStageText', it will be used instead of allocating a new SST. - new SST will get a StageText from the pool of unused stage texts (as currently) - we also need a mechanism to avoid having too many savedStageText instances (which would overflow the OS memory). Maybe something like a counter I will sleep on it ... Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 19:58 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool I think I understand your description, but I'm surprised that each skin instance doesn't have its own ScrollableStageText. I would think only the StageText instances are pooled. It seems ok to use removeFromStage to cut any references between the StageText
RE: New installer errors
In the Apache Flex installer badge, the download button is disabled: http://flex.apache.org/installer.html Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 24 avril 2014 07:27 À : dev@flex.apache.org Objet : Re: New installer errors I'm going to try to ask in a different way. Watch for a new thread. On 4/23/14 4:29 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Over the last few days and not looking good. Anyone have any idea to what the issue(s) may be and why we getting so many installs failing? There seems to be more issues on windows (permissions, https issue?) or perhaps we just have a few bad mirrors out there (anyway to check this?) or perhaps it reporting failures when it actually works? Flex 4.12 windows 9 success (5 people) 13 failures (5 people) Flex 4.12 osx 1 success 1 failure Flex 4.11 windows 1 failure Flex SDK Nightly windows 4 failures (3 people) Flex JS windows 2 success 2 failures Flex JS mac 3 success 1 failure Have a mail log to dev list button on the log window would be a useful thing I think. Thanks, Justin
RE: Question about mobile StageText pool
I have just committed a fix for this issue, based on the alternative option: - removed both StageText = ScrollableStageText and ScrollableStageText = StageText maps from StageTextPool - SST maintains a reference to its latest StageText , so the maps are not needed anymore - added some sanity checks so that savedStageText cannot be used if it has been disposed by the cyclical purge, or reused by another TextInput. I did two tests with both persistent TI container (same instance added/removed), and non-persistent. In both cases, GC is done properly (in the profiler) CheckinTests and Mustella Mobile/TextInput test pass. So it's looking good to me. Can someone please review the changes, in case I missed something: Diff: http://git-wip-us.apache.org/repos/asf/flex-sdk/diff/36cece0d Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mercredi 23 avril 2014 02:12 À : dev@flex.apache.org Objet : RE: Question about mobile StageText pool I'm surprised that each skin instance doesn't have its own ScrollableStageText. I would think only the StageText instances are pooled. Actually, this is the case: only StageText are cached. SST acts as a *key* in the reverse dictionary (SST = ST). Stage text is released (and put into the cache) when SST is removed from the stage. If the same SST is added back to the stage, and it's ST is still in the cache, then it gets the same ST instance. That's why a map SST to ST is needed. I think you also have the option of making the back referencing pool a weak reference dictionary. It's already using weak keys: private var map_StyleableStageText_to_StageText:Dictionary = new Dictionary(true); private var map_StageText_to_StyleableStageText:Dictionary = new Dictionary(true); It's worse than what I thought: I replaced all the event listeners to use weak references, still does not work. This is because each SST instance that is used as a key in the pool reverse map is still referencing: - TextInputSkin (in styleName, parent, owner, automationParent, automationOwner) - TitleWindowSkin (in document, parentDocument)... - probably other referenced I didn't see ... So it's locking them (TextInputSkin and TitleWindowSkin) in memory. I tried nulling the references when the SST is removed from stage, does not work. I also tried to disable the pool, = the instances are correctly released, so at least we know where the problem is, but this is not an option. I thought about another possibility would be to use the SST itself as a map, instead of a static map (SST = ST) . This could be done as follows: - each SST will have a savedStageText variable, which contains the last StageText instance, when the SST is not on the stage - whenever the SST is put back to stage, if it has a 'savedStageText', it will be used instead of allocating a new SST. - new SST will get a StageText from the pool of unused stage texts (as currently) - we also need a mechanism to avoid having too many savedStageText instances (which would overflow the OS memory). Maybe something like a counter I will sleep on it ... Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 19:58 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool I think I understand your description, but I'm surprised that each skin instance doesn't have its own ScrollableStageText. I would think only the StageText instances are pooled. It seems ok to use removeFromStage to cut any references between the StageText and the ScrollableStageText since a Skin not on the display list has no need for a StageText. I think you also have the option of making the back referencing pool a weak reference dictionary. -Alex On 4/22/14 10:31 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: When I look at SkinnableTextBase.partAdded it looks like it is adding a listener to the 'textDisplay'. I assume that 'textDisplay' isn't a StageText in a pool. If that's true, the SkinnableTextBase.as is correct. I would expect that 'textDisplay' is a StageTextInputSkin and internally it should be adding weak reference listeners to the actual StageText's in the pool. Or are those bad assumptions? It's a little trickier than that, because StageText itself is wrapped in a ScrollableStageText (or StyleableStageText depending on the skin) So SkinnableTextBase.textDisplay is the ScrollableStageText which is a (pooled) wrapper around StageText. And the pool has two static dictionaries ( SST = ST and ST = SST). So seeting the listeners on the SST locks the TI, because the SST are also referenced in the pool dictionary. Makes sense to you? Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 19:20 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool On 4/22/14 10:07 AM, Maurice Amsellem maurice.amsel
Question about mobile StageText pool
Hi team, I have been working on FLEX-34230 (StageText skins prevents garbage collection of component with TextInputs and TextAreas) and it appears that GC is prevented by the internal pool of StageText used in StageText-based skins (precisely in old StyleableStageText and new ScrollableStageText). Apparently, the purpose of this cache pool is to avoid creating a new StageText if one with the same characteristics is already in the pool (and returning that one). Does someone know why this pool has been introduced ? is it to improve performance because StageText allocation is slow ? I mean, maybe if the reason for it is not valid anymore, the easiest way to fix that would be simply to remove the pool, and create a new StageText everytime time one is needed. Maurice
RE: Question about mobile StageText pool
Digging further into TextInput code, I made some curious findings (at least for me): StageText is not GCed because StyleableStageText sets event listeners on changing, change, enter, events etc... when the skin is attached (in TextInputBase partAdded). 2) these event listeners should be removed when the skin is detached and partRemoved is called, but *partRemoved is never called*, = this explains why TI and TI window are not gced, they are locked by SST event listeners, which are themselves locked by the SST pool. Stepping through the code, it appears that detachSkin partRemoved are called only if mx_internal::skinDestructionPolicy is set to auto (it's set to never by default). I made a small desktop testing app, and tested it with SDK 4.12 and even SDK 4.6 = detachSkin partRemoved are never called by default. It seems that this is not a new problem: http://stackoverflow.com/questions/8150934/spark-skinnablecomponent-skindestructionpolicy This is rather weird behavior. Is that expected ? Thoughts? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 22 avril 2014 11:23 À : dev@flex.apache.org Objet : Question about mobile StageText pool Hi team, I have been working on FLEX-34230 (StageText skins prevents garbage collection of component with TextInputs and TextAreas) and it appears that GC is prevented by the internal pool of StageText used in StageText-based skins (precisely in old StyleableStageText and new ScrollableStageText). Apparently, the purpose of this cache pool is to avoid creating a new StageText if one with the same characteristics is already in the pool (and returning that one). Does someone know why this pool has been introduced ? is it to improve performance because StageText allocation is slow ? I mean, maybe if the reason for it is not valid anymore, the easiest way to fix that would be simply to remove the pool, and create a new StageText everytime time one is needed. Maurice
RE: Question about mobile StageText pool
Doing it on removing from stage would not be right in many cases since the
widget could come back on stage later?
I don't know the code well either, and I don't have any definite answer to this
question.
So you are probably right to not detach the skin when the widget is removed
from stage.
On the other hand, the bulk of partAdded/partRemoved various implementations
are about adding / removing event listeners to skin part.
So if it's not called by default, when do you remove the event listeners when
a widget skin is not in use (ie not on stage)?
This is not consistent, and probably confusing also.
I maybe be wrong, but I would expect the listeners should be removed when the
widget and skins are removed from stage ?
WDYT?
Examples :
1) SkinnableTextBase . partRemoved(partName:String,
instance:Object):void
{
super.partRemoved(partName, instance);
if (instance == textDisplay)
{
textDisplayRemoved();
// Stop listening for various events from the IEditableText.
textDisplay.removeEventListener(SelectionEvent.SELECTION_CHANGE,
textDisplay_selectionChangeHandler);
textDisplay.removeEventListener(TextOperationEvent.CHANGING,
textDisplay_changingHandler);
textDisplay.removeEventListener(TextOperationEvent.CHANGE,
textDisplay_changeHandler);
textDisplay.removeEventListener(FlexEvent.ENTER,
textDisplay_enterHandler);
textDisplay.removeEventListener(FlexEvent.VALUE_COMMIT,
textDisplay_valueCommitHandler);
}
if (instance == promptDisplay)
{
var newPromptDisplayProperties:Object = {};
if (BitFlagUtil.isSet(uint(promptDisplayProperties),
PROMPT_TEXT_PROPERTY_FLAG))
{
newPromptDisplayProperties.prompt =
promptDisplay.text;
}
promptDisplayProperties = newPromptDisplayProperties;
}
}
2) TitleWindow.partRemoved(partName:String, instance:Object):void
{
super.partRemoved(partName, instance);
if (instance == moveArea)
moveArea.removeEventListener(MouseEvent.MOUSE_DOWN,
moveArea_mouseDownHandler);
else if (instance == closeButton)
closeButton.removeEventListener(MouseEvent.CLICK,
closeButton_clickHandler);
}
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 22 avril 2014 15:12
À : dev@flex.apache.org
Objet : Re: Question about mobile StageText pool
Don't know this code that well, but when would you trigger detaching of the
skin? Doing it on removing from stage would not be right in many cases since
the widget could come back on stage later.
-Alex
On 4/22/14 4:44 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Digging further into TextInput code, I made some curious findings (at
least for me):
StageText is not GCed because StyleableStageText sets event listeners
on changing, change, enter, events etc... when the skin is attached
(in TextInputBase partAdded).
2) these event listeners should be removed when the skin is detached
and partRemoved is called, but *partRemoved is never called*, = this
explains why TI and TI window are not gced, they are locked by SST
event listeners, which are themselves locked by the SST pool.
Stepping through the code, it appears that detachSkin partRemoved
are called only if mx_internal::skinDestructionPolicy is set to auto
(it's set to never by default).
I made a small desktop testing app, and tested it with SDK 4.12 and
even SDK 4.6 = detachSkin partRemoved are never called by default.
It seems that this is not a new problem:
http://stackoverflow.com/questions/8150934/spark-skinnablecomponent-ski
nde
structionpolicy
This is rather weird behavior. Is that expected ?
Thoughts?
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 22 avril 2014 11:23
À : dev@flex.apache.org
Objet : Question about mobile StageText pool
Hi team,
I have been working on FLEX-34230 (StageText skins prevents garbage
collection of component with TextInputs and TextAreas) and it appears
that GC is prevented by the internal pool of StageText used in
StageText-based skins (precisely in old StyleableStageText and new
ScrollableStageText).
Apparently, the purpose of this cache pool is to avoid creating a new
StageText if one with the same characteristics is already in the pool
(and returning that one).
Does someone know why this pool has been introduced ? is it to improve
performance because StageText allocation is slow ?
I mean, maybe if the reason for it is not valid anymore, the easiest
way to fix that would be simply to remove the pool, and create a new
StageText everytime time one is needed.
Maurice
RE: Question about mobile StageText pool
so detaching skins does not have to be part of the lifecycle.
I agree with that, that's why I was asking about removing listeners, rather
than detaching skins. Is that the same ?
IOW, do you mean that explicitly removing listeners from the skin to the
component shouldn't be part of the component lifecycle, and all rely on GC ?
Isn't the solution as simple as using weak reference listeners to the
stagetext events?
Yes, it's probably that simple ( I have to check yet).
But the events are not set in the skins, they are set in the component
(SkinnableTextBase.partAdded / partRemoved).
So doing it that way bothers me because the component is not supposed to know
about the internals of the skins (pooling , or whatever).
So setting weak listeners in the component because we KNOW that the skin is
using a pool defeats that principle.
But maybe I am too purist ;-)
WDYT?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 22 avril 2014 18:34
À : dev@flex.apache.org
Objet : Re: Question about mobile StageText pool
I would think that most components do not use a pool of subcomponents, so
detaching skins does not have to be part of the lifecycle. IOW, the component
and its skin and its subcomponents are all available for GC at the time the
last reference to the component is broken. References from the skin back to
the component do not prevent GC in normal situations.
This makes me think the pooling changes the requirements and work to resolve
this issue should be local to the pooling if possible. Isn't the solution as
simple as using weak reference listeners to the stagetext events?
Of course, I could be wrongŠ
-Alex
On 4/22/14 7:00 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Doing it on removing from stage would not be right in many cases
since the widget could come back on stage later?
I don't know the code well either, and I don't have any definite answer
to this question.
So you are probably right to not detach the skin when the widget is
removed from stage.
On the other hand, the bulk of partAdded/partRemoved various
implementations are about adding / removing event listeners to skin part.
So if it's not called by default, when do you remove the event
listeners when a widget skin is not in use (ie not on stage)?
This is not consistent, and probably confusing also.
I maybe be wrong, but I would expect the listeners should be removed
when the widget and skins are removed from stage ?
WDYT?
Examples :
1) SkinnableTextBase . partRemoved(partName:String,
instance:Object):void
{
super.partRemoved(partName, instance);
if (instance == textDisplay)
{
textDisplayRemoved();
// Stop listening for various events from the IEditableText.
textDisplay.removeEventListener(SelectionEvent.SELECTION_CHANGE,
textDisplay_selectionChangeHandler);
textDisplay.removeEventListener(TextOperationEvent.CHANGING,
textDisplay_changingHandler);
textDisplay.removeEventListener(TextOperationEvent.CHANGE,
textDisplay_changeHandler);
textDisplay.removeEventListener(FlexEvent.ENTER,
textDisplay_enterHandler);
textDisplay.removeEventListener(FlexEvent.VALUE_COMMIT,
textDisplay_valueCommitHandler);
}
if (instance == promptDisplay)
{
var newPromptDisplayProperties:Object = {};
if (BitFlagUtil.isSet(uint(promptDisplayProperties),
PROMPT_TEXT_PROPERTY_FLAG))
{
newPromptDisplayProperties.prompt =
promptDisplay.text;
}
promptDisplayProperties = newPromptDisplayProperties;
}
}
2) TitleWindow.partRemoved(partName:String, instance:Object):void
{
super.partRemoved(partName, instance);
if (instance == moveArea)
moveArea.removeEventListener(MouseEvent.MOUSE_DOWN,
moveArea_mouseDownHandler);
else if (instance == closeButton)
closeButton.removeEventListener(MouseEvent.CLICK,
closeButton_clickHandler);
}
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014
15:12 À : dev@flex.apache.org Objet : Re: Question about mobile
StageText pool
Don't know this code that well, but when would you trigger detaching of
the skin? Doing it on removing from stage would not be right in many
cases since the widget could come back on stage later.
-Alex
On 4/22/14 4:44 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
Digging further into TextInput code, I made some curious findings (at
least for me):
StageText is not GCed because StyleableStageText sets event listeners
on changing, change, enter, events etc... when the skin is attached
(in TextInputBase partAdded).
2) these event listeners should be removed when the skin is detached
RE: Question about mobile StageText pool
Never mind my last comment.
I will use an interface such as IProxiedStageTextWrapper, something like
IPooled.
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 22 avril 2014 19:07
À : dev@flex.apache.org
Objet : RE: Question about mobile StageText pool
so detaching skins does not have to be part of the lifecycle.
I agree with that, that's why I was asking about removing listeners, rather
than detaching skins. Is that the same ?
IOW, do you mean that explicitly removing listeners from the skin to the
component shouldn't be part of the component lifecycle, and all rely on GC ?
Isn't the solution as simple as using weak reference listeners to the
stagetext events?
Yes, it's probably that simple ( I have to check yet).
But the events are not set in the skins, they are set in the component
(SkinnableTextBase.partAdded / partRemoved).
So doing it that way bothers me because the component is not supposed to know
about the internals of the skins (pooling , or whatever).
So setting weak listeners in the component because we KNOW that the skin is
using a pool defeats that principle.
But maybe I am too purist ;-)
WDYT?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 18:34 À
: dev@flex.apache.org Objet : Re: Question about mobile StageText pool
I would think that most components do not use a pool of subcomponents, so
detaching skins does not have to be part of the lifecycle. IOW, the component
and its skin and its subcomponents are all available for GC at the time the
last reference to the component is broken. References from the skin back to
the component do not prevent GC in normal situations.
This makes me think the pooling changes the requirements and work to resolve
this issue should be local to the pooling if possible. Isn't the solution as
simple as using weak reference listeners to the stagetext events?
Of course, I could be wrongŠ
-Alex
On 4/22/14 7:00 AM, Maurice Amsellem maurice.amsel...@systar.com wrote:
Doing it on removing from stage would not be right in many cases
since the widget could come back on stage later?
I don't know the code well either, and I don't have any definite answer
to this question.
So you are probably right to not detach the skin when the widget is
removed from stage.
On the other hand, the bulk of partAdded/partRemoved various
implementations are about adding / removing event listeners to skin part.
So if it's not called by default, when do you remove the event
listeners when a widget skin is not in use (ie not on stage)?
This is not consistent, and probably confusing also.
I maybe be wrong, but I would expect the listeners should be removed
when the widget and skins are removed from stage ?
WDYT?
Examples :
1) SkinnableTextBase . partRemoved(partName:String,
instance:Object):void
{
super.partRemoved(partName, instance);
if (instance == textDisplay)
{
textDisplayRemoved();
// Stop listening for various events from the IEditableText.
textDisplay.removeEventListener(SelectionEvent.SELECTION_CHANGE,
textDisplay_selectionChangeHandler);
textDisplay.removeEventListener(TextOperationEvent.CHANGING,
textDisplay_changingHandler);
textDisplay.removeEventListener(TextOperationEvent.CHANGE,
textDisplay_changeHandler);
textDisplay.removeEventListener(FlexEvent.ENTER,
textDisplay_enterHandler);
textDisplay.removeEventListener(FlexEvent.VALUE_COMMIT,
textDisplay_valueCommitHandler);
}
if (instance == promptDisplay)
{
var newPromptDisplayProperties:Object = {};
if (BitFlagUtil.isSet(uint(promptDisplayProperties),
PROMPT_TEXT_PROPERTY_FLAG))
{
newPromptDisplayProperties.prompt =
promptDisplay.text;
}
promptDisplayProperties = newPromptDisplayProperties;
}
}
2) TitleWindow.partRemoved(partName:String, instance:Object):void
{
super.partRemoved(partName, instance);
if (instance == moveArea)
moveArea.removeEventListener(MouseEvent.MOUSE_DOWN,
moveArea_mouseDownHandler);
else if (instance == closeButton)
closeButton.removeEventListener(MouseEvent.CLICK,
closeButton_clickHandler);
}
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014
15:12 À : dev@flex.apache.org Objet : Re: Question about mobile
StageText pool
Don't know this code that well, but when would you trigger detaching of
the skin? Doing it on removing from stage would not be right in many
cases since the widget could come back on stage later.
-Alex
On 4/22/14 4:44 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
Digging further
RE: Question about mobile StageText pool
When I look at SkinnableTextBase.partAdded it looks like it is adding a listener to the 'textDisplay'. I assume that 'textDisplay' isn't a StageText in a pool. If that's true, the SkinnableTextBase.as is correct. I would expect that 'textDisplay' is a StageTextInputSkin and internally it should be adding weak reference listeners to the actual StageText's in the pool. Or are those bad assumptions? It's a little trickier than that, because StageText itself is wrapped in a ScrollableStageText (or StyleableStageText depending on the skin) So SkinnableTextBase.textDisplay is the ScrollableStageText which is a (pooled) wrapper around StageText. And the pool has two static dictionaries ( SST = ST and ST = SST). So seeting the listeners on the SST locks the TI, because the SST are also referenced in the pool dictionary. Makes sense to you? Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 19:20 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool On 4/22/14 10:07 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: so detaching skins does not have to be part of the lifecycle. I agree with that, that's why I was asking about removing listeners, rather than detaching skins. Is that the same ? IOW, do you mean that explicitly removing listeners from the skin to the component shouldn't be part of the component lifecycle, and all rely on GC ? Either way, there is no good event/trigger to use to know when to remove listeners or detach skins so I would not make it part of the lifecycle. Isn't the solution as simple as using weak reference listeners to the stagetext events? Yes, it's probably that simple ( I have to check yet). But the events are not set in the skins, they are set in the component (SkinnableTextBase.partAdded / partRemoved). So doing it that way bothers me because the component is not supposed to know about the internals of the skins (pooling , or whatever). So setting weak listeners in the component because we KNOW that the skin is using a pool defeats that principle. But maybe I am too purist ;-) When I look at SkinnableTextBase.partAdded it looks like it is adding a listener to the 'textDisplay'. I assume that 'textDisplay' isn't a StageText in a pool. If that's true, the SkinnableTextBase.as is correct. I would expect that 'textDisplay' is a StageTextInputSkin and internally it should be adding weak reference listeners to the actual StageText's in the pool. Or are those bad assumptions? -Alex
RE: Question about mobile StageText pool
I'm surprised that each skin instance doesn't have its own ScrollableStageText. I would think only the StageText instances are pooled. Actually, this is the case: only StageText are cached. SST acts as a *key* in the reverse dictionary (SST = ST). Stage text is released (and put into the cache) when SST is removed from the stage. If the same SST is added back to the stage, and it's ST is still in the cache, then it gets the same ST instance. That's why a map SST to ST is needed. I think you also have the option of making the back referencing pool a weak reference dictionary. It's already using weak keys: private var map_StyleableStageText_to_StageText:Dictionary = new Dictionary(true); private var map_StageText_to_StyleableStageText:Dictionary = new Dictionary(true); It's worse than what I thought: I replaced all the event listeners to use weak references, still does not work. This is because each SST instance that is used as a key in the pool reverse map is still referencing: - TextInputSkin (in styleName, parent, owner, automationParent, automationOwner) - TitleWindowSkin (in document, parentDocument)... - probably other referenced I didn't see ... So it's locking them (TextInputSkin and TitleWindowSkin) in memory. I tried nulling the references when the SST is removed from stage, does not work. I also tried to disable the pool, = the instances are correctly released, so at least we know where the problem is, but this is not an option. I thought about another possibility would be to use the SST itself as a map, instead of a static map (SST = ST) . This could be done as follows: - each SST will have a savedStageText variable, which contains the last StageText instance, when the SST is not on the stage - whenever the SST is put back to stage, if it has a 'savedStageText', it will be used instead of allocating a new SST. - new SST will get a StageText from the pool of unused stage texts (as currently) - we also need a mechanism to avoid having too many savedStageText instances (which would overflow the OS memory). Maybe something like a counter I will sleep on it ... Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 19:58 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool I think I understand your description, but I'm surprised that each skin instance doesn't have its own ScrollableStageText. I would think only the StageText instances are pooled. It seems ok to use removeFromStage to cut any references between the StageText and the ScrollableStageText since a Skin not on the display list has no need for a StageText. I think you also have the option of making the back referencing pool a weak reference dictionary. -Alex On 4/22/14 10:31 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: When I look at SkinnableTextBase.partAdded it looks like it is adding a listener to the 'textDisplay'. I assume that 'textDisplay' isn't a StageText in a pool. If that's true, the SkinnableTextBase.as is correct. I would expect that 'textDisplay' is a StageTextInputSkin and internally it should be adding weak reference listeners to the actual StageText's in the pool. Or are those bad assumptions? It's a little trickier than that, because StageText itself is wrapped in a ScrollableStageText (or StyleableStageText depending on the skin) So SkinnableTextBase.textDisplay is the ScrollableStageText which is a (pooled) wrapper around StageText. And the pool has two static dictionaries ( SST = ST and ST = SST). So seeting the listeners on the SST locks the TI, because the SST are also referenced in the pool dictionary. Makes sense to you? Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 22 avril 2014 19:20 À : dev@flex.apache.org Objet : Re: Question about mobile StageText pool On 4/22/14 10:07 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: so detaching skins does not have to be part of the lifecycle. I agree with that, that's why I was asking about removing listeners, rather than detaching skins. Is that the same ? IOW, do you mean that explicitly removing listeners from the skin to the component shouldn't be part of the component lifecycle, and all rely on GC ? Either way, there is no good event/trigger to use to know when to remove listeners or detach skins so I would not make it part of the lifecycle. Isn't the solution as simple as using weak reference listeners to the stagetext events? Yes, it's probably that simple ( I have to check yet). But the events are not set in the skins, they are set in the component (SkinnableTextBase.partAdded / partRemoved). So doing it that way bothers me because the component is not supposed to know about the internals of the skins (pooling , or whatever). So setting weak listeners in the component because we KNOW that the skin is using a pool defeats that principle
RE:4.12.1
Yes, I did the fix but not committed yet, as I want to fix the GC issue as well De : Alex Harui [aha...@adobe.com] Envoyé : lundi 21 avril 2014 09:02 À : dev@flex.apache.org Objet : Re: 4.12.1 I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218
RE: 4.12.1
Yes, I intend to take over Lee on this ticket, but not soon. If someone else would like to work on it before I do, no problem for me. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 avril 2014 14:46 À : dev@flex.apache.org Objet : Re: 4.12.1 https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
RE: 4.12.1
Is there anything else you want to get into 4.12.1? I am working on the GC issue (FLEX-34230) Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 21 avril 2014 23:31 À : dev@flex.apache.org Objet : Re: 4.12.1 OK, I'll look into it. I just saw a commit from you. Is there anything else you want to get into 4.12.1? -Alex On 4/21/14 2:21 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Yes, I intend to take over Lee on this ticket, but not soon. If someone else would like to work on it before I do, no problem for me. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : lundi 21 avril 2014 14:46 À : dev@flex.apache.org Objet : Re: 4.12.1 https://issues.apache.org/jira/browse/FLEX-33948 please On 21/04/2014 08:02, Alex Harui wrote: I'm getting ready to try my hand at 4.12.1 release candidates. I will sync the develop branch into the release4.12.0 and build from there. Does anybody have anything they want to get in before I do this? Maurice did you have one more stage text fix? Thanks, -Alex On 4/10/14 11:44 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218 -- Lee Burrows ActionScripter
RE:[VOTE] Accept Adobe Donation
+1 De : Alex Harui [aha...@adobe.com] Envoyé : vendredi 18 avril 2014 00:32 À : dev@flex.apache.org Objet : [VOTE] Accept Adobe Donation Please vote to accept the donation of the following Flex-related code and documentation from Adobe Systems, Inc. The vote will be open for at least 72 hours. Thanks, -Alex In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuil der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklist .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tric ks-pt4.html http://www.adobe.com/devnet/flex/articles/flex4_skinning.html http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html http://www.adobe.com/devnet/flex/articles/flex4_effects_pt1.html FlexPMD is currently on Open@Adobe here: http://sourceforge.net/adobe/flexpmd/home/Home/ The Mobile Trader demo application is described here: http://www.adobe.com/devnet/flex/samples/mobile-trader-application.html And here: http://coenraets.org/blog/2011/03/flex-on-the-ipad/ The XML merge utility is a small set of files that should have been in the BlazeDS donation Squiggly is described here: http://labs.adobe.com/technologies/squiggly/ Tour De Flex is described here: http://www.adobe.com/devnet/flex/tourdeflex.html
RE: Updating documentation about the scrolling stage text issue
Would you mind doing a blog post on the ASF Flex blog about this? You can give an overview of the issue and describe how it has been fixed now. We can highlight the fact that the info in the link in question [1] is stale. I will do with pleasure (my first blog post ;-) ). Besides, it would be nice to have a description on the web site on apache SDK novelties. I will work on that when I have again some available time. Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : mercredi 16 avril 2014 20:13 À : dev@flex.apache.org Objet : Updating documentation about the scrolling stage text issue (Moving to dev) On Apr 16, 2014 10:37 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I really wish there was a way to remove the stale information on that page. I agree. Flex is in a sort of schizophrenic situation. So let's take the good side of it, and be happy that at least this kind of documentation exists, even if it's not 100% accurate. PS: even if this was possible, how long and how much people would it take to review all the doc/blogs on Flex and make sure everything is up to date with SDK 4.12 ;-) Maurice The problem is that this issue was always seen as a major one. The fact that this has been fixed needs to be widely published. Would you mind doing a blog post on the ASF Flex blog about this? You can give an overview of the issue and describe how it has been fixed now. We can highlight the fact that the info in the link in question [1] is stale. Thanks, Om [1] http://help.adobe.com/en_US/flex/mobileapps/WS82181550ec4a666a39bafe0312d9a274c00-8000.html#WSc71dc4a5c6f1e0e0-1ee7fed313283418436-7ffe
RE: [LAZY] Apache Flex and 360|Flex shirts
+1 for me too. -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 15 avril 2014 09:47 À : dev@flex.apache.org; paul.hasti...@gmail.com Objet : AW: [LAZY] Apache Flex and 360|Flex shirts +1 From me (For the T-Shirts ... havent quite gotten through all the +posts yet) ;-) Chris Von: Paul Hastings paul.hasti...@gmail.com Gesendet: Dienstag, 15. April 2014 09:26 An: Alex Harui; dev@flex.apache.org Betreff: Re: [LAZY] Apache Flex and 360|Flex shirts On 4/15/2014 11:17 AM, Alex Harui wrote: So, to tie all this back to swag (and thongs?), if you think it will benefit the community of Flex and/or the ASF, feel free to put your own money into it, or start taking up a collection. Adobe used to do some things like this for fun and to add to the buzz, but they knew/hoped that it would increase revenue. The ASF cannot do that. But you can. so in the case of flex thongs, any tom, dick or harry could just put something up on that cafepress site have 10% of sales donated to apache? no need for any official ok, etc?
RE: 4.12.1
I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. Yes, I volunteered, but in the meantime, I got committed to a critical delivery to be scheduled early May (that's why I am not very active on a.o at the moment). So if the work on 4.12.1 can wait until after that, I will be happy to keep my promise, If it can't wait, someone else can do it as you suggest. Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 11 avril 2014 00:23 À : dev@flex.apache.org Objet : 4.12.1 I'm hopeful we'll approve a FlexJS soon and folks wanting to use an installer for FlexJS need to use InstallApacheFlex 3.0 which has enough votes to release, but because it will cause a locale issue with 4.12.0, we've agreed to delay officially releasing the Installer until 4.12.1 is released. I would definitely like to get FlexJS out soon so we can generate some buzz and hopefully get a few more folks to join us at 360|Flex. So: 1) Should we close the vote on Installer 3.0 and post it to the release server and just not announce it or make the switch that auto-upgrades the Installer? One potential problem is that if folks then use that installer to install a regular SDK they may hit this locale issue, although several folks have used the installer in other locales and did not hit this issue. 2) what else do we want to fix in 4.12.1? I know Maurice sort of volunteered to the the RM, but maybe someone else should just cut an RC for 4.12.1. I'm thinking we should put the try/catch blocks back in DataGrid/ADG itemToLabel as described in [1]. I think there is one more I saw but I can't find it right now. Any others? -Alex [1] https://issues.apache.org/jira/browse/FLEX-34218
RE: Changes to Mavenizer and Flexmojos to allow deploying Flex SDKs to maven central
No objection from me
Maurice
-Message d'origine-
De : carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] De la part de
Carlos Rovira
Envoyé : mardi 8 avril 2014 00:20
À : dev@flex.apache.org
Objet : Re: Changes to Mavenizer and Flexmojos to allow deploying Flex SDKs to
maven central
sounds good! :)
+1 as well!
C.
2014-04-08 0:12 GMT+02:00 OmPrakash Muppirala bigosma...@gmail.com:
Sounds like a plan!
+1
Thanks,
Om
On Mon, Apr 7, 2014 at 2:28 PM, Christofer Dutz
christofer.d...@c-ware.dewrote:
Hi Guys,
I'm currently sitting at the ApacheCon with Alex and weh ad a long
discussion on how we could make it possible to release Flex SDKs to
Maven Central. We have come up with a solution all should be happy with.
The core of this would be to strip out any dependency to
playerglobal and airglobal and to introduce new dependencies in
GroupId org.apache.flex.thirdparty which are called
flashplayer.swc and airruntime.swc which simply contains a 1
byte dummy swc which maven automatically uses.
In flexmojos I would add a new mojo in the prepare phase of maven
which checks which version of flashplayer.swc or airruntime.swc is
referenced
and
check if
com.adobe.flashplayer.framework:playerglobal:{playerVersion}:swc
exists. I it doesn't it outputs the license agreement and asks the
user
to
accept this. If he acccepts, the file is downloaded and deployed to
com.adobe.flashplayer.framework:playerglobal:{playerVersion}:swc
in the users local maven repository. As a last step the mojo adds a
dependency
to
the build and coninues as usual.
With these changes, we should be able and allowed to publish Apache
Flex SDKs to maven central.
If you have objections ... object fast as I'm going to start working
on this right away ;-)
Chris
--
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: Docs on TLF composition?
This one maybe ? http://help.adobe.com/en_US/as3/dev/WSb2ba3b1aad8a27b0-1b8898a412218ad3df9-8000.html -Message d'origine- De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : dimanche 6 avril 2014 12:55 À : dev Objet : Docs on TLF composition? While working on TLF, I constantly forget the finer points of the composition flow. It's highly inefficient to constantly step through the code to figure out exactly what happens when and by what. I'm thinking of putting together a doc which specifies the flow and how all the classes work together. Before I do this, I'm wondering if anyone knows of any documentation explaining the architecture. Harbs
RE: Third-party tools / solutions on Apache Flex website
Anyone has objections to add Flexicious in a new Component Library section in 3rd-party? Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mercredi 2 avril 2014 04:49 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Sure: Flexicious provides custom components for Flex and Air developers. Our products include Flexicious Classic, Advanced and Spark, which are extensions to the Flex SDK DataGrid, AdvancedDataGrid and Spark DataGrid components, as well as Flexicious Ultimate DataGrid and Flexicious Data Visualization Dashboard Framework which includes Portal, Charts, Gauges, TreeMaps, Calendar/Scheduler and more. More details here : http://www.flexicious.com/Home/Products On Tue, Apr 1, 2014 at 5:40 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Sorry, rather 2~3 lines of text (to be fair with others). Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 1 avril 2014 23:40 À : dev@flex.apache.org Objet : RE: Third-party tools / solutions on Apache Flex website IMO, Flexicious does not fit in any of the existing sections. It probably falls in a new section Components Library . But then, there are a few other component libs that would deserve to be included as well (eg. Elixir, etc...). I would say, first in, first served. Can you please provide the content you would want to be included (3 ~ 5 lines paragraph) . Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mardi 1 avril 2014 23:20 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Hope its not too tacky for us to request to be listed on this page? About us : http://flexicious.com/Home/AboutUs Our products: http://flexicious.com/Home/Products http://flexicious.com/Home/Dashboard http://flexicious.com/Home/Ultimate On Tue, Apr 1, 2014 at 5:07 PM, piotrz piotrzarzyck...@gmail.com wrote: Thanks Maurice I will do this soon. :) Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-too ls -solutions-on-Apache-Flex-website-tp36116p36578.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: FlexUnit Tutorials
Once I finish converting the site to the CMS, please do add the IntelliJ tutorial -- that would actually be really useful for me as well :) I will do. Note that FlexUnit for IntelliJ has comprehensive description in IDEA online help already ( search: Testing ActionScript and Flex Application in online help), So there is no point IMO to replicate this in the tutorial. So I will rather put it as a step by step tutorial + pointers to the online documentation. Maurice -Message d'origine- De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Envoyé : mercredi 2 avril 2014 01:53 À : dev@flex.apache.org Objet : Re: FlexUnit Tutorials I can't take credit for the verbiage -- that came from the folks at DigitalPrimates. The version on the main site is not up to date. Some pushes were snuck into the main site when the 3rd party community pages went online. The Intro, 1st, 2nd, and 3rd unit have been converted to the CMS, but the others haven't. I still need to play with the bullets and their formatting. Once I finish converting the site to the CMS, please do add the IntelliJ tutorial -- that would actually be really useful for me as well :) -Nick On Tue, Apr 1, 2014 at 6:53 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi Nick, it's also on flex.a.o (because I published to add third-party section). http://flex.apache.org/flexunit/tutorial/ -Message d'origine- De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Envoyé : mardi 1 avril 2014 23:49 À : dev@flex.apache.org Objet : FlexUnit Tutorials Hey Everybody, In anticiaption of FlexUnit becoming an official release, I've been working on converting the old FlexUnit tutorial previously available at http://docs.flexunit.org to be used within our website and CMS. Wanted to see if a few of you could take a peek at http://flex.staging.apache.org/flexunit/tutorial/ and verify that the first three units are in a usable manner. If I get feedback that they are, then I'll run through the rest of the units and finish converting that content in the same manner. Thanks! -Nick
RE: Third-party tools / solutions on Apache Flex website
done -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mercredi 2 avril 2014 04:49 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Sure: Flexicious provides custom components for Flex and Air developers. Our products include Flexicious Classic, Advanced and Spark, which are extensions to the Flex SDK DataGrid, AdvancedDataGrid and Spark DataGrid components, as well as Flexicious Ultimate DataGrid and Flexicious Data Visualization Dashboard Framework which includes Portal, Charts, Gauges, TreeMaps, Calendar/Scheduler and more. More details here : http://www.flexicious.com/Home/Products On Tue, Apr 1, 2014 at 5:40 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Sorry, rather 2~3 lines of text (to be fair with others). Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 1 avril 2014 23:40 À : dev@flex.apache.org Objet : RE: Third-party tools / solutions on Apache Flex website IMO, Flexicious does not fit in any of the existing sections. It probably falls in a new section Components Library . But then, there are a few other component libs that would deserve to be included as well (eg. Elixir, etc...). I would say, first in, first served. Can you please provide the content you would want to be included (3 ~ 5 lines paragraph) . Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mardi 1 avril 2014 23:20 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Hope its not too tacky for us to request to be listed on this page? About us : http://flexicious.com/Home/AboutUs Our products: http://flexicious.com/Home/Products http://flexicious.com/Home/Dashboard http://flexicious.com/Home/Ultimate On Tue, Apr 1, 2014 at 5:07 PM, piotrz piotrzarzyck...@gmail.com wrote: Thanks Maurice I will do this soon. :) Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-too ls -solutions-on-Apache-Flex-website-tp36116p36578.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: Third-party tools / solutions on Apache Flex website
Published. Note: the testing section is not complete IMO. it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner]. Parsley would deserver a better description. Otherwise, great stuff. Maurice De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : mardi 1 avril 2014 11:41 À : dev@flex.apache.org Cc : Maurice Amsellem Objet : Re: Third-party tools / solutions on Apache Flex website Done: FLEX-34199https://issues.apache.org/jira/browse/FLEX-34199. Franck. 2014-04-01 6:09 GMT+02:00 Alex Harui aha...@adobe.commailto:aha...@adobe.com: For record keeping purposes please submit the content in a jira issue. Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com wrote: Anyway: can somebody who knows the website publication process do it for me? I can do it. However, I wasn't following this thread, so is the team ok regarding the content ad location to publish? If so, send me the content, I will format it, review it and get it published. Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 16:34 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website The new page is just a modification of an existing Apache Flex page, it follows the look feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use). Anyway: can somebody who knows the website publication process do it for me? Franck. 2014-03-31 15:26 GMT+02:00 Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com: I agree this should be a regular page. However, the web site is not that easy to modify ( CMS content and two-phase publication) + you need access to svn Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 14:27 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the About Flex or Community section (your call). Can you grant me a (temporary) write access to the website? Where should I put this new page? Franck. 2014-03-31 13:53 GMT+02:00 Justin Mclean jus...@classsoftware.commailto:jus...@classsoftware.com: HI, Any chance to get this page published anytime soon (with Andrew's modifications applied)? You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way. Thanks, Justin
RE: Third-party tools / solutions on Apache Flex website
I spent some time trying to figure out why the page was empty except the title. Finally, it was because of ANSI encoding. I changed it to UTF8, and it fixed it. The CMS system does not support ANSI, but you have to know it :) Maurice De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : mardi 1 avril 2014 13:55 À : Maurice Amsellem Cc : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Maurice! That was fast ;) Note: the testing section is not complete IMO. it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner]. Parsley would deserver a better description. Well, you're free to modify the page as you want. Franck. 2014-04-01 13:48 GMT+02:00 Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com: Published. Note: the testing section is not complete IMO. it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner]. Parsley would deserver a better description. Otherwise, great stuff. Maurice De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : mardi 1 avril 2014 11:41 À : dev@flex.apache.orgmailto:dev@flex.apache.org Cc : Maurice Amsellem Objet : Re: Third-party tools / solutions on Apache Flex website Done: FLEX-34199https://issues.apache.org/jira/browse/FLEX-34199. Franck. 2014-04-01 6:09 GMT+02:00 Alex Harui aha...@adobe.commailto:aha...@adobe.com: For record keeping purposes please submit the content in a jira issue. Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com wrote: Anyway: can somebody who knows the website publication process do it for me? I can do it. However, I wasn't following this thread, so is the team ok regarding the content ad location to publish? If so, send me the content, I will format it, review it and get it published. Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 16:34 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website The new page is just a modification of an existing Apache Flex page, it follows the look feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use). Anyway: can somebody who knows the website publication process do it for me? Franck. 2014-03-31 15:26 GMT+02:00 Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com: I agree this should be a regular page. However, the web site is not that easy to modify ( CMS content and two-phase publication) + you need access to svn Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 14:27 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the About Flex or Community section (your call). Can you grant me a (temporary) write access to the website? Where should I put this new page? Franck. 2014-03-31 13:53 GMT+02:00 Justin Mclean jus...@classsoftware.commailto:jus...@classsoftware.com: HI, Any chance to get this page published anytime soon (with Andrew's modifications applied)? You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way. Thanks, Justin
RE: Third-party tools / solutions on Apache Flex website
Well, you're free to modify the page as you want. I have extended the description on Parsley. Maurice De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : mardi 1 avril 2014 13:55 À : Maurice Amsellem Cc : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Maurice! That was fast ;) Note: the testing section is not complete IMO. it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner]. Parsley would deserver a better description. Well, you're free to modify the page as you want. Franck. 2014-04-01 13:48 GMT+02:00 Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com: Published. Note: the testing section is not complete IMO. it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner]. Parsley would deserver a better description. Otherwise, great stuff. Maurice De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : mardi 1 avril 2014 11:41 À : dev@flex.apache.orgmailto:dev@flex.apache.org Cc : Maurice Amsellem Objet : Re: Third-party tools / solutions on Apache Flex website Done: FLEX-34199https://issues.apache.org/jira/browse/FLEX-34199. Franck. 2014-04-01 6:09 GMT+02:00 Alex Harui aha...@adobe.commailto:aha...@adobe.com: For record keeping purposes please submit the content in a jira issue. Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com wrote: Anyway: can somebody who knows the website publication process do it for me? I can do it. However, I wasn't following this thread, so is the team ok regarding the content ad location to publish? If so, send me the content, I will format it, review it and get it published. Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 16:34 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website The new page is just a modification of an existing Apache Flex page, it follows the look feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use). Anyway: can somebody who knows the website publication process do it for me? Franck. 2014-03-31 15:26 GMT+02:00 Maurice Amsellem maurice.amsel...@systar.commailto:maurice.amsel...@systar.com: I agree this should be a regular page. However, the web site is not that easy to modify ( CMS content and two-phase publication) + you need access to svn Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.commailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 14:27 À : dev@flex.apache.orgmailto:dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the About Flex or Community section (your call). Can you grant me a (temporary) write access to the website? Where should I put this new page? Franck. 2014-03-31 13:53 GMT+02:00 Justin Mclean jus...@classsoftware.commailto:jus...@classsoftware.com: HI, Any chance to get this page published anytime soon (with Andrew's modifications applied)? You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way. Thanks, Justin
RE: Build failed in Jenkins: flex-sdk_release #542
probably in the code that computes the diagonal for the new media query.
I can check that easily, and remove any remaining traces. Would that be enough
?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 1 avril 2014 17:00
À : dev@flex.apache.org
Objet : RE: Build failed in Jenkins: flex-sdk_release #542
My guess is that there is an unintentional trace statement in the code,
probably in the code that computes the diagonal for the new media query.
-Alex
From: Erik de Bruin [e...@ixsoftware.nl]
Sent: Tuesday, April 1, 2014 6:25 AM
To: dev@flex.apache.org
Subject: Re: Build failed in Jenkins: flex-sdk_release #542
Well, OK then. The tinkering of INFRA seems to have solved most of the problems
with the builds on the CI machine. Only the 'release' job fails, and that seems
related to the checkintests, NOT something git/Jenkins...
Anyone have any idea what's up with this?
EdB
On Tue, Apr 1, 2014 at 3:15 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
See https://builds.apache.org/job/flex-sdk_release/542/
--
[...truncated 2319 lines...]
create-config-files:
[copy] Copying 3 files to
https://builds.apache.org/job/flex-sdk_release/ws/ide\flashbuilder\con
fig
expand-config-tokens:
[echo] expanding {airHome} and {playerglobalHome} tokens
main:
post-build:
main:
[echo] ant main target completed on 04/01/2014 02:12:23 PM
frameworks-rsls:
[echo] build.number is 20140401
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\text
Layout.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-config.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/libr
ary.swf
(492215 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/text
Layout_4.13.0.20140401.swf
(342337 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\libr
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\textLayout.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\fram
ework.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-config.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/libr
ary.swf
(798926 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/fram
ework_4.13.0.20140401.swf
(559398 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\libr
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\framework.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\mx\m
x.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-config.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/libr
ary.swf
(811581 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/mx_4
.13.0.20140401.swf
(529810 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\libr
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\mx\mx.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\rpc.
swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-config.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/libr
ary.swf
(299676 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/rpc_
4.13.0.20140401.swf
(209050 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\libr
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\rpc.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\spar
k.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-config.xml
[java]
RE: Build failed in Jenkins: flex-sdk_release #542
I have removed the debug trace statement from mx.utils.MediaQueryParser (line
554).
Sorry for that.
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : mardi 1 avril 2014 17:36
À : dev@flex.apache.org
Objet : Re: Build failed in Jenkins: flex-sdk_release #542
Grep can only find one instance of 'trace' in frameworks/tests/basicTests...
and that is commented out. I'm not at all familiar with the inner workings of
checkintests, should I be looking somewhere else as well?
EdB
On Tue, Apr 1, 2014 at 5:33 PM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
probably in the code that computes the diagonal for the new media query.
I can check that easily, and remove any remaining traces. Would that
be enough ?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 1 avril 2014
17:00 À : dev@flex.apache.org Objet : RE: Build failed in Jenkins:
flex-sdk_release #542
My guess is that there is an unintentional trace statement in the
code, probably in the code that computes the diagonal for the new media query.
-Alex
From: Erik de Bruin [e...@ixsoftware.nl]
Sent: Tuesday, April 1, 2014 6:25 AM
To: dev@flex.apache.org
Subject: Re: Build failed in Jenkins: flex-sdk_release #542
Well, OK then. The tinkering of INFRA seems to have solved most of the
problems with the builds on the CI machine. Only the 'release' job
fails, and that seems related to the checkintests, NOT something
git/Jenkins...
Anyone have any idea what's up with this?
EdB
On Tue, Apr 1, 2014 at 3:15 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
See https://builds.apache.org/job/flex-sdk_release/542/
--
[...truncated 2319 lines...]
create-config-files:
[copy] Copying 3 files to
https://builds.apache.org/job/flex-sdk_release/ws/ide\flashbuilder\c
on
fig
expand-config-tokens:
[echo] expanding {airHome} and {playerglobalHome} tokens
main:
post-build:
main:
[echo] ant main target completed on 04/01/2014 02:12:23 PM
frameworks-rsls:
[echo] build.number is 20140401
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\te
xt
Layout.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/li
br
ary.swf
(492215 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/te
xt
Layout_4.13.0.20140401.swf
(342337 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\li
br
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\text
Layout.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\fr
am
ework.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/li
br
ary.swf
(798926 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/fr
am
ework_4.13.0.20140401.swf
(559398 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\li
br
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\fram
ework.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\mx
\m
x.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/li
br
ary.swf
(811581 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/mx
_4
.13.0.20140401.swf
(529810 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\li
br
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\mx\m
x.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\rpc.
swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https
RE: Build failed in Jenkins: flex-sdk_release #542
It is a good idea to run checkintests before checking in code changes.
Yes, thank you for reminding me.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 1 avril 2014 17:56
À : dev@flex.apache.org
Objet : RE: Build failed in Jenkins: flex-sdk_release #542
Thanks for fixing.
The mustellaresultsparser checks for extraneous trace statements by examining
the flashlog.txt. It won't catch them all, but does catch the ones most folks
would see.
It is a good idea to run checkintests before checking in code changes.
-Alex
From: Maurice Amsellem [maurice.amsel...@systar.com]
Sent: Tuesday, April 1, 2014 8:40 AM
To: dev@flex.apache.org
Subject: RE: Build failed in Jenkins: flex-sdk_release #542
I have removed the debug trace statement from mx.utils.MediaQueryParser (line
554).
Sorry for that.
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 1 avril 2014
17:36 À : dev@flex.apache.org Objet : Re: Build failed in Jenkins:
flex-sdk_release #542
Grep can only find one instance of 'trace' in frameworks/tests/basicTests...
and that is commented out. I'm not at all familiar with the inner workings of
checkintests, should I be looking somewhere else as well?
EdB
On Tue, Apr 1, 2014 at 5:33 PM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
probably in the code that computes the diagonal for the new media query.
I can check that easily, and remove any remaining traces. Would that
be enough ?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 1 avril 2014
17:00 À : dev@flex.apache.org Objet : RE: Build failed in Jenkins:
flex-sdk_release #542
My guess is that there is an unintentional trace statement in the
code, probably in the code that computes the diagonal for the new media query.
-Alex
From: Erik de Bruin [e...@ixsoftware.nl]
Sent: Tuesday, April 1, 2014 6:25 AM
To: dev@flex.apache.org
Subject: Re: Build failed in Jenkins: flex-sdk_release #542
Well, OK then. The tinkering of INFRA seems to have solved most of the
problems with the builds on the CI machine. Only the 'release' job
fails, and that seems related to the checkintests, NOT something
git/Jenkins...
Anyone have any idea what's up with this?
EdB
On Tue, Apr 1, 2014 at 3:15 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
See https://builds.apache.org/job/flex-sdk_release/542/
--
[...truncated 2319 lines...]
create-config-files:
[copy] Copying 3 files to
https://builds.apache.org/job/flex-sdk_release/ws/ide\flashbuilder\c
on
fig
expand-config-tokens:
[echo] expanding {airHome} and {playerglobalHome} tokens
main:
post-build:
main:
[echo] ant main target completed on 04/01/2014 02:12:23 PM
frameworks-rsls:
[echo] build.number is 20140401
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\te
xt
Layout.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/li
br
ary.swf
(492215 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/te
xt
Layout_4.13.0.20140401.swf
(342337 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\li
br
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\text
Layout.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\fr
am
ework.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/li
br
ary.swf
(798926 bytes)
[java]
https://builds.apache.org/job/flex-sdk_release/ws/frameworks/rsls/fr
am
ework_4.13.0.20140401.swf
(559398 bytes)
[delete] Deleting:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls\li
br
ary.swf
[java] Digest information was updated in
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\libs\fram
ework.swc
[unzip] Expanding:
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\libs\mx
\m
x.swc into
https://builds.apache.org/job/flex-sdk_release/ws/frameworks\rsls
[java] Loading configuration file
F:\hudson\hudson-slave\workspace\flex-sdk_release\frameworks\flex-conf
ig.xml
[java]
https
RE: Third-party tools / solutions on Apache Flex website
Piotr, Please feel free to add the section on Fabrication. Maurice -Message d'origine- De : piotrz [mailto:piotrzarzyck...@gmail.com] Envoyé : mardi 1 avril 2014 22:01 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Hi Guys! First of all I would like to say that Third-Party Tools Solutions page looks really great and It was fantastic idea Franck! :) Thanks! @Maurice If it is possible I would like to ask you to add into Framework section couple of words about Fabrication Framework - everything what you need to know about this framework you can find here - https://code.google.com/p/fabrication/ I think it's worth to mention. This utility adds to PureMVC many useful things such as IOC mechanism, new way to handle PureMVC notifications, events and many more... Thanks, Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36575.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: Third-party tools / solutions on Apache Flex website
IMO, Flexicious does not fit in any of the existing sections. It probably falls in a new section Components Library . But then, there are a few other component libs that would deserve to be included as well (eg. Elixir, etc...). I would say, first in, first served. Can you please provide the content you would want to be included (3 ~ 5 lines paragraph) . Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mardi 1 avril 2014 23:20 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Hope its not too tacky for us to request to be listed on this page? About us : http://flexicious.com/Home/AboutUs Our products: http://flexicious.com/Home/Products http://flexicious.com/Home/Dashboard http://flexicious.com/Home/Ultimate On Tue, Apr 1, 2014 at 5:07 PM, piotrz piotrzarzyck...@gmail.com wrote: Thanks Maurice I will do this soon. :) Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36578.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: Third-party tools / solutions on Apache Flex website
Sorry, rather 2~3 lines of text (to be fair with others). Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 1 avril 2014 23:40 À : dev@flex.apache.org Objet : RE: Third-party tools / solutions on Apache Flex website IMO, Flexicious does not fit in any of the existing sections. It probably falls in a new section Components Library . But then, there are a few other component libs that would deserve to be included as well (eg. Elixir, etc...). I would say, first in, first served. Can you please provide the content you would want to be included (3 ~ 5 lines paragraph) . Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mardi 1 avril 2014 23:20 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Hope its not too tacky for us to request to be listed on this page? About us : http://flexicious.com/Home/AboutUs Our products: http://flexicious.com/Home/Products http://flexicious.com/Home/Dashboard http://flexicious.com/Home/Ultimate On Tue, Apr 1, 2014 at 5:07 PM, piotrz piotrzarzyck...@gmail.com wrote: Thanks Maurice I will do this soon. :) Piotr - Apache Flex Committer piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Third-party-tools -solutions-on-Apache-Flex-website-tp36116p36578.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: FlexUnit Tutorials
Hi Nick, it's also on flex.a.o (because I published to add third-party section). http://flex.apache.org/flexunit/tutorial/ -Message d'origine- De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Envoyé : mardi 1 avril 2014 23:49 À : dev@flex.apache.org Objet : FlexUnit Tutorials Hey Everybody, In anticiaption of FlexUnit becoming an official release, I've been working on converting the old FlexUnit tutorial previously available at http://docs.flexunit.org to be used within our website and CMS. Wanted to see if a few of you could take a peek at http://flex.staging.apache.org/flexunit/tutorial/ and verify that the first three units are in a usable manner. If I get feedback that they are, then I'll run through the rest of the units and finish converting that content in the same manner. Thanks! -Nick
RE: FlexUnit Tutorials
Remarks: - missing line between Summaries and Reviewing - Reviewing the Course Prerequisistes should not start with a bullet point - Unit 1 ( Introducing) is fine, except bullet list which are not indented. - Howevever, starting from Unit2, CMS formatting and headers have disappeared. - would be nice to have a word on using FlexUnit in IDEA. Otherwise, that's awesome tutorial! Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mercredi 2 avril 2014 00:54 À : dev@flex.apache.org Objet : RE: FlexUnit Tutorials Hi Nick, it's also on flex.a.o (because I published to add third-party section). http://flex.apache.org/flexunit/tutorial/ -Message d'origine- De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Envoyé : mardi 1 avril 2014 23:49 À : dev@flex.apache.org Objet : FlexUnit Tutorials Hey Everybody, In anticiaption of FlexUnit becoming an official release, I've been working on converting the old FlexUnit tutorial previously available at http://docs.flexunit.org to be used within our website and CMS. Wanted to see if a few of you could take a peek at http://flex.staging.apache.org/flexunit/tutorial/ and verify that the first three units are in a usable manner. If I get feedback that they are, then I'll run through the rest of the units and finish converting that content in the same manner. Thanks! -Nick
RE: Search in Apache Flex Docs?
Thank you Alex. There is another topic related to that, that was raised by someone in the mailing list: how to include/link to flashplayer and air player classes in the a.o asdoc? Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 31 mars 2014 05:44 À : dev@flex.apache.org; n...@joeflash.ca Objet : Re: Search in Apache Flex Docs? On 3/30/14 1:46 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Is it possible that Adobe shares with us their modified asdoc tools ? I'll look into it. -Alex
RE: Time to move the CI builds to a private VM?
Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave Because it's git or because it's windows ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 08:46 À : dev@flex.apache.org Objet : Time to move the CI builds to a private VM? Hi, Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave, isn't it time to start thinking about providing our own VM and running the Jenkins jobs off that? I would gladly donate my Azure VM for this purpose, but as Mustella runs on it - which I don't think we want to lose - we need someone else's VM for this purpose... Om, what is the status of your VM? EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: Time to move the CI builds to a private VM?
I agree, but this is shocking. Do other Apache projects have the same concerns? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 09:22 À : dev@flex.apache.org Objet : Re: Time to move the CI builds to a private VM? I have no idea, but we've been trying to get someone - anyone - from builds@a.o to help us out, but there has hardly been any response from them, and even less action. I think having CI is very important for the project and since Apache seems unable/unwilling to support us with the proper infrastructure, and is turning down (ignoring) any offers to help out, I think it's time we roll our own. EdB On Mon, Mar 31, 2014 at 8:54 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave Because it's git or because it's windows ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 08:46 À : dev@flex.apache.org Objet : Time to move the CI builds to a private VM? Hi, Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave, isn't it time to start thinking about providing our own VM and running the Jenkins jobs off that? I would gladly donate my Azure VM for this purpose, but as Mustella runs on it - which I don't think we want to lose - we need someone else's VM for this purpose... Om, what is the status of your VM? EdB -- 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
RE: Time to move the CI builds to a private VM?
I wasn't part on the project when it started and incubated at the ASF. What did we get from being an ASF project, apart from the Apache brand fame and durability (which I must say, is an important thing) ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 10:02 À : dev@flex.apache.org Objet : Re: Time to move the CI builds to a private VM? Apparently they do. There is this guy Hervé Boutemy, from another project, who is a bit more patient than I am, he is currently again offering to help out INFRA with the proper maintenance of the VMs. He has made the same offer repeatedly over the last few months, initially together with me, but there has never been any response from the people at builds@a.o EdB On Mon, Mar 31, 2014 at 9:33 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I agree, but this is shocking. Do other Apache projects have the same concerns? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 09:22 À : dev@flex.apache.org Objet : Re: Time to move the CI builds to a private VM? I have no idea, but we've been trying to get someone - anyone - from builds@a.o to help us out, but there has hardly been any response from them, and even less action. I think having CI is very important for the project and since Apache seems unable/unwilling to support us with the proper infrastructure, and is turning down (ignoring) any offers to help out, I think it's time we roll our own. EdB On Mon, Mar 31, 2014 at 8:54 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave Because it's git or because it's windows ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 08:46 À : dev@flex.apache.org Objet : Time to move the CI builds to a private VM? Hi, Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave, isn't it time to start thinking about providing our own VM and running the Jenkins jobs off that? I would gladly donate my Azure VM for this purpose, but as Mustella runs on it - which I don't think we want to lose - we need someone else's VM for this purpose... Om, what is the status of your VM? EdB -- 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
RE: Time for refactor? Reworking the annoying private methods
I am not sure of that , but it might be that private methods execute faster
than protected ones (because the resolution can be done at compile time).
So turning every private method to protected might have an impact on
performances.
Needs confirmation from someone who has a deep knowledge on AS3 execution in
the Flash Player.
Maurice
-Message d'origine-
De : Konstantin Elstner [mailto:f...@dashart.de]
Envoyé : lundi 31 mars 2014 13:18
À : dev@flex.apache.org
Objet : Time for refactor? Reworking the annoying private methods
Hi,
for me as Flex developer it is very annoying to find a problem / bug in the
current Flex versions.
In the most case I analyze the problem / bug and then I find the source of
the problem, but I can not integrate a workaround, because the method which is
responsible has a private scope.
Current example:
private function hideScrollBars():void { ... } from spark.components.Scroller.
I waste so much time to create some dirty workarounds around simple private
methods in many components.
So very often, I am asking myself ... why is this method private, it could be
protected and I could create a simple fix.
Also it would more simple to create a patch for bugs, or implement new custom
functions and commit it back to.
So my rhetoric question:
Is is time to restructure / rework and revalidate every as private declared
method and variable in the Flex sources?
All this private usages has a taste for me, like the Adobe guys which initial
created the classes do not completely understand the concept of mx_internal /
private / protected and public scopes ;)
Konstantin
RE: Time for refactor? Reworking the annoying private methods
I forgot about it, thanks.
So private and protected basically the same ( 56 and 57 ms)
Maurice
-Message d'origine-
De : João Fernandes [mailto:joaopedromartinsfernan...@gmail.com]
Envoyé : lundi 31 mars 2014 15:08
À : dev@flex.apache.org
Objet : Re: Time for refactor? Reworking the annoying private methods
When there is doubt regarding performance, Jackson Dunstan probably has the
answer[1] :) I also agree that we should take care of those pesky private
methods case by case.
[1] http://jacksondunstan.com/articles/1820
On 31 March 2014 12:57, Maurice Amsellem maurice.amsel...@systar.comwrote:
I am not sure of that , but it might be that private methods execute
faster than protected ones (because the resolution can be done at
compile time).
So turning every private method to protected might have an impact on
performances.
Needs confirmation from someone who has a deep knowledge on AS3
execution in the Flash Player.
Maurice
-Message d'origine-
De : Konstantin Elstner [mailto:f...@dashart.de] Envoyé : lundi 31
mars 2014 13:18 À : dev@flex.apache.org Objet : Time for refactor?
Reworking the annoying private methods
Hi,
for me as Flex developer it is very annoying to find a problem / bug
in the current Flex versions.
In the most case I analyze the problem / bug and then I find the source
of the problem, but I can not integrate a workaround, because the
method which is responsible has a private scope.
Current example:
private function hideScrollBars():void { ... } from
spark.components.Scroller.
I waste so much time to create some dirty workarounds around simple
private methods in many components.
So very often, I am asking myself ... why is this method private, it
could be protected and I could create a simple fix.
Also it would more simple to create a patch for bugs, or implement new
custom functions and commit it back to.
So my rhetoric question:
Is is time to restructure / rework and revalidate every as private
declared method and variable in the Flex sources?
All this private usages has a taste for me, like the Adobe guys which
initial created the classes do not completely understand the concept
of mx_internal / private / protected and public scopes ;)
Konstantin
--
João Fernandes
RE: Third-party tools / solutions on Apache Flex website
I agree this should be a regular page. However, the web site is not that easy to modify ( CMS content and two-phase publication) + you need access to svn Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 14:27 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the About Flex or Community section (your call). Can you grant me a (temporary) write access to the website? Where should I put this new page? Franck. 2014-03-31 13:53 GMT+02:00 Justin Mclean jus...@classsoftware.com: HI, Any chance to get this page published anytime soon (with Andrew's modifications applied)? You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way. Thanks, Justin
RE: Time to move the CI builds to a private VM?
Thanks Alex. -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 31 mars 2014 16:18 À : dev@flex.apache.org Objet : Re: Time to move the CI builds to a private VM? We got legal protection, JIRA, servers, mailing lists, a process for making decision, and more. Infra is a pain point, especially around Jenkins. I signed up for a VM but never really got it together. If someone has the time to set it up, let me know. -Alex On 3/31/14 1:35 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I wasn't part on the project when it started and incubated at the ASF. What did we get from being an ASF project, apart from the Apache brand fame and durability (which I must say, is an important thing) ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 10:02 À : dev@flex.apache.org Objet : Re: Time to move the CI builds to a private VM? Apparently they do. There is this guy Hervé Boutemy, from another project, who is a bit more patient than I am, he is currently again offering to help out INFRA with the proper maintenance of the VMs. He has made the same offer repeatedly over the last few months, initially together with me, but there has never been any response from the people at builds@a.o EdB On Mon, Mar 31, 2014 at 9:33 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I agree, but this is shocking. Do other Apache projects have the same concerns? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 09:22 À : dev@flex.apache.org Objet : Re: Time to move the CI builds to a private VM? I have no idea, but we've been trying to get someone - anyone - from builds@a.o to help us out, but there has hardly been any response from them, and even less action. I think having CI is very important for the project and since Apache seems unable/unwilling to support us with the proper infrastructure, and is turning down (ignoring) any offers to help out, I think it's time we roll our own. EdB On Mon, Mar 31, 2014 at 8:54 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave Because it's git or because it's windows ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 31 mars 2014 08:46 À : dev@flex.apache.org Objet : Time to move the CI builds to a private VM? Hi, Given the apparently total lack of support from INFRA and builds@a.o for a git based CI process on a Windows slave, isn't it time to start thinking about providing our own VM and running the Jenkins jobs off that? I would gladly donate my Azure VM for this purpose, but as Mustella runs on it - which I don't think we want to lose - we need someone else's VM for this purpose... Om, what is the status of your VM? EdB -- 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
RE: Third-party tools / solutions on Apache Flex website
Anyway: can somebody who knows the website publication process do it for me? I can do it. However, I wasn't following this thread, so is the team ok regarding the content ad location to publish? If so, send me the content, I will format it, review it and get it published. Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 16:34 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website The new page is just a modification of an existing Apache Flex page, it follows the look feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use). Anyway: can somebody who knows the website publication process do it for me? Franck. 2014-03-31 15:26 GMT+02:00 Maurice Amsellem maurice.amsel...@systar.com: I agree this should be a regular page. However, the web site is not that easy to modify ( CMS content and two-phase publication) + you need access to svn Maurice -Message d'origine- De : Franck Wolff [mailto:frawo...@gmail.com] Envoyé : lundi 31 mars 2014 14:27 À : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website Thanks Justin. I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the About Flex or Community section (your call). Can you grant me a (temporary) write access to the website? Where should I put this new page? Franck. 2014-03-31 13:53 GMT+02:00 Justin Mclean jus...@classsoftware.com: HI, Any chance to get this page published anytime soon (with Andrew's modifications applied)? You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way. Thanks, Justin
RE: Strange behavior with setMonth method of Date object
This is because April has only 30 days. 31 of april does not exit. So you should set setDate(1) before doing setMonth(3) Maurice -Message d'origine- De : after24 [mailto:vinc...@after24.net] Envoyé : lundi 31 mars 2014 18:47 À : dev@flex.apache.org Objet : Strange behavior with setMonth method of Date object Hello, I'm facing a strange behavior with the Date object : var myDate:Date = new Date(); myDate.setFullYear(2014); myDate.setMonth(3); trace(myDate); // return Thu May 1 18:31:07 GMT+0200 2014 myDate.setMonth(3); trace(myDate); // return Tue Apr 1 18:31:07 GMT+0200 2014 The returned month is false the first time. This behavior seems to occur only today(Mar 31, 2014), if I change my system date, the two trace statements returns the same date. Is it a flash player bug (the only thing I found on the Adobe bugbase is https://bugbase.adobe.com/index.cfm?event=bugid=2927909 https://bugbase.adobe.com/index.cfm?event=bugid=2927909 ) or am I missing something ? -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Strange-behavior-with-setMonth-method-of-Date-object-tp36525.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: Search in Apache Flex Docs?
Joseph is referring to the appendices section in the ASDOC: https://www.dropbox.com/s/ryp97xyeyns37rb/asdoc_appendices.png Unfortunately, I don't think creating a class called CompilerElement would work well, because it will display the mxml-only tags and props as if it was classes and props, which will add to the confusion IMO. Compare fx:Binding and BindingUtils class for example http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mxml/binding.html http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/binding/utils/BindingUtils.html Extending the asdoc compiler and xlst files to achieve a comparable result is probably too much work, as you say. Is it possible that Adobe shares with us their modified asdoc tools ? Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : dimanche 30 mars 2014 06:47 À : dev@flex.apache.org; n...@joeflash.ca Objet : Re: Search in Apache Flex Docs? Not sure I followed, but sounds like work ;-) Would it be sufficient if someone were to write up a class called CompilerElements.as and put it in the framework? -Alex On 3/29/14 9:46 PM, Joseph Balderson n...@joeflash.ca wrote: It would be useful to see all metadata, compiler directives (like conditinoal compilation), MXML compiler pseudo-properties (like itemCreationPolicy), have a mention in the ASDOCs, somewhere. So that if you're searching them, you don't have to wade through the wiki. The Adobe ASDOCs has two sections in the top left side menu: - Packages - Language Elements - Appendices (The Appendices in the Adobe asdocs have one Flex-specific section: MXML Only Tags -- we could migrate this information to the Apache Flex ASDOCs and/or Wiki.) I would recommend something similar for Apache Flex, only in the following categories: - Packages - Compiler Elements In Compiler Elements, you could have: - Namespaces - MXML language specifications - Compiler Directives - Metadata tags - MXML-only properties - etc. Basically anything that would be found in code not in the class packages, and not a part of the AS3 spec, would be in the second section. You could mention compiler-driven MXML language elements, without getting into lengthy descriptions and examples more suited to a wiki. These pages might lead to wiki pages, much as how the Adobe ASDOCs would lead to help pages with examples elsewhere in the Flex documentation. This would make more sense, since coding in Flex covers not just the class framework, but MXML compiler conventions. Right now the ASDOCs only cover the framework, not the compiler. ___ Joseph Balderson, Flex Flash Platform Developer :: http://joeflash.ca Author, Professional Flex 3 :: http://tinyurl.com/proflex3book Alex Harui wrote: On 3/27/14 7:07 PM, Joseph Balderson n...@joeflash.ca wrote: But it raises the question -- how do we get MXML coding conventions which are not a part of actual classes, but are compiler-interpreted, into the asdocs? Do you want to see it on the classes or is another doc chapter good enough? -Alex
RE: RTL support in mobile apps
This is already the technique used in many places: - TextInput / TextArea: when the text is not in edit mode, displays a bitmap cache, to ensure smooth scrolling - List item renderers (when cacheAsBitmap is set to true, which is the default on mobile, the whole item renderer is cached as a bitmap). But even with that technique, displaying long texts in Lists/ DataGrids using spark Label instead of TextField (which is I think the idea) was very slow. Maybe because of the renderer recycling. It may be worth experimenting more... Maurice -Message d'origine- De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : dimanche 30 mars 2014 19:19 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps Has anyone explored creating cached TLF? Rather than re-composing the text every time it's displayed, the composition could be cached as an image and that would be used rather than the live text. Of course, for this to work, something would have to set a flag to indicate that the text reeds to be recached when the content is changed. On Mar 29, 2014, at 9:30 PM, Maurice Amsellem wrote: Ok, managed to get the font embedded in the mobile app, but still does not display correctly. So I leave it for now, until someone gets a genius idea... Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : samedi 29 mars 2014 18:57 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Is this the right way to do it ? http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c6a9f4512 12b87fe7e87-8000.html Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : samedi 29 mars 2014 18:54 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Thanks Om, That's what I am trying now (embedding the font). Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : samedi 29 mars 2014 18:50 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Might be the font. Did you try embedding the font? Thanks, Om On Mar 29, 2014 6:43 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have completed RTL management on mobile skins. The idea was that all default mobile skins (based on StyleableTextField and ScrollableStageText) display correctly when using RTL text (Arabic/Hebrew) and layoutDirection set to RTL. So I changed StyleableTextField to correct it's matrix and textAlign and it works!! Well, almost :-( I tested it on ADL with default skins = OK: https://www.dropbox.com/s/ee61mpazlgyloof/ADL_RTL_OK.png However, when the same application run on Android or iOS device, the letter order is not inverted as it should be. https://www.dropbox.com/s/rfme0g60xxkne87/android_rtl_ko.png See for example the word in Arabic in the action bar title on both screenshots. I don't understand this difference. This is not stage iOS or Android component (such as StageText), which could have a different behavior on ALD and device. It's plain AIR rendering. So why is it OK on ADL , and KO on the device? Very frustrating... Could it be because of the font used , that wouldn't be the same on ALD (Windows) and device? Or is it an AIR bug because RTL is not supposed to work, although it does.. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 22:36 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps I assume this was a release version and not a debug version? Damn, I fell in the trap again. Thanks for reminding me. I have re-done the tests with release packaging, almost same results: 21- 25 FPS for TextField 1 ~ 4 for spark Label. Either way, I don't think TLF will get out to 25fps. Yes, 15 would have been fine. but 4 fps is really too bad. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. Yes, that was my intention. Crossing fingers that it works. Thanks Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 24 mars 2014 21:56 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps I assume this was a release version and not a debug version? Either way, I don't think TLF will get out to 25fps. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. -Alex On 3/24/14 1:46 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I just did a quick test to compare TLF and TextField on mobile. Basically, replaced StyleableTextField cell renderer on MobileGrid
RE: RTL support in mobile apps
Hi, I have completed RTL management on mobile skins. The idea was that all default mobile skins (based on StyleableTextField and ScrollableStageText) display correctly when using RTL text (Arabic/Hebrew) and layoutDirection set to RTL. So I changed StyleableTextField to correct it's matrix and textAlign and it works!! Well, almost :-( I tested it on ADL with default skins = OK: https://www.dropbox.com/s/ee61mpazlgyloof/ADL_RTL_OK.png However, when the same application run on Android or iOS device, the letter order is not inverted as it should be. https://www.dropbox.com/s/rfme0g60xxkne87/android_rtl_ko.png See for example the word in Arabic in the action bar title on both screenshots. I don't understand this difference. This is not stage iOS or Android component (such as StageText), which could have a different behavior on ALD and device. It's plain AIR rendering. So why is it OK on ADL , and KO on the device? Very frustrating... Could it be because of the font used , that wouldn't be the same on ALD (Windows) and device? Or is it an AIR bug because RTL is not supposed to work, although it does.. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 22:36 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps I assume this was a release version and not a debug version? Damn, I fell in the trap again. Thanks for reminding me. I have re-done the tests with release packaging, almost same results: 21- 25 FPS for TextField 1 ~ 4 for spark Label. Either way, I don't think TLF will get out to 25fps. Yes, 15 would have been fine. but 4 fps is really too bad. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. Yes, that was my intention. Crossing fingers that it works. Thanks Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 24 mars 2014 21:56 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps I assume this was a release version and not a debug version? Either way, I don't think TLF will get out to 25fps. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. -Alex On 3/24/14 1:46 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I just did a quick test to compare TLF and TextField on mobile. Basically, replaced StyleableTextField cell renderer on MobileGrid by spark Label-based renderer. Test results: - iPad 3 (retina) - slow iOS packaging , GPU rendering - Mobile grid with 4 columns of text, and 200 rows StyleableTextField = 25 fps when scrolling Spark Label = 1 to 3 fps when scrolling ( UI is very slow, almost frozen). So of course mobile grid displays a lot of text, including multi-line, but that's where performance is needed, not on button and titles, IMO. I could also have used TextLine, but it does not support multi-line, which TextField does, so it's not equivalent. So for me, spark Label is not good enough on mobile, even on recent devices. I will explore the other track (RTL using TextField). What do you think? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 11:19 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Hi Carlos, 1) It's not proven yet that TLF is fast enough on mobile, especially when there are lots of text to display, such as in lists of datagrid. Plus I have discovered that the old TextField is actually capable to display RTL , but the Flex positioning is broken, so the text does not appear (probably because it was not supposed to work that way). So IMO, the question is still open, and I won't rush into replacing TextField by TLF on mobile. It would be probably much simpler to fix the layout. Right now we need to deal in different ways with TextInput in mobile and browser and this defeat the code once run everywhere. What do you mean? From the SDK developer standpoint, or from the end-user developer stand point ? From the SDK standpoint, the difference is only on the skin, the 'host' component is the same. From the end-user developer, you must use TextInput in both cases, so where's the difference ? The behavior is different, but that's inherent to mobile vs desktop (eg. you don't have softkeyboard or restricted keyboards on desktop). Please explain Maurice -Message d'origine- De : carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] De la part de Carlos Rovira Envoyé : lundi 24 mars 2014 10:54 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps Hi, if there are plans to introduce TLF on mobile TextInput this will change my priorities about change the internals of MaskedTextInput component
RE: RTL support in mobile apps
Thanks Om, That's what I am trying now (embedding the font). Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : samedi 29 mars 2014 18:50 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Might be the font. Did you try embedding the font? Thanks, Om On Mar 29, 2014 6:43 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have completed RTL management on mobile skins. The idea was that all default mobile skins (based on StyleableTextField and ScrollableStageText) display correctly when using RTL text (Arabic/Hebrew) and layoutDirection set to RTL. So I changed StyleableTextField to correct it's matrix and textAlign and it works!! Well, almost :-( I tested it on ADL with default skins = OK: https://www.dropbox.com/s/ee61mpazlgyloof/ADL_RTL_OK.png However, when the same application run on Android or iOS device, the letter order is not inverted as it should be. https://www.dropbox.com/s/rfme0g60xxkne87/android_rtl_ko.png See for example the word in Arabic in the action bar title on both screenshots. I don't understand this difference. This is not stage iOS or Android component (such as StageText), which could have a different behavior on ALD and device. It's plain AIR rendering. So why is it OK on ADL , and KO on the device? Very frustrating... Could it be because of the font used , that wouldn't be the same on ALD (Windows) and device? Or is it an AIR bug because RTL is not supposed to work, although it does.. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 22:36 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps I assume this was a release version and not a debug version? Damn, I fell in the trap again. Thanks for reminding me. I have re-done the tests with release packaging, almost same results: 21- 25 FPS for TextField 1 ~ 4 for spark Label. Either way, I don't think TLF will get out to 25fps. Yes, 15 would have been fine. but 4 fps is really too bad. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. Yes, that was my intention. Crossing fingers that it works. Thanks Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 24 mars 2014 21:56 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps I assume this was a release version and not a debug version? Either way, I don't think TLF will get out to 25fps. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. -Alex On 3/24/14 1:46 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I just did a quick test to compare TLF and TextField on mobile. Basically, replaced StyleableTextField cell renderer on MobileGrid by spark Label-based renderer. Test results: - iPad 3 (retina) - slow iOS packaging , GPU rendering - Mobile grid with 4 columns of text, and 200 rows StyleableTextField = 25 fps when scrolling Spark Label = 1 to 3 fps when scrolling ( UI is very slow, almost frozen). So of course mobile grid displays a lot of text, including multi-line, but that's where performance is needed, not on button and titles, IMO. I could also have used TextLine, but it does not support multi-line, which TextField does, so it's not equivalent. So for me, spark Label is not good enough on mobile, even on recent devices. I will explore the other track (RTL using TextField). What do you think? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 11:19 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Hi Carlos, 1) It's not proven yet that TLF is fast enough on mobile, especially when there are lots of text to display, such as in lists of datagrid. Plus I have discovered that the old TextField is actually capable to display RTL , but the Flex positioning is broken, so the text does not appear (probably because it was not supposed to work that way). So IMO, the question is still open, and I won't rush into replacing TextField by TLF on mobile. It would be probably much simpler to fix the layout. Right now we need to deal in different ways with TextInput in mobile and browser and this defeat the code once run everywhere. What do you mean? From the SDK developer standpoint, or from the end-user developer stand point ? From the SDK standpoint, the difference is only on the skin, the 'host' component is the same. From the end-user developer, you must use TextInput in both cases, so where's the difference
RE: RTL support in mobile apps
Is this the right way to do it ? http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c6a9f451212b87fe7e87-8000.html Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : samedi 29 mars 2014 18:54 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Thanks Om, That's what I am trying now (embedding the font). Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : samedi 29 mars 2014 18:50 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Might be the font. Did you try embedding the font? Thanks, Om On Mar 29, 2014 6:43 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have completed RTL management on mobile skins. The idea was that all default mobile skins (based on StyleableTextField and ScrollableStageText) display correctly when using RTL text (Arabic/Hebrew) and layoutDirection set to RTL. So I changed StyleableTextField to correct it's matrix and textAlign and it works!! Well, almost :-( I tested it on ADL with default skins = OK: https://www.dropbox.com/s/ee61mpazlgyloof/ADL_RTL_OK.png However, when the same application run on Android or iOS device, the letter order is not inverted as it should be. https://www.dropbox.com/s/rfme0g60xxkne87/android_rtl_ko.png See for example the word in Arabic in the action bar title on both screenshots. I don't understand this difference. This is not stage iOS or Android component (such as StageText), which could have a different behavior on ALD and device. It's plain AIR rendering. So why is it OK on ADL , and KO on the device? Very frustrating... Could it be because of the font used , that wouldn't be the same on ALD (Windows) and device? Or is it an AIR bug because RTL is not supposed to work, although it does.. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 22:36 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps I assume this was a release version and not a debug version? Damn, I fell in the trap again. Thanks for reminding me. I have re-done the tests with release packaging, almost same results: 21- 25 FPS for TextField 1 ~ 4 for spark Label. Either way, I don't think TLF will get out to 25fps. Yes, 15 would have been fine. but 4 fps is really too bad. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. Yes, that was my intention. Crossing fingers that it works. Thanks Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 24 mars 2014 21:56 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps I assume this was a release version and not a debug version? Either way, I don't think TLF will get out to 25fps. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. -Alex On 3/24/14 1:46 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I just did a quick test to compare TLF and TextField on mobile. Basically, replaced StyleableTextField cell renderer on MobileGrid by spark Label-based renderer. Test results: - iPad 3 (retina) - slow iOS packaging , GPU rendering - Mobile grid with 4 columns of text, and 200 rows StyleableTextField = 25 fps when scrolling Spark Label = 1 to 3 fps when scrolling ( UI is very slow, almost frozen). So of course mobile grid displays a lot of text, including multi-line, but that's where performance is needed, not on button and titles, IMO. I could also have used TextLine, but it does not support multi-line, which TextField does, so it's not equivalent. So for me, spark Label is not good enough on mobile, even on recent devices. I will explore the other track (RTL using TextField). What do you think? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 11:19 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Hi Carlos, 1) It's not proven yet that TLF is fast enough on mobile, especially when there are lots of text to display, such as in lists of datagrid. Plus I have discovered that the old TextField is actually capable to display RTL , but the Flex positioning is broken, so the text does not appear (probably because it was not supposed to work that way). So IMO, the question is still open, and I won't rush into replacing TextField by TLF on mobile. It would be probably much simpler to fix the layout. Right now we need to deal in different ways with TextInput in mobile and browser and this defeat
RE: flex-sdk_mustella-mobile - Build # 621 - Failure!
Anyway, I have to undo the commit because it does not work. So let's see if it fixes the mustella failure. Maurice De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : samedi 29 mars 2014 19:26 À : dev@flex.apache.org; Maurice Amsellem Objet : Re: flex-sdk_mustella-mobile - Build # 621 - Failure! Any chance this is related to a recent commit? EdB On Sat, Mar 29, 2014 at 6:36 PM, flex.muste...@gmail.commailto:flex.muste...@gmail.com wrote: flex-sdk_mustella-mobile - Build # 621 - Failure: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella-mobile/621/ Changes for Build #621 [maurice.amsellem] FIXED - FLEX-24502 Mobile optimized skins and item renderers don't show text when mirrored [...truncated 12942 lines...] [java] waited 1600 [java] ClobberProcess, it was already null [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] getting directory from the swf file [java] derived directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs [java] Launching: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml -screensize 640x960:640x960 -profile mobileDevice -XscreenDPI 240 Launching: C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] USING directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs [java] time: 12:36:15.118 [java] SCRIPTDONE! 12:36:22.491 [java] GET /ScriptComplete?0 HTTP/1.1 [java] Before Wait loop 12:36:22.491 waiting = 0 [java] After Wait loop 12:36:22.491 waiting = 0 [java] clobberProcess false [java] Total Results so far: 6 [java] waited 1500 [java] ClobberProcess, it was already null [java] removing the xml app file [java] Grab log, do parse = false [java] Grabbing the log from: C:\Users\ApacheFlex\AppData/Roaming\Macromedia/Flash Player/Logs/flashlog.txt to: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.log [java] apollo adj with : C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.swf [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.swf [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java
RE: RTL support in mobile apps
Ok, managed to get the font embedded in the mobile app, but still does not display correctly. So I leave it for now, until someone gets a genius idea... Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : samedi 29 mars 2014 18:57 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Is this the right way to do it ? http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c6a9f451212b87fe7e87-8000.html Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : samedi 29 mars 2014 18:54 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Thanks Om, That's what I am trying now (embedding the font). Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : samedi 29 mars 2014 18:50 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Might be the font. Did you try embedding the font? Thanks, Om On Mar 29, 2014 6:43 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have completed RTL management on mobile skins. The idea was that all default mobile skins (based on StyleableTextField and ScrollableStageText) display correctly when using RTL text (Arabic/Hebrew) and layoutDirection set to RTL. So I changed StyleableTextField to correct it's matrix and textAlign and it works!! Well, almost :-( I tested it on ADL with default skins = OK: https://www.dropbox.com/s/ee61mpazlgyloof/ADL_RTL_OK.png However, when the same application run on Android or iOS device, the letter order is not inverted as it should be. https://www.dropbox.com/s/rfme0g60xxkne87/android_rtl_ko.png See for example the word in Arabic in the action bar title on both screenshots. I don't understand this difference. This is not stage iOS or Android component (such as StageText), which could have a different behavior on ALD and device. It's plain AIR rendering. So why is it OK on ADL , and KO on the device? Very frustrating... Could it be because of the font used , that wouldn't be the same on ALD (Windows) and device? Or is it an AIR bug because RTL is not supposed to work, although it does.. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 22:36 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps I assume this was a release version and not a debug version? Damn, I fell in the trap again. Thanks for reminding me. I have re-done the tests with release packaging, almost same results: 21- 25 FPS for TextField 1 ~ 4 for spark Label. Either way, I don't think TLF will get out to 25fps. Yes, 15 would have been fine. but 4 fps is really too bad. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. Yes, that was my intention. Crossing fingers that it works. Thanks Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : lundi 24 mars 2014 21:56 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps I assume this was a release version and not a debug version? Either way, I don't think TLF will get out to 25fps. I'd suggest doing a simple test to see if TextField really can do RTL (text starting from the right edge) or just knows how to place characters in a string based on some positioning information. -Alex On 3/24/14 1:46 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: I just did a quick test to compare TLF and TextField on mobile. Basically, replaced StyleableTextField cell renderer on MobileGrid by spark Label-based renderer. Test results: - iPad 3 (retina) - slow iOS packaging , GPU rendering - Mobile grid with 4 columns of text, and 200 rows StyleableTextField = 25 fps when scrolling Spark Label = 1 to 3 fps when scrolling ( UI is very slow, almost frozen). So of course mobile grid displays a lot of text, including multi-line, but that's where performance is needed, not on button and titles, IMO. I could also have used TextLine, but it does not support multi-line, which TextField does, so it's not equivalent. So for me, spark Label is not good enough on mobile, even on recent devices. I will explore the other track (RTL using TextField). What do you think? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 24 mars 2014 11:19 À : dev@flex.apache.org Objet : RE: RTL support in mobile apps Hi Carlos, 1) It's not proven yet that TLF is fast enough on mobile, especially when there are lots of text to display, such as in lists of datagrid. Plus I have discovered that the old TextField is actually capable to display RTL , but the Flex positioning
RE: flex-sdk_mustella-mobile - Build # 621 - Failure!
Undone commit. See what happens. Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : samedi 29 mars 2014 19:30 À : Erik de Bruin; dev@flex.apache.org Objet : RE: flex-sdk_mustella-mobile - Build # 621 - Failure! Anyway, I have to undo the commit because it does not work. So let's see if it fixes the mustella failure. Maurice De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : samedi 29 mars 2014 19:26 À : dev@flex.apache.org; Maurice Amsellem Objet : Re: flex-sdk_mustella-mobile - Build # 621 - Failure! Any chance this is related to a recent commit? EdB On Sat, Mar 29, 2014 at 6:36 PM, flex.muste...@gmail.commailto:flex.muste...@gmail.com wrote: flex-sdk_mustella-mobile - Build # 621 - Failure: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella-mobile/621/ Changes for Build #621 [maurice.amsellem] FIXED - FLEX-24502 Mobile optimized skins and item renderers don't show text when mirrored [...truncated 12942 lines...] [java] waited 1600 [java] ClobberProcess, it was already null [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] getting directory from the swf file [java] derived directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs [java] Launching: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml -screensize 640x960:640x960 -profile mobileDevice -XscreenDPI 240 Launching: C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] USING directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs [java] time: 12:36:15.118 [java] SCRIPTDONE! 12:36:22.491 [java] GET /ScriptComplete?0 HTTP/1.1 [java] Before Wait loop 12:36:22.491 waiting = 0 [java] After Wait loop 12:36:22.491 waiting = 0 [java] clobberProcess false [java] Total Results so far: 6 [java] waited 1500 [java] ClobberProcess, it was already null [java] removing the xml app file [java] Grab log, do parse = false [java] Grabbing the log from: C:\Users\ApacheFlex\AppData/Roaming\Macromedia/Flash Player/Logs/flashlog.txt to: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.log [java] apollo adj with : C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.swf [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.swf [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarIconMain.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\13_beta\bin\adl.exe [java] C
RE: Next Donation from Adobe
Great news. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 28 mars 2014 16:48 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe On 28/03/14 15:42, Alex Harui wrote: 7. The Squiggly spell-checker source code Awe-*some* ! Tom
RE: ScrollableStageText
Hi Lee, Someone else on this list also noticed this trace. I have added them when there is a problem disposing the TI image proxy (should never happen), but apparently it has not effect on the behavior. Can you please provide a simple code where this happens, so I can try to reproduce it and fix it. Maurice -Message d'origine- De : Lee Burrows [mailto:subscripti...@leeburrows.com] Envoyé : vendredi 28 mars 2014 21:53 À : Apache Flex Dev Mailing List Objet : ScrollableStageText Hi All, Getting this trace from ScrollingStageText.disposeProxy: [WARN] SST found empty bitmap data in: null Seems to happen when custom renderers (with editable TextArea) are generated for a list (and also when renderers are disposed). Any ideas? -- Lee Burrows ActionScripter
RE: flex-sdk_mustella-mobile - Build # 615 - Fixed!
Frankly, the failure was really strange ( persistence of view data in ViewNavigator), so maybe a timing issue ? Maurice -Message d'origine- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : jeudi 27 mars 2014 04:35 À : dev@flex.apache.org Objet : Re: flex-sdk_mustella-mobile - Build # 615 - Fixed! How about that? The build fixed itself. Thanks, Om On Mar 26, 2014 8:18 PM, flex.muste...@gmail.com wrote: flex-sdk_mustella-mobile - Build # 615 - Fixed: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella-mobile/615/ Changes for Build #613 [bigosmallm] Fix for https://issues.apache.org/jira/browse/FLEX-34189 Changes for Build #614 Changes for Build #615 [...truncated 12744 lines...] [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.swf [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] getting directory from the swf file [java] derived directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs [java] Launching: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mob ile\components\ActionBar\swfs\ActionBarTest.xml -screensize 640x960:640x960 -profile mobileDevice -XscreenDPI 240 Launching: C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.xml [java] USING directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs [java] time: 22:17:01.005 [java] SCRIPTDONE! 22:17:08.496 [java] GET /ScriptComplete?0 HTTP/1.1 [java] Before Wait loop 22:17:08.496 waiting = 0 [java] After Wait loop 22:17:08.496 waiting = 0 [java] clobberProcess false [java] Total Results so far: 6 [java] removing the xml app file [java] Grab log, do parse = false [java] Grabbing the log from: C:\Users\ApacheFlex\AppData/Roaming\Macromedia/Flash Player/Logs/flashlog.txt to: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ActionBar\swfs\ActionBarTest.log [java] apollo adj with : C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarApp1.swf [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarApp1.swf [java] waited 1500 [java] ClobberProcess, it was already null [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarApp1.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarApp1.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs\ButtonBarApp1.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe [java]
RE: Air iOS app - Blank white screen
Can you try profiling it with Adobe Scout / Scout Companion? I have tried it with non-debug iOS apps, but not with export release apps, but it may work. Maurice -Message d'origine- De : Flexicious.com [mailto:flexici...@gmail.com] Envoyé : mercredi 26 mars 2014 13:26 À : dev@flex.apache.org Objet : Re: Air iOS app - Blank white screen tried with 3.9, 4.0 as well as air 13. On Wed, Mar 26, 2014 at 1:47 AM, Raj Raju raj.virtu...@gmail.com wrote: Can you try to make the build with latest air sdk 4.0 ( 4.0.0.1619 ). I guess the problem will be resolved with this new sdk . You can find the link below http://labsdownload.adobe.com/pub/labs/flashruntimes/air/air4-0_sdk_wi n.zip http://labsdownload.adobe.com/pub/labs/flashruntimes/air/air4-0_sdk_wi n.zip Cheers, Raju.M. On Wed, Mar 26, 2014 at 9:38 AM, Flexicious.com flexici...@gmail.com wrote: We have a fairly large air app, and for some reason, when we package it for iOS, it does not launch correctly. Just a plain white screen. When we launch it in debug mode (or even using Fast packaging), it works fine. Only with the export release build it simply launches a plain white screen and does nothing. Anybody seen anything similar? Any idea if there is an error of some sort, any way to find out what the error is?
RE: flex-sdk_mustella-mobile - Build # 614 - Still Failing!
Very strange error. mobile/ViewAndViewNavigator/tests/ViewAndViewNavigator_persistence arrayPersistence Failed AssertMethodValue (method cannot be shown)(body:step 2) method returned false, expected true The test case body is the following: setup RunCode code=FlexGlobals.topLevelApplication.resetApp() waitTarget=navigator waitEvent=myEvent / RunCode code=FlexGlobals.topLevelApplication.navigator.pushView(views.Sect1View2, basicArray) waitTarget=navigator waitEvent=viewChangeComplete / /setup body RunCode code=FlexGlobals.topLevelApplication.navigator.pushView(views.Sect1View2) waitTarget=navigator waitEvent=viewChangeComplete / AssertMethodValue method=value = FlexGlobals.topLevelApplication.navigator.activeView.data != basicArray value=true / Does it mean that pushing a new view does not clear the view's data ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mercredi 26 mars 2014 18:33 À : dev@flex.apache.org Objet : Re: flex-sdk_mustella-mobile - Build # 614 - Still Failing! This is not one of the regular failures... Anyone have an idea what may have gone wrong? EdB On Wed, Mar 26, 2014 at 6:02 PM, flex.muste...@gmail.com wrote: flex-sdk_mustella-mobile - Build # 614 - Still Failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella-mobile/614/ Changes for Build #613 [bigosmallm] Fix for https://issues.apache.org/jira/browse/FLEX-34189 Changes for Build #614 [...truncated 12880 lines...] [java] starting the baseline server: Wed Mar 26 12:02:10 ACT 2014 [java] apollo adj with : C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.swf [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.swf [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.xml [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] getting directory from the swf file [java] derived directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs [java] Launching: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mob ile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.xml -screensize 640x960:640x960 -profile mobileDevice -XscreenDPI 240 Launching: C:\ApacheFlex\dependencies\AdobeAIRSDK\3.7\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.xml [java] USING directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs [java] time: 12:02:11.157 [java] FAIL: mobile/ViewAndViewNavigator/tests/ViewAndViewNavigator_persistence arrayPersistence [java] SCRIPTDONE! 12:02:16.642 [java] GET /ScriptComplete?0 HTTP/1.1 [java] Before Wait loop 12:02:16.642 waiting = 0 [java] After Wait loop 12:02:16.642 waiting = 0 [java] clobberProcess false [java] Total Results so far: 1 [java] waited 1500 [java] ClobberProcess, it was already null [java] removing the xml app file [java] Grab log, do parse = false [java] Grabbing the log from: C:\Users\ApacheFlex\AppData/Roaming\Macromedia/Flash Player/Logs/flashlog.txt to: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\ViewAndViewNavigator\swfs\ViewAndViewNavigatorMain.log [java] apollo adj with :
RE: ApacheCon Slides
Yes, I agree with you. -Message d'origine- De : Deepak MS [mailto:megharajdee...@gmail.com] Envoyé : mardi 25 mars 2014 07:52 À : dev@flex.apache.org Objet : Re: ApacheCon Slides I looked into this slide: Why FlexJS? Adobe Flash Player used to be in every browser Adobe AIR used to run on most computers Executives no longer carry Flash-capable devices AIR apps require installation and upgrades AIR apps have some fidelity issues Flash-based solutions no longer desirable Large MXML and ActionScript code bases I honestly felt that it's depicting flex\flash in a negative way. Subject says 'Why FlexJS?', but instead it talks 'Why we shouldn't use flex\flash'. Flex is so popular because the way it is(running on flash player with super rich UI). Only problem is it cannot run on mobile devices on browser because of flash player limitation. And this is where FlexJS comes into picture. And I feel we need to portray FlexJS as a powerful alternative for running flex based apps on mobile browsers. I don't think FlexJS would give exact same output as flash player. And hence I would strongly encourage my customers to use our flex applications on desktops\laptops and I would give a alternative app(compiled with FlexJS) for their mobile browsers, which would be light weight. I am assuming that FlexJS would be used to convert MXML\ActionScript code. And if we say 'Flash based solutions no longer desirable' and if people stop creating flex applications, then the whole purpose of FlexJS would get defeated, I reckon. That was my perspective. I don't know, all those pointers may sound correct for some too. May be it all depends on how each individual would take it :) Agree with Om regarding a mention of new features\enhancements\skinning. On Tue, Mar 25, 2014 at 4:57 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, 2. The numbers on slide 32 is a outdated. We have more than 40,000 installs of the Flex SDK since we started keeping track. BTW where do you get the 40,000 number from. I can only see 30,000 in the google stats. That only include 4.9 and up are you including 4.8 in that and if so how did we measure that it got 10,000 downloads? Thanks, Justin
RE: Please go vote for INFRA ticket
Voted. Will pass to a few colleagues. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 25 mars 2014 10:16 À : dev@flex.apache.org Objet : Please go vote for INFRA ticket Hi, https://issues.apache.org/jira/browse/INFRA-7488 Currently, most if not all our CI builds are failing due to (apparently) config issues on the server. The people at builds@a.o and INFRA don't seem to appreciate the importance to this project of a rapid solution, even after repeated message trying to convince them. Can you please visit the link above and vote on the ticket to (maybe) speed up the resolution. Thanks, EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: ApacheCon Slides
Few remarks: Slide 6: Native Applications = Native mobile applications , to avoid the confusion with AIR apps. Slide 7: Desktop + Web + Mobile Slide 8: the green smiley should not cover the flex logo Slide 9: IntelliJ ultimate = I think the correct name is IDEA IntelliJ (ultimate version is not required to program in Flex, but I may be wrong). Slide 10: Profile = you should mention Profiler included in FB Premium Slide 11: Different skins can have completely different usability concept . Desktop skin shows a lot of fields in a simple dialog . Mobile skin uses a step-by-step wizard approach Slide 12: AMF communication = you can also call methods in the back end and retrieve complex results, more will RPC call. General: I think since the slide title is Building Enterprise Apps, maybe you should have a slide on the many DI/IOC frameworks for Flex. Overall, greate presentation, thanks Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : lundi 24 mars 2014 22:07 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Guys, I just uploaded my stuf a few minutes ago: http://events.linuxfoundation.org/sites/events/files/slides/Building%20Enterprise%20Level%20Applications%20with%20Apache%20Flex%20and%20Java-v9-20140313_1547.pdf (Noticed too late that I should have shortended the file name ;-)) I thought I'd concentrate on why Flex is great for building Enterprise applications and only briefly go into Flexmojos as this is an Apache Conference. Doing a full Flexmojos introduction would have exploded the timeframe, so I decided to describe the ecosystem, what the different fragments are and how they all together create the big picture. Hopefully it will make a few people more interesed in Flex and guide them to the other talks (I added references tot he other talks at the end) Feedback greatly appreciated. Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Montag, 24. März 2014 21:03 An: dev@flex.apache.org Betreff: ApacheCon Slides ApacheCon required that we upload our slide decks by today. I just posted my slides. If you have time, please take a look and let me know if you think I should make changes. The FlexJS session is essentially the same as the 360|Stack presentation from last year. What's Happening in the Apache Flex Project http://events.linuxfoundation.org/sites/events/files/slides/ApacheCon14_Fle x.pdf FlexJS: Flex For javaScript: http://events.linuxfoundation.org/sites/events/files/slides/ApacheCon14_Fle xJS.pdf Thanks, -Alex
RE: ApacheCon Slides
What software are you using for the slides? Powerpoint ? Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 09:45 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Justin ... Have to admit that it seems to be easier to extend Flexmojos than dropping that dam shadow ;-) Tried the Shadow effect, but that added even more shadow ... it was somehow part of the template they gave us ... perhaps Alex can give me a tip. Even when switching the font that too had a shadow ;-) Chris Von: Justin Mclean jus...@classsoftware.com Gesendet: Montag, 24. März 2014 23:58 An: dev@flex.apache.org Betreff: Re: ApacheCon Slides Hi, I just uploaded my stuf a few minutes ago: http://events.linuxfoundation.org/sites/events/files/slides/Building%2 0Enterprise%20Level%20Applications%20with%20Apache%20Flex%20and%20Java -v9-20140313_1547.pdf Lots of info + liking the positive tone you have going there :-) You may want to consider dropping the drop shadow on the text IMO makes it a little hard to read. Thanks, Justin
RE: ApacheCon Slides
If you can send me the ppt or pptx, I could remove the text shadow and send it back to you. Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 11:06 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Jup Von: Maurice Amsellem maurice.amsel...@systar.com Gesendet: Dienstag, 25. März 2014 10:37 An: dev@flex.apache.org Betreff: RE: ApacheCon Slides What software are you using for the slides? Powerpoint ? Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 09:45 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Justin ... Have to admit that it seems to be easier to extend Flexmojos than dropping that dam shadow ;-) Tried the Shadow effect, but that added even more shadow ... it was somehow part of the template they gave us ... perhaps Alex can give me a tip. Even when switching the font that too had a shadow ;-) Chris Von: Justin Mclean jus...@classsoftware.com Gesendet: Montag, 24. März 2014 23:58 An: dev@flex.apache.org Betreff: Re: ApacheCon Slides Hi, I just uploaded my stuf a few minutes ago: http://events.linuxfoundation.org/sites/events/files/slides/Building%2 0Enterprise%20Level%20Applications%20with%20Apache%20Flex%20and%20Java -v9-20140313_1547.pdf Lots of info + liking the positive tone you have going there :-) You may want to consider dropping the drop shadow on the text IMO makes it a little hard to read. Thanks, Justin
RE: ApacheCon Slides
Just checked again ... IntelliJ IDEA (Community) doesn't Support ActionScript and Flex ... so it is only the Ultimate Version: Good to know. Thank you. -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 11:10 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Just checked again ... IntelliJ IDEA (Community) doesn't Support ActionScript and Flex ... so it is only the Ultimate Version: http://www.jetbrains.com/idea/features/editions_comparison_matrix.html Chris Von: Maurice Amsellem maurice.amsel...@systar.com Gesendet: Dienstag, 25. März 2014 10:35 An: dev@flex.apache.org Betreff: RE: ApacheCon Slides Few remarks: Slide 6: Native Applications = Native mobile applications , to avoid the confusion with AIR apps. Slide 7: Desktop + Web + Mobile Slide 8: the green smiley should not cover the flex logo Slide 9: IntelliJ ultimate = I think the correct name is IDEA IntelliJ (ultimate version is not required to program in Flex, but I may be wrong). Slide 10: Profile = you should mention Profiler included in FB Premium Slide 11: Different skins can have completely different usability concept . Desktop skin shows a lot of fields in a simple dialog . Mobile skin uses a step-by-step wizard approach Slide 12: AMF communication = you can also call methods in the back end and retrieve complex results, more will RPC call. General: I think since the slide title is Building Enterprise Apps, maybe you should have a slide on the many DI/IOC frameworks for Flex. Overall, greate presentation, thanks Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : lundi 24 mars 2014 22:07 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Guys, I just uploaded my stuf a few minutes ago: http://events.linuxfoundation.org/sites/events/files/slides/Building%20Enterprise%20Level%20Applications%20with%20Apache%20Flex%20and%20Java-v9-20140313_1547.pdf (Noticed too late that I should have shortended the file name ;-)) I thought I'd concentrate on why Flex is great for building Enterprise applications and only briefly go into Flexmojos as this is an Apache Conference. Doing a full Flexmojos introduction would have exploded the timeframe, so I decided to describe the ecosystem, what the different fragments are and how they all together create the big picture. Hopefully it will make a few people more interesed in Flex and guide them to the other talks (I added references tot he other talks at the end) Feedback greatly appreciated. Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Montag, 24. März 2014 21:03 An: dev@flex.apache.org Betreff: ApacheCon Slides ApacheCon required that we upload our slide decks by today. I just posted my slides. If you have time, please take a look and let me know if you think I should make changes. The FlexJS session is essentially the same as the 360|Stack presentation from last year. What's Happening in the Apache Flex Project http://events.linuxfoundation.org/sites/events/files/slides/ApacheCon14_Fle x.pdf FlexJS: Flex For javaScript: http://events.linuxfoundation.org/sites/events/files/slides/ApacheCon14_Fle xJS.pdf Thanks, -Alex
RE: ApacheCon Slides
What did you want to Point out on slide 11? I mean skinning is on the appearance, not on the behavior. So the word usability may be confusing. Usually, you use skins to change the size, color, layout, etc. So for me having two skins, one that displays all fields in one single dialog and the other in step by step wizard, Exceeds the usual scope of skinning (which does not mean it's not possible). Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 11:06 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Maurice, Thanks for the Feedback. - At first I wanted to say Native mobile applications but I can also create native Desktop applications with the captive runtime ... am I correct? I wanted to emphasis on mobile in my speach though. - What is exactly the Status on Windows 8? I marked this read as a marker for myself ... sort of forgot to check this - I am planning on using PowerPoint for performin the presentation ... therefore the PDF Version does not share the step by step appearance of Zombie and Smiley Pictures ;-) - What did you want to Point out on slide 11? - You are right, that I should lay more emphasis on how easy client-Server communication can be with Flex RemoteObjects. - I'll also add a Slide on the IOC Frameworks ... do you have any stats on These? Which ones are most popular ... ist there a sort of comparison? X uses [Metadata] and Y uses ... Something like that? But thanks for the Feedback ... I'll probably update the slides this evening. Chris Von: Maurice Amsellem maurice.amsel...@systar.com Gesendet: Dienstag, 25. März 2014 10:35 An: dev@flex.apache.org Betreff: RE: ApacheCon Slides Few remarks: Slide 6: Native Applications = Native mobile applications , to avoid the confusion with AIR apps. Slide 7: Desktop + Web + Mobile Slide 8: the green smiley should not cover the flex logo Slide 9: IntelliJ ultimate = I think the correct name is IDEA IntelliJ (ultimate version is not required to program in Flex, but I may be wrong). Slide 10: Profile = you should mention Profiler included in FB Premium Slide 11: Different skins can have completely different usability concept . Desktop skin shows a lot of fields in a simple dialog . Mobile skin uses a step-by-step wizard approach Slide 12: AMF communication = you can also call methods in the back end and retrieve complex results, more will RPC call. General: I think since the slide title is Building Enterprise Apps, maybe you should have a slide on the many DI/IOC frameworks for Flex. Overall, greate presentation, thanks Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : lundi 24 mars 2014 22:07 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Guys, I just uploaded my stuf a few minutes ago: http://events.linuxfoundation.org/sites/events/files/slides/Building%20Enterprise%20Level%20Applications%20with%20Apache%20Flex%20and%20Java-v9-20140313_1547.pdf (Noticed too late that I should have shortended the file name ;-)) I thought I'd concentrate on why Flex is great for building Enterprise applications and only briefly go into Flexmojos as this is an Apache Conference. Doing a full Flexmojos introduction would have exploded the timeframe, so I decided to describe the ecosystem, what the different fragments are and how they all together create the big picture. Hopefully it will make a few people more interesed in Flex and guide them to the other talks (I added references tot he other talks at the end) Feedback greatly appreciated. Chris -Ursprüngliche Nachricht- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Montag, 24. März 2014 21:03 An: dev@flex.apache.org Betreff: ApacheCon Slides ApacheCon required that we upload our slide decks by today. I just posted my slides. If you have time, please take a look and let me know if you think I should make changes. The FlexJS session is essentially the same as the 360|Stack presentation from last year. What's Happening in the Apache Flex Project http://events.linuxfoundation.org/sites/events/files/slides/ApacheCon14_Fle x.pdf FlexJS: Flex For javaScript: http://events.linuxfoundation.org/sites/events/files/slides/ApacheCon14_Fle xJS.pdf Thanks, -Alex
RE: ApacheCon Slides
Cool. -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 11:43 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Found out how to do it ... great you have 1000 Places where you can add shadows in PowerPoint ... it was the Formeffects where not the font or the slide had a shadow, but the Frame containing the text ... well at least the shadow's gone now ;-) Von: Justin Mclean jus...@classsoftware.com Gesendet: Dienstag, 25. März 2014 11:37 An: dev@flex.apache.org Betreff: Re: ApacheCon Slides Hi, Have to admit that it seems to be easier to extend Flexmojos than dropping that dam shadow ;-) Know what you mean I open have many stand back I'm using photoshop moments :-) Justin
RE: ApacheCon Slides
Where the Skin takes care of the Wizard Logic. After all the User Dialog doesn't care how the fields are presented as Long as they are. Maybe I didn't understand what you meant by wizard logic. That being said, this discussion is getting out-of-topic, so sorry for starting it and for the noise. Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 11:41 À : dev@flex.apache.org Objet : AW: ApacheCon Slides But I think it's not only appearance ... that's the Point. At least what I especially like about Flex skinning. In GWT and other alternatives you kann only control the layout and formatting, but in Flex you can also have an alternate usability pattern. I couldn't create a User Dialog in GWT where the Desktop Skin has all fields on one Screen and on the mobile Counterpart the fields are split up in several Wizard steps. Where the Skin takes care of the Wizard Logic. After all the User Dialog doesn't care how the fields are presented as Long as they are. But perhaps that's only my Interpretation. Chris Von: Maurice Amsellem maurice.amsel...@systar.com Gesendet: Dienstag, 25. März 2014 11:19 An: dev@flex.apache.org Betreff: RE: ApacheCon Slides What did you want to Point out on slide 11? I mean skinning is on the appearance, not on the behavior. So the word usability may be confusing. Usually, you use skins to change the size, color, layout, etc. So for me having two skins, one that displays all fields in one single dialog and the other in step by step wizard, Exceeds the usual scope of skinning (which does not mean it's not possible). Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : mardi 25 mars 2014 11:06 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Maurice, Thanks for the Feedback. - At first I wanted to say Native mobile applications but I can also create native Desktop applications with the captive runtime ... am I correct? I wanted to emphasis on mobile in my speach though. - What is exactly the Status on Windows 8? I marked this read as a marker for myself ... sort of forgot to check this - I am planning on using PowerPoint for performin the presentation ... therefore the PDF Version does not share the step by step appearance of Zombie and Smiley Pictures ;-) - What did you want to Point out on slide 11? - You are right, that I should lay more emphasis on how easy client-Server communication can be with Flex RemoteObjects. - I'll also add a Slide on the IOC Frameworks ... do you have any stats on These? Which ones are most popular ... ist there a sort of comparison? X uses [Metadata] and Y uses ... Something like that? But thanks for the Feedback ... I'll probably update the slides this evening. Chris Von: Maurice Amsellem maurice.amsel...@systar.com Gesendet: Dienstag, 25. März 2014 10:35 An: dev@flex.apache.org Betreff: RE: ApacheCon Slides Few remarks: Slide 6: Native Applications = Native mobile applications , to avoid the confusion with AIR apps. Slide 7: Desktop + Web + Mobile Slide 8: the green smiley should not cover the flex logo Slide 9: IntelliJ ultimate = I think the correct name is IDEA IntelliJ (ultimate version is not required to program in Flex, but I may be wrong). Slide 10: Profile = you should mention Profiler included in FB Premium Slide 11: Different skins can have completely different usability concept . Desktop skin shows a lot of fields in a simple dialog . Mobile skin uses a step-by-step wizard approach Slide 12: AMF communication = you can also call methods in the back end and retrieve complex results, more will RPC call. General: I think since the slide title is Building Enterprise Apps, maybe you should have a slide on the many DI/IOC frameworks for Flex. Overall, greate presentation, thanks Maurice -Message d'origine- De : Christofer Dutz [mailto:christofer.d...@c-ware.de] Envoyé : lundi 24 mars 2014 22:07 À : dev@flex.apache.org Objet : AW: ApacheCon Slides Hi Guys, I just uploaded my stuf a few minutes ago: http://events.linuxfoundation.org/sites/events/files/slides/Building%20Enterprise%20Level%20Applications%20with%20Apache%20Flex%20and%20Java-v9-20140313_1547.pdf (Noticed too late that I should have shortended the file name ;-)) I thought I'd concentrate on why Flex is great for building Enterprise applications and only briefly go into Flexmojos as this is an Apache Conference. Doing a full Flexmojos introduction would have exploded the timeframe, so I decided to describe the ecosystem, what the different fragments are and how they all together create the big picture. Hopefully it will make a few people more interesed in Flex and guide them to the other talks (I added references tot he other talks at the end) Feedback greatly appreciated. Chris -Ursprüngliche Nachricht
RE: Please go vote for INFRA ticket
That's funny :-) try again ? -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : mardi 25 mars 2014 12:02 À : dev@flex.apache.org Objet : Re: Please go vote for INFRA ticket On 25/03/14 09:16, Erik de Bruin wrote: https://issues.apache.org/jira/browse/INFRA-7488 This system is currently down for maintenance Tom
