>From a design perspective, for being able to use paste, speech to text, and >emojis, I have Idea that comes from something Richard said.
When a user clicks on a field to edit, that field could appear to start from its location and grow to take up most of the screen. It would actually be a mobile native field that is created on the fly. Then the user could use native field capabilities and it would look like it was designed that way on purpose. When they click a 'done' button, it would shrink down to regular size, process the contents, and put them into the LC field. If done right, that could be pretty sharp and would address the issue of fields being in scrolling groups - something I don't think we can do with native mobile fields. Sent from my iPhone > On Jun 27, 2017, at 4:17 PM, Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > hh wrote: > > >> Richard G. wrote: > >> ... beyond the performance gains by moving "low level binary data > >> processing" to javaScript (would be nice if someone has time to > >> post some apples-to-apples comparisons) ... > > > > "Low level binary data processing" means for me for example to invert > > the color data of an image of medium screen size (say 1920x1080) > > _without_ using any js-package, only using pure HTML5/javascript. > > What is "js-package"? If the "js" isn't JavaScript, what is it? > > > > Now please define "apples-to-apples comparisons" for that use-case, > > best with your LC script version (so that we have the fastest possible > > LC script version), and I'll add my version so that everyone can do > > his own comparisons. > > > > [Use latest LC 8.1.5, the image is a LiveCode object, say image 1] > > [Simple invert means for me (r,g,b) -> (255-r,255-g,255-b)] > > > > on mouseUp > > -- start timing > > ... > > -- end timing > > end mouseUp > > I don't have a collection of image processing scripts handy for such testing, > but I've seen some in the forums I may be able to hunt down if they're useful. > > > >> Richard G. wrote: > >> ... what I find most interesting in these discussions is that most of > >> the interest expressed thus far has been for UI elements, something > >> previously seen as LC's sweet spot. > > > > Just the same with most externals ?! > > If we expand the conversation from "externals" to all forms of extensions in > general, then certainly LCB-based widgets tend to be GUI controls. > > But if we look at the types of externals most commonly used in LC at the > moment, we have tsNet, the MER collection, and others, most of which provide > some pretty great functionality but are rarely creating GUI controls. > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
