Re: Setting up Flex SDK for development
Hi, FWIW, the downside to making the repo into an IDE-compatible SDK, regardless of how you do it, is that you've mixed in a lot more non-Apache code so you have to be careful about the content of your patches and checkins. However, it is way easier to do most changes in an IDE compatible SDK and I'd guess many folks are doing it that way. This is how I do and there's very little risk that you'll check in something you shouldn't. Also you can go to each project (in frameworks) and compile via ant when testing which make for a much quicker workflow when fixing bugs. Most IDEs have support for ant as well so you may not need to do anything via the command line if you that's your choice. Thanks, Justin
Re: Setting up Flex SDK for development
This thread [1] from the archives might come in handy. I don't think all the information in there made it into the Wiki, but there is some information in there as well. EdB 1: http://mail-archives.apache.org/mod_mbox/flex-dev/201307.mbox/%3c853dd4e8-18ae-4a31-9373-39e8fd77d...@classsoftware.com%3E On Sat, Mar 29, 2014 at 7:03 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, FWIW, the downside to making the repo into an IDE-compatible SDK, regardless of how you do it, is that you've mixed in a lot more non-Apache code so you have to be careful about the content of your patches and checkins. However, it is way easier to do most changes in an IDE compatible SDK and I'd guess many folks are doing it that way. This is how I do and there's very little risk that you'll check in something you shouldn't. Also you can go to each project (in frameworks) and compile via ant when testing which make for a much quicker workflow when fixing bugs. Most IDEs have support for ant as well so you may not need to do anything via the command line if you that's your choice. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Setting up Flex SDK for development
On 3/28/14 10:51 PM, jude flexcapaci...@gmail.com wrote: The instructions (README) may sound more complicated than it actually is. I'm planning on setting up Mustella as well. If you don't have it setup as an IDE compatible way how do you have it set up and how are you working on it? I use FB as a text editor, but do just about everything else from ant and the command line. In most scenarios, I'm more efficient without an IDE, but that's in part because I've been in this code for so many years. -Alex
Re: Setting up Flex SDK for development
Hi, I use FB as a text editor, but do just about everything else from ant and the command line. In most scenarios, I'm more efficient without an IDE, but that's in part because I've been in this code for so many years. This may help someone - in FB right click on build.xml and select run as ant build... and you can select targets, ant build will run selected targets. Justin
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
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 ? 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
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!
Any chance this is related to a recent commit? EdB On Sat, Mar 29, 2014 at 6:36 PM, 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] 240 [java] getting directory from the swf file [java] derived directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ButtonBar\swfs [java] Launching: [java]
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 is
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]
Re: Search in Apache Flex Docs?
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: 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
