Tear 0.2 - a simple maemo WebKit browser.
 

Hi guys, I'm back and in need of testing :) So, here's a 0.2 version which has bookmarks and history, but crashes sometimes and i need to find out what causes it. Also if it appears stable anyway, I'm focusing now on getting a newer WebKit build run on the tablet (the one in extras is too old and is built with libssl-0.9.7 which i guess causes the https not working).

Also the code is in garage SVN now, feel free to abuse it. :) Needs the included VAPIs to compile and Vala 0.5.2.

New things in 0.3 /not yet uploaded to garage, need some feedback/:

• WebKit 39752 + fixed password field input method (edit in invisible mode) + libicu dependency removed (you can uninstall it) + web inspector files included in deb. Get it here and dev package here. Now requires only libidn11 which is 110k
• Tap and hold menu doesn't persist after clicking on element.
• Web inspector can be opened from right click menu.
• Changed when sqlite3 is used, using temp memory views for selects. May be still crashy, hopefully less. Made some major changes this morning and didn't test it much.

New things in 0.2.2:

• Tap and hold menu - still doesn't contain anything too useful :) Also shows up when clicking on links - annoying, I know.
• Info Banners for Zoom operations.
• Zoom to 100% in View menu.
• Kinetic scrolling is harder to trigger (10x10 dead zone).

New things in 0.2.1:

• Requires newer WebKit build - either pronvit's or my newer build.
  libwebkit requires libicu38, which is quite big and can be found here:
  http://repository.maemo.org/extras-d...emo1_armel.deb
• Zoom In/Out enabled.
• Kinetic scrolling /implemented by Ignacius/.

New things in 0.2:

• Initial implementation of Bookmarks (no editing or deletion).
• History completion and drop-down.
• Google search if no address punctuation.
• No Javascript and no images switch.
• Hid the not-yet-working menu items.

Known issues:

• Crashes sometimes. Sqlite suspected and still trying to fix it.
• The menus are common for all windows, so Full screen, no js and no img toggle menu items are not indicating the real state.

Screenshot:
http://bundyo.org/maemo/tear/tear_acid3.png

http://bundyo.org/maemo/tear/tear_webinspector.png

Download in Garage /0.2.2/:
https://garage.maemo.org/frs/?group_...elease_id=2308
Download from my site:
http://bundyo.org/maemo/tear/tear-0.3-1_armel.deb
110k/215k

P.S. Not Extras-devel ready yet in my opinion, and I probably won't be able to upload it with the auto builder anyway. Andrew, does your mud-builder support external vapis?

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Thanks! Wouldn't it be a better idea though to port an existing browser that uses WebKit, and QT based since that is the future of the tablets? That way we could use existing plugins/extensions and the like.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Latest Webkitgtk supports ns plugins, and we don't know if QT is the future :) Yet.

Desktop apps in my opinion are not very well suited for the tablet, they work, but they need quite a bit of tweaking to fit in the screen. Plus as I mentioned in the other thread - I'm not very proficient with C :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

downloaded, will be trying it out.

hmm, only chinook extra held the correct webkit lib...

