A JUMP Extension for JDeveloper 10g

Check out the Project Page on sourceforge.net

Description, Installation & Configuration
Usage
Advanced topics
Next Features

Description, Installation & Configuration
Top

Description
Installation
Configuration

Description

Top of Section

This extension is made out of several components:

jdevextension.jump.projectbuilder.deploy.DeployJUMP
An addin, triggered on the JUMP Deployment Profile, that can deploy the project to a prc-file, as well as run it onto the Palm OS Emulator (POSE).
A Configuration Panel, to locate the appropriate resources on the system. The required resources are:
- The location of the bat-file that starts the compilation using Pila & JUMP
- The location of the graphical resources editor
jdevextension.jump.config.JUMPLocation
An addin triggered from the Tools menu, that dumps the informations mentionned above..
jdevextension.jump.projectbuilder.wizard.JUMPWizardMain
A wizard, that generates a JUMP Project from scratch, with a skeleton for the java code, a graphical resources file, a deployment profile, and the appropriate bmp-files. The java code implements the basic life cycle of a Palm OS Application.
jdevextension.jump.projectbuilder.deploy.CreateJUMPProfile
An addin, triggered from the Navigation Pane (on a Project), to generate the deployment profile for an existing set of files, like the samples provided with JUMP.
jdevextension.jump.projectbuilder.deploy.hConverter
An addin, triggered from the navigation pane, from a file having a .h extension. This .h file is the file associated with the graphical resource file, and that contains some #define directives. This utility turns the content of those directives into public static int statements.
The content of the conversion is placed in the clip-board, and can be pasted into the appropriate java-file.
An association between the resource-files and their editor.
This extension provides the definition of a node that can be associated with the Pilrc Editor, to edit the graphical resources from the Navigation Pane.

Installation

Top of Section

Installation goes exactly like for any other extension. The jar-file called JUMPExtension.jar is to be dropped into the [JDEV_HOME]\lib\ext directory. Then JDeveloper has to be restarted.

Once JDeveloper has been restarted, the extension has to be configured to work properly. This configuration has to be done once. It is done from the menu Tools | Preferences | JUMP Config. Two values have to be provided:

The location (full path) of the Palm OS Emulator executable (Emulator.exe)
The name of the directory where file named makeJUMP.bat is located

In addition, a radio button will tell JDev where to redirect the output of the different commands, in the Log Window of JDeveloper, or in a separate system console.

Config Panel

Association with the Graphical Resource Editor

JDeveloper now provides the possibility to call an external program or command file from the IDE. The extension comes with a bat-file called runPilRC.bat, to launch the Resource Editor with the appropriate file. We are going to associate this bat file with the right kind of node.

Go to Tools | External Tools...
Hit the Add button
In the External Progarm Options tab:
- In Program Executable, provide the full path to runPilRC.bat
- In Arguments, say ${file.path}
In the Display tab:
- Caption for Menu Item, say PilrcEdit
- Tooltip Text, say Editor for Palm Resources
- In Icon Location, navigate to jar:file:/[JDEV_HOME]/jdev/lib/ext/JUMPExtension.jar!/jdevextension/jump/projectbuilder/node/smallPalm_16x16.gif
In the Integration Tab:
- Check Navigator Context Menu
- Check Code Editor Context Menu
- Check Reload Open Files
In the Availability Tab:
- Check When Specific File Types are selected
- Shift RcpNode into the Right Pane
Then click OK

Usage
Top

Generate a new JUMP Project
Edit a resource file
Compile and Deploy
Test

Simplest case: Generate a new JUMP Project

Top of Section

We want it to generate the simplest JUMP infrastructure. First you need to create a new Project in JDeveloper.
Then, you can invoke the Gallery (File | New), and you select the Projects Node, under the General Folder:

New JUMP Project

Choose JUMP Project skeleton. Once again, this has to be done in an existing JDeveloper Project, as the same JDeveloper project can possibly contain several JUMP Projects.

