> -----Original Message----- > From: [email protected] [mailto:qt- > [email protected]] On Behalf Of > Nicolas Arnaud-Cormos > Sent: Thursday, August 22, 2013 4:23 PM > To: [email protected] > Subject: [Qt-creator] Qnx Plugin status for 3.0 > > Hi all, > > With Qt Creator 3.0 being worked on, we look at the current status of the > Qnx plugin, and would like to propose a major change: splitting the plugin in > 2 > plugins: > * Qnx plugin (for Qnx devices), > * BlackBerry plugin (obviously for BlackBerry devices, using the BB10 NDK). > > Currently, the two are merged into one for historical reasons, but there's no > technical reasons to do it: > * Qnx is mostly working like the remote linux plugin > * BlackBerry has its own set of tool to package/deploy the application > * there are actually only 2 classes shared (QnxAbstractQtVersion, > QnxBaseQtConfigWidget) between the two, and a bunch of utility methods > in QnxUtils > > The plan is to have a Qnx plugin, and a BlackBerry plugin depending on the > Qnx one. > [...]
Is there a use case for using the Qnx plugin without the BlackBerry one, or do you envision other plugins that depend on the Qnx plugin, but not the BlackBerry one? Every additional plugin has some overhead (load-time, mostly). If this split is just for a 'cleaner architecture' I'm not sure it's worth it. Regards, Kai _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
