The JCOP Tools provide several views to aid the development of Java Card applications. The following views are included with the tools:
|
JCOP Explorer |
|
| The JCOP Explorer shows your projects, packages and applets and assigned AIDs. You can quickly change the elements' Java Card properties by double-clicking on an item. |
 |
JCOP Shell |  |
|
The JCOP Shell is a command line environment which enables communication with card simulations
and physical cards on APDU level.
For more information, refer to the description of the JCOP Shell. |
 |
CAP File Properties |  |
|
After a CAP file is built, the calculated component sizes and dependencies are displayed
in the CAP File Properties view.
The CAP File Properties view contains detailed information about the content of the selected package
(consider that a cap file contains the code for all applets of one package). The information includes the file location,
the code sizes and the AID's of the package, all included applets and their imports. Note: If the view is empty, (re)build your applet and create the CAP file. |
||
 |
Java Card Bytecode |  |
| The Java Card Bytecode view shows the generated Java Card bytecode as well as the current locals stack as you type. Data in this view is only visible if you load an applet in the editor view and place the cursor inside its code. This view contains detailed information about the code of the selected applet (method). | ||
 |
Java Card Memory |  |
| The Java Card Memory view shows information about the memory subsystem if supported by the underlying simulation. The information will be displayed whenever the simulation is suspended. The memory view contains information only if you are running a JCOP simulation in debug mode and the execution is suspended (waiting at a breakpoint). If the simulation is still running, the text "The virtual machine is not suspended" will be displayed. | ||