[squeak-dev] How should one implement a custom window color for a custom window?

H. Hirzel hannes.hirzel at gmail.com
Sat Sep 16 11:47:15 UTC 2017


On 9/16/17, tim Rowledge <tim at rowledge.org> wrote:
> A couple of months back Eliot asked about this and I have a few minutes to
> spend to maybe fix it.

> I notice that Model>windowColorToUse sends #customWindowColor, which is not
> implemented.

There was also an issue earlier this year with the tool 'Extras' menu
, then 'Graphical imports' not following the user interface  theme. A
partial solution was implemented. I'll dig out the details and answer
in the approriate thread.


> Which would seemingly lead us to expect a debugger but I see
> some very… interesting code in UserInterfaceTheme where a dNU: is caught and
> Very Odd Things are done. Ten out of ten for creative and intriguing code,
> minus several million for completely obscured intent.
> At the least it would be nice to have an implementation *somewhere* that
> explains what is being done, why, and maybe even how we can move to a
> simpler scheme.
> Related things I noticed -
> EToys-Squeakland adds Object, StringHolder & TranscriptStream class >
> windowColorSpecification which seem to be in need of removal.
> PreferencesPanel class>windowColorSpecification is seemingly in need of the
> chop
> WindowColorRegistry, the only sender of windowColorSpecification, is in the
> deprecated categories, though yes, i nthe 5.1 deprecation pile so maybe is
> has to stay for now.
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Strange OpCodes: WK: Write to Keyboard

More information about the Squeak-dev mailing list