That's exactly how I'm implementing it (Spannable strings in the native EditText view). It's pretty simple and fast to do it this way; and I would think that any amount of syntax highlighting is better than none? This might serve well until we get around to a more complete VE for mobile.
On Wed, Jun 4, 2014 at 12:54 PM, Brion Vibber <[email protected]> wrote: > Yeah, Ace has some bad touch support too, and it's got serious problems > with RTL and variable-width characters. If we do syntax highlighting, > staying in the native editor widget is probably best for performance and > consistency of behavior on both Android and iOS. (Text edit widgets support > annotated text with some styling, which should be enough for our needs.) > > -- brion > > > On Wed, Jun 4, 2014 at 9:52 AM, Yuvi Panda <[email protected]> wrote: > >> On Wed, Jun 4, 2014 at 3:52 PM, Yuri Astrakhan <[email protected]> >> wrote: >> > I wonder if the code editor extension can be adapted to work for wiki >> > markup. >> >> Possibly, although ACE (the one we use on desktop) has somewhat >> terrible perf on Mobile the last time I checked (a few months ago). >> Lots of cursor placement issues as well. >> >> If we do it on Android, it'll most likely just use Android Spannables >> in a regular EditText - should be much faster and bug free, I think. >> >> -- >> Yuvi Panda T >> http://yuvi.in/blog >> >> _______________________________________________ >> Mobile-l mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/mobile-l >> > > > _______________________________________________ > Mobile-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mobile-l > >
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