Welcome Page of the Wizard

Provide some relevant informations

Summary

The generated components

Edit a resource file

Top of Section

If some UI changes have to be made, then you want to edit the graphical resource file:

Invoke

Edit

Whenever you've added some components, the .h file has been changed. You want the java file(s) to reflect those changes.

Invoke

Ready

Select and Paste

Compile and Deploy

Top of Section

Once your project is ready, you want to generate the prc after it.

Deploy

Your call!

Test	Top of Section

Once your project has been generated, you can test it.

Invoke

Fully featured! With menu and so on!

See the JUMP Documentation for more details about the way to write Palm Applications in Java.

Advanced Topics
Top

Structure of the Shell Scripts

This extension involves three major components:

JUMP, of course
Pila
PilrcEdit

When the deployment is requested, JDeveloper will actually start a script to do all the job, which is called makeJUMP.bat.


@echo off
rem ----------------------------------------------------------------
rem To be used from the JDeveloper JUMP Extension, not in standalone
rem ----------------------------------------------------------------
setlocal
title JDev Extension for JUMP 2 - Java User Module for Palm
set PROJECT_NAME=%1
set JUMP_HOME=%2
set J2SE_HOME=%3
set PRJ_HOME=%4
rem 
@echo Making project %PROJECT_NAME%
@echo JUMP Tools location %JUMP_HOME%
@echo J2SE located in %J2SE_HOME%
@echo Project directory is %PRJ_HOME%
if "%PROJECT_NAME%"=="" goto usage
goto run
:usage
@echo Usage: %0 [className]
@echo [className].jump might hold project properties
goto theEnd
rem
:run
call %JUMP_HOME%\init
cd %PRJ_HOME%
@echo Making [%PROJECT_NAME%]
@echo -----------------------
@echo Compiling %PROJECT_NAME%.java
@echo -----------------------
%J2SE_HOME%\javac %PROJECT_NAME%.java
@echo -----------------------
@echo Building %PROJECT_NAME%.asm
@echo -----------------------
pilrc -R %PROJECT_NAME%.res %PROJECT_NAME%.rcp
@echo -----------------------
@echo Jumping %PROJECT_NAME%
@echo -----------------------
java Jump %PROJECT_NAME%
@echo -----------------------
@echo Assembling %PROJECT_NAME%
@echo -----------------------
pila %PROJECT_NAME%.asm
@echo -----------------------
@echo Done !
@echo -----------------------
rem %PROJECT_NAME%.prc
:theEnd
del *.bin
del *.res
del *.asm
del *.class
rem Load the PRC
%JUMP_HOME%\userin.vbs
call ~usrin.bat
del ~usrin.bat 2> nul
if /I "%usrin%" == "Y" %PROJECT_NAME%.prc
endlocal
rem pause
exit

As seen above, JDeveloper is sending 4 arguments, used afterwards.
All the skill - and configuration - is located in the file called init.bat, run by the above. This script actually sets a couple of environment variables, used by makeJUMP.bat.


@echo off
rem
rem Oliv fecit, A.D. 2002
rem
@echo Setting Env for JUMP 2
title JUMP 2 - Java User Module for Palm
rem JUMP_HOME is the ABSOLUTE location of the current script
set JUMP_HOME=D:\_Jump\jump
rem JAVA_HOME is the ABSOLUTE location of java.exe
set JAVA_HOME=D:\JDev903.1035\jdk\bin
rem 
set PILRC_HOME=%JUMP_HOME%\..\pilrc-2.8
set PILA_HOME=%JUMP_HOME%\..\Asdk1a1\bin
set PATH=%JUMP_HOME%;%JAVA_HOME%;%PILRC_HOME%;%PILA_HOME%;%PATH%
set CLASSPATH=%JUMP_HOME%\jar\jump.jar;.

This script has to be modified to fit your environment.

Next Features
Top

Automatic generation of an Ant build-file per Palm Application - Implemented Dec4, 2003

End of Text