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

That is correct. If you've made the change to the service file in /usr/share/dbus-1/services/com.nokia.osso_browser.service, that should be enough. If you want to save a little memory, you can disable browserd (tablet-browser-service).

I've just updated the browser-proxy script to 1.4. One little bugfix and one big new feature: if you select "Web" from the menu, the system browser will be started (starting browserd as well, if needed). As long as the system browser is open, all links will open in the system browser instead of Tear. As soon as you close the last system browser window, links should again open in Tear. (At this point, however, you'll have to kill the leftover browserd process if you don't want it running.)

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

Is there a way I can change the default download location to something other than the root folder?

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

This should be optional imho, and if you could make two versions, one with, one without the feature, or encapsulate the related code so that I could comment it out, I'd be happy.
I prefer having two icons in my personal menu, one which sets tear as default, one for microb, so that I can decide each time which browser I want to activate, and also keep both open. Memory doesn't seem to be much an issue for my use cases.

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

You still will have two icons in your menu for browsers: "Web" for MicroB and Tear.

Unfortunately, it's not possible to pick which browser to use by default if MicroB is open. When MicroB is open, it receives all of the open-link messages from other applications and browser-proxy never sees the messages to relay to Tear.

If you install browser-proxy, it works like this:

• Click a link in some application with no browser open: browser-proxy receives the message and opens a Tear Dashboard window and then another Tear window with the link.
• Click a link in some application with only Tear open: browser-proxy receives the message and opens a new Tear window with the link.
• Open "Web" from the launcher: browser-proxy receives the message and starts browserd (if it's not already running) and then launches MicroB.
• Click a link in some application with only MicroB open: MicroB receives the message and opens the link. browser-proxy never sees the message because MicroB grabbed it.
• Click a link in some application with both MicroB and Tear open: MicroB receives the message and opens the link. browser-proxy never sees the message because MicroB grabbed it.

In a way, with browser-proxy installed it works sort of like you want: your default browser is whichever browser is running (when only one browser is running). With two caveats: First being that when no browser is running, the default is Tear.[1] The second being that when both browsers are running, the default is MicroB.[2]

[1] Of course you can change the default browser used when no browser is running by putting /usr/share/dbus-1/com.nokia.osso_browser.service back to its original state of "Exec=/usr/bin/browser".
[2] There is no way around using MicroB by default when both browsers are open without hacking some binaries, AFAIK.

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

Hmm by open web you mean open new browser window would open microb if tear and microb aren't running? For me with the latest script it only opens tear.

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

Opening the "Web" application: for me, it's Home > Applications list > Internet > Web. (I don't recall if I made the Internet category myself with Panels or if it was there by default).

I would expect "Open new window" on the Home screen bookmarks list to work like the other bookmarks entries and like opening a link from another application: the message will be seen by browser-proxy (if MicroB is not running), and it will tell Tear to open the link.

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

Well, --disable-dbus-transformation seems to only affect auto capitalization of DBus.Object methods. It still capitalizes my methods on registration :(

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

vala -C and sed? :D

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

Ok thanks for the clarification. It works as you posted.

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

I would rather prefer something not that hack-ish :p

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

Hi All!

Only just installed it and so far am impressed by performance with AJAX sites!:D

A simplistic question, perhaps a side-effect of my FireFox-centric thinking.:rolleyes:

Is it possible to set a default URL that loads when Tear is launched? Or should I not desire that kind of thing, and embrace a new paradigm?

It's just that I like to have my browsers' default homepages be my personal website - so that I know when my ISP is down

Thanks,

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

Menu >> Tools >> Options: homepage

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

Hmmm...

Menu >> Tools >> Options: homepage was the first thing I tried (while enjoying the about:config paradigm!) before posting the question.

I modified the string to be the URL of my desired site, both with and without the http:// . However, after exiting Tear and re-launching, it would just come up with a blank page and and oscillating activity bar at the bottom of the screen. Selecting the dashboard and clicking on the buttons would take me to sites as expected, and MicroB still worked, so I knew I had a good connection.

So, I tried killing all instances of MicroB, thinking it was somehow freaking out Tear - still no dice.

I then powered off the N810 and back on, and now Tear when launched brings up the home page as expected. <sigh>

Sorry to bug everyone with problem that is probably unrelated to Tear. I've suspected that something has been whacked-out with my N810 since I mucked around with Dbus last week.

Thanks,

Steve

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

i'm starting to wonder if i have a corrupted db.

bookmarks come and go, settings are missing, and when tear crashes it gives me pages i have not browsed in days (and maybe over multiple days), but not ones i had open just seconds ago...

so, how do i go about fixing it, without clearing it fully?

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

First get it to your PC, try to open it with for instance this:
https://addons.mozilla.org/en-US/firefox/addon/5817

Try to open Tear without a DB, see if you still get any problems.

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

Roger, will do ones i get home

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

That may even help rebuilding it:
http://forum.idimager.com/viewtopic.php?f=4&t=8165

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

ugh, database comes up clean...

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

Hmm, can you check with the SQLite Manager if there are some opened = 1 history entries and how much of them. If there are any - try to clean them and return the db to the tablet. Also check the permissions of the db in the .tear/ folder.

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

no opened right now, so no clue there.

as for permissions, user users...

btw, whats the point of keeping a history thats 9477 entries long?

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

Well, stats? :D There are clean history / auto clean options now.

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

err, is there a way to recover a deleted setting (hitting the fat x in options)?

ah, never mind, it returns on restart of tear. Still, if thats the case, why have not the zoom amount setting returned?

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

The defaults are set on start.

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

ok, now i really wonder where that setting have hid itself.

or maybe i have missunderstood. there is supposed to be a setting that controls the zoom increment, yes?

anyways, thanks to the our recent ability to use tear for anything relying on dbus for url opening, i have foound that tear indeed fails to open a connecion when said dbus url passing is used.

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

@Qwerty12: Can you try to login in the bug tracker at http://bugs.bundyo.org ?

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

I tried, but I get "No such login". Tried registering and I get "Username not available". Entered "qwerty12" in the pwd recovery box and still no e-mail. :)

But, if it's anything Mer related; you'd be better off asking Stskeeps, and not me.

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

No, its bug system related :) I have a whole bunch of accounts and seems noone is able to login :D

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

Okay, the tracker registration is working now.

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

I tried this but javascript cookies are not supported yet. Is this true ?

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

Yes. True.

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

And will this be supported ?

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

Honesty, I don't know. Cookies with CURL are supported with a hack, and I'm not sure if I can isolate this problem and fix it.

Plus Curl is not used anymore in WebKitGtk, so there's no one to patch it.

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

Okay, 0.3.5 is out along with libwebkit 41137-13, check the front page for more info. Currently only on my site and garage, because Qole is nowhere to be seen. He will update later, so you can wait if you want :)

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

heh, i am still missing that zoom_step setting for some reason...

and i would love to know why tear fails to trigger the wifi connection when passed a url over dbus...

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

Well, seems navigation_requested isn't requested every time :D

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

Are there any plans for tear to be able to remember passwords of sites? The only two remaining problems I have with tear are it doesnt remember the passwords of a couple sites I have to login to whenever I visit, and it still wont let me log into usatoday.com

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

Ok repo updated.

You Europeans have to remember I'm 9 hours behind you... And we were on the road all day...

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

Hey, Bundyo:
1. Thank you... profusely.
2. Is it just me, or does the update process overwrite one's userstyles.css file? If so, a warning to those who'll need to make a backup copy...

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

Sweet; thanks for the update. Now able to play in both Mer and Diablo with this :)

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

Remember passwords as to fill them in automatically? Not sure when.