Installation Experiences (by UweGeuder - 07 Feb 2003)
In the install.properties file I did not really understand how install.path should be set. I used "." (dot) and it think it worked.
I did not succeed to use the prepacked ant. Firstly, it doesn't seem to contain anything that can be run from the command line. After adding my own wrapper I got an error about missing SAX classes. A completely separate Ant download and installation did it without further (obvious) problems.
After the installation the plugin looks nice and functional. However I haven't been able to use it because of the JDK problem described in JavaTwoMicroEdition.
-- PavlinZahariev - 20 Feb 2003
Hi, install.path is the path to folder, where installation archive was unpacked. Its probably redundand and you are right that "." should work. I'll change this in next release.
Prepacked ANT is actually not an ANT installation. Please see my note above about ant setup. Directory /${install.path}/ant contains a task for calculating file size (handy aftet jar generation) and an optional component for FTP task, which I use to deploy to remote servers.
Please see my note about target JDK in JavaTwoMicroEdition.
Cerainly there are plenty of bugs in the plugin itself. Some were already fixed and others are still waiting to be discovered :).
I'm sorry to react, that late on this note. I was watching plugin forum for reactions. Please post your notes primarily there.
-- Lee Crawford?
This is great work! I had some trouble, though, getting the run targets in the autogenerated ant build.xml file to work. In particular, I had to add a line to the run target for the midlet name and also change 'deploy' to the 'deploy.local.path' property. These changes were required:
<target name="runner" depends="checkdist">
<exec executable="${toolkit.home.dir}/bin/emulator">
<arg line="-Xdevice:${device.type}"/>
<arg line="-Xverbose:class,classverbose"/>
<arg line="-Xdescriptor:${project.dir}>${deploy.local.path}/${project.name}.jad"/>
<arg line="${midlet0.name}"/>
</exec>
</target>
Also, it would be nice to have separate targets for each of the useable device types. I added the following to obtain this:
<target name="run-defaultGray">
<antcall target="runner">
<param name="device.type" value="DefaultGrayPhone"/>
</antcall>
</target>
<target name="run-defaultColor">
<antcall target="runner">
<param name="device.type" value="DefaultColorPhone"/>
</antcall>
</target>
<target name="run-motorola_i85s">
<antcall target="runner">
<param name="device.type" value="Motorola_i85s"/>
</antcall>
</target>
<target name="run-blackberry">
<antcall target="runner">
<param name="device.type" value="RIMJavaHandheld"/>
</antcall>
</target>
<target name="run-palm">
<antcall target="runner">
<param name="device.type" value="PalmOS_Device"/>
</antcall>
</target>
<target name="runner" depends="checkdist">
<exec executable="${toolkit.home.dir}/bin/emulator">
<arg line="-Xdevice:${device.type}"/>
<arg line="-Xverbose:class,classverbose"/>
<arg line="-Xdescriptor:${project.dir}/${deploy.local.path}/${project.name}.jad"/>
<arg line="${midlet0.name}"/>
</exec>
</target>
-- PavlinZahariev - 18 Mar 2003
Lee, thank you for your opinion!
I think, that putting all these targets (and any other new phone emulator option) into ant script could be very usefull if want to automate the process of running emulators. In current version of the plugin, you can simply use the combo next to "Run" toolbar button to select different phone, then press "Run" or "Debug".
I fixed some bugs in last version. The new build is posted bellow.
Also I gonna release the sources, which by far are not as good as I'd wish too, but I think there is a usefull framework how to manip with options which can be stored in project.iws and also edited in dialog.
Please, let's discuss this plugin in forums, otherwise this page becomes huge and messy.
as far as i can see, j2mesupport allows only SUN WTK.
am i wrong?
most part of j2me products is created for some custom platforms, for example Siemens SMTK and Nokia NDS. is it possible to use plugin with such developing toolkits?
ps sorry my english 
-- TWikiGuest - 10 Aug 2003
3rd party SDK for J2ME availability
Your plugin working just great !
I have a question though - I'm using device-specific SDK (for
Motorola) - is it possible to customize your plugin for my needs ?
-- AleksandrKostick - 23 Oct 2004
3rd party SDKs
I'm receiving multiple requests for 3rd party SDK integeration.
It is Nr.1 on my todo list, but since I have no experience at all with such SDKs, I need to dig "a bit" into the field and find a way how to integerate diferent platforms without having to destruct the plugin code each time. I'd be very thankful if you guys provide me with some structured information about the SDK you wish to have integrated (thanks to DJINN, who emailed me about Motorola\SDK v4.3). Also please be patient, because free time is (as almost always) an issue too.
-- PavlinZahariev - 24 Oct 2004
How to install plugin for IntelliJ 4.5?
Hi, i tried to find description how to install J2ME plugin for IntelliJ 4.5 (j2mesupport_041009.zip), but I didn't find it. Main plugin page only states "...After a successful installation of J2MESupport ...", but I didn't find any description how to do it. I'd be grateful for a hint, as I'd like to use IntelliJ for J2Me development.
Cheers.
-- MichalSankot - 29 Oct 2004
Hint for installing plugin for IntelliJ 4.5
I was able to get "J2ME Support" to show up in project settings for IntelliJ 4.5 by:
- Expand j2mesupport_030220.zip, edit install.properties and run the install.bat (which runs ant). This will put j2mesupport.jar in the plugins directory (also works with jar file in j2mesupport/lib).
- Rename j2mesupport_041009.zip to j2mesupport.jar copying over the j2mesupport.jar created in previous step.
-- PaulBaclace - 10 Nov 2004
|
|
