Re: Galeon2 extensions plan
Tim Bannister <[email protected]>
| Newsgroups | gmane.comp.web.galeon.devel |
|---|---|
| Message-ID | <[email protected]> |
On 21 Oct 2002, Marco Pesenti Gritti wrote: > 3 Mime dialogs > > I think it's better to separate the two implementations because: > > - They are very different implementation. And the base one is dead > simple. > - It would be unacceptable to bloat galeon base with an unnecessary > mime database and dialog code > - There are some conflicts. > I dont want predefined mime types in the base (I want to be asked to > save a tgz). > If someone install the plugin and use it, if he goes back to base for > some reason, he will get not editable predefined actions. Even the base needs to try to Do The Right Thing for file extensions. Users new to Galeon will often want saved files to have an extension that reflects their media type (eg ".tar.gz" for gzip encoded application/tar) If you access https://example.com/secureimage.cgi and get JPEG image data, the saved file should have the extension ".jpeg" (or ".jpg"). There could be an optional plugin to allow the choice of GNOME suggested or original extension, of course. But for naive users the former behaviour will help. -- mailto:[email protected] - +447980408788 - Tim Bannister ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en