IDEA is the most cool for j2se development, but most poor for j2me

now I had to debug a j2me game project. it use nokia 7650 sdk, but except nokia 7210 sdk, all others nokia sdk should make the idea throws a exception when try to config the run, and tryp to run. I have send you the exception, but do not find fixing in 5.0.1. You must do not understand the j2me develoment, or you should not do not support j2me for a long time, and support it in such poor way. There is no preverify, no obfuscating in the build process. And excepiton for so man y SDK. Now I think switch to JBuilder....

7 comments

IDEA is new to J2ME. I think you should file requests in JIRA for the things you
want IDEA to do better with J2ME.

Evans Zhang wrote:

now I had to debug a j2me game project. it use nokia 7650 sdk, but except nokia 7210 sdk, all others nokia sdk should make the idea throws a exception when try to config the run, and tryp to run. I have send you the exception, but do not find fixing in 5.0.1. You must do not understand the j2me develoment, or you should not do not support j2me for a long time, and support it in such poor way. There is no preverify, no obfuscating in the build process. And excepiton for so man y SDK. Now I think switch to JBuilder....

0

yes, I post my 2 requests in JIRA, but how many years you implement them? hope not later than 2010...

0

Evans Zhang wrote:

yes, I post my 2 requests in JIRA, but how many years you implement them? hope not later than 2010...


IDEA 5.0 just came out. Requests for big new features probably won't be
implemented until 6.0 in a year or two.

0

Hello Evans,

First of all - you are wrong. J2ME Plugin was tested with S40, S60 and S90
sdks and everything works fine. Second - I've fixed that exception - please
try last EAP build. And after all - we can't support ALL emulators. Now only
emulators with Unified Emulator Interface and some nokia emulators (e.g.
7210) are supported. If you want to work with another emulator you can simply
extend J2ME Plugin with your own one. You have just implement how to start
emulator and how to manage its libs. And thats all.

About preverify: why do you need it separately from build? It is internally
in it now. Without preverification your midlet wouldn't run on any emulator.

About obfuscating - I agree with you - it's hard to start develop j2me without
built-in obfuscation. But as I know noone can use just standart obfuscating
- you always have to do something with jar to minimize it. So some ant task
are essential. We would provide build.xml to simplify starting j2me development.

Did i answer your questions?

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

now I had to debug a j2me game project. it use nokia 7650 sdk, but
except nokia 7210 sdk, all others nokia sdk should make the idea
throws a exception when try to config the run, and tryp to run. I have
send you the exception, but do not find fixing in 5.0.1. You must do
not understand the j2me develoment, or you should not do not support
j2me for a long time, and support it in such poor way. There is no
preverify, no obfuscating in the build process. And excepiton for so
man y SDK. Now I think switch to JBuilder....



0

JBuilder right choise for you, good luck

0

Evans Zhang wrote:

have send you the exception, but do not find fixing in 5.0.1. You
must do not understand the j2me develoment, or you should not do not
support j2me for a long time, and support it in such poor way. There


I'm sorry you've been having such a bad experience, but I have to
disagree - J2ME support is not perfect, but certainly not poor.
I've been doing j2me development with IDEA since somewhere in the EAP
for the 4.x series (using remote debugging), and for a long time IDEA
was the only environment that allowed me to do remote debugging with one
of Nokia's emulators (and I did try them all - JBuilder, Netbeans,
Eclipse, WSAD/J9/J2ME or whatever it is called this week), and with the
J2ME module setup things have become much, much more convenient.
Bear in mind that Nokia's j2me emulators are finicky at the best of
times (and truly atrocious the rest of the time. heh.)

Certainly, in the meantime the competition has become much stronger -
Netbeans in particular is starting to look better and better...

Regards,
Edwin

0

Hello Anna!

without built-in obfuscation. But as I know noone can use just standart
obfuscating - you always have to do something with jar to minimize it.


I don't understand - what do you mean with 'have to do something with
jar' - that's what the obfuscator does, isn't it?

'Standard obfuscating' would probably not be the most optimal, but even
a default profile of 'preserve midlet-class shrink&obfuscate everything
else' will work for most of the cases. For more fine-grained control,
you could always resort to ant-tasks (similar to the j2ee setup -
'normal' support is there, and flexible enough to be tweaked)

So some ant task are essential. We would provide build.xml to simplify
starting j2me development.


that would certainly help - or.. provide a way to call an obfuscator
from the build process itself ;-). It's a logical next step, methinks.

Regards,
Edwin

0

Please sign in to leave a comment.