DELETE WHEN FINISHED
Review of other design system
Clear definition of a toolbar
From examples below understand what constitutes as a toolbar
addressing different types for different components
Related Pages: << Links to related pages, if relevant >>
Description
A toolbar is a grouped set of buttons and other types of components used to apply action to data
<< Most communicative screenshot of the component >>
Types
<< Relevant only if the component has several distinct types (e.g. editable tables, nested tables). In this case, each type should be described in a sub-page. The main page should be used only for the common grounds of the component>>
...
Type
...
Usage
...
Image
...
Link to the relevant page
...
...
Link to the relevant page
...
Usage & Behavior
General guidelines
Structure
do we have vertical toolbar?
take 2 rows?
...
| Table of Contents |
|---|
Description
A toolbar is a grouped set of controls, allowing users to perform actions on related content.
...
Usage & Behavior
The toolbar may apply to the whole page, or be associated with a data table, list, or chart.
Type | Image |
|---|---|
 | |
 | |
Chart |  |
Page |  |
General guidelines
Structure
The toolbar is shown as a horizontal, single row.
It may contain one or more controls.
Placement and Positioning
The toolbar is located on top of a data container (Data table, Widget, List Etc…) and takes the full area (e.g. the data table).
It uses the maximum width of the data set In some casesarea.
Where relevant, the row of a toolbar can accommodate additional non-related components (e.g. a widget with a title text)Right aligned- actions toolbar should be divided into two areas:
Action area - aligned to the left, including controls that impact the data (e.g. delete).
View area - aligned
to the right, including controls that impact the view of the data (e.g. print, search, change view mode etc.).
If there is only a view area, it will be aligned to the left, depending on the context of the user flow.
Content
A toolbar
...
may include:
a variety of
...
controls, such as Action Menus, Buttons,
...
Internal Logic
<<if there is a certain mechanism that cannot be separated from the component. See example: Data tables internal logic >>
States
<<Remove non-related states or use NA to emphasize the component don’t have that state. See Text fields states >>
State | Image | Comment |
|---|---|---|
Regular |
|
|
Hover |
|
|
Active |
|
|
Selected |
|
|
Selected, Hover |
|
|
Disabled |
|
|
Read Only |
|
|
Error |
|
|
Warning |
|
|
Focused |
|
|
Focused, Hover |
|
|
Focused, Selected |
|
|
Interaction
<<for example, how to change value – type, arrows, use slider. See example: Numeric stepper interaction>>
Validations and errors
<<Show images for Errors and warnings. See example: Radio button validations and errors>>
Transitions
<<Where possible describe shortly and demonstrate transitions or animations of the component pattern with animated GIF>>
Best practices
<Whenever a recommendation (not a must) is provided>>
Use:
<…>
<…>
Don’t use
<…>
<…>
General
<…>
Future Version (TBD)
< Edge cases, uncertain aspects, incomplete description>
<…>
- <…>
and a Search component.
information items, such as counters and statuses (See data table example above).
Dialog Buttons cannot be used within a toolbar.
If there are sets of controls (for example, table-level actions vs. row-level actions), they should be separated by a vertical divider.
In case of a large number of items, a three-dotted Icon Button may be used, allowing users to open an Action Menu (see the chart example above). In this case, the icon button will be the last control.
Internal Logic
Toolbar controls can be applied to selected items or the entire related content.
Toolbar controls can be enabled/disabled in response to data selection (e.g., a Delete control will be disabled if no data was selected).
States
The toolbar itself has no states. Each control on the toolbar will behave according to its own states.
Validations and errors
The toolbar itself has no validations or errors. Each control on the toolbar may have its own validations.
Best practices
Use:
if the user can perform actions or change the view of the related content.
if the related content allows multi selection.
Don’t use:
On a single-selection data table, if all actions can be performed only at a row-level.
If a ribbon pattern is used.
General:
Where possible, consider using only Icon Buttons, with corresponding Tooltips.
Icon buttons with text should be used to emphasize one or two specific actions.
Accessibility Compliance
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.
Design
Zeplin link | Screen thumbnail |
|---|
<<Short Zeplin link. You
Use this
>>
<<Screen with 200 width>>
Code
...
toolbar cannot come together with Ribbon.
Examples
...
Delete at the end anything below this
How much to hide - Burger menu?
should tags be used?
Links -
...
https://www.carbondesignsystem.com/patterns/text-toolbar-pattern/.- text toolbar for rich editing of text
...
Sap
.png?version=1&modificationDate=1602071737157&cacheVersion=1&api=v2)
.png?version=1&modificationDate=1601982390519&cacheVersion=1&api=v2)
Code
...