On 1 July 2014 21:03, Mark Wilcox wrote:
> 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.
>
Sounds a way to go. Even better would be to have a well structured and
promote
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 c
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 platfo
I assume CEF doesn't build the WebRTC support in the Chromium project by
default because it has extra dependencies on the audio stack. I guess
LiveCode could include such support if it wanted.
Does LiveCode plan to bundle CEF on Android? Given the built-in web view
in Android is already based on C
Thanks Alejandro - I just tested and on OSX with revBrowserOpenCEF (which
is Chrome 32) - I get a score of 472 rather than 503 for Chrome 32. It
looks like webRTC is not available on Chrome 32 version in CEF for OSX.
I'm not sure about Android and iOS versions yet?
On 1 July 2014 00:13, Alejandr
According to http://html5test.com/
this new Chromium Embedded Framework
is identified as Chrome 31 and scores 450
from 555 points.
http://forums.livecode.com/viewtopic.php?f=89&t=20501
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/WebRTC-support-and-Chromium-E
