Jump to: navigation, search

Difference between revisions of "UX/PatternsLibrary"

< UX
(Details Panel)
(Details Panel)
Line 3: Line 3:
 
=== Details Panel ===
 
=== Details Panel ===
  
The details panel contains detailed information for an object in Horizon and is typically opened by clicking on the object name from a list in a panel.  For example, you would click on an instance name from the Instance panel to view specific details for that instance.
+
The details panel contains detailed information for an object in Horizon and is typically opened by clicking on the object name from a list in a panel.  For example, you would typically click on an instance name from the Instance panel to view specific details for that instance.
  
Generally, you would need a Details panel if there is too much information to easily fit within a row in a table.  For example, an Instance includes a source, flavors, quotas, and networks - way too much stuff to fit into a row.  In addition, the details panel should allow users to take an Action on a object based on the information displayed in the Details panel.  For example, a user should be able to update the flavor for a specific instance within the Instance details panel.
+
Overall, you would need a Details panel if there is too much information to easily fit within a row in a table.  For example, an Instance includes a source, flavors, quotas, and networks - way too much stuff to fit into a row.  In addition, the details panel should allow users to take an Action on a object based on the information displayed in the Details panel.  For example, a user should be able to update the flavor for a specific instance within the Instance details panel.
 
 
When creating a details panel,
 

Revision as of 15:08, 8 June 2015

Patterns

Details Panel

The details panel contains detailed information for an object in Horizon and is typically opened by clicking on the object name from a list in a panel. For example, you would typically click on an instance name from the Instance panel to view specific details for that instance.

Overall, you would need a Details panel if there is too much information to easily fit within a row in a table. For example, an Instance includes a source, flavors, quotas, and networks - way too much stuff to fit into a row. In addition, the details panel should allow users to take an Action on a object based on the information displayed in the Details panel. For example, a user should be able to update the flavor for a specific instance within the Instance details panel.