Re: [Nxtcommand-developers] Making Icommand ready for differentNXTCOMMimplementations

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

>> Puttng the NXTComm interface in package 'icommand' would even be better.
>> I need  this interface to support multiple implementations.
>>
>> Then I do not need an Interface NXTCommand.
>>
>> This would however mean a "bigger" change in the API.
>>
>> NXTComm.open() and NXTComm.close() instead of NXTCommand.close()
>
> That's fine. Makes more sense really, since you are opening/closing the
> communications link.

But what package would NXTComm reside in, and we still need to make those 
for Bluez etc... don't we? i.e. BluezNXTComm, RXTXNXTComm... We need to give 
the user one singleton class they can use to access methods.

- Brian