maemo.org - Talk - Tear 0.3.1 - a would be beta WebKit based browser

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - Tear 0.3.1 - a would be beta WebKit based browser (https://talk.maemo.org/showthread.php?t=28539)

Re: Tear 0.3.1 - a would be beta WebKit based browser

Hello,

Great browser. Fast and easy to use!

I uninstalled on accident and now am unable to reinstall. I am told that the package is missing libpcre3. I tried to install libpcre3 and am told that it is not compatible. I'm stuck!

Any ideas?

BTW I read Sondjata's post. How did you get it to work? Thanks!

Re: Tear 0.3.1 - a would be beta WebKit based browser

I just tried tear using no scrollbars and I agree with the above poster , its great! Would it be possible to add an option to invert scrolling? Meaning whan dragging on the page from top to bottom it will make it scroll down, the same for left to right also.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by Bundyo (Post 307339)

Loading which homepage at launch? Custom?

Yes, the one you define in Options, or Page/Set Home Page.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by lschumanfcoe (Post 307394)

http://repository.maemo.org/extras/p...sso1_armel.deb

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by Bundyo (Post 306888)

Okay, 0.3.5 is out along with libwebkit 41137-13, check the front page for more info.

Thanks for the new version. Next time you update, as well as updating the front page, could you post the changelog in here as a new post? That way, people who are already following this thread don't have to skip back to the first page, and it would make the conversation flow a bit better.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Any plans to implement Flash- and adblocking features in Tear?

For mobile use (esp. for those with tethered and metered data plan) the ability to block bandwidth-wasting elements can be extremely useful, but everyone may sometimes wish to keep CPU (and therefore battery) wasting fluff at a minimum.

Quick googling showed that there are some scripts or CSS "user styles" being used with Midori, which is likewise based on WebKit. Could any of these be used with or adapted for Tear?

FlashBlock for Midori (WebKit)

FlashBlock WannaBe

AdBlock in Midori!

The Midori FAQ also lists some user styles and scripts.

And another script, BlockFlash2

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by lschumanfcoe (Post 307394)

I kept activating and deactivating Maemo Extras Dev until Tear 0.3.5 showed up (previously grabbed it directly from the source) until the error went away. I try not to keep Extras Dev active.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by Peet (Post 307474)

Hmmm..If any of these work, perhaps it will deal with that whole memory hog issue I have with Tear. Anyone try any of the above?

Re: Tear 0.3.1 - a would be beta WebKit based browser

Thanks, still says it's an incompatible package, but I appreciate the help anyway! I will next try Sondjata's suggestion....

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by lschumanfcoe (Post 307480)

Thanks, still says it's an incompatible package, but I appreciate the help anyway! I will next try Sondjata's suggestion....

I also did an apt-get update from the terminal

Re: Tear 0.3.1 - a would be beta WebKit based browser

Well, I disabled and enabled the extras-devel repository several times and no go. Oh well, thanks anyway!

Re: Tear 0.3.1 - a would be beta WebKit based browser

Is there a FAQ for Tear that's more detailed than the Tear page on the wiki? I want to ask some questions about Tear but don't want to repeat what's been asked and answered. However, it's not likely that I'll read all 70+ pages of previous messages.

Re: Tear 0.3.1 - a would be beta WebKit based browser

talmage, I think you want to do a search on this thread and also (if relevant) the bug tracker or (failing that) this forum. Doing a search will hopefully narrow down the things you'd need to read.

Re: the wiki page, my goal was to be mostly friendly toward noobs, but still document many of the questions & issues that come up over & over (some of which are pretty technical). So if you find the answer to your question, please feel free to add it.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by pelago (Post 307424)

@Bundyo:

Or worst case, how about a link in your signature. Dude, you're a rock star, deal with it.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by daperl (Post 307551)

@Bundyo:

Or worst case, how about a link in your signature. Dude, you're a rock star, deal with it.

I would prefer this approach. This is a bit anal, but if you have the same information in two places and it later gets corrected, it either has to get corrected in two places or one of them goes out of date.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by buurmas (Post 307544)

talmage, I think you want to do a search on this thread and also (if relevant) the bug tracker or (failing that) this forum. Doing a search will hopefully narrow down the things you'd need to read.

buurmas, I did search the thread and didn't find anyone asking my question. Same thing for the bug tracker. What I observe about Tear happens every time I use it. I can't believe I'm the only one who sees it.

If searching doesn't reveal an answer, then I guess I'm free to post.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Now go here and replace your /etc/hosts file:
http://pgl.yoyo.org/adservers/
And it's nearly equivalent to microB.
...but what about greasemonkey? That would be cool...

Re: Tear 0.3.1 - a would be beta WebKit based browser

There will be userscripts support at some point.

Re: Tear 0.3.1 - a would be beta WebKit based browser

This new -2 version is very solid on my N800. I'm already using it more than the stock browser.

One thing that has always bugged me about the old browser is the lag time, especially when going back to a previous page.
Tear handles this much faster.

Kudos again. Looking forward to future updates.

Re: Tear 0.3.1 - a would be beta WebKit based browser

i do wonder if the marker park of the scrollbar (or whatever that part that one can drag around) should have a bit larger minimum size when using the thumb sized scrollbar...

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by gogol (Post 307621)

Now go here and replace your /etc/hosts file:
http://pgl.yoyo.org/adservers/
And it's nearly equivalent to microB.
...but what about greasemonkey? That would be cool...

May be interesting to someone... I'm blocking those nuisance at present by using the name servers from http://www.fooldns.com

They have also a nice list of bad guys at http://fooldns.com/rules.txt :cool:

Re: Tear 0.3.1 - a would be beta WebKit based browser

@Bundyo

To help with the memory usage, commit #52 now adds maemo-launcher support via an optional "--maemo-launcher" (I *hate* WAF BTW :)) argument. It wont mess up your deb building script as it's disabled by default (and I didn't adapt that to support maemo-launcher) but if you build a deb with dpkg-buildpackage, you should get one that uses maemo-launcher (DEB_BUILD_OPTIONS="nolauncher" dpkg-buildpackage -rfakeroot to build w/out maemo-launcher if using the debian/ folder).

Quote:

Originally Posted by maemo-launcher's README

The maemo-launcher is a daemon to speedup applications startup time and
memory sharing between processes. It supports booster modules, which are
the ones in charge of preinitializing and keeping the interesting state.

Certainly (in my biased opinion ;)), it is faster to start up. :)

