[haiku-bugs] Re: [Haiku] #5821: [FileTypes] some images open in WebPositive
- From: "stippi" <trac@xxxxxxxxxxxx>
- Date: Mon, 26 Apr 2010 16:18:54 -0000
#5821: [FileTypes] some images open in WebPositive
----------------------------------+-----------------------------------------
Reporter: diver | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1/alpha2
Component: Kits/Application Kit | Version: R1/Development
Keywords: | Blockedby:
Platform: All | Blocking:
----------------------------------+-----------------------------------------
Comment(by stippi):
In the case when there are many applications with support for the specific
type indeed a seemingly random application will be picked. This can easily
be solved by specifying a preferred application for the specific type. I
don't believe we will or should have applications which claim support for
the same specific type in the default image. So this problem comes up when
the user installs many similar applications and then he will know what's
going on and can fix this easily.
The second case of seemingly random applications launching is when there
are many applications claiming support for the super type. But this is
exactly the situation that you point out, which is that one application
will already be configured as preferred for the super type.
So for me, it boils down to your argument that there is now more
configuration necessary than before, which I believe is wrong. Let me show
you how that is not the case for me: Haiku predefines several MIME types
for text. Many of which have a preferred application hard-coded. For
x-email it's Mail. For x-source-code it's Pe, a 3rd party package. For
html it is BeZillaBrowser, another 3rd party app. This just shows how
broken the system was before. When I run a clean image of Haiku for the
first time, I always have to configure Pe to be the preferred app for
several text/ MIME types, since I want makefiles and jamfiles to open in
Pe. With my change, I won't have to do this anymore, since Pe should claim
support for these specific types, while StyledEdit should not and with my
change, the system will ''automatically'' pick Pe (granted, as long as I
have only one editor installed, but that should be the case). If we were
to put another editor on the image to replace Pe, the system would still
work, without having to mess with the predefined MIME types, just like we
would have had to mess with text/html prior to my change.
IMHO, the different super types have very different needs actually. With
image/* it's almost sensible to have a '''preferred''' application, but
already image/svg+xml shows how the system can be flawed. With text/*,
StyledEdit is not a '''preferred''' application, it is a '''fall-back'''
application at best. And in fact I believe this is the situation for the
majority of types, i.e. application/*. For video/* and audio/* we have
another case similar to image/*. But here it is even more sensible to
control the preferred application via the super type and handle special
cases with sub-types.
In any of these cases, I find it more practical, if the system
automatically choses an application that handles a type well, and not a
'''fall-back''' application that just handles the super type. I believe it
will require ''less'' configuration, as seen in my example for text files
where I have to manually configure Pe to replace StyledEdit.
As for reverting the changes, you have not managed to convince me at all
and I would like feedback from other users before I would revert this
change.
--
Ticket URL: <http://dev.haiku-os.org/ticket/5821#comment:7>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
