|
87
|
1 |
|
|
|
2 |
- testmidletstart is simple native console program. Started from eshell to test that Java
|
|
|
3 |
applications can be started from native applications. The name of the Java application to be started
|
|
|
4 |
has currently been hard coded to SPtesti (midlet-name).
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
- midlets/sptest contains the SPtesti midlet.
|
|
|
8 |
If you modify the .java code, you can easily compile the .java file like this:
|
|
|
9 |
javac -source 1.4 -target 1.4 -cp \epoc32\release\winscw\udeb\java_signature_test.jar testimidletti.java
|
|
|
10 |
Then you can update the .jar file using WinZip.
|
|
|
11 |
|
|
|
12 |
When SPtesti midlet is started, it shows the command line and instance count in the form.
|
|
|
13 |
When the midlet is restarted, it shows the new command line and new instance count.
|
|
|
14 |
|
|
|
15 |
|
|
|
16 |
- midlets/plat_req contains platRequest midlet.
|
|
|
17 |
The .jad file has some sample platform request URLs that edited in the midlet and then used
|
|
|
18 |
when making platform request.
|
|
|
19 |
When making platform requests that start native applications, this midlet must be signed to
|
|
|
20 |
operator or manufacturer domain.
|