Re: WebKit engine for default browser
 

I just finished reading every single post and I am very excited. I am relatively new to really configuring my n800 to work how I want it to. I like having the options, but I can't help but think the average end user would be quite intimidated by all the tinkering and patience involved. microB is ok, but has some almost intolerable speed and navigation problems IMO. Here is what I have as far as questions/suggestions

To install, is the first post updated with the latest method and files? To me it doesn't look like it is, just because of the date on it, but the files it links to could be updated without the post being updated. I got a bit confused after reading everything of what files to get, which red-pill to take, if I actually need the drugs, and if I need to configure a bunch of options on it when I do install it. If it is not updated could I suggest editing it so that it links to a separate page that is the most current. The more time users are allowed to use the software the faster they can give you feedback and the development can be sped up.

Would it be possible, make all the options configurable similar to in firefox when navigating to about:config? Then restart the browser and all the newly configured options are enabled. Could this be used to make it easy for the user to enable/disable scroll bars, disable/enable webkit?

I also like the idea of "keybinds" for lack of a better term, that use taps in combination with hardware keys, but I think there should be a simple way for the user to define them.

When using the virtual scroll bar version, is there a way to click on links that are under the virtual scroll bar? Maybe this is not an issue, but since my n800 is out on repair and I cannot try for myself just yet, I can only guess what it looks and how it functions. Speaking of that, could someone post a current screen capture? I would like to see what it looks like :)

One more thought. Could there be a way to make the address bar etc. on the bottom either semi transparent or only visible when I am at the top or bottom of the page? Then if it was easy to set the virtual scroll bar so that a double tap on the very top or bottom brings the user back to the address bar, much real estate would be gained.


Sorry for the novella length post. I like how this discussion is going and hope it continues. I think you are really on to something good and I would like to help if I can.

Thanks for the hard work and effort!

@ tso, n800 4ever. You can have my pop out camera, but you'll have to pry my dual full size SD slots from my cold, dead hands ;)

Re: WebKit engine for default browser
 

I update first post always and links are to latest version. Yes, I know, installation is somewhat complicated. But there's one reason for this which I can't fix. Don't want to write much technical details here so I'll just say that (thanks to Nokia) default microB engine is hard-coded in browser daemon and its startup script. So to use my webkit engine you have to install several fixed packages. They are system packages and application manager will allow to install them only in 'red-pill mode'. That's only reason why installation is so complex and I currently don't know how to fix it. (There is one not so good solution, maybe I'll try it.)

Not sure that using about:config but all options will be configurable in next version. Currently there's already separate application to easily switch microb/webkit.

Of course, links can be clicked.

I almost can't change anything in browser ui because it's closed-source, but for address bar I see one solution, I'll try.

Re: WebKit engine for default browser
 

On the latest OS2008, libicu40 is installed. Why don't you build against this version?

Re: WebKit engine for default browser
 

Are you sure? I don't see it.

Re: WebKit engine for default browser
 

Strange, I could swear it was installed 2 days ago :)

Re: WebKit engine for default browser
 

red pill mode seems to show today i was doing clean up it was there will check again

Re: WebKit engine for default browser
 

libicu40 is in Diablo Extras-devel. If he builds with this version, it won't work with Chinook one, while with 38, 40 should work as well.

Re: WebKit engine for default browser
 

Not installed, but available @ diablo extras-devel

Re: WebKit engine for default browser
 

changing 38 from chinook extras to 40 from diablo won't help much

in any case I applied (and finally fixed bug in it) anti-icu patch so next version won't depend on libicu at all

Re: WebKit engine for default browser
 

Yeah, seems its possible to replace it with GLib:

https://bugs.webkit.org/show_bug.cgi?id=15914