ugh, that webkit version is a bit to large for me right now :(

btw, it seems the deps on the package are a bit broken. even with the right repo active, app manager refuses to install it...

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Yes, there's no other for now.

BTW, some icons are missing. Fixed.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I'm not sure where you're getting your information, but Qt certainly isn't 'the future of the tablets'. If anything, the platform will support both.

Besides, even if you were correct about the 'future', it's at least a year away, if not more like two. . . .

Re: Tear 0.2 - a simple maemo WebKit browser.
 

libwebkit 1.0 is in the Debian repos; that's what Midori is using... Have I mentioned how much I like Midori yet? ;)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Um, what exactly do you like about Midori? :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I should have said 'seems to me' because it was just my own impression, no special sources involved. And also, especially after buying Trolltech, standardizing on one widget set seems to be more economical for Nokia. Has Nokia stated to suppport both for the period you mentioned?

Re: Tear 0.2 - a simple maemo WebKit browser.
 

QT will be added officially in Harmattan (at least 2 years from now), QT4 libs will be installable in Fremantle, but not officially supported. In Harmattan GTK and QT are meant to coexist, Nokia will decide if to drop GTK support after that, but i doubt it.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Whoa! I'm just wondering to contribute. In summer I made some programming with vala and webkit to make a browser for maemo based on webkit but since I had a x64 ubuntu installed I was unable to make the sdk work. Now I installed a 32 bit Ubuntu. I have some ideas i would like to share with you.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Okay, go ahead :) Do you want write access? Or just ideas? :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

juergbi was saying on #maemo that he was going to look at the build script in mud and updating them for the newer versions of libgee & vala.

Then, it should just be a case of ensuring that vala is in your Build-Depends. I've not yet seen how Vala is supposed to handle additional vapis which aren't installed in the system-wide folder.

Worst case: you should be able to bundle them with your source?

Re: Tear 0.2 - a simple maemo WebKit browser.
 

They're already in Garage SVN, i didn't specify them explicitly in the build script, but maybe i should.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I haven't write any code yet so svn write access doesn't matter so much. I've been watching the code and I see you are storing the bookmarks on a sqlite database. I think It would be better if we integrate with maemo's bookmarks. Some time ago, I send an email to the maemo-developers list if there was some way for accessing the bookmarks. As it seems, the piece of code for doing this is closed source and Nokia isn't providing any specification for accessing it. Fortunately, the file (/usr/share/bookmark-manager/bookmarks/MyBookmarks.xml) where they are stored, it's an xml and complies with the xbel standard, so it shouldn't be so difficult to write some library for accessing them. Related to this, I would like to see some support for plugins to add bookmarks support so we can later add del.icio.us and related sites support, or send a link through IM, email or even sms.

I've been trying to compile webkit svn version on maemo's sdk but it doesn't make for me. It should be great if webkit-gtk developers can fix it, and even more wonderful if they can add support for finger navigation if hildon extensions are activated at compile time.

Eventually, I think I would start writing a lib in vala for accessing xbel files.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I'm planning on including plugin support, since it shoud be quite easy in Vala. As for MicroB xml bookmarks - if they comply to a standard, isn't there already some C lib to support it and we can just create some bindings for it (if there are none already)?

I also didn't have any luck with latest webkit commpilation - of about a dozen revisions i've tried, only one compiled, but javascript engine crashes on any mention of js in the page. Still trying though, since the march one doesn't have zoom and can't retrieve favicons from it (i want to add them in the history lists). The favicon issue can be worked around, but the zoom is needed.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

For what it seems, there isnt any lib in c for accessing xbel files. Also, Midori has an internal implementation we could use. Favicon icons should be necessary also for bookmarks.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Probably, it is libxml based anyway.

XBEL Documentation (not too big):
http://xbel.sourceforge.net/language...ment-structure

SQLite will probably be faster and more memory efficient than internal XBEL implementation, maybe some syncing with MicroB's bookmarks and also other sources will be best (like delicious for instance). Of course, you can prove me wrong :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Thanks for Tear! Looks great and renders fast on my N810 with Diablo. Much better than MicroB, and it didn't crash yet.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

You are right that probably using sqlite would be more memory efficient than xbel approach. Also, I'm thinking on refactoring the code so we could replace the bookmarks backend without much effort if we at some point in the future want an xbel backend. This would also make easy to make providers for del.icio.us and so. I'm going to send you my email so we can contact each other easily. Should we make a ToDo list so we know what to work on, without overlaping each other?

Re: Tear 0.2 - a simple maemo WebKit browser.
 

It seems I can't send you a private message, so my email is pvaneck AT gmail.com

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Could you post a link to libwebkit for me, please? When I search for it on google, the most I don't understand, I'm not so familiar with linux;)
TIA

