Perhaps my application is extensible, users can write plugins for it via api provided by my application, such api and headers will not expose any qt-specific objects.
For instance:
// public declaration available to my app's user
class MyApplication
{
const char* virtual name() const = 0;
};
// private declaration
class MyApplicationExport MyApplicationPrivate
: public MyApplication,
public QApplication{
const char* virtual name() const {return qName();}
};
// public declaration available to my app's user
class MyApplication
{
const char* virtual name() const = 0;
};
// private declaration
class MyApplicationExport MyApplicationPrivate : public MyApplication, public QApplication
{
QString qName() const;
const char* virtual name() const {return qName();}
};
To copy to clipboard, switch view to plain text mode
Questions
1.) Is this the way to go for something like an extensible application? Any potential issue with this setup?
2) As far as I understand, my app's users are indirectly programming with Qt, through an abstract layer of my application, will there be any licensing issues with Qt?
Bookmarks