Julien Pierre wrote: > > I think a much more elegant solution in OS/2 would be to use something > like a MIMETYPE Extended Attribute on the files to query the MIME type. > This EA may in fact already be defined. If it is not, I think it is an > opportunity for Warpzilla here to innovate a little and use it. > Warpzilla could write this new MIMETYPE EA to files that it saves from > the web, where the MIME type is available, to the local disk. That way, > if the file is loaded later on in Warpzilla, the same MIME type will be > available, regardless of the extension, or the filename that the user > chooses to save the file as. I believe this is similar to the way the > Mac does things, and the proper way to do things in OS/2.
It looks like I am not the first one to have this idea. See the output of the following google search : http://www.google.com/search?hl=en&q=os%2F2+extended+attribute+and+mime+type Apparently there are already some applications that use such an EA for a MIME TYPE. I think I remember seeing it in the MMPM/2 documentation as well. It may be even be defined in the core OS/2 documentation. Admittedly, not all OS/2 applications write that EA, but they should at least preserve it. Warpzilla would still have to deal with opening local files that don't have the EA. In that case, I would like to have Warpzilla prompt me through a UI to choose a MIME type, listing MIME types known to Mozilla (accross built-in loaders, plug-ins, and helpers). If the file was writable and the file system supported EAs, then the MIME type chosen would be persisted to the file in the EA, so that the prompt would occur only once. As a last resort, a Windows-like registry mapping of extensions to MIME types would be acceptable.
