Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

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

Hi Stefano,

I'm a little confused about what our goal is for CLDC integration. Are you 
basically uploading iCommand code directly to Windows Mobile devices and 
running it from there, without the PC taking any action once the cell phone 
device takes command of the NXT?

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.

BTW Do you develop and compile the code on a PC and then upload it to your 
cell phone? How does the code get uploaded to your cell phone?

- Brian

----- Original Message ----- 
From: "Stefano Sanna" <ger...@ti...>
To: <ptg...@ch...>
Cc: "iCommand Developers" <nxt...@li...>
Sent: Friday, November 24, 2006 1:13 PM
Subject: Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2


> Hi Peter, hi all.
>
> Peter Joosten wrote:
>> We could icommand CLDC into a seperate project in subversion.
>> But how about the next idea ?
>>
>> We could use a java preprocessor, and integrate the code into the
>> "standard" icommand project. This works just like C/C++ #define,
>>  #ifdef #end-if, ...
>>
>> 1. Benefits:
>>    Prevents duplicate code. So we only have to maintain 1 source tree.
>> 2. Possible draw back:
>>    You have to generate the source code for a specific platform by the
>>    preprocessor, before it can be run. (But thats the way C programmers
>>    work all the time)
>>
>> Preprocessing can be done by an Ant target of de build.xml
>
> [...]
>
> From my point of view, porting from JSE to JME is not an automatic
> task, it a creative work. The developer has to substitute classes of
> standard edition with the (more or less) equivalent of micro edition,
> how event he/she has to optimize code if necessary. Moreover, JME
> version will be split into specialized versions for different kind of
> devices. For instance, current version of JNXT works on Windows Mobile
> devices and has a pen-based input; upcoming version for Symbian OS will
> be joypad based: the two versions will be managed through the
> configuration manager of Netbeans, which has been design to handle this
> kind of specific issues of JME development.
>
> I suggest to keep the two separate projects: iCommand and iCommand_CLDC.
> The more iCommand gets enhanced, the more we will have to carefully port
> it to CLDC.
>
> Best regards,
> Stefano.
>
> -- 
> Stefano Sanna - ger...@ti...
> Personal web site: http://www.gerdavax.it
> AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE
>
> Best of Banana
>
> Fratelli D'Etails
>
> Gerda: "Mi hanno contattato per avere idee nuove..."
> Dada:  "... e le vanno a chiedere proprio a te???"
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Nxtcommand-developers mailing list
> Nxt...@li...
> https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers
>