Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Brian B. <bba...@mt...>]

----- Original Message ----- 
From: "Stefano Sanna" <ger...@ti...>
>>
>> If that is the case, maybe the best thing to do would be to use the 
>> NXTComm interface, creating NXTCommCLDC. The user can choose to use CLDC 
>> via the icommand.properties file setting. So far we have NXTCommRXTX, 
>> NXTCommBluez, and NXTCommSun (using the Java Communications API). It 
>> looks like your changes to the code are exclusively in the NXTComm class.
>
> I changed code in the Properties class and others. Even if we use 
> different implementations for NXTComm interface, the bytecode for standard 
> edition will be not compatible with JME devices. In other words, once the 
> code as been modified, it must be compiled especially for the JME target. 
> The same is required for libraries.
>
> That's why I suggest to have to source tree for JSE and JME. It

Could we keep the same source tree but just have two seperate releases: one 
compiled for standard JVM and one compiled specifically for JME? (2 
different downloads on the home page but one common source code base).  Some 
of the other classes would be useless to the JME build and could be excluded 
with the ANT-build script.

- Brian