[squeak-dev] InputSensor, EventSensor miscategorised?

Frank Shearar frank.shearar at gmail.com
Fri Jan 29 21:28:09 UTC 2016


On 29 January 2016 at 20:41, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Hi Frank,
>
>> On Jan 29, 2016, at 12:01 PM, Frank Shearar <frank.shearar at gmail.com> wrote:
>>
>>> On 29 January 2016 at 18:07, tim Rowledge <tim at rowledge.org> wrote:
>>>
>>>> On 29-01-2016, at 9:43 AM, Chris Muller <asqueaker at gmail.com> wrote:
>>>>
>>>> You can't unload a superclass without unloading its subclasses.  So,
>>>> let me rephrase the question:  How could EventSensor be unloaded and
>>>> then reloaded?
>>>
>>> Ah, wrong question in this case. I suggest that we don’t need to even consider the issue of unloading either sensor class since it would be better to clean things up and simply get rid of InputSensor completely.
>>
>> In a Trunk image, only Smalltalk at: #Sensor points to EventSensor.
>> Nothing points to InputSensor. Nothing points to
>> EventPointerConstants.
>>
>> So why not in a postload of ST80, evaluate
>>
>>    Environment current bind: #Sensor to: EventSensor
>>
>> ?
>
>  Sounds reasonable, but why not use (or add) EventSensor class>>initialize?  The post load strikes me as too fancy.

Because I'd forgotten I could do that :) There is an EventSensor
class>>install which sounds like it would do the right thing, but it
doesn't. It seems like the right thing to do then is to add an
initialize like this:

initialize
    Environment current bind: #Sensor to: EventSensor.

Sound good?

frank

>> frank
>>
>>> tim
>>> --
>>> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
>>> Strange OpCodes: DCBP: Detonate Chair on Bad Password


More information about the Squeak-dev mailing list