Steps

AppWave Studio uses five different steps to create and broadcast your tool. Each step contains elements that must be performed in order to create an App. Many of these steps may be automatically completed during the creation and mastering of your App. The type of application you start with (i.e., from a template, an install, or from scratch) determines the level of detail you must complete.

The five steps in creating an App are defined below.

Label

Description

Using the Start Step

There are three options available to build a new App: create from install or create from scratch. You can also add to an existing App. Each has different operations that are necessary to complete.

Note: Another option is to Create an App with One Click. This option is initiated in the Apps tab.

Using the Launch & Brand  Step

The Launch & Brand step is where you select the launch executable and brand the App with product information.
The working folder is populated, and you can set any parameters needed for the application and select an icon to use. The product information entered here is used by the AppWave Host to identify it. This information includes name, version, edition, and publisher. It also includes web site information, system requirements, and product description. You can define multiple entry points for application suites that have more than one application.

Using the App Step

You can configure the following App elements:

Files: Add, remove, or organize files and folders. You can also change the properties of each file as required.

Registry: Add or create new registry entries. You can also view and change attributes.

Environment Variables: Add and/or edit environment variables.

Runtimes: When a product (for example the .NET framework required by RADStudio) needs an execution runtime, it is provided to those who master applications.  Once you make a selection you are requested to save your changes to the current working file in order to analyze required runtime changes.

Custom Scripts: You can attach scripts to key application triggers, such as activation, start, close, and deactivation that can accomplish whatever is necessary.  These scripts are typically small executable files and batch files. Exe, bat, and cmd files are supported to perform acts such as

  Establish a connection to a shared network location before the application starts

  Run a file backup/archive process for user created documents after the application has exited.

Using the Test Step

Opens the Master and Test Your Application page. This displays the output folder and file name. You can change the output folder and edit the file name.

When you click Edit in the App field, a dialog opens asking you to select the App file (extension .stp) to associate with the .tca file.

You also choose the type of Compression you want to use and click the Advanced button to select an encryption type.

For more information see: Understanding the Studio File.

Using the Broadcast Step

This step requires an AppWave URL, either using the default or one that you select.

You can choose the option to remaster the project before broadcasting. This option is selected by default.