This message was intended for the list
> -----Original Message-----
> From: Peter Joosten [mailto:ptg.joosten@...]
> Sent: Wednesday, November 08, 2006 6:24 PM
> To: Brian Bagnall
> Subject: RE: [Nxtcommand-developers] icommand.nxtcomm.bluez
> > So rather than a package for each, we could just make an
> interface called
> > NXTComm with the relevant read and write methods, then have
> > RXTXNXTComm, etc... The code could default to the best/most
> > common one but
> > if the variable exists then use the appropriate object.
> I will take care of it.
> > A user named Rojit from the leJOS mailing list says he got more
> > than one NXT
> > brick working with iCommand but then I changed it to singleton
> > static method
> > calls to match leJOS (i.e. Motor.A.forward() instead of
> > nxt.motorA.forward() ). Not many people have multiple NXT bricks
> > but if it's
> > possible to control more than one through Bluetooth we should
> > implement it
> I will see if I can come up with a proposal.
> I will also look at the usage of static, access modifiers, ...
> The existing code can use some cleaning up.
> > and close() althogether. People seem to favor the commands that
> > match leJOS
> > though. I'm not really sure what to do.
> Stick to the Lejos API as much as possible.
> > > icommand-bluez-native (eclipse CDT, c)
> > > ======================================
> > > How about the name of the native library?
> > > Proposal: libicmdbluez.so
> > >
> I will commit a project icommand-bluez under icommand-projects
> Peter Joosten.