[Bf-taskforce25] Some thoughts I need to share

[joe]

I think the transform panel in the button windows is out; that didn't
seem to work well for sequencer strips.  Besides, I think we shouldn't
treat the buttons window as a dumping ground for most everything, if
nothing else it forces users to constantly change tabs and scroll
around a lot to get what they're looking for.

BTW, kindof off-topic, but I think we should have named tabs of some
sort or another in the buttons window.  I think it's one of *the* most
confusing things for new users, and I'm not sure if tooltips are
enough.  I'm not sure how this would work exactly though, heh.
Perhaps there could be a space to display the name of the currently
active tab.

Joe

On Wed, Jul 22, 2009 at 12:00 PM, Nathan Vegdahl<cessen at cessen.com> wrote:
>>> Some people claim the vertical pannels (T & N keys) are not well
>>> space-optimized when you just need Transform options and everything else
>>> collapsed for example, because it's vertical designed. In this case you
>>> just have a most empty grey pannel that could be better used.
>>
>> I think quite a few people are unhappy about this, will be reviewed &
>> worked on further. Floating panels may come back, and perhaps the
>> transform properties also belong in the smaller T-key panel.
>
> I actually wonder if it would make sense to just put transform
> properties in the buttons window?  For objects that is essentially
> already the case (which is redundant with the n-panel).  Dunno if
> there's a good way to integrate them into the buttons window for the
> general case, though.  But it's just a thought.
>
> If we can do that, though, then we could eliminate the n-panel
> altogether, and just have the tools panel.  Seems like it might be
> cleaner, if it's feasible to do.
>
> --Nathan V
>
> On Wed, Jul 22, 2009 at 6:04 AM, Brecht Van Lommel<brecht at blender.org> wrote:
>> Hi,
>>
>> On Mon, 2009-07-20 at 13:09 +0200, Mickaël Guédon wrote:
>>> There is a thread on the BlenderClan forum about Blender 2.50, and
>>> people react to good and bad things about it. So I'm here to share some
>>> of their most interesting thoughts with you.
>>>
>>> We do think there is a problem about the Materials pannel in Object Data
>>> context.
>>> Well why this pannel is not in the Material context if it's all about
>>> Materials ?
>>
>> In latest svn, the material panel is no longer in the object data
>> context.
>>
>>> About Texture mapping pannel placed in the Texture context, we think
>>> this is not a very good idea since you cannot see the preview of what
>>> you are doing about mapping (which can be viewed in the Material
>>> context, but you have to click one more time and that's time consuming).
>>
>> Solved by the mixed texture/material preview I think.
>>
>>> Some people claim the vertical pannels (T & N keys) are not well
>>> space-optimized when you just need Transform options and everything else
>>> collapsed for example, because it's vertical designed. In this case you
>>> just have a most empty grey pannel that could be better used.
>>
>> I think quite a few people are unhappy about this, will be reviewed &
>> worked on further. Floating panels may come back, and perhaps the
>> transform properties also belong in the smaller T-key panel.
>>
>> Brecht.
>>
>>
>> _______________________________________________
>> Bf-taskforce25 mailing list
>> Bf-taskforce25 at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>