Re: Tear 0.3.1 - a would be beta WebKit based browser

What do you have against waf? Except napalm that is :D

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by Bundyo (Post 307674)

What do you have against waf? Except napalm that is :D

Probably stems from not having a great understanding of Python, but I find it... odd. :p

Like, I'd expect being able to manipulate CFLAGS from the command line as standard, I see how autotools stuff fits in with each other (it took me 30 mins to realise I was adding the extra-cflags option to the wrong wscript :\), and it obfuscates gcc output by default (I'm a geek: I need to see if the CFLAGS I added are being applied :p).

But, that said, it is bearable and I should really get acquainted with the WAF book. :p

Re: Tear 0.3.1 - a would be beta WebKit based browser

Tear 3.5-2 is really great! thank you for your work.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Is 3.5-2 in qole's repo yet?

Re: Tear 0.3.1 - a would be beta WebKit based browser

I uninstalled and reinstalled, then downloaded the .deb for 3.5-2 from the link in help>about and installed that, it still says 0.3.5-1 in the about menu

Re: Tear 0.3.1 - a would be beta WebKit based browser

This should help you make sure you have 0.3.5-2:

Quote:

Originally Posted by qwerty12 (Post 307221)

Quick way to check (looking at the first page): Does searching for a phrase not present on the page bring up a message telling you that the phrase was not found? If so, you have -2.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Ok...I hadnt seen anything in the thread about it not showing correctly in help>about.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Freshly updated Tear on my N800... ooooh

Being able to move the toolbar to the top, remove the scrollbar, start in full screen, and a few other tweaks makes me one happy camper.

Thanks for this update, and your attention to all of our requests.

Re: Tear 0.3.1 - a would be beta WebKit based browser

Quote:

Originally Posted by bros1 (Post 307120)

thanks for release.
I tried 0.3.5-2 on N810.
It falls when tap & hold, every time.

For me, sometimes :

When the link I tap&hold on is at the bottom of a page, the appearing menu shows it's top at the bottom of the page, and I can't get it up.
( In maemo-browser I get the whole menu visible.)

EDIT :
Known issue ?

With the new (0.3.5-2) Tear I still can't log into Hotmail.
I get into the start page after logging in, but when I click on the E-mail icon Tear seems to search endlessly.
A copy from the url box gets longer the longer I wait until I stop Tear.

