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

what about this on the normal one when i tap on the profile and the search, am using this version WebKit 41128 if this info helps someone

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

This might be a stupid question (but I couldn't find anything when searching for password or management). Has password management been implemented yet?

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

Nope.

About the popup issue - I suspect a javascript problem and will investigate.

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

Bundyo, thank you for your work.

I have a problem with phpbb3 forums when tear opens download dialog instead of post message.

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

i spotted basically the same thing, but in a invision powerboard forum.

could it be related to the way the sending of the post is implemented? it seemed to only happen when using the full page post writing interface, not the quick post interface...

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

When clicking on send or when clicking on open reply?

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

send, iirc...

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

Is there any way to force Tear to open links in a new window? Some links do and some don't.

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

Tap and hold -> Open in New Window?

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

/me votes for the forum send bug

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

Just tried this for the first time last night. It is indeed faster than MicroB, although not quite as blazing as I was expecting given previous comments. E.g. www.bbc.co.uk homepage 17 seconds in MicroB, 13 seconds in Tear. Although simpler pages like Google search results were almost instant in Tear and a few slow seconds in MicroB.

Other than Webkit, is Tear all new code or is it a port of an existing browser? Is there a 'philosphy' behind it, e.g. small and light, or big and featuresome? Do you want feature requests on the garage site?

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

i suspect that the impression of speed comes from webkit/tear actually being done when the load bar disappears.

microb is like a jobs keynote taken to extreme, there is always 1 more thing that needs to be done with the page before the user can start scrolling around and look at the page content.

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

Tear is all new code, written in Vala, at the moment there's no philosophy behind it, other than easy to use. Probably will get cross-engine at some point, but its too early to talk about that anyway :)

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

Bundyo

My tap&hold menu consists of: Inspect Element, Cut, Copy, Paste.

Am I just not hitting the link, or is there something else going on?

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

your using the latest webkit? deb found at the top of first post of this thread...

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

Opps, still on preview 5, I will d/l and install 5.1 and give it a try.

I am using Tear almost exclusively now. Thanks for all the hard work.

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

Hmm.. noticing an odd issue using the iPhone version of the Google Reader site. If I select mark all as read, it'll just get stuck on loading for a while, but if I then click the load more items, it'll load up instantly (while marking the ones I told them to mark all as read).

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

First, thank you so much for this browser. It has brought me back to using the tablet as a real browser, needing to run to my computer only for having many sites open at the same time or for sites that need a large screen.

Speaking of odd issues with Google Reader, I can't seem to scroll by dragging in the browser window without "clicking" on one of the elements. I've noticed similar issues on other sites when I coincidently scroll using a hyper link. It doesn't click immediately, I can scroll up and down as long as I don't release, but when I release it "clicks" the link. For what it is worth, I see the same behavior in Microb.

Am I just too twitchy, or has any one else encountered the same thing? Is it possible to add a delay after scrolling before a tap on a link is registered? Or is this behavior strictly in the java that google (and/or another site) uses on the page?

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

This whole send download thing is very strange. WebKit decides what is a download by the content-type of the response, which for the message form is exactly the same when loading the first time and when clicking on send/preview. The only difference seems to be the form post http request.

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

Haha, I think it's just fast because you can begin browsing the page before it fully loads. The problem with microb is if the page isn't coded correctly it'll take longer to load an element that wasn't done right (and often isn't needed to see the content).

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?

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

They're both just wrapped-up stand-alone programs shared libraries; nothing no one but qwerty12 should be the wiser.

EDIT: see above

Much thanks to qwerty12: Binary Officer, badge #012

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

While your idea sounds good and correct, you'll want to replace browser instead. browser.launch is a shared "library" that maemo-invoker runs (/usr/bin/browser is a symlink to /usr/bin/maemo-invoker) because it's built to use maemo-launcher which preloads gtk stuff and is said to make a gtk program launch faster.

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

Update: looks like the decongestants hit me harder than I thought...

file:///media/.../bookmarks.html worked!

Thanks

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

Oh, yeah, that! I've only done a statusbar thingy, but I think the resultant .so files are just a switch when building. I think... If so, then I also think you just have to put it in the proper /usr/lib/hildon-... directory. Anyway, thanks for setting me straight.

But because of the above, I still would want to change "browser.launch" and leave "browser" alone 'cause I want to get all that launcher stuff for free. Right?

Maybe I should do more checking and less thinking...

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

The application has to be built for maemo-launcher (not terribly experienced on this - I only have ever modified one program to be compatible with maemo-launcher) specifically; so replacing browser.launch isn't likely to work because maemo-invoker expects a shared library and you aren't gonna get a GTK speed increase on a script :)

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

That's what I meant. Build a shared library. Like the ones that "Hello World" spits out. But a general wrapper for script invocation is a great idea. Or maybe just a Python invoker wrapper. Isn't that kind of what "osso_games_startup.launch" is? Or am I missing your/the point entirely?

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

just had two things show up...

1. to paste something into a text area, i had to use the long tap menu. the paste option of the osk didnt work (seems to work in the full screen one tho. bu that keyboard has its own issues).

2. sometimes the dashboard comes up empty when opening a new window using the + button.

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

hey, you probably know this, but some link buttons on facebook don't work in tear, such as the 'post' button for posting a message to someone's wall. also, the double tap, drag to select text only selects one word, and it won't copy after being selected.
great browser. my tablet feels new again.

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

Selection in Tear is done by holding down the menu key and just dragging. Actually while the menu button is down, the kinetik scrolling is off so you might fix something else this way :)

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

when i try to edit maemo wiki, tear asks me if i want to download something like php=??=bla09, when i press the save button