Forum

I just wanted to solicit a bit of feedback about our scripting interface and the articles and sample code posted so far. We have put a lot of work into creating a comprehensive object model, and although some things are not yet exposed there should be enough for "real world" extensions.

We have already posted a couple of samples that cover quite a bit of ground. Although the extensions are relatively short, there is still a lot to digest. So for those of you who are thinking about the scripting inteface or have already started working with it, what do you think? Did we provide enough functionality and documentation? Did we start out with samples that are too complex? Are there basic how-to type articles that you would like to see?
 

I just started looking at what you guys have done. And at first glance I like the examples. In fact, I emailed you for the API download, but I'm wondering if using the script/extension interface would be simpler.

Still exploring.
-Steve
      
-Steve

I guess that depends on your level of experience and what you want to do with the software. Many things can be done through the scripting interface, and much easier than with the API, so I would recommend using that if you can. Creating a plug-in using the API requires knowledge of COM and a development environment such as Visual C++ or Delphi that can create COM objects with custom interfaces based on our type library. So I can still send you the SDK if you wish, but you should be aware of what you're getting into.
      
Anatoly Ivasyuk
DTLink Software

I am far more comfortable in a CBuilder/Visual Studio or Delphi environment than the scripting language. But I'm going to continue with the learning curve on the script language, or actually the learning curve is finding all the necessary COM objects to do what I want.

Thanks
-Steve
      
-Steve