On Saturday 02 November 2013 22:36:03 Alex Merry wrote: > Moving this to the list. > > On 02/11/13 19:36, David Faure wrote: > > On November 2nd, 2013, 6:21 p.m. UTC, *Alex Merry* wrote: > > Related question: would it make sense to try to implement this by > > directly enumerating the QImageIO plugins (and reading their JSON > > files)? Possibly with some hacks for the built-in decoders. > > Because it looks to me like we could then ditch the .desktop > > files for the plugins (including the ones for Qt's own > > plugins/built-in code).> > > If we want to get rid of the .desktop files, why don't we just implement > > KImageIO on top of QImageReader/Writer, rather than duplicate its code? > Only that QImageReader/Writer do not make it easy to correlate mimetypes > and image format names.
Right. But do we still need image format names? (I guess the answer lies in http://lxr.kde.org/ident?i=KImageIO but I didn't dig into it yet) And if we do need this, how about we add that feature to QImageReader/Writer instead? -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel