Hi David, > > It took me a while but I have a code base now for QtCreator that keeps > > all previous functionality. > > > > For that I separated the MIME type handling code in QtCreator in the > > stuff that is also in qmime and the application-specific code that > > needs to run on top of that. The continued development in the qmime > > repository made this task quite challenging. Until the code in qmime > > becomes a part of Qt 5 I'd likd to keep the code synchronzied between > > the qmime and the QtCreator repository. > > > > Who should I contact about adding my changes into QtCreator? My favorite > > scenario would be to add a branch where I add changes step by step. Is > > there a review person I should contact? How do you integrate > > contributors into the QtCreator team? > > IMHO this is premature; at some point I'll change qmime to use > QStandardPaths to locate the mimetype files to read; shouldn't QtCreator > simply install XML files into the right location? That will make its code > quite different from what you probably have right now.
QtCreator actually provides a UI to modify the MIME type information that already is in the MIME database. Unfortunately you just brought up a problem with the approach I have been following. QtCreator allows you modify the entries in the MIME database. In my current code I allow that on the contents of the singleton that stores the information. I need to fix that. > And meanwhile you'll have to keep syncing the two copies and porting the > code all the time... I agree. That will not be nice. I need to cover the time though between now and when QtCreator may officially depend on a Qt MIME type addon. If I could add patches to QtCreator until the file structure of qmime could be used then synching the two copies wouldn't be that hard to maintain. What do you think? Michael _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
