I actually like it that the type of �windows are having different colors. In the bar at the bottom, I can quickly determine monticello browser, test runner, package browser, method finder, just by checking the color. I vote against throwing away the colors.�

The default behaviour of the gray colors is absolutely more suitable than the colored version.�

Kind regards,

Bart

On Tue, Dec 15, 2009 at 1:58 PM, Marcus Denker <denker@acm.org> wrote:

On Dec 15, 2009, at 1:53 PM, Alain Plantec wrote:

>
>
> From: Alain Plantec <alain.plantec@univ-brest.fr>
> Date: December 15, 2009 1:52:28 PM GMT+01:00
> To: Pharo-project@lists.gforge.inria.fr
> Subject: windowColorSpecification
> Reply-To: alain.plantec@univ-brest.fr
>
>
> Hi all,
>
> For now, Pharo has kept the squeak color specification framework based on the
> WindowColorSpec class and on the dynamic discovery of window colors.
> (it relies on the searching of all windowColorSpecification implementors).
> Do we want to keep that ?
> I would vote for getting rid of it.

Please remove it! I personally think that the only use of window-colors is to be able
to tell windows appart quickly. (but even that I personally think is not worth having an
ugly UI for). But than *changing* the window color is the last thing that anyone should
be able to do!

� � � �Marcus
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



--
imagination is more important than knowledge - Albert Einstein
Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein
Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein
The true sign of intelligence is not knowledge but imagination. - Albert Einstein
Gravitation is not responsible for people falling in love. - Albert Einstein