[Bf-funboard] (reply to David Cuny & Groo) Ctrl-T, Ctrl-P, etc

[Ton Roosendaal]

Hi,

Thanks Groo. I agree with the below summary. we can also look at  
including the object name in the dialog, although it should remain  
easily readable.

I'd prefer to store this info at a todo list, because it also has a  
relation to a couple of other issues:

- wireframe colors
- conventions for mousebuttons
- the new context sensitive toolbox
- configurable hotkeys

I doubt we can implement all issues for 2.30 (end of oct) though. My  
proposal is to first solve the main topics as described in the UI doc  
(menus, buttons, toolbox, looks) and then move on to all the other  
issues.

Nevertheless, discussions and design proposals remain welcome here.  
Good to be ready before a coder starts hacking, er! :P

-Ton-


On Saturday, Sep 27, 2003, at 18:45 Europe/Amsterdam, The Fallen Weeble  
wrote:

> Whew... alright, this is what I propose (and I apologize because I  
> think
> there have been a few too many proposals already, but...) is as  
> follows:
>
> 1. The basic process remains as is (select objects, select active,  
> issue
> command, confirm).
>
> 2. The "Active" state is a subset of the "Selected" state.
>
> 3. Objects in the "Active" state should have a more distinguishing  
> color
> (suggest white).
>
> 4. Parenting and tracking on single objects should return an error  
> since
> it doesn't make logical sense (suggest "Error: must have more than one
> object selected").
>
> 5. Confirmation dialog should have more clear language (suggest "Make
> Active Object Parent" and "Track Active Object").
>
> Can we agree to use this as a starting point and go from there?  Right
> now we're doing a lot of needless running in circles and repeating
> ourselves.  Luke, while it remains to be seen whether or not your
> confirmation/selection dialog would add or detract, I think it would be
> a good idea to see how this works out.  If it substantially clears up
> the issue (as I think it will), then we're cool.  If not, we can move
> from there with other approaches such as yours.
>
> I apologize if I sound like I'm talking for the active developers, but  
> I
> think this would be a feasible way to go and shouldn't be too difficult
> to implement.  I wouldn't mind trying, but I'm pretty sure someone more
> familiar with the codebase could get it done faster.  However, if  
> anyone
> wants to send me an email, pointing me in the right direction, I'll see
> if I can't do anything.
>
> Let's get this resolved and move on.
>
> Later.
>
>   Groo
>
> _______________________________________________
> Bf-funboard mailing list
> Bf-funboard@blender.org
> http://www.blender.org/mailman/listinfo/bf-funboard
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton@blender.org  
http://www.blender.org