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).