[Cooker] Generalize update-menu when installing.

[Gourichon Stephane 01 44 27 88 04]

I have an idea that, IMHO, would be very beneficial for the comfort of
the end-user.

In the spirit of the automated 'update-menu' when installing RPMS,
which provide unified menus acrosses window managers, there should be
a mime-type <=> application association database (whatever form it
takes).  This would complete what you've make to kappfinder and
wmconfig: instant update (and no limitation to a pre-programmed
"kappfinder database")

Thus, when I install gv, a file in a wmconfig-like directory declares
that gv know how to handle application/postscript and application/pdf
(and gzipped files). In whatever clever way, kfm of gmc will take that
into account immediatly.

BTW, when right-clicking on a file icon, there should be more than a
list of applications that can open this mime type, but also:

1) a way to easily open the dialog that allows to choose the default
   application to launch for the mime-type associated with the file,
   or for this file alone, or all files in this directory (or other
   matching mechanism).
   Example: I may have a directory ~/sound/work where all .wav files
   are to be, by default, edited with my favorite editor (say,
   broadcast 2000) because they are under work, and in other
   directories a simple wav-playing program should be called.

   (But... I should write this to a KDE/kfm mailing-list, no ?...)

2) a way to query urpmi and ask it "which on earth (yet uninstalled)
   application do I need to launch this program ?". A window would
   pop-up and give the user a list of application he might install
   from any urpmi path. (A mechanism like netscape plug-in finder)


Oh, BTW, file extensions suck, mime-type rules. A file(1)-like
mechanism (or simply calling the file utility) is a good (not perfect)
way to identify a file type. The extension /may/ be an indication of
the file content, but we should never rely on it (kfm does this,
partly).  What I mean: do not consider file extension as the basis for
your database (but I'm sure you would have done the Right Thing
anyway).

--
Stéphane Gourichon