> 11.3.3 | Borland JBuilder X

> If you want to use JBuilder X and it is not installed, first install JBuilder X and follow the installation wizard instructions. Run the SMTK installation program in maintenance mode. The SMTK will find the installed JBuilder X IDE. Select JBuilder X to integrate the SMTK into JBuilder X.
> After integration of SMTK into JBuilder X you can examine the integration by opening the menu
> Tools → Configure JDKs… (see Figure below).
> Figure 48: JBuilder X – JDK settings
> The libraries included with the SMTK can be examined by opening the menu
> Tools → Configure Libraries… (see Figure below).
> Figure 49: JBuilder X – Siemens Library

> 11.3.3.1 | Examples

> There are sample projects provided with the SMTK. These projects can be found in the JBuilderSamples directory of the SMTK installation directory. This directory is accessed by opening a project using the menu File → Open Project… (see Figure below).
> Figure 50: JBuilder X – Sample Projects
> Open the Project (e.g. “HelloWorld.jpx”), rebuild the sources and start the debugger using the micro edition (context menu “HelloWorld.jad” → Micro Debug using “HelloWorld” ).
> Figure 51: JBuilder X – Starting the debugging session

> 11.3.3.2 | Starting Debug Session without Downloading Java Files

> It is possible to start a debugging session without download of the Java files (*.jad and *.jar) again. The emulator has to be started with an additional parameter “-noload” and downloading of the Java files is suppressed. Please add the parameter in the following emulator running configuration line as described in the figures above.
> Select the project properties (e.g. “HelloWorld.jpx”) and edit the emulator configuration.
> Figure 52: JBuilder X – Edit project properties for starting the emulator
> Set the additional emulator parameter “-noload” and press OK.
> Figure 53: JBuilder - Runtime Configuration
> Keep in mind, that you have to remove this emulator option before starting debugging session with download of Java files. The Java files are not updated in the Flash files system of the module while option “-noload” is set!
> The same procedure is used for all different JBuilder IDE versions.