[Pharo-project] [Fwd: windowColorSpecification]
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
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
Bart Gauquie a écrit :
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. Hi Bart, But we can keep the colors, For UITheme that make use of them we can maybe simply use existing defaultColor message as an example.
The default behaviour of the gray colors is absolutely more suitable than the colored version. I'm confused :)
Alain
Kind regards,
Bart
On Tue, Dec 15, 2009 at 1:58 PM, Marcus Denker <denker@acm.org <mailto:denker@acm.org>> wrote:
On Dec 15, 2009, at 1:53 PM, Alain Plantec wrote:
> > > From: Alain Plantec <alain.plantec@univ-brest.fr <mailto:alain.plantec@univ-brest.fr>> > Date: December 15, 2009 1:52:28 PM GMT+01:00 > To: Pharo-project@lists.gforge.inria.fr <mailto:Pharo-project@lists.gforge.inria.fr> > Subject: windowColorSpecification > Reply-To: alain.plantec@univ-brest.fr <mailto: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 <mailto: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 ------------------------------------------------------------------------
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I like the colors too. I cannot work with the OS X theme where everything looks exactly the same. Also it would be cool if the transcript could be orange again. Lukas 2009/12/15 Bart Gauquie <bart.gauquie@gmail.com>:
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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
Hi Lukas, My purpose is not to remove them. The question is do we keep WindowColorSpec and related stuffs with the possibility to change colors from the preference browser, the "Pale" and "White" color themes ... My position is that we should not give the possibility to change window colors individually and simplify window color handling. Lukas Renggli a écrit :
I like the colors too. I cannot work with the OS X theme where everything looks exactly the same.
Also it would be cool if the transcript could be orange again.
I liked it in orange also :) Thanks Alain
Lukas
alain I think that if your solution is that we get a color for each kind of tools but without been able to change it via preference. Then this is ok Am I correct? Stef
Hi Lukas,
My purpose is not to remove them. The question is do we keep WindowColorSpec and related stuffs with the possibility to change colors from the preference browser, the "Pale" and "White" color themes ... My position is that we should not give the possibility to change window colors individually and simplify window color handling.
Lukas Renggli a écrit :
I like the colors too. I cannot work with the OS X theme where everything looks exactly the same.
Also it would be cool if the transcript could be orange again.
I liked it in orange also :)
Thanks Alain
Lukas
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
My purpose is not to remove them. The question is do we keep WindowColorSpec and related stuffs with the possibility to change colors from the preference browser, the "Pale" and "White" color themes ...
Yeah sure. I completely agree. I never used those themes.
My position is that we should not give the possibility to change window colors individually and simplify window color handling.
Yep, perfect. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
Lukas Renggli wrote:
My purpose is not to remove them. The question is do we keep WindowColorSpec and related stuffs with the possibility to change colors from the preference browser, the "Pale" and "White" color themes ...
Yeah sure. I completely agree. I never used those themes.
Well, the first thing I always did in my images is to set the theme to White :-) Never could stomach the 60's staring back at me through windows colors ;-) Michael
participants (6)
-
Alain Plantec -
Bart Gauquie -
Lukas Renggli -
Marcus Denker -
Michael Rueger -
Stéphane Ducasse