On Thursday 15 September 2011 10:55:41 ext David Faure wrote: > > > On the other hand I'm not sure that querying the association with > > > applications and the open/view/edit distinction belongs there, it > > > doesn't > > > seem very cross- platform -- but that's a separate discussion. > > > > Similar to KDE, I wanted to express the difference between open/view and > > edit, and also leave room for potential other uses. > > KDE doesn't do that, actually :-)
I was referring to the second parameter of KMimeTypeTrader::query() which is genericServiceType. It is either 'KParts/ReadOnlyPart' or 'Application'. The KEditFileType utility exposes that as 'Embedding' and 'General' tabs. I creatively translated that into open/view and edit. > The desktop entry standard says: in the .desktop file of the application, > list the mimetypes it supports. This doesn't leave room for open/edit > distinctions. > > We use "service menus" (a different kind of .desktop file, filemanager- > specific) to complement that and offer additional context-menu actions. Thanks for that input. I see that now in my /usr/share/kde4/services/katepart.desktop. > But I think determining mimetypes is a big enough job in itself, and the > relation to applications shouldn't be rushed in with it. We might even have > to get more freedesktop.org standards about this first, the current > solution for determining the default application preference order is > different between KDE and gnome, as well as the extra stuff like open/edit > and service menus. I see where you are going. We'll need to provide libQtCore.so for either Gnome, KDE or whatever else, then. Mark Shuttleworth might appreciate that though. To make the discussion about an API easier I could separate the applications out into a seperate class QMimeTypeHandling. What do you think? _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
