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

When I post message the forum returns:
HTTP/1.1 200 OK
Date: Fri, 06 Mar 2009 10:44:10 GMT
Server: Apache/2.0.63
X-Powered-By: PHP/5.2.6
Cache-Control: private, no-cache="set-cookie"
Expires: 0
Pragma: no-cache
Content-Encoding: gzip
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Transfer-Encoding: chunked

As I can see the Content-Type is valid, but maby other headers say something more to you.

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

Ah yes, I hadn't noticed this and hadn't added it into my calculations. Taking that into account, Tear is indeed considerably faster than MicroB.

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

@Bundyo - Dude, this is an awesome addition to my N800! :D

Thank You!

Now for the silly question: :o

I know in microb that I can open a html file stored on MMC1 (N800)

Is this possible in Tear?

I've tried: file:///mmc1/.../bookmarks.html (copied from microb) with no luck.

Thanks
M

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

It should work. Did you forget 'media' in front of '/mmc1'?

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

Could you add a "Open link in background window" to the tap'n'hold menu?
With it tear would be almost perfect :)

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

Hmmm. I thought I copied and pasted.... but at this point I don't really remember. I'll re-try typing it directly:)

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

this is a nice browser. i've tried the webkit engine for microb and it crashes. it also doesn't seem quite as fast as tear. is there a way to make tear my default browser?

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

you could retry the webkit-eal, the crash issue is fixed now...

as for making tear default, from what i can tell, there is no easy way :(

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

If I were a hacker and I wanted to play around, the first thing I would do is make a cp -a of /usr/bin/browser.launch to browser.launch.orig. Then I would make sure that my new browser could take an url as a command-line argument. I would then copy my new browser to /usr/bin/browser.launch and see if that worked. If that fails, maybe I would then do a

strings browser.launch.orig | sort | less

to see what that reveals. It seems to reveal a few things. I would guess there might be one or two dbus messages to catch.

Something similar could probably be done with bookmark.launch.

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

if there are dbus messages, then maybe dbus-switchboard can be poked into handling it?