Difference between revisions of "Trove-Clustering-UI"
| Line 4: | Line 4: | ||
=== Blueprint === | === Blueprint === | ||
https://blueprints.launchpad.net/horizon/+spec/database-clustering-support | https://blueprints.launchpad.net/horizon/+spec/database-clustering-support | ||
| + | |||
| + | === Future Blueprints === | ||
| + | https://blueprints.launchpad.net/horizon/+spec/database-clustering-ux-improvement | ||
=== Mock Screenshots === | === Mock Screenshots === | ||
| Line 21: | Line 24: | ||
Or, should we stick with the first option? | Or, should we stick with the first option? | ||
| + | |||
| + | [2014/07/16] - After Trove meeting, the decision was for option #1 for v1 and create a new BP for UX improvement for option #2 (accordion). | ||
Latest revision as of 18:52, 16 July 2014
Introduction
This article describes the UI flow for Clustering in Trove. Since the first iteration of clustering will be for MongoDB, the UI for Clustering will follow in the same footsteps.
Blueprint
https://blueprints.launchpad.net/horizon/+spec/database-clustering-support
Future Blueprints
https://blueprints.launchpad.net/horizon/+spec/database-clustering-ux-improvement
Mock Screenshots
These are the new items needed in Horizon:
Discussion
Should we consider adding an accordion style row expansion in the Clusters table?
Something like this:
Or, should we stick with the first option?
[2014/07/16] - After Trove meeting, the decision was for option #1 for v1 and create a new BP for UX improvement for option #2 (accordion).
