Please guide me how to dev J2ME to my E680

[overconda]

I'm newbie in J2ME programming but actually I work on PHP at my office.

I have ..
1. J2ME Wireless Toolkit 2.2
2. Motorola SDK 5.1.2 for J2ME

I have J2ME book but it's very general information. It said about compile on KToolbar in WTK but has not said about specific phone model , just like E680.

I can write a small program and compiled with KToolbar but I have no idea to make it Touchscreen or using E680 components. Do you know how can I start the right way

Thank you very much

[tazzix]

I use NetBeans 4.1 www.netbeans.org it even allows visual editing and navigation flow creation. However, for UI I normally use thinlet (like XUL). Do remember to install NetBeans Mobility Kit as well. This should be a good start setup. Otherwise you may want to shell out for JBuilderX with MobileKit, but nothing beats opensource

Have a look at my page, things are not updated though in a long time:
http://tazzix.com/index.php?l=p01/p31

[rpconnect]

i am a complete newbie to j2me development and can strongly suggest the netbeans stuff. in less than a couple of hours i had put together an app that communicated through the OS and to a bluetooth serial port connection. Plus it comes w/ a bunch of example apps that really helped me get up and running. best of luck.....

[tazzix]

@rpconnect

Bluetooth serial port?
Oh I thought moto had left out the JSR for bluetooth. But you have the phone and I don't, yet

I have some APIs for MIDP1.0, I finished a wrapper on ksoap to save myself from writing similar code again and again, and most phones ship the JSR for SOAP anyways so this brings SOAP to every J2ME phone. I was about to start a sync API to work on BT, SOAP, IR, file. But did not have the motivation to start and its making this not only MIDP2.0 dependent, but also on the JSR for bluetooth.

Earlier I had ported thinlet, and implemented charts, floating point emulation, and OO Mapping for the ugly RMS. All being MIDP1.0 compatible mean that the target audience would be huge for any application utilizing these APIs.

Its only that I have not made any full blown application yet on top of them.

[maxx_730]

They did leave out JSR-82, he probably used cytux's way to communicate with the system.

[mudassar]

@overconda
hi.. although the above suggestions are pretty good and if u can .. follow em. But if u r still interested in MIDP, the touch screen features are not hard to implement...

there is a well supported class in MIDP 2. called CUSTOMITEM. google it out with tons of examples. In short, what it does is, it lets u create ur own graphics from scractch.. say u want a background image and on top of it u wanna place some buttons or text which is clickable, because this class has pointer-press events.. so u can use those events to make a graphical touch to ur application..
u can create ur own checkbox's or radio buttons by using Graphics and paint method. Graphics and paint is the key on this class... so draw anything u wish from scratch....make it clickable by using pointer events...

i do it all the time

[rpconnect]

@rpconnect
Bluetooth serial port?
Oh I thought moto had left out the JSR for bluetooth. But you have the phone and I don't, yet

maxx_730 is right, even though Mot. is responsible for specifying JSR-82 it just aint on the phone. to get to the bt com port i use rms records to send shell commands to the OS (thanks to cytux!!!)

Earlier I had ported ... OO Mapping for the ugly RMS.

can you elaborate a bit on this??

[tazzix]

@rpconnect

That sounds really interesting to use J2ME just for the front end and leave the power work to the unrestricted power OS. That's where I like Python like on the Nokia Series 60 phones.

I will look for more details of cytux's work.

About the OO mapping...
I have a small framework inspired by an article somebody from IBM wrote. This way you can store objects or collections into the RMS and retrieve them later. I also have basic filtering and iterators which can be used for searching, sorting, etc. My floating point emulation class is also compliant to this framework. Its very convinient and on these devices there is usually no size restriction on RMS so you can do wonders

There are some details on my site and the reason why I can not GPL this code but any Java person may free me from this restriction and the code can become free.

[tazzix]

@overconda
hi.. although the above suggestions are pretty good and if u can .. follow em. But if u r still interested in MIDP, the touch screen features are not hard to implement...

there is a well supported class in MIDP 2. called CUSTOMITEM. google it out with tons of examples. In short, what it does is, it lets u create ur own graphics from scractch.. say u want a background image and on top of it u wanna place some buttons or text which is clickable, because this class has pointer-press events.. so u can use those events to make a graphical touch to ur application..
u can create ur own checkbox's or radio buttons by using Graphics and paint method. Graphics and paint is the key on this class... so draw anything u wish from scratch....make it clickable by using pointer events...

i do it all the time

You can do it in MIDP1.0 as well. Initially http://thinlet.com/ supported J2ME but discontinued it, I ported its newer releases to MIDP which can be found on thinlet yahoogroups.com, they also release an official MIDP release last month but I modified mine too much to also support non-touch screen devices that I'll stick to my own version.

And its based on XUL, and there is a NetBeans plugin, not to forget the UI designer. So now I do not put a week in a project for UI widgets and design, I put half a day

[cytux]

Thinlet sounds interesting. I found here:

http://ngphone.com/j2me/opensource/ui.htm

some other GUI development kits and don't decided which I will prefer, cause I don't yet needed it. Has anybody some ideas what would he prefer and why?