Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Stefano S. <ger...@ti...>]

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???"