David, I agree with most arguments, but i have some remarks. Did you though about use case of "portable" application on win (single .exe) and bundles on Mac Os X? How will they install mime types and where? For example, Qt Creator has no installer on OS X and it can't copy xml files to proper location and call update-mime-database.
Only thing can be done is to put xml files into bundle, like current implementation does. Next, we have to put these xml files manually/using script during building app bundle. Much easier to put one huge database near app. I agree that use-case of "global" mimes types - shared by all applications is quite useful - for example for win-KDE developers. >From the other side, not so many people use qt-based applications under >win/mac and we can't afford to install mime files into filesystem, they should >be placed inside bundle. So we have 2 use-cases - "global" and "local" mime types. I agree, global mime types should be implemented using update-mime-info, but what about local? We can store text files, plain xml files (foo:)), single binary file. I think in perspective we have to support all 3 ways. Next, about in-memory mime types. How can we have to support plugin architecture? If i developed plugin for QtCreator that handles some specific mime type - "image/blp", for example. In my opinion, user should install single *.dll as a plugin and he shouldn't manually copy xml description for image/blp with it to let Creator know how to open this format. The workaround here is to use 3rd location and store xml/plain text files in Qt resources (and store file within .dll), but i really dislike this way, better in-memory mime types. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
