On Mon, Feb 18, 2013 at 07:32:29PM +0100, Bert Freudenberg wrote:
> 
> On 2013-02-18, at 19:28, Louis LaBrunda <Lou at Keystone-Software.com> wrote:
> 
> > Hi Bert,
> > 
> > Thanks for the reply.
> > 
> >> On 2013-02-18, at 18:09, Louis LaBrunda <Lou at Keystone-Software.com> wrote:
> >> 
> >>> Hi Dave,
> >>> 
> >>> I have written two classes to manage a bunch of irsend command calls (to
> >>> change the cable box channel) at a given time and reschedule it for another
> >>> day.  I have two questions.
> >>> 
> >>> 1) Where would be a good place in Squeak to document how each class works?
> >>> The classes are fairly simple.  One class holds the information for what
> >>> command should be run and when.  The other class manages a group of similar
> >>> (by programmer choice) commands and run then at the proper time.  How they
> >>> work together requires some documenting.
> >> 
> >> The class comment.
> > 
> > I thought about the class comment but it looks like it takes only one line.
> > Unless I'm looking in the wrong place or at it wrong?
> 
> Click the the question mark button between instance and class in the system browser.
> 
> The one line is just an annotation for convenience.
> 
> >>> 2) It seems to me the two classes I have written would fit nicely into your
> >>> OSProcess... group of classes.  I would like to make these classes
> >>> available under the MIT licence and I hoping you will accept them into the
> >>> fold and distribute them with your package.  I'm not familiar enough with
> >>> Squeak to even know where to start to distribute them on my own.
> > 
> >> Certainly calling out to a special-purpose tool does not belong in the generic OSProcess package.
> > 
> > It is not a special-purpose tool.  There is no mention of LIRC or irsend in
> > either class.  The classes run and schedule any command that Dave's
> > OSProcess>command: can handle.  It does things like run the command every
> > Tuesday at 20:00 hours.
> 
> It's up to Dave then. Still seems rather special-purpose to me ;)

Well sure, by all means, please send a copy :) If it's not too big you can
just post it to the list here.

If it looks like a good fit, we can put it in OSProcess. There is also nothing
wrong with you just making a small project on SqueakSource (or whatever is
replacing it, I'm not sure I've figured that out). You could just say your
project depends on OSProcess, and that would be fine too. That way you could
enter it on SqueakMap (the package catalog) so that someone looking for irsend
could spot it more easily.

Dave