Re: Tear 0.2 - a simple maemo WebKit browser.
 

@Ignacius: okay. I'll send you a mail later.

@derhorst: It's in Chinook extras-devel repo, e.g. here:
http://repository.maemo.org/extras-d...emo1_armel.deb

Re: Tear 0.2 - a simple maemo WebKit browser.
 

This browser looks promising, but I've got only one problem so far--
Installing it.

My device only has about 10mb free, yet libicu38 requires 14mb after unpacking... is there any way around needing libicu38, or should I just try to make more space?

(hmm, that aufs kernel isn't looking so bad right about now...)

Thanks ahead of time!

Re: Tear 0.2 - a simple maemo WebKit browser.
 

libicu is required by WebKit for Unicode support, sorry :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Libwebkit is moaning about not being compatible:( I use the latest diablo. I've added the chinook extras in app. manager back in the days when diablo came out.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I did install it from xterm, but there were no problems with compatibility.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I can only confirm what derhorst say...
"Unable to install libwebkitgtk-1.0.
Incompatible application package."

Re: Tear 0.2 - a simple maemo WebKit browser.
 

iirc, thats app manager talk for the package not being in the "user" subgroup...

Re: Tear 0.2 - a simple maemo WebKit browser.
 

...which, iirc, means "apt-get install" or the evil "RED PILL".

Re: Tear 0.2 - a simple maemo WebKit browser.
 

I think it is in user/other...

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Very nice, after this is updated to the newest webkit, and there is touch scrolling, it is going to kick MicroB's a55....

No real stability problems so far, faster than MicroB.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

There is touch scrolling in SVN, added by Ignacius, however didn't release it until I got fixed the sqlite3 problems and get a newer WebKit running (which i couldn't yet). My recent job change is leaving me with even less time for that unfortunately. :)

The stability problems show up after a while. :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Releasing an update which requires the new WebKits and has zoom and kinetik scrolling. Look in the first post.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Wow! Kinetic scrolling works pretty well! Only, it doesn't seem to distinguish betwen a tap and a scroll, so every little tap on the page (even to stop scrolling) moves the page a little. I also experienced enough random crashes while trying to scrol to make it unusable for me... The only command line output: If you need me to run any more diagnostics, let me know. I am using your compilation of webkit.

As for zooming -- either add a "Zoom to 100%" option, display a "100% zoom" notification when it's reached, or do both. Other than eyeballing it, there's currently no way to see if 100% zoom is reached. I would also put the zoom options under view in the menu, in addition to their current location.

Lastly, with my n800 and its on-screen keyboard, I'm unable to enter passwords in password text boxes. This kills quite a few websites (here, e-mail, etc...)

Overall... with a few annoyances fixed, I'd gladly use this instead of the built-in browser!

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Thanks for the update. I like Tear a lot :)

I keep getting "incompatible application package" when trying to install the new webkit library. I guess I'm doing something wrong... any ideas?

Re: Tear 0.2 - a simple maemo WebKit browser.
 

dpkg -i is your friend ;)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Thanks. It worked!

IMHO it is the BEST browser for the tablet.
I am heavy Midori user but always kept an eye on Tear...

It certainly got to the point were I choose it as my primary browser.

I love the kinetic scroll (though it is a bit too sensitive at the moment). The zoom is a huge advantage over Midori and it zooms in/out instantly (much faster than microb).

Pages are being rendered blazing fast (I LOVE WebKit) and I finally can see RTL+Unicode perfectly!

Thanks !! :)

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Its still unstable after some use :( I hope to fix that soon.

Re: Tear 0.2 - a simple maemo WebKit browser.
 

Tear is a really great addition to the NIT! I have one problem. Some links just don't work in tear.

Example: my.yahoo.com - sign in link in upper right corner of screen won't work
Example: www.google.com - same thing, dead sign in link in upper right of screen.

Really looking forward to seeing this develop! Thanks & please keep up the great work!