Introducing the Components of the SDK
What kind of development you decide to do depends largely on what you need to accomplish and what you are capable of doing, so it’s really an individual decision. For example, you may be a C++ programmer who is interested in creating a compiled plug-in for SOFTIMAGE|XSI; or you may be a technical director who just needs to automate some repetitive tasks.
XSI’s SDK can accommodate both types of users, since it provides support for both C++ programmers and script authors. The SDK consists of these APIs:
• The Scripting Command API—provides access to the same commands that drive the SOFTIMAGE|XSI user interface. This is a great API to get started with, since most commands are logged to history, so you can find out how to script in XSI interactively.
• The XSI Object Model—can be used either with the Active Scripting Engine to create VBScript, JScript, PerlScript and Python scripts or any .NET language, such as C#.
• The C++ API—pure C++ development kit available to create compiled library files for plug-in and shader development for XSI.
For more information on these APIs, see Understanding the XSI SDK Architecture.
|
In previous releases of XSI, the object model could also be used with the COM (Component Object Model) Compiler to create compiled ActiveX plug-ins. However, it is now strongly recommended to use either C# or the C++ API to create compiled plug-ins and the legacy COM API Developer's Guide is now available only for historical purposes. |
In addition, the dotXSI file format provides a text-based file conversion format which comes with its own API, the Crosswalk SDK. Together, these features allow you to import and export information between XSI and another 3D animation package or a game engine.
SOFTIMAGE|XSI v6.01