Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Could anyone write a little how-to on how to make Tear the default browser using dbus-switchboard? To someone not used to its workflow, it's a fairly daunting enterprise. I'd really like links in Pidgin IM conversations to open in Tear, as well as searches from the search home applet.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

sadly i do not think that there is a way to do that, at least i dont think anyone more knowlegable then me have found a way...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I tried registering for an account (same username) but it seems I still haven't gotten the email to verify my account (I registered last afternoon).

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

guest posting is allowed, iirc...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Ah thanks tso, I've reported it. I should try other bookmarklets to see if they have a similar issue.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Humm, in this post, Bundyo claims it's doable, so maybe he has figured it out.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Here's a thought: Many of us owning an N810 right now will likely end up running Mer on it sooner or later, as the de-facto upgrade path from Diablo. Mer is presently using Midori as its default browser. Tear, however, is better, and designed for Maemo/Hildon from the ground up, whereas Midori is, IMHO, a pretty shaky port of a desktop app. Bundyo, have you thought about getting together with the Mer people and hammering out a collaboration to get Tear into Mer as its default browser?

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Maybe this is a bug. On the website csusms.com, I can't type in the full account name, only 5 digits. MicroB works fine.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I'm planning to get it running on Mer, but hadn't talked with anyone yet and there's nothing set in stone.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I notice there's a "Port Tear" task listed in here, so it might be a good idea to get together to avoid duplicated efforts.

Bundyo, anything about the dbus-switchboard thing above? :)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Its partially possible as discussed previously - apparently most Nokia software is directly opening the browser with dbus and not relying on mime types. Probably other programs do the same thing.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Looks like a bug - html maxlength atribute is subtracted by 2.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Not sure about the search home applet, but for pidgin, go to preferences, the browser tab, choose "Manual", and type /usr/bin/tear %s in the "manual" text box.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Yup, and as I understand it, the purpose of dbus-switchboard is to intercept these calls and reroute them to more useful handlers, such as Tear. However, the previous mentions of dbus-switchboard in this thread seem to only refer to people wondering how to do it, and the same question has come up and gone unanswered in switchboard's own thread as well. So far you seem to be the only one who knows how to do it - could you share?

@TrueJournals: Ah, you rock! Thanks, that already takes care of 85% of my external link opening. Should've looked more carefully!

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

You can get Tear to open a link using two ways:
and

However the first one won't start a new browser if there isn't one started, while the second will. I'm not using dbus-switchboard, I'm only telling what I read in this thread. Let me check.

One piece:
http://www.internettablettalk.com/fo...ard#post269960
Second piece:
http://www.internettablettalk.com/fo...027#post274027

