Re: WebKit engine for default browser
 

When selecting the webkit engine, the browser locale seems always to be english.

With the microb default engine many websites automatically show me a german user interface. I guess in this case the browser selects the locale based on the system settings.

With the webkit engine such websites show the english user interface. Any way to change the browser locale for Webkit. e.g. via gconf?

Re: WebKit engine for default browser
 

holy moley, i am impressed. this is way faster than the default browser engine, kinetic scrollings rocks aswell! the official maemo developers should definitely look into this.

Re: WebKit engine for default browser
 

ok, I'll make it honor system locale. and will think about how to implement simple adblocking, don't like ads much too.
have to do some other things now so have less time to spend for this project

Re: WebKit engine for default browser
 

Oh, I forgot to toss my thanks for the kinetic scrolling. Particularly in the simpler web pages, it feels swell!

Re: WebKit engine for default browser
 

i would say that noscript has a interesting way of "blocking" ads. basically, do not allow external scripts to run.

that, in combo with the ability to turn of flash should kill most ads...

Re: WebKit engine for default browser
 

I likely will just match everything webkit tries to load against patterns stored in gconf - easy to implement and flexible.

Re: WebKit engine for default browser
 

Updated to latest version. This works really smooth. Just downloading some files doesn't work. I often download waypoint files from http://www.geocaching.com/ so the download link is a button.

Re: WebKit engine for default browser
 

is there a collection of gconf settings that will bring back the scrolling areas and the instant selection?

Re: WebKit engine for default browser
 

you can open gconf editor and select show key documentation in view options. then go /apps/osso/browser/webkit and you'll see avaiable values for keys.

for example fingerscrolling=1 for scrolling areas

Re: WebKit engine for default browser
 

i keep forgetting that "gconf" is registry "done right" ;)

Re: WebKit engine for default browser
 

First, this is incredible and I'd like to profusely thank pronvit for the great work. Browsing on the tablet at this speed is amazing; switching back to gecko makes me want to bang my head against the wall it's so slow. I'm definitely using this as my primary browser.

That said, in gconf the available settings appear to beIs this the full list of available options? Specifically is there a key to change zoom mode to true zoom instead of font size?

Also, before I started monkeying with gconf, using kinetic scrolling was beautiful and perfect, but now it seems to not cache offscreen areas of the page (i.e. until scroll stops moving, all that appears in the newly exposed region is a finely tiled image of whatever used to be on the bottom of the screen). This behavior continues even after resetting all gconf keys. Any idea why this happens or how to fix it?

Thanks again pronvit for all your hard work -- this is by far one of the best enhancements I've come across for the NITs

EDIT: Hmm, this didn't work the first time, but a reboot after --recursive-unset appears to have fixed the problem, and now I am able to set scrollbars=0 and kscrollfading to 0.95, which are IMO ideal. This is awesome.

Re: WebKit engine for default browser
 

currently there's no option to change zoom mode. I just didn't think it may be useful. I will add it if it is useful for you.

Re: WebKit engine for default browser
 

I installed webkit-eal from the garage page a few days ago on my n800 running diablo, and although I can open local pages it crashes every time I try to access a webpage. What kind of debug info can I give to help?

Re: WebKit engine for default browser
 

crazy question but how can I tell if the default browser is using webkit?

Ive followed the only obvious install instructions on post 133 but cant see anything alter.

Re: WebKit engine for default browser
 

Just go to http://acid3.acidtests.org : if the score is around 94, your are using webkit !

Re: WebKit engine for default browser
 

also, when a page loads, the loading bare will show percentage, not number of elements downloaded.

oh, and if webkit crashes for some reason, browserd will reload the page in microb, and continue to use that until all browser windows are closed.

another way to see if your using webkit is the frame around tapped links. in webkit it will barely be visible, but in microb its a solid frame.

and i think by default the start page on a empty browser window is different in webkit also.

now, i would love for the selector app to use radio buttons and a ok button rather then the drop down list it uses right now. that or have the drop down list show the currently used engine when started.

Re: WebKit engine for default browser
 

Did you already restart your tablet after webkit-eal installation? I had the same propblem after the first install until I did do a restart.

Re: WebKit engine for default browser
 

Whoa... this is impressive! Installed the deb, rebooted, and I'm flying where I used to crawl!

Re: WebKit engine for default browser
 

luck indicated that the tearing issues could be that webkit is redrawing the page faster then the lcd can fully update.

maybe something to look at for a more smooth experience?

Re: WebKit engine for default browser
 

Having used this awesome webkit package for a while now I thought I would post what I have noticed. I am not posting all the amazing good things because they have already been pointed out.

First I would recommend radio buttons, or icons for the engine chooser as tso mentioned above. Second, I noticed that it does not respond to hardware buttons initially. I usually just minimise and then restore and then it will. Third, there are still issues with the thumb keyboard. When typing this post, a return closed the keyboard instead of sending me to the next line. There was one other thing that has slipped my mind. If i think of it i will post it here. Overall i am very impressed. If downloading worked i think it would eliminate my need to ever change the engine back to microb. Hope this is helpful and keep up the good work!

