Um, the Workplace Shell does have a way of associating both Windows-type 
file extensions AND arbitrary 'Filetypes' with certain applications.

There is even a freeware editor for these associations called: ASSOEDIT
http://hobbes.nmsu.edu/pub/os2/util/system/assoed20.zip for those that do 
not like the WPS way of managing those assoications.

Mozilla/2 should use the file-type information already on the system, and 
add its own stuff in the same manner.
It should not displace the current default viewer for already registered 
EG it could register itself as a viewer to PNG files as well as 
registering an WPS-filetype (which is just an arbitrary string) 
"image/png" and associate it with itself. When saving receiving a PNG type 
file, Mozilla/2 should then write
the matching information to the EA's.

If one would then right-click on the file, and next its the menu entry 
"Open", that menue will contain all programs associated 1) with the 
extension 2) with the WPS file-type. 

The download process should look at the registered files and if it finds a 
match among the registered assoiciations, then it should offer to open the 
file with that application. (eg for application/pdf call Acrobat Reader)

I'm totally against yet-another file-type registry.

Can't see a fly in the ointment, perhaps someone else will..

Best regards, Martin

Reply via email to