|
 Originally Posted by NIN_ru
Some thoughts about legacy Isis: as far as I understand, browseradapter talks with browserserver, which render pages, and share buffer with it. The idea is to manage browseradapter to talk with modern CEF3(see it's Off-screen Rendering feature), instead of browserserver. Does anyone know is this possible?
 Originally Posted by https://code.google.com/p/chromiumembedded/wiki/GeneralUsage
Off-Screen Rendering
With off-screen rendering CEF does not create a native browser window. Instead, CEF provides the host application with invalidated regions and a pixel buffer and the host application notifies CEF of mouse, keyboard and focus events. Off-screen rendering does not currently support accelerated compositing so performance may suffer as compared to a windowed browser.
Is that relevant?
Also, it appears that Chromium now uses Blink as a rendering engine - which is a Google fork of WebKit. Could that be a compatibility problem? Also, I suppose there is the question of (proprietary) Flash support. I suppose it's question of modularity.
I looked at Wikipedia for a list of Browsers. From that and for general information, here are links to those that are webkit based and OSS.
Web (!)
Konqueror
Midori
Origyn
QupZilla
Rekonq
Uzbl
In legacy terms, it would be nice if the current browser was 'stabilised' (not frequently graying out and reloading). I am personally happy with it otherwise. On Open webOS, of course, there is less restriction. Uzbl appears interesting as a modular component that could perhaps integrate with the legacy flash player. Is flash redundant yet? I still get updates for the desktop - in fact perhaps that indicates that a future browser user may be able to access a free plugin...
|
|
|