OLPC Human Interface Guidelines/The Sugar Interface/Controls/Custom Controls: Difference between revisions
| Line 4: | Line 4: | ||
=====When to Use Custom Controls===== |
=====When to Use Custom Controls===== |
||
We have created a set of control widgets to suit most basic needs for application development. Using these controls wherever possible ensures that the interfaces across activities remain consistent and clear, and also maintains the visual style of the interface. Nonetheless, their basic functionality may prove limiting in some cases, and we certainly hope to inspire new and exciting uses of the various capabilities of the laptops, including their collaborative nature, and don't want to stifle additional ideation and design. For this reason, we are providing a general set of guidelines for the creation of custom controls that match the visual style of Sugar and maintain some basic standards for compatibility and usability within the Sugar interface. |
|||
Before implementing a custom control, be sure that the need truly exists. In some cases, you may find that a combination of simpler controls may suffice. In other cases, more complex functionality can be accommodated though use of a palette. Additionally, be sure that the need is a functional one; Custom controls should have additional or different behavior that the current controls don't provide, and not simply define a different aesthetic for existing ones. Again, think carefully about the requirements for the control, and be sure that the functional need itself merits the work associated with creating the new control. |
|||
=====Control Color Palette===== |
=====Control Color Palette===== |
||
Revision as of 19:03, 1 May 2007
When to Use Custom Controls
We have created a set of control widgets to suit most basic needs for application development. Using these controls wherever possible ensures that the interfaces across activities remain consistent and clear, and also maintains the visual style of the interface. Nonetheless, their basic functionality may prove limiting in some cases, and we certainly hope to inspire new and exciting uses of the various capabilities of the laptops, including their collaborative nature, and don't want to stifle additional ideation and design. For this reason, we are providing a general set of guidelines for the creation of custom controls that match the visual style of Sugar and maintain some basic standards for compatibility and usability within the Sugar interface.
Before implementing a custom control, be sure that the need truly exists. In some cases, you may find that a combination of simpler controls may suffice. In other cases, more complex functionality can be accommodated though use of a palette. Additionally, be sure that the need is a functional one; Custom controls should have additional or different behavior that the current controls don't provide, and not simply define a different aesthetic for existing ones. Again, think carefully about the requirements for the control, and be sure that the functional need itself merits the work associated with creating the new control.