I'm getting the impression that the LiveCode roadmap is primarily user demand driven, so there isn't really a long term strategy apart from "keep the platform relevant and grow the user base". :)
If you really want something relatively simple like this in the roadmap I think pledging for the new campaign with a Premium (or maybe Pro) license and asking them to do it sooner rather than later is the best way forward! Alternatively it's simple enough that you could contract someone to do it after all the refactoring is sorted for significantly less than the cost of a Premium license. I think the main issue with doing this for mobile platforms is backwards compatibility. On Android the WebView completely changed (to a modern Chromium base from an old WebKit base) in one of the recent releases (can't remember which 4.x version) - making sure it works identically on both might be tricky - Android has always had a simple method for doing this though. On iOS this was only doable via fake URL load requests in the WebView before iOS 7, then iOS 7 added an almost completely undocumented and slightly cumbersome way of doing it properly. Now iOS 8 has added a new WKWebView with a much nicer way of doing it (and much better JavaScript performance!). So, it's going to be cheaper and easier to do via an external/extension if you only care about newer platform versions but to get it into the engine where it belongs means supporting all the platform versions that LiveCode does. -- Mark Wilcox m...@sorcery-ltd.co.uk On Tue, Jul 1, 2014, at 09:28 AM, David Bovill wrote: > Ah yes - I see the Chromium Embedded framework is really desktop only - I > missed that. I'd like to down what the long term strategy regards browser > controls cross mobile and desktop is. > > For instance *revBrowserAddJavaScriptHandler* is for now CEF specific - > is > the plan to add this to mobile platforms? > > > On 1 July 2014 14:08, Mark Wilcox <m...@sorcery-ltd.co.uk> wrote: > > > > > For iOS it's against the App Store rules to include your own browser > > engine (no downloadable code execution allowed) and not even technically > > possible to ship the V8 JavaScript engine (because you can't mark memory > > both writable and executable - so can't ship your own JIT compiler). As > > far as I know Safari doesn't yet support WebRTC on Mac OS or iOS. Even > > when it does, there's not yet any guarantee that it will have a common > > video codec with other implementations because the standards people > > can't agree on a mandatory one. > _______________________________________________ > 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
