On Thursday 15 September 2011 09:50:02 ext David Faure wrote: > As Wolf-Michael noted, the API for creating mimetypes doesn't really belong > in there; that's far too system-dependent, and far too "rare" compared to > queries.
If there are no objections then I will go ahead and remove - QMimeTypeRegistry::insertMimeType() - QMimeTypeRegistry::insertServiceAction() - QMimeTypeRegistry::iregisterApplication() - QMimeTypeRegistry::iunregisterApplication() > And the implementation should parse the files generated by update-mime- > database, which is much faster -- and I can provide the code for that, > having already written all that code for KDE. That sound to me like the starting point for the Linux backend. > So, from qmime.git, neither the API nor the implementation make much sense > to me, only the unit tests are reusable. Well, the API can still provide > input for qtaddonmimetype.git of course. I will see if I can integrate the unit tests into mine. > 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. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
