Talk:OLPC Human Interface Guidelines/The Sugar Interface/Toolbars: Difference between revisions
(New page: It seems to me that in this paradigm, the ubiquitous "config" dialog should be just one of the tools or tabs - that is, it should take over the screen the instant you select the item. If t...) |
(config dialog) |
||
| Line 1: | Line 1: | ||
== Config / options / customize dialog == |
|||
It seems to me that in this paradigm, the ubiquitous "config" dialog should be just one of the tools or tabs - that is, it should take over the screen the instant you select the item. If this is so, I think it would be good to provide a placement and some guidelines for this. For instance: should it go in one of the top toolbars (edit? Pro: makes it less conspicuous), or in the bottom list of toolbars (pro: gives space for the various tabs of configuration in the top)? Where should it be placed? |
It seems to me that in this paradigm, the ubiquitous "config" dialog should be just one of the tools or tabs - that is, it should take over the screen the instant you select the item. If this is so, I think it would be good to provide a placement and some guidelines for this. For instance: should it go in one of the top toolbars (edit? Pro: makes it less conspicuous), or in the bottom list of toolbars (pro: gives space for the various tabs of configuration in the top)? Where should it be placed? |
||
Revision as of 20:35, 4 September 2007
Config / options / customize dialog
It seems to me that in this paradigm, the ubiquitous "config" dialog should be just one of the tools or tabs - that is, it should take over the screen the instant you select the item. If this is so, I think it would be good to provide a placement and some guidelines for this. For instance: should it go in one of the top toolbars (edit? Pro: makes it less conspicuous), or in the bottom list of toolbars (pro: gives space for the various tabs of configuration in the top)? Where should it be placed?
I know, the idea with Sugar is to keep because-it's-there configuration options to a minimum. I'm thinking of the Develop activity: obviously you want no pernicious silliness about tab settings. But some amount of config-dialog content is inevitable, and you don't want to make Sugar into a straitjacket. Homunq 16:35, 4 September 2007 (EDT)