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

It actually works for me. Maybe some dependency?

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

Uninstalled and reinstalled and now it works fine.

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

I'm having the launching problem, too, but it works from the command line (although it takes a few tries sometimes; I don't know why).

Actually, the one weird problem that's popped up for me -- and I was wondering if anyone else has seen this -- is that I'm having an issue where I visit a webpage (as an example, let's say I'm trying to reply to a thread on 4chan, because it happens all of the time on there now where it wasn't before), and the browser wants to download the whole webpage. If I'm on a page where it happens often as the page is loading (like Facebook), I'll see a request to save the page faster than I can hit cancel.

It's not like it's bugging me any; I'm just curious if anyone else has seen this pop up yet.

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

Hmm... that's really weird. Have you tried restarting your tablet to see if that fixes the issue? Also, are you SURE you have 0.3.1-4? Try uninstalling and installing it again, maybe? It's also quite possible I missed a dependency somewhere... I'll check that out tomorrow.

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

Installed -4 outright, and it works fine. I'm amazed at how well you've got tearbookmarks looking like the original plugin! This, with Bongo's bookmark manager make an awesome paring (and of course, Tear itself!).

Although, the anal retentive side of me asks: Why is the bookmark manager installed in /usr/bin/tear-bookmarks/? It's quicker for me if it's in /usr/bin as I can run it from the command line quickly if I wish :)

Plus, looking at /usr/bin/tear-bookmarks/, which only has images (minus the bookmark manager, which as said above, would be better in /usr/bin), that folder should really be in /usr/share.

Ah, I see, the bookmark manager loads images from the same folder. But I guess that could be changed? (Looking at the os.chdir?)

@Bongo,

In this case, 'self.window.set_title("Bookmarks")' should be 'gtk.set_application_name("Bookmarks")' (Looks better in the task switcher)

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

Glad to hear you like it :)

I stuck the bookmark manager in /usr/bin/tear-bookmarks as a quick fix. I didn't want to go through bongo's code and change it to look in /usr/share/tear-bookmarks for the images (I realize it wouldn't be terribly difficult...), so I just stuck everything in /usr/bin. Sloppy, I know... but it works. I'll work with bongo more to get this working properly for the next version.

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

@Bongo

http://pastebin.com/f64b29c4c

Removed the double import hildon, correctly set the title, fix the tap & hold to work properly & remove the hardcoded /home/user, inherit generic bookmark icon (as there's no desktop) and give the add bookmark dialog a title & set the same size as the microb bookmark prog

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

gah, i still feel that webkit is slower then it used to be.

it seems to be using more time on images then microb is using. and imo, that does not sound right.

now i recently recalled that i have a tuned microb setup, with a highly limited number of concurrent downloads. could something similar be hammering webkit? is it trying to download to many things at ones, choking the cpu in the process?

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

No, CURL is reusing the handle/s it has (P.S. It is a multihadle, so not one job). Have to dig more in WebKit one of these days.

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

Personally, I don't remember a time WebKit/Tear was faster than it is now, for me. In fact, I used to find it slower, particularly because the smearing problem used to be much worse (I used to think the name "Tear" was poking fun at the smearing problem - as in, "tearing" - and that it was part of the concept ...).

Right now, my only regret with regard to Tear is me being to lazy to build the latest SVN code ;).