[Bugs] #374 UNSP: color chooser behaves differently than the rest of the menus

SugarLabs Bugs bugtracker-noreply at sugarlabs.org
Thu Feb 19 16:10:28 EST 2009


#374: color chooser behaves differently than the rest of the menus
------------------------------------------+---------------------------------
    Reporter:  sascha_silbe               |          Owner:  eben                       
        Type:  defect                     |         Status:  assigned                   
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  design                     |        Version:  Git as of bugdate          
    Severity:  Unspecified                |     Resolution:                             
    Keywords:                             |   Distribution:  Unspecified                
Status_field:  Unconfimed                 |  
------------------------------------------+---------------------------------
Changes (by eben):

 * cc: benzea, tomeu, erikos (added)


Comment:

 Ah, that's bad!  That's what I get for not having a chance to actually
 test it. =)

 The color chooser is what we (the designers) have been referring to as a
 "palette button."  The button serves the sole purpose of revealing the
 associated palette.  As such, the primary action of a palette button
 should be to reveal the palette on left click, and hide it on a second
 click (just like most menus).  For consistency, right-click can be
 redundant and serve the same function.

 Another way to think of this is as a dialog.  Sugar, for the most part,
 avoids dialog windows.  It does so, in many cases, by attaching the dialog
 to a button in the form of a palette.  Some buttons use palettes for
 secondary adjustments and configuration—contextual settings, so to
 speak—but palette buttons simply serve to reveal the information in the
 palette.

 We have a design for this which includes the automatic addition of a
 little gray downward pointing arrow to the right of the button to indicate
 the difference in function, but that hasn't been implemented yet.  Likely,
 we'll just subclass ToolButton as PaletteToolButton and wrap it so as to
 add the arrow, but keep the API otherwise the same.  benzea, do you have
 any input in this area, or is a basic subclass all we need?

-- 
Ticket URL: <http://dev.sugarlabs.org/ticket/374#comment:3>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system


More information about the Bugs mailing list