From kfm-devel  Sat Oct 08 10:41:40 2011
From: Marcus Harrison <marcus () harrisonland ! co ! uk>
Date: Sat, 08 Oct 2011 10:41:40 +0000
To: kfm-devel
Subject: Re: mimetype problems...
Message-Id: <1731346.aqJUIxjHRG () marcus-inspiron-1011>
X-MARC-Message: https://marc.info/?l=kfm-devel&m=131807052728384

On Thursday 20 January 2011 20:48:07 Kevin Krammer wrote:
> On Thursday, 2011-01-20, David Faure wrote:
> > Yep. However it would actually be correct here, since it would also
> > fulfill the contract where "invokeBrowser starts a webbrowser". Except
> > that this time, konqueror would show an imageviewer part. The only
> > trouble here is that it assumes that all webbrowsers can show non-
html
> > files embedded, and while this is true of konqueror and iirc firefox, I
> > wonder if e.g. rekonq can do that?
> 
> I would be surprised if any webbrowser would have a problem with such 
links.
> Webpages contain links to all sorts of data types, they have to cope with
> clicks on them anyway.
> 
> Cheers,
> Kevin

The problem is generally /how/ browsers cope with such links. If you try to 
open a PDF in firefox, for example, it opens a Download dialogue ("Would 
you like to open, or save the file?"), defeating the point of opening the web 
browser at all (if you're going to open the web-browser just to tell it to 
open the document viewer, why not just open the document viewer?).

I also don't see why opening a remote image in the image viewer is worse, 
or "less correct", than opening it in a browser. If this discussion is on how 
Konversation should open unknown mimetype links, I'd think the solution 
would be new KRun(url) as David pointed out.

Marcus Harrison