And that's about all I can find. I ran dbus-switchboard and customized some things but didn't succeed in getting anything to run in Tear.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I'm not sure how deep your interest goes, but you might find this diagram and the surrounding text informative.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Hmm, I'm seeing a problem here... The dbus method that the browser uses is called new_window (I believe). Since tear uses OpenAddress (and probably doesn't respond to new_window), applications would call tear with new_window, and tear would just open and ignore the address.

Haven't fact-checked/tested any of this, so feel free to correct me.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Thanks, that's rather interesting in fact.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

We all would love Tear. Stskeeps uploaded your webkit from Extras and it built for x86 only :/

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I noticed the same thing in this finnish onlinebank http://www.op.fi
Webkit engine (both in Tear and Nokia browser) only allows you to type in 2 characters in password (Salasana) field. Microb working just fine.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

@Jaykie: How many characters the password should be?

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I would give it a spin soon.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Build error is:
webkit/webkitwebnavigationaction.cpp:144: error: 'WEBKIT_TYPE_WEB_NAVIGATION_REASON' was not declared in this scope

armel build log (failed) and x86 build log (worked)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

It just occured to me that I've only been nitpicking and uttering wishes so far, and forgot to ever write a note of appreciation: Thanks, Bundyo, for working on this great app. Thanks to Tear I spend a lot more time with my N810 now, and get a lot more use out of it. While things worked before with MicroB, loading up complex pages took so long, and the browser was so unresponsive while it was loading (scrolling during load was nigh-impossible) that I actually tended to avoid a lot of browsing on the device, which runs counter to its intended purpose. Tear is what was missing from the equation there. And I also really like various elements of its UI approach, particularly the one-click bookmarking. So, again, thanks for adding a lot of value to my N810!

If Mer adopts Tear as its default browser, that'd probably be the biggest single upgrade it can include to kick Diablo's ***^W finely-shaped behind.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

( Searching this thread for "zoom" gave no hint, so here goes.)

Running Tear 0.3-6 on an N810 :
Often zoom-in increases also page width, making horizontal scrolling necessary.

This trick mostly makes zoom increase only text size.
(tested only with ITT pages)

Zoom back to 100 % (or less if necessary) to make page width fit screen.
Reload page.
Scroll page.
Then zoom in.

This almost always works with ITT pages that are lists of threads,
but less often with pages in a thread.

I tested this both with open keyboard in full-screen mode using the +/- and menu keys,
and with closed keyboard in small-screen mode using the menu.


( I write this in microB after crashing Tear 4 times;
back-spacing the cursor in the quick reply window with the D-pad
when the cursor is at the beginning of a line
seems always to freeze Tear.
I suppose this is known and mention it just in case.)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Yes, reproduced it. Only if there's text though.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I don't think I've asked this yet: is there a way to customize key bindings in tear to change d-pad scrolling to page-by-page, as opposed to line-by-line? (These are the instructions to do this for microb.)

Thanks much.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Not yet...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Bundyo, I left several Feature Requests in the Garage: Select All; adding a text-select toggle button like in Quick Clip Viewer; and Find Text on Page.

I looked at the Bug Tracker on the Summary page and it showed zero bugs. Am I going to the right place to place Bug Reports and Feature Requests?

(Again, I can't say thanks enough for Tear. What a pleasure it is!)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I saw them and transferred whatever needed to be transferred. I already added Select All to the menu. The real tracker is here: http://bugs.bundyo.org

Please check if I moved everything.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

@Bundyo : I was wondering if you are the one and only Tear developper ? I see people asking for features or reporting bugs for 91 pages in this thread. How can you handle such a amount of feedback ?

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Yes, I'm the only active one at the moment. Its not that much really - its almost the same all those pages ;)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Well Sir, then you deserve a medal because it blows me away with the resources that Nokia has that they couldn't have come up with something as efficient as tear for web browsing. I actually think it would have been a game changer for people that would have purchased the N810 if it wasn't for the slow browsing speed. Tear really is eye opening with how fast it renders websites and I'm truly appreciative for all your efforts.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

I'm only writing an interface for webkit, which is actually doing the rendering :)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

You might downplay your contribution in your eyes, but you've made the N810 user experience a whole hell of lot more enjoyable, so I still think you should get that medal even if it's only a virtual one. :)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Nonetheless ...

:):):)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

bundyo look at what just the interface can do, my isp just reduced my connections bandwith because i have used too much of it, now the deal is due to low bandwith microb cannot even open the home page tethering to my phone BUT TEAR HAS SAVED ME AND I HAVE BEEN USING IT TO SURF EVERY SITE Even now posting this, it is find playing modesty but tear has really made our days better on this tablet have used it since day one and am realy happy Thanks mille fois.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Hey Bundyo, I noticed that the bug I filed disappeared (about bookmarklets like Evernote not working). Did I file it wrong or was it just fixed?

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Probably you filed it wrong, did you confirm twice at the end?

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard
 

Ok I'll try re-adding it. Also for the "google.com/calendar/gp" issue I have the same problem myself. It will load the events, but then blip and restart the process (showing the events listed in that day and then reload yet again. I couldn't find a way to comment on existing bugs there as a guest.

Edit: Posted the bug. http://bugs.bundyo.org/viewissue.php?issue_no=39