Open GoogleCodeExporter opened 9 years ago
The blue color is indeed too different and attracts too much attention.
The idea behing having different colors for build-in-progress statuses is that
developpers can make sure a build is triggered after their commit and wait for
build
to be finished. That way, we make sure they don't leave with not-yet-finished
builds.
However, I understand that you can be interested in not having different
colors. I
could provide simple settings to switch from the "complete" color-set to a more
"simple" one.
Thanks,
Alexis
Original comment by Alexis.S...@gmail.com
on 26 Mar 2009 at 6:36
That would be great!
If there's a way I could help, let me know.
Original comment by jan.sol...@gmail.com
on 27 Mar 2009 at 2:41
Or simply let the user chose icons for each states ?
Original comment by Laroua...@gmail.com
on 9 Apr 2009 at 4:09
Or use another nuance of green for state "currently building, and there was no
project which did not build at the last check" instead of blue not to attract
attention.
Original comment by giter...@gmail.com
on 9 Apr 2009 at 8:34
Yes, the blue is too distracting. I had changed that in beta version 0.8.1, but
it
was not proposed through the auto-update.
I have upgraded v0.8.1 to 0.9 and made it available to everyone.
The next step is to allow configuring the colors.
Original comment by Alexis.S...@gmail.com
on 10 Apr 2009 at 7:30
Hello.
Regarding:
"The next step is to allow configuring the colors."
Is it possible to implement this step?
I want to share my feelings.
I'm a Daltonist (Color blind) and the dark green (Currently building) is very
confusing me (I guess other Daltonist people as well).
When I see this green, I think it is Red and I'm going to check the build
report.
Then I figure out that everything is ok and it's just another build process.
Actually the previous blue solution could helped me (this is what I would have
set if there was an option to do it).
But unfortunately, no way to set it in other color.
Can you please assist?
Tx,
Meir.
Original comment by mei...@gmail.com
on 5 Feb 2015 at 9:01
Original issue reported on code.google.com by
jan.sol...@gmail.com
on 25 Mar 2009 at 9:04