Henning wrote:Well, I'm sure his planned rewrite will include some 'spywork'.
ActiveX would suspend the, W-L-M, cross-platform idea, to just Windows.
Spywork? What is that?
If any development language wants to be truly useful and successful it has to adopt most of the technologies that the operating system it is targeted for.
Whether you like it or not Windows is highly dependent on COM internally and ActiveX is a part of COM.
As Bernd claims that KBasic is compatible with VB6 any VB developer will expect this feature out of the box.
I am not saying Bernd to implement support of ActiveX at core level in KBasic. It should be something external so that the core code is not disturbed and it can remain portable across OSs.
What I am telling is that there should be some way by which a developer can exploit and use ActiveX controls, DLLs & TypeLibs. But unfortunately at present KBasic does not have support for loading external controls whether ActiveX or QTs Components.
For ActiveX/COM support I did point Bernd to an Open Source lib called Display Helper (find it: http://disphelper.sourceforge.net/). Of course using this lib directly is not possible unless Bernd adds support for calling external C/C++ libs like Python or compiles this library in KBasic itself. On way out is to build an extension or component loading interface as VB has support for ActiveX.
