That's a good point on the colors.  Even though I'm an old fan of Smalltalk/V I
found myself
writing code that changed the "Easter Egg Bright" colors of the debugger and walk
back windows
as soon as I started doing any serious development.

And sure enough here in Squeak the first thing I do is set the preference for
#uniformWindowColors to true.
Makes all the windows white by default.

Incidentally the code still exists in the image to check for the
#uniformWindowColors flag
but it is no longer being initialized in the Preferences by default.  Was that
intentional?

  - Steve

Dino wrote:

> What we need would be something like Java RMI so we don't have to go downloading
> the whole image all the time...  Smalltalk almost feels like a whole operating
> system...  nobody wants a new operating system just to program in one specific
> language.  When I started with Squeak, I didn't like the idea of carrying around
> 5mb of stuff, I'd prefer just to carry a small 100k of code around with me.
>
> Some of my friends who disbelieve in Squeak also don't like the super-bright
> colors that morphic comes with...  I think they are more used to the nice
> contrast of emacs or something.  Squeak was the first time I ever programmed in
> a "green" background.
>
> The font is also a little queer...  it would be cool if there were obvious and
> easy ways to change the font and color...  would make Squeak a whole lot more
> pleasant to beginners who are used to programming hard-core C in B/W xterms
> using some fixed-width font.
>
> -- Dino
>
> Peter Smet wrote:
> >
> > If Smalltalk is to become a more effective 'virus', programs
> > must be able to be passed along and replicated without
> > a 5-10 MB image. A virus is only as plentiful as the number
> > of hosts it can infect. Practically, this will mean users
> > should be able to hack together small utility programs and
> > pass them along and run them without moving Megabytes across
> > the network.