Hi, Here is a brief status of the implementation of Mobile Text Input, along with some questions:
Implementation overview: The change is mainly on the class StyleableStageText, which now takes the opposite approach than the previous one: - display proxy image bitmap by default - display StageText only when editing StageTextInputSkin/StageTextAreaSkin has been modified to use this class - to make it easier to change StageTextInputSkin internal StyleableStageText component, the variable textDisplay is now of type IStyleableEditText Behavior changes: - scrolling and overlapping of text is well managed , as it always uses the bitmap proxy, which is a Flex component: all the text inputs are scrolling - text occluding while editing is not managed yet, which means the edited text may overlap other UIs. (TO BE DONE) Testing: - tested on iPad 2 and iPad 3: TI in scrolling forms, TI in callouts - *NEEDS TO BE TESTED ON ANDROID* - memory consumption tests yet to be done - mustella test yet to be run Questions: - Can someone please test on Android ? - I have chosen to directly replace StyleableStageText. Maybe I can also leave the old StyleableStageText with a different name, so that it can be used in case there is an issue with the new one ? or the other way? Now that it is an interface, it's easy to subclass the StageTextInputSkin, and override createTextDisplay() to use another class. Maurice