[Bf-funboard] New Logical Renderbuttons Layout

Matt Ebb bf-funboard@blender.org
Sat, 11 Oct 2003 20:58:40 +1000


This is a multi-part message in MIME format.

------=_NextPart_000_006E_01C3903A.72A22E00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

A good reason to discuss this is to think about the organisation of the =
buttons within the panels. That's the whole point of doing this =
re-design - the old buttonswindows have evolved and become disorganised =
over time, so now we have the opportunity to group them more logically =
within collapsible panels.

We need to be thinking now about how to best group the controls while =
the redesign is happening, rather than just replicate the same old =
semi-random, squashed up buttons.

Matt


  ----- Original Message -----=20
  From: Roel Spruit=20
  To: bf-funboard@blender.org=20
  Sent: Saturday, October 11, 2003 8:50 PM
  Subject: RE: [Bf-funboard] New Logical Renderbuttons Layout


  I think you are missing a part of the design conversation. Ton made a =
proposal on blender.org about collapsable panels, vertical layouts etc. =
(basically everything you described)=20
  and he is already implementing it....I don't see the reason to discuss =
this any further?

  Roel
------=_NextPart_000_006E_01C3903A.72A22E00
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.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>A good reason to discuss this is to =
think about the=20
organisation of the buttons within the panels. That's the whole point of =
doing=20
this re-design - the old buttonswindows have evolved and become =
disorganised=20
over time, so now we have the opportunity to group them more logically =
within=20
collapsible panels.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We need to be thinking now about how to =
best group=20
the controls while the redesign is happening, rather than just replicate =
the=20
same old semi-random, squashed up buttons.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Matt</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3DRoel@spruitje.nl href=3D"mailto:Roel@spruitje.nl">Roel =
Spruit</A>=20
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dbf-funboard@blender.org=20
  href=3D"mailto:bf-funboard@blender.org">bf-funboard@blender.org</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, October 11, =
2003 8:50=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Bf-funboard] New =
Logical=20
  Renderbuttons Layout</DIV>
  <DIV><BR></DIV>
  <DIV><SPAN class=3D766324810-11102003><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
  think you are missing a part of the design conversation. Ton made a =
proposal=20
  on blender.org about collapsable panels, vertical layouts etc. =
(basically=20
  everything you described) </FONT></SPAN></DIV>
  <DIV><SPAN class=3D766324810-11102003><FONT face=3DArial =
color=3D#0000ff size=3D2>and=20
  he is already implementing it....I don't see the reason to discuss =
this any=20
  further?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D766324810-11102003><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D766324810-11102003><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Roel</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_006E_01C3903A.72A22E00--