Notices

Tear FAQ:

What is it?

A kickass Webkit-based browser - by the kickass Bundyo - that beats the **** out of the original shitty "browser" Nokia provided for Diablo.

How can I has install?

Go to the first page of this thread and install both Webkit and Tear debs using the application manager.

You can, alternatively, go to http://qole.org and add his repository and have the convienence of being able to install Tear, with the dependencies automatically installed (including Webkit) for you. You will also have the update notifier flashing when Bundyo puts out an update and Qole adds it to his repo.

How can I has select txt?

Hold the Menu key (under the Back key on an N800 - the thing that looks like the Undo arrow in Windows and - for an N810 - the button that is all singled out and happens to be under the down dpad button on the keyboard) and select your text. And let hilarity ensue.

How do I remove a bookmark?

Click the arrow pointing upwards in the toolbar; choose your bookmark; and hit the previously-grey star that will have now turned orange.

Today was a good day... All I see is green...

Wow, this was taken seriously?
(Although, I do happen to be serious with the answer to the first question)

Now I can haz a cheezburger.

Here is a feature request in the convoluted form of:
http://qwerty12.qole.org/find.diff

Took and butchered code from the Tomboy Maemo port and changed it to work for Vala and Webkit. I had trouble connecting it to the menu... It's far from clean but I hope you can implement a proper solution.

Better find some programming books You're rapidly going that way

Is there really a need to trash other people's work like this? I'm sure you guys wouldn't appreciate it if someone from Nokia claimed Tear was a steaming pile of **** in it's official documentation.

I don't think that was entirely serious...

Integrated, 10x.

My words are harsh and rude, but I stand by them. If it helps, I publically have called myself names, using the same offensive words that I use against others.

But Nokia have got my money for it. Not resentful at all, I happen to love my tablets and would like to buy the next "tablet" when I get the money.

It wasn't particularly speedy in Chinook but Nokia made it worse with the invention of browserd that premiered in Diablo. The SVN build of MicroB was already proving to bring a huge improvement, in terms of speed, to MicroB but instead of shipping that, they decided to introduce browserd which did not help any - it just made MicroB worse.

I've thrown my tablet against a hard wall due to frustration with browserd. Totally my fault, I know, but there is only so much I can take of it locking up. Tear crashes often but I have no problems because:

1. It is fast in loading pages.
2. It has an easily accessable history.
3. It has "Crash Recovery". I didn't see Nokia bothering with this one.

Finally, like most of Nokia's stuff, they could never open-source browser-ui so that improvements involving that could be made. The Fremantle one will be open-source - a huge step forward - but it's a shame they never bothered with Diablo. So, in total, I don't feel remorse for the words I used due to what I've listed above.

Iirc, browserd was nokia's attempt st crash recovery. The idea being that in the event of a crash, only the affected window should die, or even "recover" on its own (restart microb, reload page)...

The speed issue is one of using a alpha grade javascript engine, thanks to freezing the code at arounf firefox 3 alpha 2...

Btw, a lot of the nokia decisions can be summed up in one word, differensiation...

Closed-source projects are sitting ducks for criticism, in my opinion...

In Fremantle forward, if you say that the browser is crap, then someone will tell you to go fix it yourself. And if someone wants a feature, they can just submit a patch (like qwerty12 did for Tear just now).

And if Nokia doesn't like the patch, someone will just fork the project...

A whole new world...