Opened 15 years ago
Last modified 4 years ago
#4412 assigned bug
Several MIME types have only the generic icon.
Reported by: | bga | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | User Interface | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Several MIME types under the application hierarchy (and the application super type itself) only have the generic file icon. This is after a clean build from Linux using xattr (with ReiserFS). See attached screenshot.
Attachments (1)
Change History (9)
by , 15 years ago
Attachment: | MIMETypes.jpg added |
---|
comment:1 by , 15 years ago
comment:2 by , 15 years ago
If BeOS' FileTypes' listview had shown icons like Haiku's does, the generic icons would likely not feel as strange as they might do now to a person having grown accustomed to Haiku's (prior) use of the colorful Be Application icon.
I personally wouldn't mind using Haiku's "Be Resources"-icon for the application supertype (and subtypes) and let the generic icon have its icon all to itself. (The resources icon looks like the generic one - a plain document - but with a tiny app icon in it.) But then of course the Resource type would need a new icon.
comment:3 by , 15 years ago
Milestone: | R1/alpha1 → R1/alpha2 |
---|
comment:4 by , 15 years ago
Milestone: | R1/alpha2 → R1 |
---|---|
Version: | R1/pre-alpha1 → R1/Development |
Not an alpha blocker.
comment:6 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:7 by , 8 years ago
Component: | - General → User Interface |
---|
comment:8 by , 4 years ago
I don't think there is a much more specific icon that would apply, reading rfc 2046 gives the impression that this is mostly binary data, so perhaps a derivite icon based on the Generic icon is fine, with some ones and zeros on it?
This is intended. BeOS uses the generic file icon for all mime types that don't provide an icon (themselves or by inheritance). I think it's Tracker that provides it since BeOS' application/* does not have an icon. The end result is that the generic icon gets used for the application subtypes that have no icon.
Haiku's application.super used to have the "Be Application" icon, overriding Tracker's generic icon. It's great that the application supertype has an icon, but it was the wrong one. There is no good reason to use the icon of the "Be Application" (our executables) by inheritance for all application/ subtypes without icons. Most of them are not executable. There are probably application subtypes around which aren't even binary. It does not make sense to display e.g. Word, Excel or postscript documents, URL types, compression formats, etc, using the Be Application icon, as if they were applications.
One could likely have the same result (having the generic icon for application subtypes) by removing the icon of Haiku's application.super, but I think it's more correct for the supertype to have an icon than for Tracker to use its fallback icon.