A sample :
*****://co119w.col119.mail.live.com/mail/InboxLight.aspx?n=594904074&n=913120617&n=18411853 67&n=2004025068&n=1701381906&n=1821026695&n=189625 3727&n=275024369&n=2068083542&n=678111231&n=294888 549&n=687105549&n=740694535&n=1216968955&n=6721621 44

( At the same time maemo-browser had no problem, I tested back and forth.)
/EDIT

Great upgrade ,
browsing newspapers with many photographs seems much quicker than before ,
"Open file", "Find" , very welcome !

( I'm eagerly looking forward to a future "Save as", maemo-browser isn't to good at that.)

Tear has long been my (almost) only browser !!

Re: Tear 0.3.1 - a would be beta WebKit based browser

Can't build tear from svn.
vala 0.5.7
sh ./project-build.sh
Checking for program gcc : ok /usr/bin/gcc
Checking for compiler version : ok 3.4.4
Checking for program cpp : ok /usr/bin/cpp
Checking for program ar : ok /usr/bin/ar
Checking for program ranlib : ok /usr/bin/ranlib
Checking for compiler could create programs : ok
Checking for compiler could create shared libs : ok
Checking for compiler could create static libs : ok
Checking for flags -O2 : ok
Checking for flags -g -DDEBUG : ok
Checking for flags -g3 -O0 -DDEBUG : ok
Checking for flags -Wall : ok
Checking for gcc : ok
Checking for program valac : ok /usr/bin/valac
Checking for package gthread-2.0 : ok
Checking for program version valac >= 0.1.6 : ok 0.5.7
Checking for program msgfmt : ok /usr/bin/msgfmt
Checking for program intltool-merge : ok /usr/bin/intltool-merge
Checking for header locale.h : ok
Checking for package glib-2.0 >= 2.10.0 : ok
Checking for package gconf-2.0 >= 2.10.0 : ok
Checking for package gobject-2.0 >= 2.10.0 : ok
Checking for package gtk+-2.0 >= 2.10.0 : ok
Checking for package hildon-1 >= 1.0 : ok
Checking for package hildon-fm-2 >= 1.9 : ok
Checking for package gnome-vfs-2.0 >= 2.10.0 : ok
Checking for package conic >= 0.16 : ok
Checking for package libpcre >= 6.5 : ok
Checking for package libosso >= 2.0 : ok
Checking for package sqlite3 >= 3.0 : ok
Checking for package webkit-1.0 >= 1.0 : ok
Configuration finished successfully; project is now ready to build.
[ 1/24] valac: src/tear.vala src/uim.vala src/about.vala src/settings.vala src/dbqueue.vala src/connmanager.vala src/imagemenuitem.vala src/ovbox.vala src/drawer.vala src/quickbar.vala src/tearwebview.vala src/downloadmanager.vala src/downloaditem.vala src/checkbutton.vala src/option.vala src/urifuncs.vala src/blocker.vala src/blockerrule.vala src/dbusservice.vala src/dbusserver.vala src/optionsmanager.vala src/menu.vala
quickbar.vala:9.2-9.23: warning: Tear.Quickbar.model hides inherited field `Gtk.ComboBox.model'. Use the `new' keyword if hiding was intentional
quickbar.vala:81.24-81.29: warning: result variable type incompatible with return type
dbqueue.vala:93.10-93.15: warning: result variable type incompatible with return type
dbqueue.vala:43.7-43.206: warning: result variable type incompatible with return type
quickbar.vala:110.28-110.33: warning: result variable type incompatible with return type
quickbar.vala:123.24-123.29: warning: result variable type incompatible with return type
optionsmanager.vala:200.8-200.29: warning: result variable type incompatible with return type
optionsmanager.vala:320.10-320.15: warning: result variable type incompatible with return type
option.vala:24.14-24.31: warning: deprecated syntax, don't use `new' to initialize structs
optionsmanager.vala:277.4-277.15: warning: `null' incompatible with return type `string`
optionsmanager.vala:282.13-282.24: warning: `null' incompatible with return type `string`
ovbox.vala:120.31-120.50: warning: deprecated syntax, don't use `new' to initialize structs
ovbox.vala:204.26-204.45: warning: deprecated syntax, don't use `new' to initialize structs
ovbox.vala:205.25-205.44: warning: deprecated syntax, don't use `new' to initialize structs
tearwebview.vala:287.42-287.71: warning: unhandled error `GLib.Error'
tearwebview.vala:288.9-288.198: warning: unhandled error `GLib.Error'
tearwebview.vala:289.9-289.79: warning: unhandled error `GLib.Error'
tearwebview.vala:296.44-296.73: warning: unhandled error `GLib.Error'
tearwebview.vala:297.9-299.6: warning: unhandled error `GLib.Error'
tearwebview.vala:300.9-300.53: warning: unhandled error `GLib.Error'
tearwebview.vala:308.41-308.68: warning: unhandled error `GLib.Error'
tearwebview.vala:309.39-309.69: warning: unhandled error `GLib.Error'
tearwebview.vala:310.9-314.6: warning: unhandled error `GLib.Error'
tearwebview.vala:315.3-315.36: warning: unhandled error `GLib.Error'
tearwebview.vala:316.3-316.93: warning: unhandled error `GLib.Error'
tearwebview.vala:318.9-321.6: warning: unhandled error `GLib.Error'
tearwebview.vala:322.3-322.46: warning: unhandled error `GLib.Error'
tearwebview.vala:323.9-323.63: warning: unhandled error `GLib.Error'
tearwebview.vala:324.9-324.52: warning: unhandled error `GLib.Error'
optionsmanager.vala:226.8-226.29: warning: result variable type incompatible with return type
optionsmanager.vala:372.10-372.15: warning: result variable type incompatible with return type
optionsmanager.vala:239.18-239.30: warning: deprecated syntax, don't use `new' to initialize structs
optionsmanager.vala:247.8-247.13: warning: result variable type incompatible with return type
optionsmanager.vala:267.18-267.30: warning: deprecated syntax, don't use `new' to initialize structs
optionsmanager.vala:20.24-20.29: warning: result variable type incompatible with return type
optionsmanager.vala:25.3-25.78: warning: unhandled error `GLib.Error'
uim.vala:126.2-126.25: warning: Tear.UIManager.get_action hides inherited method `Gtk.UIManager.get_action'. Use the `new' keyword if hiding was intentional
urifuncs.vala:37.6-37.17: warning: `null' incompatible with return type `string`
urifuncs.vala:42.6-42.17: warning: `null' incompatible with return type `string`
tear.vala:1560.29-1560.34: warning: result variable type incompatible with return type
uim.vala:97.3-97.32: warning: unhandled error `GLib.Error'
quickbar.vala:161.24-161.29: warning: result variable type incompatible with return type
quickbar.vala:210.10-210.15: warning: result variable type incompatible with return type
tear.vala:1304.9-1304.35: warning: result variable type incompatible with return type
downloaditem.vala:15.14-15.31: warning: deprecated syntax, don't use `new' to initialize structs
downloadmanager.vala:16.3-16.78: warning: unhandled error `GLib.Error'
tear.vala:1345.5-1345.12: error: The name `append' does not exist in the context of `Tear.WebKitView'
tear.vala:1351.5-1351.12: error: The name `append' does not exist in the context of `Tear.WebKitView'
tear.vala:1353.24-1353.34: error: The name `escape' does not exist in the context of `Gtk.Menu'
tear.vala:1729.9-1729.30: warning: result variable type incompatible with return type
tear.vala:1368.6-1368.13: error: The name `append' does not exist in the context of `Tear.WebKitView'
tear.vala:1369.6-1369.13: error: The name `append' does not exist in the context of `Tear.WebKitView'
tear.vala:1383.39-1383.46: error: Arithmetic operation not supported for types `Tear.WebKitView' and `double'
tear.vala:1388.21-1388.29: error: The name `get_uri' does not exist in the context of `Tear.WebKitView'
tear.vala:1388.15-1388.32: error: var declaration not allowed with non-typed initializer
tear.vala:1393.61-1393.63: error: The name `uri' does not exist in the context of `Tear.BrowserWindow.connect_signals.__lambda19'
tear.vala:1401.43-1401.43: error: Argument 1: Cannot convert from `WebKit.WebFrame' to `string'
tear.vala:1404.21-1404.29: error: The name `get_uri' does not exist in the context of `Tear.WebKitView'
tear.vala:1404.15-1404.32: error: var declaration not allowed with non-typed initializer
tear.vala:1409.16-1409.18: error: The name `uri' does not exist in the context of `Tear.BrowserWindow.connect_signals.__lambda20'
tear.vala:1412.43-1412.45: error: The name `uri' does not exist in the context of `Tear.BrowserWindow.connect_signals.__lambda20'
tear.vala:1416.49-1416.51: error: The name `uri' does not exist in the context of `Tear.BrowserWindow.connect_signals.__lambda20'
tear.vala:1416.46-1416.46: error: Argument 1: Cannot convert from `WebKit.WebFrame' to `string?'
tear.vala:1426.51-1426.51: error: Argument 2: Cannot convert from `WebKit.WebInspector' to `WebKit.WebView?'
tear.vala:1809.25-1809.30: warning: result variable type incompatible with return type
checkbutton.vala:8.2-8.20: warning: Tear.CheckButton.label hides inherited property `Gtk.Button.label'. Use the `new' keyword if hiding was intentional
checkbutton.vala:12.2-12.19: warning: Tear.CheckButton.active hides inherited property `Gtk.ToggleButton.active'. Use the `new' keyword if hiding was intentional
tear.vala:710.22-710.27: warning: result variable type incompatible with return type
tear.vala:723.9-723.35: warning: result variable type incompatible with return type
tear.vala:824.8-824.29: warning: result variable type incompatible with return type
tear.vala:668.2-668.78: warning: unhandled error `GLib.FileError'
tear.vala:834.8-834.29: warning: result variable type incompatible with return type
tear.vala:845.8-845.29: warning: result variable type incompatible with return type
tear.vala:961.4-961.79: warning: unhandled error `GLib.Error'
about.vala:32.21-32.96: warning: unhandled error `GLib.Error'
Build failed

Re: Tear 0.3.1 - a would be beta WebKit based browser

@daperl

(In response to http://talk.maemo.org/showpost.php?p...&postcount=481)

After LD_PRELOADing g-inspector into maemo-launcher and having it popup with browser-ui, looking at the Quarks List, I can say that there is no function. But I did notice a shitton of GdkPixBuf references.

So, after some observation, I noticed that the File Manager has the 'Z' icon overlayed, like how MicroB overlays favicons.
Grepped hildon-desktop for "qgn_" and I found /usr/share/icons/hicolor/16x16/hildon/qgn_indi_bkilled.png. Guess what this icon was? Yep, the 'Z' that it overlays.

Ran the trusty g-inspector and used its Widget Picker on the icon with the 'Z' and it told me that its GType was HNAppButton.

I then grabbed the source to hildon-desktop, grepped for HNAppButton and it pointed me to src/hn-app-button.c

Looked in here and I saw a ton of PixBuf functions that got the current icon and overlayed that 'Z' over it if it found the program to be in a hibernated state. :)

Re: Tear 0.3.1 - a would be beta WebKit based browser

so basically someone at nokia abused that overlay code to put site icons on top of the browser app icon?

Re: Tear 0.3.1 - a would be beta WebKit based browser

In order to save other less knowledgeable Maemo users like me (haha) from thinking they have a problem reinstall, just FYI -- the bookmark feature will NOT show up until you actually add a bookmark.

I reflashed my N810 and restored my apps/data. Everything except a few apps restored just fine, but I thought one of those bad apps was Tear because it wasn't showing the latest version number on the About screen, and it kept defaulting to the dashboard instead of the homepage I'd previously set, etc. What made me think something was really wrong was that not only were all my bookmarks missing, but so was the bookmark menu option (via the ^ icon). So I was thinking that for some reason it was reverting back to a really old version, likely because of some repository problem. After about two hours of troubleshooting and reinstalling, I realized that it was all good. Oops.

I hope this helps someone else. I guess I also hope that there's someone out there as stupid as me to encounter this problem which automatically makes me less stupid....or at least stupid in a group instead of by myself. Haha.

I did want to report that a reflash and a restore does seem to reset everything associated with Tear -- all my bookmarks and settings were gone. Is there a way I could've avoided that?

-- Chris

Re: Tear 0.3.1 - a would be beta WebKit based browser

@qwerty:

I'm not sure we're talking about exactly the same thing. Maybe you could post a picture. I'm familiar with pixbuf compositing; here's a screen shot of my bookmark menu. Notice how the favicons are overlayed on the "new tab" icon. That's done programatically.

Attachment 3796

What I wasn't able to figure out was how microb changes the icon in the Task Switcher. Here's another screen shot.

Attachment 3797

Re: Tear 0.3.1 - a would be beta WebKit based browser

he is quite clearly talking about the latter, as the Z icon he talks about is something that maemo will show if you run the system without swap, and load a lot of apps, as the older ones will get a z on top of them (think the classical cartoon image of someone sleeping).