Re: WebKit engine for default browser
 

How fast is it on Google Maps (with StreetView)?

Re: WebKit engine for default browser
 

Indeed the Javascript performance is quite impressive.

Is there already a Browser for Maemo available, using the new Tracemonkey Javascript enginge which will be introduced with Firefox 3.1? Would be interesting to see a direct comparision between Webkit and Tracemonkey on the N8x0. As far as I understand even in the new Fennec Alpha 2, Tracemonkey isn't enabled yet.

At least on my desktop computer there doesn't seem to be a big difference between the Webkit nightly builds and Firefox 3.1 as far as Javascript performance is concerned. On some pages Firefox 3.1 seems to be a bit faster on others Webkit is a tad faster... But overall the difference is barely noticable.

Re: WebKit engine for default browser
 

Just a few glitches noticed (not including the ones you already listed):

1) The keyboard doesn't come up when tapping in a password field (but does everywhere else)
2) The keyboard automatically comes up on many websites that place the curser in a field, which can be a little annoying (for example, Google)
3) The hardware buttons like Zoom +/- and fullscreen don't work (but using the menu to do these functions does)
4) The scrollbar is really jumpy and stutters a lot

Re: WebKit engine for default browser
 

I uploaded new webkit-eal package (0.0.6)

fixed problems with links opening in new window
now entering string in url field that doesn't look like url will launch google search, if it looks like web address, then http:// or ftp:// will be prepended automatically

iskarion,
now I'm trying to rebuild microb engine and then will try to update its javascript engine with latest from FF 3.1b to see how fast is it. it seems that to update engine isn't hard but I'm getting different strange errors when building even default microb-engine package

BrentDC,
I'll check issues with keyboard (I always use hardware keyboard on n810)
hardware buttons work when input focus is on browser (not web page), eg. on url field.

Re: WebKit engine for default browser
 

That's strange. For me, on my N800, the only button that works (albeit extremely intermittently) is the menu key. The zoom and fullscreen buttons are totally dead; it doesn't matter where the focus is (field, image, window, etc.)

Keep up the good work!

Re: WebKit engine for default browser
 

BrentDC, really strange. but in any case this is still need to be fixed in proper way so I hope it will then work on any model

Re: WebKit engine for default browser
 

Fullscreen, zoom, esc, and menu are all dead on my n810 too, but it does not matter, other keys are ok.

pronvit, you are GENIUS! :D

Google Reader was painful to use with old engine, now it is really fast and useful, 12 times faster i would say ;)

EDIT: All hw keys are now working... (maybe something to do with multiple windows?)

Re: WebKit engine for default browser
 

Meanwhile I figured out how to enable Tracemonkey for Fennec Alpha 2
http://www.internettablettalk.com/fo...0&postcount=16
With Tracemonkey enabled, the Javascript performance is quite comparable to Webkit.

Re: WebKit engine for default browser
 

Thank you. This bug was very annoying to me.

Re: WebKit engine for default browser
 

Great to see downloads, but not popping up the on-screen keyboard for password fields is a show-stopper for me and my n800 currently (although I do plan on purchasing a bluetooth keyboard...). Rendering random pages seemed to work well, though, and way faster than microb!

Re: WebKit engine for default browser
 

All I can say is: WOW, great job:D
With the default engine for example engadget took forever to load, webkit is much faster. I hope we will see this on Pandora one day.

Re: WebKit engine for default browser
 

I installed your packages to test them out. I installed this with "sudo dpkg -i package1 package2 package3" in the terminal; the less hair-raising alternative to "red pill mode".

This is a nice package. I really like that you've made it easy to switch between browser rendering engines. (Although it would be nice if the little app for that was listed in the Control Panel instead of the main menu).

Awesomely fast! With the old Gecko engine, it was EMBARASSING how long it took to load the locally stored home page. With the webkit engine, that page is rendered and usable much more quickly. Google maps operates better, too, although Street View doesn't seem to work. (Just gives a grey box).

