Both options are not available right now, but I was asked several times already whether it's possible to export the features of KLayout rather than integrating a scripting engine into KLayout. In order words: whether to provide the KLayout API as a library.
This would open some opportunities and technically that is possible. For example, you could export KLayouts MainWindow or LayoutView as an ActiveX control with the ActiveQt framework. The Ruby classes could basically be exported as a COM server too.
But: that's a BIG effort and first of all the architecture of the application has to be turned upside down and the application and widgets parts have to be separated more clearly. Second, doing so creates some legal issues - you don't want to include a GPL'd component into your application if you want to sell it.
Comments
See this. Basically:
David
Hi Andski,
you mean as an engine or as a UI component?
Both options are not available right now, but I was asked several times already whether it's possible to export the features of KLayout rather than integrating a scripting engine into KLayout. In order words: whether to provide the KLayout API as a library.
This would open some opportunities and technically that is possible. For example, you could export KLayouts MainWindow or LayoutView as an ActiveX control with the ActiveQt framework. The Ruby classes could basically be exported as a COM server too.
But: that's a BIG effort and first of all the architecture of the application has to be turned upside down and the application and widgets parts have to be separated more clearly. Second, doing so creates some legal issues - you don't want to include a GPL'd component into your application if you want to sell it.
Matthias