Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2
Status: Beta
Brought to you by:
bbagnall
From: Brian B. <bba...@mt...> - 2006-12-07 18:31:16
|
We're talking about making two seperate code bases, correct? One code base for iCommand for PC's and one code base for Cell Phones/PDA's using JME? In other words, if we make a change to the Motor class in the iCommand project we'll have to remember to manually go and make the same change to the Motor class in the JME project too? To me, that sounds like a nightmare and not the proper way to structure the project. We should go with the one tiny pre-processor command in the NXTCommand class (plus a different ant-build script for the JME version) and then we can keep the iCommand project unified. Stefano, do you agree with this? I'm just going by guesswork since I've never done this before. If we use the preprocessor command, does that get in the way of your own development projects? - Brian ----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" <nxt...@li...> Sent: Wednesday, December 06, 2006 3:39 PM Subject: RE: [Nxtcommand-developers] iCommand 0.5 CLDC pre2 > Brian, maybe you can roll some dice to make a decision ;-) > > Maybe from an academic point of view, preprocessor is the way to go. > > As far as I understand, Stefano, prefers to have a seperate ported > ICommand copy in his project. Maybe that should be the main argument > to make a decision. See how it works. > >> >> Well, I'm probably the last guy who should have final say on which way to > |