The lack of finger scrolling so far isn't too bad. I'm liking being able to select things so easily. (Although I wouldn't mind having finger scroll back).

The widget with the web page hoardes any events sent to it, so key events like Fullscreen and Menu, even though unused, do not make their way out to the parent widget while it is focused. Widgets which do that are a pet peve of mine ;)

Again, this is astoundingly great. Practically seamless, too. Fantastic work. If not Main, may this hit Extras with grace and dignity!

Re: WebKit engine for default browser
 

seems i may have overestimated the bulk of libicu.

have it all installed now, and throwing engadget or cnet at webkit is kinda fun to watch. what takes longest is the darn adds ;)

Re: WebKit engine for default browser
 

Great Job.

Zoom keys and full screen switch doesn't work.

Re: WebKit engine for default browser
 

Thank you for all your good words, I'm glad you like this project. Now I'm trying to fix found problems, will post update when it's done.
And happy holidays!

Re: WebKit engine for default browser
 

Please also consider releasing the source! Personally, I doubt there's much I could do with it, but I'm sure some others would be happy to continue and expand on your work to make this even better!

Re: WebKit engine for default browser
 

Hi pronvit,

I'm loving this. It's awesome so far.

Is it me or is Flash even playing faster which would make no sense to me? I'm rewatching youtube videos again and there IS less to no frame skipping. I uninstalled some stuff to free up space before installing webkit so this could be the reason for the difference. A flash benchmark will reveal the truth.

Here are my findings on the problems:
1. It crashes most every time a page is loading and I click the stop icon. when I try to browse after stopping is when it crashes.

2. when typing like I am right now, I have to hold the shift or ctrl button while typing a letter or upper case letter. I can't just click the shift key, let go, then type the 'i' key to get a capital 'I'.

3. I have to click either the inner browser window or the outer frame to get certain things to work. If I want the min/max to work I have to first touch the outer frame or the min/max will not work. If I want my scroll hardware to scroll the page up or down I have to first give focus (touch) the web page first.

4. If I scroll down to the middle or bottom of a page and then click through to another, the scroll bars are left where I was on the previous page. ie half way down, etc.

5. I can't shut off flash. I personally have it off most all of the time to save processing time, memory and not see stupid advertisements.

6. Wherever I browse, within a website, the url does not update page to page. So on internettablettalk I am still showing as being at the main url even though I am on this thread.

Thanks again and I hope some of this helps.

Re: WebKit engine for default browser
 

http://mifki.s3-external-3.amazonaws..._0.0.6.tar.bz2
http://mifki.s3.amazonaws.com/engine...mifki1.tar.bz2

webkit itself from nightly builds page, in browser-daemon only preloading microb engine removed, browser-eal and microb-eal updated to latest versions without changes

Re: WebKit engine for default browser
 

Question!

How could you compile webkit nightly version R39370 on scratchbox?
When I tried, I got this error message in the configure step.

To solve this problem, I compiled and installed bison 2.4 on scratchbox.
Finally I passed this problem, and then completed configure step.

But in the compile step, I got new error message.

How could you solve this problem?

Re: WebKit engine for default browser
 

You need bison 2.2, its not working with bison 2.4. I had the same problem before.

I have 39474 compiled and working if someone wants it (and with more features enabled). 100/100 on Acid 3.

http://bundyo.org/maemo/webkit/libwe...9474_armel.deb

And dev:
http://bundyo.org/maemo/webkit/libwe...n39474_all.deb

Thanks to pronvit for hinting me that my builds were working from the beginning and the problem was in my TV. :)

Re: WebKit engine for default browser
 

yes, use bison 2.2, sometimes newer doesn't mean better:)

Re: WebKit engine for default browser
 

Bundyo, open WebCore/platform/network/curl/ResourceHandleManager.cpp and replace m_cookieJarFileName(0) with m_cookieJarFileName("/home/user/.webkitcookies") for cookies to work. I can't find way to set this from outside

