Extension Definition

An ACT scripted extension has two basic components:

  • XML extension definition file: Defines and configures the content of the extension using XML elements. Each element has a set of required and optional attributes. The element <callbacks> specifies the functions or methods that the extension is to invoke from all those defined in the extension's IronPython script. While you can create the XML file manually, the ACT App Builder automates its creation.

  • IronPython script: Defines the functions invoked by user interactions and implements the extension's behavior. The content of the script is not case-sensitive. You can debug the script by entering commands in the ACT Console or taking advantage of the ACT Debugger.

Note:  You use the IronPython language to develop the functions that the extension executes. Comprehensive information about IronPython is available at IronPython.net, including documentation. Additionally, obtaining a copy of David Beazley's book, Python Essential Reference, is highly recommended. This book is considered the definitive reference guide on the Python language.

For script examples, you have supplied extensions and templates that you can download. Additionally, you can log into the Ansys customer site and search solutions using the following filter selections:

  • For Product, select ACT Customization Suite.

  • For Product Family, select Scripting.

To further limit the solutions shown, you can use the search box at the top of the page.

In addition to the XML file and at least one IronPython script, an extension can include supporting files, such as image files, custom wizard help files, input files, and installed IronPython function libraries and C# assemblies.

While the content in the XML file and the script depend on the Ansys product that is being customized, the need for these two basic components remains consistent.

The following topics describe how to create a very simple extension named ExtSample1: