From: Martin K. <mk...@iu...> - 2006-09-13 11:36:26
|
Hello guys, I made a quick port to J2ME using CLDC 1.1 and MIDP 2.0 for Java mobile phones. Actually almost everything worked as I expected, the "largest" portion to re-implement was the transport code (OscPort). The only class that was missing in MIDP 2.0 was the BigInteger class, which I fortunateley found as a pure Java implementation on the net. A part from that the rest of the code was pretty portable, I needed to apply a few changes to the way Vectors were used (addElement() instead of add() and copyInto() instead of toArrray(). This can be easily ported back to the J2SE javaosc, which actually allows to use the same code base for all. Although the UDP transport is fully functional right now, I don't see any point of paying a mobile phone provider for transmitting OSC messages to a device next to myself, so I will implement something like a OscPortInBT and OscPortOutBT in order to allow local Bluetooth communication. Maybe the class hierarchy for the transport layer could be changed accordingly to something like: OscPort | | OscPortIn OscPortOut | | OscPortInUDP OscPortOutUDP OscPortInTCP OscPortOutTCP OscPortInBT OscPortOutBT If you want I can add the TCP layer for J2SE and UDP/TCP layer for J2ME right away, I will probably need some time to do the Bluetooth part I reckon. I have an important request regarding the portability of javaosc. Right now it seems that javaosc is compiling on J2SE as well as on J2ME Personal profile (based on JDK 1.3.1) and on J2ME MIDlet profile. I didn't try it, but I reckon it even compiles on JDK 1.1 This is really great like that, and I think with little effort this portability could be maintained in the future changes to javaosc. cheers, Martin |