Instantiate Engine

This page shows you how to instantiate the iink runtime and configure it to fit your needs.

Engine creation

The iink SDK runtime is represented by an Engine object. This object will let you create other key objects, configure the recognition and fine-tune the SDK behavior.

Data provided in parameter corresponds to your activation certificate. Please check its validity if the engine creation fails.

Configuration

A new engine must be configured to let iink SDK know which kind of content is to be recognized.

Being a flexible toolkit, iink SDK also comes with many configuration parameters. While the default values make sense in most cases, it may sometimes be required to configure them to suit your needs.

Accessing the configuration

Configuring the recognition

To recognize math, shapes or text in any language, the engine needs to be created and pointed to the required assets.

Assets packages consist in a set of configuration files (*.conf) that specify required recognition parameters combined to binary files called resources files (*.res). The resources files host everything that the engine requires for the recognition.

MyScript iink SDK default configurations should be suitable for most needs. So in most cases, you don't have to care for them. If you need to go further, you can learn how to modify or write your own configuration files (advanced).

Make sure to properly deploy these files along your application as well. A good practice is to implement error management at editor level to be notified of recognition configuration error.

Language recognition configuration

Default language for text recognition is en_US english. So one of the first recognition tuning you might want to do is modifying the language.

MyScript language names start with a two-letter language code (using the ISO-639 standard), followed by an underscore and a two-letter country code (using the ISO-3166 standard). For example en_US for US English.

MyScript delivers some ready to use language packs so that updating language is an easy task that you can perform in a few steps:

Step 1 Download the corresponding language pack, so in our example, select the italian language:

Packs for additional languages or content types are available on MyScript Developer Portal or from your MyScript Partners account.

Step 2 Install the pack in your application project: The language pack consists in a *.zip archive containing a configuration file (*.conf), and associated resources files (*.res) to be extracted in your project path.

Make sure to properly deploy these files as the .conf file refers to the .res files with relative paths. So take care to keep the archive folder structure when extracting the files

Step 3 Modify the engine configuration language in you application code:

  • Set the value of the configuration-manager.search-path key to the folder(s) containing your language configuration file(s) (*.conf).
  • Set the value of the lang key to match your language

For instance, set it_IT for the Italian language, as corresponding resources are described in it_IT.conf:

When using Recognizers, the language configuration key should be prefixed by recognizer.

Content-specific configuration

MyScript iink SDK comes with many configuration options. Some are general, like the ability to choose the location of the temporary folder to store work data on the file system, and some depend on the type of content you manipulate. For instance, it is possible to activate or deactivate the solver for math equations.

The full list of supported configuration options can be found in the dedicated section.

Editor-level or Recognizer-level configuration

Engine-level configuration corresponds to the default, global configuration. It is possible to override configuration values at editor-level or recognizer-level which is useful if you manage several parts or recognizers with different configurations.

Injecting configuration at the editor level is also very convenient when working with a "Raw Content" content type, because this content type is flexible and allows specific behaviors according to its editor configuration:

text_math_shape.json
{
  "raw-content": {
    "configuration": {
      "analyzer": {
        "bundle": "raw-content2",
        "name": "standard"
      },
      "math": {
        "bundle": "math2",
        "name": "standard"
      }
    },
    "classification": {
      "types": [
        "text",
        "shape",
        "math",
        "drawing"
      ]
    },
    "recognition": {
      "types": [
        "text",
        "shape",
        "math"
      ]
    },
    "convert": {
      "shape-on-hold": true
    },
    "shape": {
      "snap-axis": []
    },
    "eraser": {
      "erase-precisely": false,
      "dynamic-radius": true
    },
    "auto-connection": false,
    "edge": {
      "policy": []
    },
    "interactive-blocks": {
      "auto-classified": [
        "text",
        "math",
        "shape"
      ],
      "feedback": [
        "text",
        "math"
      ],
      "feedback-hints": [
        "text",
        "math"
      ]
    },
    "pen": {
      "gestures": [
        "scratch-out",
        "strike-through"
      ]
    },
    "line-pattern": "grid",
    "guides": {
      "show": [
        "alignment",
        "text",
        "square",
        "square-inside",
        "image-aspect-ratio",
        "rotation"
      ],
      "snap": [
        "alignment",
        "text",
        "square",
        "square-inside",
        "image-aspect-ratio",
        "rotation"
      ]
    }
  },
  "convert": {
    "convert-on-double-tap": false
  },
  "math": {
    "solver": {
      "options": "algebraic",
      "numerical-computation": [
        "at-right-of-equal-sign",
        "at-question-mark"
      ],
      "enable-syntactic-correction": false,
      "display-implicit-multiply": false,
      "auto-variable-management": {
        "enable": true,
        "scoping-policy": "closest"
      }
    }
  }
}
interactivity.json
{
  "raw-content": {
    "classification": {
      "types": [
        "text",
        "drawing"
      ]
    },
    "recognition": {
      "types": [
        "text",
        "math"
      ]
    },
    "convert": {
      "shape-on-hold": true
    },
    "shape": {
      "snap-axis": [
        "triangle",
        "rectangle",
        "rhombus",
        "parallelogram",
        "ellipse"
      ]
    },
    "eraser": {
      "erase-precisely": false,
      "dynamic-radius": true
    },
    "auto-connection": true,
    "interactive-blocks": {
      "feedback": [
        "math"
      ]
    },
    "pen": {
      "gestures": [
        "underline",
        "scratch-out",
        "strike-through"
      ]
    },
    "line-pattern": "grid",
    "guides": {
      "show": [
        "alignment",
        "text",
        "square",
        "square-inside",
        "image-aspect-ratio",
        "rotation"
      ],
      "snap": [
        "alignment",
        "text",
        "square",
        "square-inside",
        "image-aspect-ratio",
        "rotation"
      ]
    }
  }
}
drawing.json
{
  "raw-content": {
    "line-pattern": "none",
    "recognition": {
      "types": []
    },
    "classification": {
      "types": []
    },
    "convert": {
      "shape-on-hold": false
    },
    "shape": {
      "snap-axis": []
    },
    "interactive-blocks": {
      "auto-classified": []
    },
    "eraser": {
      "erase-precisely": true,
      "dynamic-radius": true
    },
    "auto-connection": false,
    "guides": {
      "show": [],
      "snap": []
    },
    "pen": {
      "gestures": []
    },
    "rotation": [
      "image"
    ]
  }
}

To avoid any side effects when injecting a configuration JSON, it is recommended that you first reset the configuration to its defaults:

To restore your part configuration after reopening its package, you can save it in its metadata.