[Nxtcommand-developers] Making Icommand ready for different NXTCOMM implementations

[Peter J. <ptg...@ch...>]

We should separate API (for end users) from implementation.

At this moment from the icommand.nxtcomm package the NXTCommand class is
part of the API (method close()).

package icommand.nxtcomm should NOT be part of the API

Proposal:

Make an interface NXTCommand in the package icommand.platform.nxt
with open() and close() methods.

Change access modifiers in icommand.nxtcomm to package (= no access
modifier) as much as possible to prohibit access by end users. 

In the distribution Javadoc of package icommand.nxtcomm will not be
included, since it is no longer part of the API.

Peter Joosten.