Re: [Nxtcommand-developers] Making Icommand ready for different NXTCOMM implementations
Status: Beta
Brought to you by:
bbagnall
From: Peter J. <ptg...@ch...> - 2006-11-09 01:23:37
|
On Thu, 2006-11-09 at 02:21 +0100, Peter Joosten wrote: > 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. > Putting the interface in the "icommand" package would be a good (/better?) alternative ! > 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. > > |