Icon-mime type associations

[Thomas Leonard]

On Thu, Sep 16, 2004 at 12:55:34PM +0200, Allan Sandfeld Jensen wrote:
[...]
> I would still advocate for a more detailed content based hierachy.  Besides 
> being used for selecting icons, it could also be used in file-managers to 
> list all wordprocessing files or executables, without tying the file-manager 
> to a limited and quickly outdated list of predefined mimetypes.

Also, it makes it easier to find a type if it's in a catagory like
'Wordprocessor documents'. Please go ahead and define some (looks like
GNOME and KDE both have this).

Eg:
	<mime-type type='image/png'>
	  <catagory:usage catagory='bitmap-image'>
	</mime-type>

However, either we need a pre-defined list of catagories, or we need a way
to specify translations, which means making a catagory an object in its
own right.

We can use the existing inheritance for this:

	<mime-type type='image/png'>
	  <sub-class-of type='catagory/bitmap'>
	</mime-type>

Treating them as types would allow other advantages; a user could search
for a 'A word-processor document with July in the name" (rather than
searching specifically for a Lyx file, for example).

It seems we're building up quite a list of things that behave like MIME
types but aren't actually (application/executable,
audio/gstreamer-supported-format, catagory/bitmap). Maybe they should all
use non-offical media types.

> To be a bit more specific. We currently have inheritence based on _format_, 
> WAVE is also RIFF, Ogg/Vorbis is also generic Ogg, etc. 
> I would like to have a parallel system based on _type_ (or usage). MSWORD-doc 
> is also a type of wordprocessing-document, shellscripts is also a type of 
> executables, Type1 is also a type of Font, etc.


-- 
Thomas Leonard			http://rox.sourceforge.net
tal at ecs.soton.ac.uk	        tal197 at users.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1