Thanks Om for getting in. I will do some benchmarks when I have time to compare TLF and TextField on mobile.
Yet, read my other post where I manage to display bidi text using TextField (I check in the debugger, the text is passed to StyleableTextField.text, so this is definitely TextField). But when setting layoutDirection to RTL, the text disappears. This looks like the bug with StageText that I fixed recently. Il will try "cancelling" the RTL mirroring on StyleableTextField to see if the text reappears. However, I have no explication how this can be possible, if TextField is not supposed to handle RTL. Maurice -----Message d'origine----- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : samedi 22 mars 2014 00:58 À : dev@flex.apache.org Objet : Re: RTL support in mobile apps I worked on an intensive page layouting application that was built for the web and was later ported to iPads. It used TLF extensively, essentially reading TextFlow xml and drawing TextLines on a sprite and doing all kinds of layout control. The text rendering performance was quite bad on iPad1, but it improved considerably with iPad2. Alex may be right in that we may not have that kind of performance problems with the latest devices. It is probably worth a try switching to FTE/TLF for mobile and see how things perform. Not sure how it will affect everything else, though. Thanks, Om On Fri, Mar 21, 2014 at 4:44 PM, Alex Harui <aha...@adobe.com> wrote: > 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-165a04e11269 > 51a2 > >d98-7ffe.html > > > http://help.adobe.com/en_US/flex/using/WS02f7d8d4857b1677-165a04e11269 > 51a2 > >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 > >
