![]() |
Re: WebKit engine for default browser
no, they use the same libwebkit.
|
Re: WebKit engine for default browser
hmm, when kinetic scrolling got reimplemented, did that include the ability to te it via gconf? im playing around with some settings but cant really tell any diff...
|
Re: WebKit engine for default browser
Maybe it was answered before and i missed it. But why hns has a different version of the libwebkit from Bandyo? or to be more exact why hns needs to disable some options?
It came to me as I've got the latest stuff from hns and through qole's repo I'm getting an update to the latest (from Bandyo). Anyways, thank you guys (Bandyo, hns and qole) for making the experience so much better. |
Re: WebKit engine for default browser
Quote:
|
Re: WebKit engine for default browser
This seems rather cool: https://lists.webkit.org/pipermail/w...il/007253.html
(Short version: An ARM-optimized version of some recent improvements to WebKit's JavaScript engine, improving performance on the NITs and other ARM devices.) How about whipping up a libwebkit build with this? It's supposed to be fairly stable (it's passing the WebKit regression test suite, anyway). (Meh, this is a duplicate of my earlier post to the Tear 0.3 thread. Maybe we should have a central libwebkit thread, and separate threads for its frontends.) |
Re: WebKit engine for default browser
anyone else having interface freeze issues when eunning both this and tear at the same time lately?
|
Re: WebKit engine for default browser
Quote:
|
Re: WebKit engine for default browser
glad to see there is still life in this :)
|
Re: WebKit engine for default browser
arg, im torn. i find the eal kinetic more tolerable (maybe because i was able to tweak its treshold) but its a bit more buggy then tear at present (crashes to disfunctional microb, wrong titles on backwards longtap)...
|
Re: WebKit engine for default browser
Quote:
|
| All times are GMT. The time now is 10:39. |
vBulletin® Version 3.8.8