Hello, 

I would like to ask something and maybe initiate some discussion.
I was wandering how is it possible that the UI project got "frozen".
Long time ago there was talk about tabbing.
When tool and property areas were added, they were referred to as experimental.
But, they were very soon full of different stuff, and now I e.g. noticed that 
in 
node editor development there is talk about making the property area wider to 
fit in node props and similar.(instead of
displaying the node properties in ------ property editor?)
So, after looking forward for some kind of unification to property access, now 
I end up very often with 
my screen just full of property areas and have to call it a mess. 
Especially windows which tend to have something on both sides - like animation 
windows(channel names on left, props on right),or 3d view(tools, props, and the 
so much discriminated last operator area) / tend to end up as very narrow.
 Am I using it wrong or is this just unfinished ?
Is scrolling and opening/closing panels so often considered efficient?
Some time ago, I wrote a proposal to wiki, which tried to target these issues:
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Proposals/UI/December_2010_-_Vilem_Novak

I thought that when the proposal got ignored, that maybe some other solutions 
for these problems are planned, 
but since then, stable releases of the 2.5x series are out and there is silence 
about this area.

Don't take me wrong please, as a python coder, I just have to love the amount 
of freedom the coder has 
now while making addons. I really like how far has blender changed code wise, 
and want to say a big thanks to everybody involved. Just as a user - I often 
feel some discomfort. Btw. as far as I had the possibility to test it, In 
cycles branch,
 the UI interaction is more satisfactory than in trunk.

If you read that far, thank you.
Vilem


_______________________________________________
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Reply via email to