Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Yes, sometimes pages don't get unmarked after closing. 10x.

Not this year, sorry. :)

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Particularly since its usage is beyond Tear. Maybe the right time is when the stable first release is ready?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

The original idea was to try to get some testing of this release before cutting a 3.0 final release and announcing it to the wider world, especially for Fremantle (where I've been completely unable to test). I've yet to hear back from anyone regarding the release, though, and while for Diablo I can only assume that the 17 people who downloaded it from Garage (plus whoever's installed the extras-devel package, I don't have stats for that) are having no problems, I'm less comfortable making that assumption for Fremantle.

Since only two people have downloaded the Fremantle packages from Garage, I'm going to assume that the population of Fremantle users watching this thread is low, and cut a 3.0 release and hope that nothing blows up for them ... anyway, that should be up sometime later today.

ETA: Not to mention, like many developers, I'm TERRIBLE about writing documentation, release announcements, and the like, and so I've been putting it off :o

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

For Diablo I have found it works fine and causes no problems. The only negative I've seen is minor: when I click on a bookmark in Tear Bookmarks in the desktop Task Navigator, it opens in a new window rather than replacing the webpage in the already-open window (like it did in the built-in MicroB Bookmarks).

Thanks for coding and sharing this.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

i think you would find that for each that loved the microb behavior, there is one that hates it.

basically, either case depends heavily on what the user is planning to do, reuse the window for a unrelated browse, or open up a second page to look up something in response to something on the first page.

the only real solution i see if for the system to ask each time a bookmark is accessed from said menu, while a window is already open, if it should be opened in a new or existing window.

btw, i think said bookmarks menu development is on ice pending folder support in tear bookmarks management.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Hang on, I think that's got to do with Tear Bookmarks's behavior, nothing to do with Browser Switchboard. That said, the built-in bookmarks behave the same way too, which is a definite behavior change from when Browser-Switchboard isn't installed (wonder if I should document this).

Most definitely. I'd fall into the "hates the MicroB behavior" category.

Less intrusive would be to make a pref in browser-switchboard for it -- but the point is moot anyway, since I'm not aware of a way to control whether a link passed to any of the browsers other than MicroB should open in a new window or an existing window. Without that support we can't do much about this.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

and the setting would be potentially wrong half the time, even for the same user, as it may well be that the user would want to reuse a window one time, but open a new one a different time.

oh, and i think its tear that decides, and its set to open a new window every time a url is passed to it, just observe the behavior when using feed circuit to read rss updates.

and things get even more interesting ones one have multiple windows open. What window, if any, should be recycled?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Actually either way is fine with me, and, as I said from the start, it's trivial (and apparently moot). I was just surprised by the change/inconsistency.

Main points remain: It works just fine; thanks!

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

I've started a new thread for discussion of the new Browser Switchboard 3.0 release, and future releases as well.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

A would like to file a bug (or configuration problem?) here: tear does not seem to be able to save any changes in google calendar. Message I get: Oops, we couldn't create this event, please try again in a few minutes.
Microb can, Fennec also; With Midori it is the same.

Btw: I was installing from Qole´s repository, Version is 0.3.5-1; if I look into www.bundyo.org I see tear-0.3.5-2_armel.deb.
However, if I click it, it starts the program manager, runs through, but apparently installs nothing: About still reads 0.3.5-1;

What is the recommended repo for installing and what is the newest version?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

newest is 0.3.5-2, tho it will report -1.

as for the save issue, could be related to webkit problems with javascript cookies.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

n810 owners are very sad that there is no new tear version for diablo :(

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

i think bundyo have promised a update, once the fremantle version is working acceptably...

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

wow. Tear (diablo) has really evolved since the last time I used it; super fast. dunno what I've been missing! btw, anyone have any issues with the yahoo mail login not working?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Actually, I frequently use Tear to access local html files while offline.. Its stuborn tendency to ask me if i want to connect on every link transition -- even to another local file -- is a little irritating after a while.

I would hope this would be a preference.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

i think it will be able to tell the diff, as a http:// is not the same as a file://

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Thanks for superb browser. I really like Tear and its kinetic scrolling, but I do have a question for Tear users.
Do any of you use handwriting on your devices? I have found it as a fastest way to type on N800 (if BT keyboard isn't near by).
Handwriting on Tear and Google search doesn't really work because if there's more than one search word the first one(s) will be erased. Is there a way to get around this problem or should I just learn to use the virtual keyboard?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

i have problem with buttons/inputs being dark/black.
See scr. There is no style on buttons

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

@FunBob: no idea :(

@asidana: can you file me a bug?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

where do i file a bug? sorry :)

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

http://bugs.bundyo.org/viewissue.php?issue_no=82 i couldn;t change Tear for Maemo4 to Tear for Maemo 5

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

[ N810 , OS 43-7 ]

Strange difference Tear - MicroB
(if that is the name of the standard maemo browser).

With Tear I went to the Yellownotes thread
http://talk.maemo.org/showpost.php?p...7&postcount=53
to download
yellownotes-applet-diablo_0.4_armel.deb .

>The open/save/cancel dialog box called the file
attachment.php?attachmentid=3763&d=1248601909 .

Then tested from
http://talk.maemo.org/showpost.php?p=200737&postcount=2
with
yellownotes-applet-diablo_0.2_armel.deb .

>It was called
attachment.php?attachmentid=2042&d=1215695113 .

In both cases trying to open the file resulted in
"No handler configured for this type".


The same procedure with MicroB gave file names as expected,
and app. man. opened for successfull install.

( I have noticed that the two browsers often name downloads differently. )

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Well, they are different browsers :) The version of Webkit used in Tear can't detect such filenames that change on the fly.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

I dont understand. Are you saying the filenames are constantly changing?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

No, just that the returned header has the real filename in it.

He also talks about opening the file automatically - and since Tear doesn't know what it is - auto open through OS doesn't work. MicroB changes the filename accordingly before saving and opening it at the end correctly calls app manager. Both browsers probably use the same calls to the OS.

I'm using Hildon.mime_open_file ( dbus_service.connection, fname );

If you open an .install or .deb file where its filename is contained in the URL, it will work. If you first rename the downloaded file to something.install or something.deb - it will also work.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

I don't quite understand.

Downloading and installing the same file
yellownotes-applet-diablo_0.2_armel.deb
from garage
works the same way in tear and MicroB:

click on file
open/save/change folder/cancel window appears with correct file name
clicking on open starts the app. man.
>ready to install

Why the difference to the downloads from the yellownotes thread mentioned in #1103 ?
Is the returned header with included flename different,
so that Tear in the garage case works ?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Because the URLs in this forum don't contain the file name.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Bundyo, do you think we could have a new Diablo version of Tear that uses the keyboard like MicroB in Fremantle ? At least the spacebar and backspace keys? I still alternate between my N810 and N900, but am having an increasingly hard time, because these convenient refexes are settling in... :-)

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Well, that should be easy, file me a bug.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Done. May I also insist on the old "connect to network when loading with home page" one ?... :-)

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

do anyone else experience a crash when going to this page:
http://jkontherun.com/2010/02/01/dua...e-and-android/

with tear on a N800 or N810?

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Sort of -- it crashes tear on my N900.

-jkq

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Yes, with Javascript enabled, it crashed tear on my N800. Restarting tear, it offered to load that page again, I said OK, and as it started to load, I disabled Javascript. It took a long time, but loaded and displayed fine. (Too much crap for a single webpage IMO.)

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

been kinda quiet lately. Would be nice if we got to see a bugfix release of some sort.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Yup. Just yesterday I lost another long blog post because I had forgotten all about the TEXTAREA bug... :-)

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

That one is unlikely to be fixed unless someone can provide a small unicode lib.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

Happens to me too,
unless I remember to write it in leafpad / conboy / yellownotes
and then paste it.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

See:
http://bugs.bundyo.org/viewissue.php?issue_no=33
http://talk.maemo.org/showpost.php?p...5&postcount=16

I'm hoping this will be fixed in Mer.

Re: Tear 0.3.1 - a would be beta WebKit based browser
 

have anyone else noticed a issue with tapping images, and not getting a back button when said image have loaded?