On 31 January 2016 at 13:42, Bert Freudenberg <bert at freudenbergs.de> wrote:
> On 30.01.2016, at 19:49, Frank Shearar <frank.shearar at gmail.com> wrote:
>> I'm not really interested in InputSensor &
>> EventSensor's relationship. I care that Kernel has these classes, when
>> nothing in Kernel even uses them. They don't belong there.
>
> Isn’t the Kernel’s purpose to provide things to be used by the rest of the system?

Sure, but EventSensor isn't. "Kernel" means the most important/central
part of something, and I'd argue that keyboards and mice aren't. I
don't write interactive programs, I guess, so I don't want

>> Thing is, Sensor is referenced by a whole ton of packages - Tools,
>> Graphics, Sound, Morphic. So clearly putting EventSensor in ST80 is
>> wrong. Therefore, I think we need to put InputSensor, EventSensor and
>> EventSensorConstants into _System_.
>
> I guess the distinction between “Kernel” and “System” isn’t quite clear to me.

I guess, for me, Kernel contains those things that are essential to a
running Smalltalk image. System contains stuff that's generally useful
to most things - most, but not all.

> But yes, it looks odd compared to the other classes in “Kernel-Processes”. Probably it was put there originally because it provide the interrupt watcher process.
>
> Being I/O related it would fit better in “System-Support” with Beeper and Clipboard. (although System-Support looks like a catch-all category … glad you’re thinking about better organization)

Yeah, that sounds good. I had thought of "System-Sensor", as a
possible alternative.

And I agree re System-Support being the "misc" bucket. I wouldn't mind
figuring out how to split that category into more meaningful units.

frank

> - Bert -