[tuhopuu-devel] RE: gui color
K. Richard Rhodes
tuhopuu-devel@blender.org
Sat, 9 Aug 2003 17:50:26 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_000C_01C35E9E.B71EF950
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Just a thought... Why not a simple comma delimited file?
--
256,128,128 #3d back color
128,128,128 #plum buttons
...
--
my pseudocode (heh...) anywho, this would make "Themes" from other =
users (and the supplied ones :) also... this could also be expanded =
with image support (gtk themes like)
K
=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
What on earth !
You would stifle the creative control of the users !
Woow that is silly. And foolish. If somebody wants to make a mess of
blender then they should beable to.
It you want control. You should separate the gui code to a simjple=20
hackable file
so themes could be dropped in.
I like changing the background color. Helps my eyes.
And plus blender would be stepping back in stead of moving forward.
^v^
On Saturday, August 9, 2003, at 06:00 AM,=20
tuhopuu-devel-request@blender.org wrote:
>
>> Completely off topic, but regarding MadProf's patch
>> with customisable colors, I think it would be wise to
>> add some code to block certain color combinaison, to
>> avoid eye-breakers like this:
>> http://www.aprilcolo.com/oh/blender.jpg
>
> *grins* Yeah... But the trouble is that is would be rather
> hard to do proper colour blocking, without doing a proper
> "all colours are related" type code thing, which would be
> rather tricky, I think. (Kind of how the different shades of
> colours WHITE, LIGHT, HILITE, MEDIUM, GREY, DARK work
> currently, all derived from one colour). Another way to do
> it would be to only allow the use of (x) built in "themes",
> or sets of colours defined by the mighty inerrant
> code-wealding wosnames (in other words, us :-) ).
------=_NextPart_000_000C_01C35E9E.B71EF950
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2>Just a thought... Why not a simple =
comma=20
delimited file?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>--</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>256,128,128 #3d back =
color</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>128,128,128 #plum =
buttons</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>--</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>my pseudocode (heh...) anywho, =
this would=20
make "Themes" from other users (and the supplied ones :) also... =
this=20
could also be expanded with image support (gtk themes =
like)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>K</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
=
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D</FONT></DIV>
<DIV>What on earth !<BR>You would stifle the creative control of the =
users=20
!<BR>Woow that is silly. And foolish. If somebody wants to make a mess =
of<BR>blender then they should beable to.<BR><BR>It you want control. =
You=20
should separate the gui code to a simjple <BR>hackable file<BR>so =
themes could=20
be dropped in.<BR><BR>I like changing the background color. Helps my=20
eyes.<BR>And plus blender would be stepping back in stead of moving=20
forward.<BR><BR>^v^<BR>On Saturday, August 9, 2003, at 06:00 AM, =
<BR><A=20
=
href=3D"mailto:tuhopuu-devel-request@blender.org">tuhopuu-devel-request@b=
lender.org</A>=20
wrote:<BR><BR>><I><BR></I>>><I> Completely off topic, but =
regarding=20
MadProf's patch<BR></I>>><I> with customisable colors, I think =
it would=20
be wise to<BR></I>>><I> add some code to block certain color=20
combinaison, to<BR></I>>><I> avoid eye-breakers like=20
this:<BR></I>>><I> <A=20
=
href=3D"http://www.aprilcolo.com/oh/blender.jpg">http://www.aprilcolo.com=
/oh/blender.jpg</A><BR></I>><I><BR></I>><I>=20
*grins* Yeah... But the trouble is that is would be =
rather<BR></I>><I> hard=20
to do proper colour blocking, without doing a proper<BR></I>><I> =
"all=20
colours are related" type code thing, which would be<BR></I>><I> =
rather=20
tricky, I think. (Kind of how the different shades of<BR></I>><I> =
colours=20
WHITE, LIGHT, HILITE, MEDIUM, GREY, DARK work<BR></I>><I> =
currently, all=20
derived from one colour). Another way to do<BR></I>><I> it would be =
to only=20
allow the use of (x) built in "themes",<BR></I>><I> or sets of =
colours=20
defined by the mighty inerrant<BR></I>><I> code-wealding wosnames =
(in other=20
words, us :-) ).<BR></I><BR></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_000C_01C35E9E.B71EF950--