Project Packaging

Project packages are self-contained compressed archives including all the files needed by the project.

Packaging A Project

In order to share your new app or project, you will need to package it.

Follow the steps below.

  1. Go to the File menu on the Scripting Workbench.

  2. Choose Package.

  3. Select a format for your project package:

    • Project Package is an unprotected format that contains the active project and all its related components (macros, modules, and apps) in a single file.
    • Read-Only Package stores your project and its components in a file that can be read but not edited.
    • Encrypted Package stores your project in an encrypted file where all the macros will be hidden. This file can be read but not edited.

  4. Choose Save. Your project package is saved in the selected location.

Project Licensing and Encryption

Licensing associates a particular app, project, or macro with a specific copy of Image-Pro.

Encryption protects your work against unauthorized use or modification. To use this feature, follow the steps below:

  1. Go to the File menu on the Scripting Workbench.

  2. Choose Package.

  3. Choose Encrypted Package.

    Before assigning a name to your package you will be prompted to choose one of the following encryption options:

    • Basic Encryption is the same as the current method where the project package is protected by a secret key, and its code is never revealed.. You will not be able to see the code but can run the macros or apps without restrictions.
    • Password Protected is a new option that may be of interest for some (to keep some projects private in a multi-user environment for instance). In this case the project is protected by a unique private password, which is required in order to load the project. Once the project is loaded, the code is visible but read-only. Note that if the password is lost, the project can’t be loaded.
    • Licensed is the option that associates the project license with an Image-Pro serial number. The first time such a project will be loaded, you will be prompted to enter a license key, which will then be remembered if valid. The license key as well as the project’s encryption password is also dependent on a secret key that the project developer is the only one to know. A checkbox allows to start the Project License Generator automatically once the project is packaged.
    • Upload to App Center let you send your package to the App Center automatically.

  4. Choose your encryption option and click OK.

Project License Generator

The license key required for licensed projects is created by a tool accessible from within the Scripting Workbench or from the Scripting tab.

  1. Click License Generator. You will see the Licensing dialog.

    This tool prompts for the project package, the secret key defined when the project was packaged, an optional serial number as well as an optional expiration date. The combination of all this information results in a 25 characters string which is similar to the Microsoft product keys.

  2. Enter the requested information and click Generate.

Changing any of the information will result in a totally different license key, and as many license keys as desired for a given project can be created using the tool.

Time limited projects are highlighted in the macro explorer so that users are aware of the availability of their projects.

Expired projects will fail to load.