Java/OPL issues

The resource compiler and Aiftool were originally developed as part of the EIKON framework — which was developed in C++. Consequently, while the tools are nominally programming language neutral, they are actually more useful for C++ developers than Java or OPL developers.

The issues related to using these tools in OPL and Java are detailed in the following sections.

OPL developers should not use Aiftool.

This is because the OPL translator will automatically create the aif for an OPL program which uses the APP keyword. The use of the keyword is described in the OPL SDK.

Java developers can use Aiftool to provide a customised icon and caption for their applications.

However Java applications either cannot, or should not, be made to implement the other system level capabilities and MIME type priorities which may also be specified in the aif file: see Application capabilities and MIME support. Consequently, it is not necessary to specify them in a Java aif resource file.

OPL developers have full access to the functionality of the resource language and resource compiler. They are recommended to use the epocrc tool to compile resources: for details, see Resource compiler with preprocessing epocrc.bat.

However, unlike in C++ development, resource files in OPL do not allow direct access to the Uikon framework. Consequently, while OPL developers can use resource files to localise toolbars/menus, they cannot use them to automatically generate the user interface.

Java developers do not need to use the resource compiler.

While it is theoretically possible for Java developers to access the information stored in resource files, there is little benefit. In C++ and OPL resource files are used to localise applications, however Java provides classes for this purpose.

In addition, Java applications cannot use resource files to automatically build the user interface — which is a key advantage of using resource files in C++.