[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [Bug 154698] Won't open some TIFF files
From:       Pino Toscano <toscano.pino () tiscali ! it>
Date:       2007-12-29 0:00:05
Message-ID: 200712290100.09833.toscano.pino () tiscali ! it
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Alle sabato 29 dicembre 2007, James Richard Tyrer ha scritto:
> It is totally unnecessary and very likely to cause problems.

It is necessary, and below I'll explain why.

> > Each .desktop is addressed to a different subject. -
> > libokularGenerator_foo.desktop Tells _okular_ that foo is a generator
> > available - okularApplication_foo.desktop Tells _KDE_ that okular is
> > an application for the mimetypes the foo generator can read -
> > okularFoo.desktop
>
> No, this is totally unnecessary, you can use one 'desktop' file with all
> of the MIME types in it [see attached] like the other KDE applications
> do and it will work fine.

This is *exactly* the way I don't want.
If someone installs a 3rd party backend associated to a -different- mimetype, 
then your okular.desktop will be totally unuseful for making that backend 
visible to the "world".

The idea is that each backend "advertizes" itself about its presence to okular 
and to KDE (acting as redirect to okular).

> > Tells _KDE_ that okular is a KPart for the mimetypes the foo
> > generator can read (essential for printing and konqueror embedding)
>
> The KPart is a slightly different issue.  It is harder to fix but will
> cause even more confusion since if the user doesn't use the correct
> embedded Okular, it won't work.

There are lots of users using KPDF and okular embedded within konqueror.
I'm not going to stop that usage just because you don't understand the real 
problem, and why we chose the current solution.

> > This was one of the cleanest solution we had so far; other solutions
> > requires special threatment in the mimetype handling (like virtual
> > mimetypes). Albert and me had a discussion with David Faure about
> > this, and we agreed that _for now_ this can be an acceptable (and
> > no-code needed) solution.
>
> Since part of this issue can be easily fixed, I see no reason not to do
> so.  Please take the time to try it before you tell me that a very
> complicated solution is preferable to a simple one because it is
> "clean".  Replace the "okular.desktop" file with the one that is
> attached and remove all of the files: "okularApplication_*.desktop" from
> you system.  Notice that everything still works the same.

... until you have no 3rd part backends (like I explained above).

> Users normally "fiddle around" with the settings of which application is
> used to open a given MIME type.  That is why it is part of the GUI.  You
> seem to be making what I feel is a big, but common, mistake which is to
> presume that users will not change the defaults.

With the current system, users can actually change the file associations.
That's another one of their advantage.

-- 
Pino Toscano

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]