<div dir="ltr">Hi Frank,<div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 25, 2016 at 8:18 AM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Kernel-Processes has Delay, Process, Monitor, Mutex, FutureMaker,<br>
Promise, etc. All these work together. They fit nicely in the<br>
category.<br>
<br>
And then there's InputSensor, EventSensor and EventSensorConstants. What.<br>
<br>
Where _should_ these classes belong? Maybe we should have a<br>
Kernel-Device or Kernel-Input category?<br></blockquote><div><br></div><div>IMO they don't belong in the Kernel at all. I would add a UserInterface package and put the prerequisites for Morphic, Smalltalk-80 and Graphics in there. I'd also consider Headful and Headless packages for precursors of headful and headless apps.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(I'll not mention how Kernel's InputSensor >> #keyboard uses<br>
TextConverter that causes a dependency on Multilingual, which of<br>
course has a dependency on Kernel... oh, wait, I did.)<br>
<span class="HOEnZb"><font color="#888888"><br>
frank<br></font></span></blockquote></div><div><br></div><div class="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>