On Tuesday, April 30, 2013 08:10:32 Kevin Ottens wrote: > Why not reuse KPluginFactory either as is or slightly modified? What we're
most of KPluginFactory is mostly about the macros. i'm not sure registerPlugin makes any sense anymore given the new interface metadata features in Qt5's QPluginLoader. It is only used by KPluginFactory::create(const char *iface, QWidget *parentWidget, QObject *parent, const QVariantList &args, const QString &keyword), which i'm not sure is used in many places (not the easiest thing to grep or search in lxr for). it incurs overhead for every plugin as the name is stored in a global hash. would be nice if that could be removed .. i need to look further into QPluginLoader and what it is possible of though. there is also a fair amount of boilerplate in KPluginFactory around the QVariantList, component names and translation catalogs (which is currently commented out ..) so that could all go. Automatically loading the correct translation catalog is something that needs to be re-added somehow as well .. and as I look at it, I'm not sure how that would get into Qt proper. In any case, I guess I could start with a copy of KPluginFactory, but I don't think much would survive. I'll look into it in any case .. and if David has any feedback before I do so, that'd be very much appreciated. -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
