In my talk on GCF at Akademy, I said in my plan-of-action list that GCF would support ActiveX and KParts components. When I said that, I had imagined that the whole thing would take a couple of months time.
Being around KDE devels helps speed up the process. You can checkout from the SVN sources today and see that there is support for ActiveX and KParts components in GCF. What do I mean by that?
In your GCF Component’s GUIXML file you can have XML elements like this now
<activex title=”Media Player” control=”{22D6F312-B0F6-11D0-94AB-0080C74C7E95}” name=”mediaPlayer” parentWidget=”CStdMainWindowComponent.workspace” />
This will load the media-player ActiveX control on to the workspace widget of the main window 🙂
You can also do this
<kpart mimeType=”text/html” title=”Text Editor” readOnly=”true” name=”part” parentWidget=”CStdMainWindowComponent.workspace” />
[[[GCF also supports serviceType and libraryName for loading kparts :).]]]
This will load the KateDocument part and load it into the workspace. Whats more, the GUI of KateDocument (from its KXMLGUIClient) will be merged with GCF’s GUI. I had quite a few questions about how to do this, but when you have David Faure (of KHTML founder fame) and Till Adam (of Akonadi fame) are sitting right next to you, its easy to figure out solutions to problems.
The whole kparts/activex support isnt perfect, but it is getting there.. Its been a very productive day. 🙂 🙂