Scripting Editor Imprimer cette rubrique Page précédente Un niveau supérieur Page suivante

Accueil >  Programmers' Reference >

Scripting Editor

The Scripting Editor of Authentic Desktop uses the Form Editor components of the Microsoft .NET Framework, and thus provides access to the Microsoft .NET Framework. This means that JScripts and VBScripts not only work with the Authentic Desktop API—which is a COM API and the API of Authentic Desktop—but can also access and use classes of the Microsoft .NET framework.


You can therefore create and use your own macros and forms within Authentic Desktop, and thus add to and modify the functionality of your installation of Authentic Desktop.


Note:Visual Basic is not supported as a language in the scripting environment. Only VBScript and JavaScript are. Ensure that you use VBScript syntax and not Visual Basic syntax in the scripting environment.


Note:Microsoft's .NET Framework 2.0 or higher is a system prerequisite for Scripting Editor, and it must be installed before Authentic Desktop is installed.



The Scripting Editor

The Scripting Editor (screenshot below) opens in a separate window and is accessed via the Tools | Scripting Editor menu command in the Authentic Desktop GUI. The programming languages that can be used in the Scripting Environment are JScript and VBScript. The scripting language can be changed by right-clicking the Project item in the Project window, selecting Scripting Language, and selecting the language you want.







What you can do with the Scripting Editor

In the Scripting Editor, you can create Forms, Event Handlers, and Macros to build up a Scripting Project. A Scripting Project can then be set as the Global Scripting Project for Authentic Desktop, thus enabling scripts in the Scripting Project to be used in the application. Additionally, different Scripting Projects can be assigned to different Authentic Desktop projects, thus allowing different scripts to be used for different Authentic Desktop projects.


Every script project can define the .NET runtime version it wants to use. An application can handle multiple scripting projects with different .NET runtime versions simultaneously, but the appropriate .NET version must be installed. For example, script projects with .NET 4.0 will only run on computers having .NET 4.0 installed.



Documentation about the Scripting Editor

The documentation describing the Scripting Environment (this section) is organized into the following parts:


An overview, which provides a high level description of the Scripting Editor and Scripting Projects.
A list of steps required to create a Scripting Project.
An explanation of Global Declarations, together with an example.
A description of how to create Forms.
A discussion of Authentic Desktop-specific event handlers.
An explanation of how to use macros in the Scripting Editor and in Authentic Desktop.


© 2019 Altova GmbH