Again, I was not highly involved in this code, but IIRC, the TextLines are never flipped, so if you choose a flipped layoutDirection the TextLines are re-flipped. But if you start flipping TextFields without embedded text they go blank.
Does that explain what you're seeing? -Alex On 3/21/14 5:00 PM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >Thanks Alex. That was also my understanding. > >Regarding TextInput / TextArea, there is no issue with regard to RTL in >using StageText ( embedded in StyleableStageText or ScrollableStageText) . > >Now something strange that gets me puzzled. > >I did some experiments with mobile components that use TextField >(actually StyleableTextField) and I managed to displayed Arabic/Hebrew >(list , titles and nav bar) > >https://www.dropbox.com/s/4e4untcp3f4jeb2/List_arabic_LTR.png > >But this works only if the surrounding View or the application >layoutDirection is set to "ltr". >And indeed, you notice that the text is RTL but the layout is still LTR. > >Now, if I set layoutDirection to RTL either at the Application or View , >then everything disappears: > >https://www.dropbox.com/s/jzu1veecjm64m51/list_Arabic_RTL.png > > >I thought that layoutDirection = RTL was "merely" applying a mirroring >transform to the display. > >I am confused. > >Maurice > >-----Message d'origine----- >De : Alex Harui [mailto:aha...@adobe.com] >Envoyé : samedi 22 mars 2014 00:44 >À : dev@flex.apache.org >Objet : Re: RTL support in mobile apps > >I wasn't on the mobile components team (I did some mobile work but mostly >worked on other SDK stuff), but fundamentally, if there's a TextField >involved, then there is no RTL support. You need TextLines for RTL. You >may be able to swap in the "desktop" skins for TextInput/TextArea and pay >the performance and memory hit to get RTL text, but then I'm not sure how >well StageText will work with that, if at all. Essentially, the mobile >team traded off RTL support for better performance. Now, that was >several years ago and phones and tablets are faster, so it might be worth >revisiting that decision. > >-Alex > >On 3/21/14 3:41 PM, "Maurice Amsellem" <maurice.amsel...@systar.com> >wrote: > >>Hi Team, >> >>Ori Segal has reported a problem in TextInput default skin with RTL >>(Hebrew, arabic) layout. >>I have fixed this problem. >> >>Now he has reported a problem in TextInput "prompt" text not being >>displayed in RTL. >> >>So I did a small test: set layoutDirection="rtl" to a sample mobile app >>(with buttons, mobilegrid, etc..) and almost every text disappeared. >> >>The only texts that seem to be displayed correctly are: >>- TextInput / TextArea with the default text (that is using native >>StageText) >>- spark Label, that is using TextLine (and the new FTE/TLF engine). >>Everything else, that uses the mobile-optimized StyleableTextField, >>will not display RTL (apparently because it's based on the old >>TextField engine). >> >>Reading the articles below, it seems clear enough that RTL is NOT >>supported on AIR mobile (with a few exceptions): >> >>http://sourceforge.net/adobe/flexsdk/wiki/Mobile%20Text%20Components/ >>http://help.adobe.com/en_US/flex/using/WS02f7d8d4857b1677-165a04e112695 >>1a2 >>d98-7ffe.html >>http://help.adobe.com/en_US/flex/using/WS02f7d8d4857b1677-165a04e112695 >>1a2 >>d98-7ffd.html >> >>Alex, as you seem to have been involved in that, do you confirm? >> >>Something else: >>The first article says: >>" Primarily for performance reasons and support for native predictive >>text input and editing, mobile will use TextField-based text in all >>critical areas. This is expected to be a short-term solution until a >>performant version of FTE arrives on mobile." >> >>So has FTE been optimized for mobile since the article was written , >>for example in AIR 4.0? >> >> >>Thanks >> >>Maurice >
