Re: WebKit engine for default browser
 

true that, but iirc there was a 20-30MB lib that wbkit depended on.

at last the exsisting one did, this new one i do not know...

Re: WebKit engine for default browser
 

Nah, libwebkit is the only one needed.

Re: WebKit engine for default browser
 

Great! Want to test this out...

Re: WebKit engine for default browser
 

Forgot, there is also icu library for unicode support, quite big too. but not sure maybe something else needs it to and it's already installed

Re: WebKit engine for default browser
 

libicu is for unicode support, it should be already installed.

Re: WebKit engine for default browser
 

****, pronvit, you pwn.

Re: WebKit engine for default browser
 

Besides the obvious advantage of choice between rendering engines (performance, stability, bugs, compatibility, development) this allows also the user to pick either one while not having to relearn a new interface nor does she have to unlearn the old interface hence allowing the user to go back on forth because this part is the same. If you ever use an alternative keyboard layout and switch to another (forced or otherwise) you know what I'm talking about. E.g. laptop -> desktop, qwerty -> dvorak, or language layouts. Or say IE at work, with a real browser at home.

Re: WebKit engine for default browser
 

LOL your're right.

I'm currently using Win at work and OSX at home, just switched, and still am trying to get used to CMD+C/CMD+V instead of CTRL+C/CTRL+V and so on... :)

Re: WebKit engine for default browser
 

one reason why the masses out there get stuck with our lovely n800 is exactly by threads like this.
I can only imagine what the webkit does or will do, but i do not understand it.
Could anyone of you just simply write down what the webkit does and how to
get it?

thnx in advance guys.

Re: WebKit engine for default browser
 

pronvit: What revision of webkit are you compiling? Are you using libsoup or curl for the http backend? Pango or freetype? How have you managed to compile it? Last time Bundyo and I tried, it gived us some compiling errors. Tear is a great project I think. It lets us make some things that with maemo browser you couldn't, like have plugins. Also is written in Vala which is a great language. The stability problems you are having could be mainly because of webkit not being stable enough. As for icu library, there is a bug opened so that it will kill these dependency. Things are starting to look great on the webkit front, but it should need some stabilty before considering ready for every day use.