Re: WebKit engine for default browser
 

Just a question does local database storage is enable in this version of WebKit (a part of HTML5 specs) ?

Re: WebKit engine for default browser
 

That did the trick. Pronvit: If this step is inevitable maybe it is an idea to show a popup after installing Webkit telling to reboot?

Even though I like the speed increase of Webkit I will keep using Gecko/Microb for a while because I've grown dependent on these things:

- minimum font size
- dpad key scrolling (smooth scrolling whole pages)
- custom stylesheets
- set location bar to a custom search engine string
- make cookies session only for privacy

I made the Speeddial script. There are some Mozilla specific bits in there (the xml dom functions) that can be changed to work with Webkit. So if there is demand for it I'll give it a try.

Re: WebKit engine for default browser
 

on the button respone, its as simple as tapping inside the actual web page. its an annoyance the first time round tho, i agree.

Re: WebKit engine for default browser
 

Sounds like you need an intervention. ;)

Re: WebKit engine for default browser
 

Hum ... i ll try to install and try to not reboot :)

I think a simple sudo /etc/init.d/osso-browser restart should do the trick :)

Re: WebKit engine for default browser
 

no. I disabled all html5 features and svg. I'm not sure this is right. and also I don't know how much this affects speed/memory usage, but they are useless _for me_ and I disabled them hoping this will make it faster/smaller. if somebody needs them I'll recompile with these features enabled for you.


for everybody: sorry I'm not answering everybody personally but I read and take into account all your ideas and bugreports for next versions.

Re: WebKit engine for default browser
 

Just want to post a thank you to pronvit for the hard work and the easy to install deb. This exactly gives the NIT web browser a good kick in the butt.

I can confirm this, long feeds from Feedcircuit (over 100 entries containing pictures and links) load much much faster than before. In fact, it was almost painful to use for that specific feed.

The kinetic scrolling is great, since I do a lot of one-handed browsing of these long Feedcircuit pages. My thumb would get tired very quickly. Would there be any way to adjust the scroll acceleration? I'd like it to keep scrolling just a tiny bit further with a quick flick :)

Thanks again!

Re: WebKit engine for default browser
 

One more thing, webkit seems to accept inputting Japanese characters into textboxes with maemocjk. The latest SSU seemed to break that functionality for me with MicroB. (ie: type Japanese into the Google search text input box)

Re: WebKit engine for default browser
 

please read this post http://www.internettablettalk.com/fo...&postcount=209

for example try to change kscrollstep from 20 to something less or better change kscrollfading from 0.9 to 0.95, try different values (you have to reopen browser window after changing values)

Re: WebKit engine for default browser
 

By the way, because I removed ICU library dependency, there may be some problems with complex encodings (like Japanese, especially right-to-left languages), if you notice something please send me message with address of page with problems

Re: WebKit engine for default browser
 

http://maemo.org/downloads/product/OS2008/gconf-editor/ seems to be dead.

Is there a way to manually edit it?

Re: WebKit engine for default browser
 

http://repository.maemo.org/extras-d...emo1_armel.deb

sorry I turned on all maemo repos and didn't notice that gconf-editor is in non-default extras-devel

Re: WebKit engine for default browser
 

Thank you,

turned out right for me.

After playing with the settings a bit, the screen started to tear on kinetic scrolling, even when I reset the values back to their original number.
fixed the scrolling.

Re: WebKit engine for default browser
 

I'd be very glad if the following keyboard shortcuts implemented:
CTRL-W close window
CTRL-R reload
BACKSPACE back in history
PAGE_UP entire page up
PAGE_DOWN entire page down

I know there are more, but these are the ones I use the most. Thank you again, I just tried his today for the first time, and it is excellent!

Re: WebKit engine for default browser
 

never understood the use of backspace for going back in history.

one accidentally unfocused input box is all it takes...

Re: WebKit engine for default browser
 

alt-left makes the most sense to me for going back in history, and alt-right for going forward, of course.

slightly off-topic: i had a keyboard (IBM, i think) with "back" and "forward" buttons just above the left and right cursor keys. they just sent alt-left and alt-right signals--no special drivers necessary. it was convenient for 3d shooters before mouse-look became ubiquitous, because i could use those keys for side-stepping.

Re: WebKit engine for default browser
 

unfortunately I can't determine if input box is currently focused (need to find out how to do this and modify webkit for this) so no backspace for now. other shortcuts will work in next ver.

Re: WebKit engine for default browser
 

So no need to reboot, just restarting browserd daemon and close all web page open.

It s seems you use an old version of webkit as it doesn't support opendatabase html5 api.

and other question ... how to set the user agent ? it doesn t support about:config ... and see no conf file in common place ... nor with gconf.

Thanks

Re: WebKit engine for default browser
 

hmm.. browserd is restarted during installation, strange that you have to do this manually

I already wrote about disabled html5 above. hm.. I can add config parameter for user-agent if you need it (situation is simple - no settings for things I never use)

Re: WebKit engine for default browser
 

I installed under Blue Pill mode, and had to restart the tablet. Maybe if you install with Red Pill this will automatically work...