Re: WebKit engine for default browser
 

Reuploaded them with the cookie fix.

Re: WebKit engine for default browser
 

Thank you very much! :)
I will try it!

Re: WebKit engine for default browser
 

Webkit does not support perpect cookie handling yet.
Refer this link :
https://bugs.webkit.org/show_bug.cgi?id=14730

Re: WebKit engine for default browser
 

yes, but with my small change it works fine, libcurl does everything.

Re: WebKit engine for default browser
 

Spent two days trying to recomplile microb-engine (mozilla) with their new javascript engine.. I thought it will be easier to add fast engine to microb than implement everything in webkit (downloads, finger nav and so on)
But it seems to be impossible. Their code is too weird. So now I'll finally do my primary job and then continue to work on webkit. bye-bye mozilla..

Re: WebKit engine for default browser
 

Please try my new version. It's somewhat experimental because I implemented finger scrolling in unusual way.

The problem with finger scrolling is that (without hacking webkit) I don't know if motion event will be handled by javascript on the page (for example to pan google maps, to select text (however this isn't javascript-related)) or I can use it for scrolling. That's why simple implementation when any tap+move = scroll is very bad.

Instead of this I reserved 100px scrolling areas in right and bottom parts of window. So when you tap and move near right edge you will scroll vertically, and near bottom edge to scroll horizontally. Moving in remaining window area will pass this events to page for handling in javascript. So think of my implementation as of wide invisible scrollbars. Btw, I removed default scrollbars.

For me such solution is quite convenient. Try it and tell me what do you think.

Oh, download link: http://mifki.s3.amazonaws.com/webkit....0.7_armel.deb

upd. Fullscreen/zoom keys now should work too!

Re: WebKit engine for default browser
 

i just managed to download that first version, but now im looking at a access denied error. like the scrolling solution tho. seems one can do scrolling on the whole page as long as one drag out of one of the "zones"...

see a fair bit of tearing while scrolling tho...

Re: WebKit engine for default browser
 

fixed dl link.

Re: WebKit engine for default browser
 

thanks, really love the scolling as i get used to it.

just need some small indicators about where in the page one have scrolled...

Re: WebKit engine for default browser
 

have one idea about this but don't know yet how to implement, will try

Re: WebKit engine for default browser
 

played around a but and the page tearing seems to mostly happen when browsing this very forum using the minimalism theme...

and when can we expect password inputs and full screen keyboard to work?

im tempted to say that i want to use this as my main engine already! :D

Re: WebKit engine for default browser
 

New version is here with several important changes!

First of all, problem with onscreen keyboard and password fields finally solved (but no fullscreen keyboard support yet). Also some problems with switching hardware keyboard language fixed, hardware menu and back buttons fixed.

I had to add some changes to webkit library itself and to avoid conflicts with other versions (eg. provided by Bundyo) I now install my own version of webkit in webkit-eal package. So you can remove libwebkit package or install whatever version you like and it won't interfere with my webkit engine, just update webkit-eal, everything is inside.

webkit-eal_0.0.8_armel.deb

Forgot, url field now correcly updated when navigating.

Re: WebKit engine for default browser
 

Hmmm... it doesn't seem to work anymore.... Installed webkit-eal 0.0.8, switched engine, but browser just shows a blank window when opened, and I can't get to any websites...

Re: WebKit engine for default browser
 

Hmm.. maybe I broke something....
try reboot device or in terminal run '/etc/init.d/tablet-browser-daemon restart' as root

Re: WebKit engine for default browser
 

Same here, browser window just stays white. Restarted browserd as root and got:

Re: WebKit engine for default browser
 

Same issue here, reboot does not resolve it.

Re: WebKit engine for default browser
 

what
ls -all /usr/lib/libw*
will output?

Re: WebKit engine for default browser
 

Output of that command: