Re: WebKit engine for default browser
 

sb2 dpkg-buildpackage -rfakeroot -d -b

As bundyo said, webkit won't build with scratchbox 1, at least not without workarounds. When I tried compiling with the ordinary Maemo SDK, the resulting library kept crashing in the CSS parsing code. With Maemo SDK+ the package builds and runs fine.

Re: WebKit engine for default browser
 

And your only mod to SB 2 was the bison 2.2 upgrade? Other than that, you're still using the old toolchain (2005q3-1)?

Re: WebKit engine for default browser
 

I don't remember if I needed to update it at all. But WebKitGtk for sure requires 2.2, and doesn't build with 2.4 (at least with the svn version I tried before returning to 2.2).

Re: WebKit engine for default browser
 

seems osso-browser with webkit is still somewhat unstable. i had it crash after i stopped the download/render of a page and then tried to go back a step in browser history.

Re: WebKit engine for default browser
 

Sorry, I didn't mean for you to repeat yourself. I was wondering if hns concurs with you. hns, do you concur with Bundyo that the only toolchain mod to SB 2 is the bison 2.2 upgrade? :)

Re: WebKit engine for default browser
 

I uploaded a new version of libwebkit. This one should allow multiline editing for textareas and fix a bug with copy/paste. The binary package also has SVG enabled now.

Re: WebKit engine for default browser
 

perfect, works like a charm. where do i mail the beer? :D

Re: WebKit engine for default browser
 

Sorry, but I'm a little confused. Does this webkit have everything that Bundyo's latest has, plus the changes you just made?

Re: WebKit engine for default browser
 

Yes, excluding what he disabled. I will post mine later.

Re: WebKit engine for default browser
 

If I wanted to install both Tear and Webkit-EAL, would each install their own version of libwebkit? Would there be a conflict?

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
 

If i understood correctly, it is in the hns' todo list to reimplement this too.

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
 

Nope, but I'm planning to reimplement that for the next release. (Right, I'm planning a next release... Bundyo's recent libwebkit builds are working pretty well for me, so I guess it's time to release webkit-eal 0.11 soon)

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
 

looking forward to this release ...:)

Re: WebKit engine for default browser
 

i found myself wondering if there was anything new on this front...

Re: WebKit engine for default browser
 

Now you've got me wondering too...

Re: WebKit engine for default browser
 

same as above... :p

Re: WebKit engine for default browser
 

I offer my 'me too' on this issue..

Re: WebKit engine for default browser
 

I'm utterly indifferent in regards to seeing a newer webkit-eal... *cough*

Re: WebKit engine for default browser
 

I also found myself wondering.. could someone educate me a little on this webkit vs gecko vs <rendering engine x>. What makes webkit superior to others? Is it more accurate rendering, lower cpu/memory etc consumption, speed, flexibility, features or what?

I often see commenters in blogs (who probably have no idea what webkit is) touting it as some kind of holy grail of browser tech. Is this just hype and reasoning along the lines of "iPhones browser uses webkit and it's good -> for a browser to be good it must use webkit" or is it better?

Just interested, not trying to start flamewars or anything.

Re: WebKit engine for default browser
 

cant speak for webkit usage in general, as different uses have different tweaks (google's chrome browser for instance uses a custom javascript engine).

in any case, the version of gecko found in diablo (and maybe earlier, not sure) is a alpha-version with a poorly optimized javascript engine, so if your browsing pages with lot of ajax or similar (hell, even ad areas are javascript powered) the gecko engine will be slower then the webkit engine...

Re: WebKit engine for default browser
 

I use tear as my primary browser, and have tried the webkit engine, but the only downside to both is that it wont let you login to some pages, namely usatoday for me, as well as a few others.

Re: WebKit engine for default browser
 

could be related to issues with javascript cookies, at least in tear as i think its using wget to handle the actual downloading (not sure about webkit-eal).

Re: WebKit engine for default browser
 

The answer is in this thread but I'm too bored to search right now. :)

From my memory (not so good lately) it is something about the implementation is not complete yet on the ssl stuff.

Re: WebKit engine for default browser
 

This webkit engine this thread is talking about was good while tear was not there yet. Now tear is the better browser and webkit-eal was discontinued.

Re: WebKit engine for default browser
 

The first versions of the Tear browser were here long before the webkit-eal was implemented.

Re: WebKit engine for default browser
 

if the project is discontinued, i would love to read that from hns directly...

Re: WebKit engine for default browser
 

That's true, but they were unusable. The original developer of webkit-eal was who proved that webkit can be compiled and actually work on the tablets. That motivated me to get my build in shape at last. After he disappeared without leaving the last sources behind, hns took over and adapted the webkit-eal engine to the webkit build I'm using (and contributing the HIM support on the way). So currently webkit-eal and Tear use the same webkit engine. Correct me if I missed something. :)

Re: WebKit engine for default browser
 

webkit-eal has a long and rocky history, iirc...

Re: WebKit engine for default browser
 

Wow, this thread reads like a novel...
Unfortunately, I cannot access pages 41 to 43
I cannot add new entries into Google calendar with tear, and it crashes all the time. webkit-eal works...

Re: WebKit engine for default browser
 

...finaly I could read the missing pages also. There should be some kind of public funding for open source programmers.

Re: WebKit engine for default browser
 

Peter, do you know if webkit-eal can work with, and save to the web, a TiddlyWiki on tiddlyspot.com? TiddlySpot hosts personal TiddlyWikis for free; but tear can't work with it at all, and MicroB can't save to it.

Also, how good do you find webkit-eal for general browsing?

Re: WebKit engine for default browser
 

watch out tho, the version of webkit-eal that shares webkit version with tear has the same text input issue.

that is, if there is any text in a input area, and one tries to move the cursor to the left f the first letter (into the side of the area) then webkit will hang, taking the browser with it.

Re: WebKit engine for default browser
 

Yes, you're right. Sorry. I was still associating webkit-eal with pronvit.