The archive file can be used together with a Prolog query answer loop. The archive can be either combined with the runtime library or the development environment. In the following we will show the combination with the runtime library. The combination with the development environment works similarly.

We start explaining the command line approach. As a first step the archive file has to be added to the class path. This means we cannot any-more invoke the runtime library with the –jar option. Instead we have to explicitly provide the main class name. The main class name will be the name of the toolkit. To initialize the mini-mal logic extension we need also to pass an –e option to the toolkit:

java –cp interpreter.jar;minlog.jar \
jekpro.platform.headless.ToolkitLibrary \
  -e jekmin.platform.headless.CapabilityMinlog    # on windows
java –cp interpreter.jar:minlog.jar \
   jekpro.platform.headless.ToolkitLibrary \
   -e jekmin.platform.headless.CapabilityMinlog    # on linux and mac

For the –e option we provide the Jekejeke Minlog capability. This capability would not be found if the archive file would not be in the class path. The –e option causes the toolkit to initialize the capability and thus to provide the functionality of the Jekejeke Minlog capability. The –e option also causes to prompt the end-user for the license.

One can alternatively use the settings dialog to both extend the class path and to set an –e option. These settings will then be stored in the user profile and recalled upon starting the runtime library. This will allow starting the runtime library via the –jar option and nevertheless have the Jekejeke Minlog capability available.

Last but not least all these steps can also be performed programmatically in a Prolog text already for the runtime library. The class path can be extended by the archive file via the sys-tem predicate sys_add_path/1 and extension capability can be initialized via the system predicate sys_init_capability/1.