[Bf-funboard] New Logical Renderbuttons Layout

[Ton Roosendaal]

Hi,

Thanks for the work you do, however... I gave an extensive review of =20
your first proposal, and don't see anything from it back...

I realize that having fixed width panels limits logical design quite =20
some. Nevertheless, it remains the purpose that a vertical layout =20
should look nice too.

Please check on my comments first! I've pasted it below, please not =20
that this is about your first mockup.

-----------paste----------------

There's an important issue still, and that's if we stick with fixed =20
sizes of the Panels. To enable both vertical and horizontal layout =20
aligning nicely.

My proposal would be to have a standard horizontal layout first, =20
divided in 4 panels of 320 width. This then will give compatibility =20
with older releases, and allows a nice vertical layout too.

If really needed, we can make a fifth/sixth panel by default 'tabbed' =20=

in an other one.

For your version, you only have to put the 'Other' panel in the =20
remaining panels...

- "Extensions" belongs in in the first Panel
- "Play animation" as well
- "dispwin" and "dispview" should be in "Render" panel
- "Rt" is a debug button for coders only... put it somewhere!

Then:
- What is the "Save animation" option?
- anti and mblur remain using 5-8-11-16 samples, no slider
- I can live with renaming OSA into "Antialiasing, but I'd like to hear =20=

others about it. It's a bit history here you know! :)
- "Play Rendered" can remain "Play" (it plays anything, also not =20
rendered). Tooltips should be used to explain further info, a button =20
name is a reminder.
- title for first panel is incorrect

Design:
It looks like you used the "uiAutoBlock" function, which spreads =20
buttons out in a box. This doesnt always give good design... things =20
that belong together can be put together.
Inside a Panel, the order of buttons seems not to be logical...


-Ton-


On Saturday, Oct 11, 2003, at 11:41 Europe/Amsterdam, William Reynish =20=

wrote:

> Due to=A0a few=A0drawbacks of my RenderButtons mock-up=A0on the =
Blender =20
> Funboard ealier, I have updated and changed it a bit. Here it is:
> =A0
> http://www.shadeless.dk/renderbuttons.gif
> =A0
> All the buttons have been organised into groups. In this case, there =20=

> are 6 groups; Save, Options, Render, Other, Format and Presets. This =20=

> makes it much easier for the user to make sence of the buttons. It is =20=

> now clear that Quality has to do with saving, and that Width and =20
> Height has to do with the frame size.
> The idea is the you can collapse the groups (especially useful while =20=

> in Vertical mode)so that you can concentrate on certain aspects and =20=

> make more room for what you are concentrating on.
>
> I have also changed the names of some buttons. Here is the list of =20
> changes:
> Odd > Upper
> X > Time difference
> OSA > Anti-aliasing
> Play > Play Movie
> These names seem more logical. How could you possibly guess that 'X' =20=

> meant disabling the time difference in Field rendering? Calling the =20=

> button 'Time difference' seems more logical. Anti-aliasing is a common =
=20
> name for removing the aliasing in images. This term is used in =20
> photoshop, Maya, XSI, and countless other programs - having it called =20=

> OSA just confuses people. Then, ofcourse thereis the =20
> Upper-Lower/Even-Odd discusssion, and I think that Upper and Lower are =
=20
> more widely used. I changed the Play button to Play Movie because it =20=

> should be clear that it is playing the movie. I also added the Show =20=

> Image button so that you could have the last rendered image shown (the =
=20
> same as pressing F11). This seemed logical, because Play Movie and =20
> Show Image are related buttons - having one as just a hotkey and the =20=

> other in the RenderButtons is wierd.
> I have made a new Level numberbutton for Motionblur so that you=A0can =20=

> chose the Motionblur level independantly=A0from Anti-aliasing.=A0
> =A0
> You will notice that the Anti-aliasing, Panorama, Edge, Motionblur and =
=20
> Fields buttons are animated to show how it will look when they are =20
> depressed. The settings for each button should only be active when it =20=

> is depressed, so that it is clear to the user that the settings are =20=

> relevant to the button it belongs to.
> =A0
> My proposal is also to make it possible to edit Numberbuttons by just =20=

> leftclicking on them. You could always click the arrows to move the =20=

> number up or down.
> =A0
> =A0
> Tell me what you think!
> -Monkeyboi (William)
> =A0
> PS
> I'm working on giving the EditButtons the same treatment. I should be =20=

> finished soon.. I planning on doing roughly the same to all the =20
> Buttonwindows.
> =A0
> PPS
> Changes since the last post are:
> =A0
> Button options (like under Anti-aliasing) has changed appearence
> The percent buttons are not a slider anymore
> Added Show image
> Changed odd/even to Upper/Lower
> Added Level Setting for Motionblur
>
> ------------
> Yahoo! Mail - Gratis: 6 MB lagerplads, spamfilter og virusscan
>
>
------------------------------------------------------------------------=20=

--
Ton Roosendaal  Blender Foundation ton@blender.org =20
http://www.blender.org