On 29/09/11 21:52, Harri Porten wrote: > On Thu, 29 Sep 2011, Thiago Macieira wrote: > >> On Thursday, 29 de September de 2011 04:13:41 Philip Ashmore wrote: >>> Hi there. >>> >>> Believe it or not, this issue was thrashed out years ago and the solution >>> still in use today is called the Component Object Model - COM. >>> >>> I've written a really simple implementation you can play with called >>> v3c-dcom http://sourceforge.net/projects/v3c-dcom/ >> >> For those of us not familiar with COM programming, can you briefly explain >> what >> would be necessary to achieve this? What would be in the public headers and >> what would the plugins need to do? > > Unlike the Q_INTERFACES approach such a system would solely rely on .h > files and have no need to pre-process, compile and link anything. And > fwiw, Qt already had a COM-compatible system once that did not survive the > beta phase however: > > http://qt.gitorious.org/qt/qt-integrity/blobs/HEAD/dist/changes-3.0.0-beta6 If I understand correctly, that was a customer API, not part of Qt's implementation, which is what's being discussed here.
Yes, COM is difficult to pick up, but Qt already provides an ActiveX framework http://developer.qt.nokia.com/doc/qt-4.7/activeqt.html although it's Windows only. > > I just don't know whether I wanted to ask for that much as I'd be fine > with evil casts as long as I know what to cast to :) Which was the case in Windows before COM. > > Harri. > _______________________________________________ > Qt5-feedback mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
