You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Users value and prioritize different pieces of information in different ways, which can also change over time. Distributed software cannot predict or know these subjective values/priorities, but it can provide generic abilities such that users can specify them
The ability tweak or otherwise customise an application allows users to:
More closely align the use of the software to their needs
Allows users to 'make it your own', 'feel more at home' and 'be more in control'.
Allows users to improve their productivity/effectiveness
Describe the solution you'd like
The ability to Move components (drag-and-drop) all "sections" (component, graph, whatever) of the dashboard so as to suit my individual priorities and preferences, including:
Cannot see changes in real-time (area of control/change divorced from area of impact)
Cannot factor in other issues (component width options, pinning, among other things)
Additional context
Consider the implications of current and future 'resizable' components (like expand chart area now).
Add a 'move' icon in a similar location to 'expand chart area' icon for each component
But: The current Expand chart area icon is actually more commonly used as a move icon.
Suggestion: Change Expand chart area icon to double-arrow (rather than quad arrow), OR use left (<) and right (>) chevrons, as the present expand chart area icon 'hides' the histogram
Proposed Expand: OR
Proposed Collapse: OR
Consider additional abilities
Ability to Resize components
For example: Small, Medium, Large, or with resizable drag controls at component boundaries, or via context menu
Users may also want a 'dynamic' size component, such that it 'fills' the space, as opposed to a 'fixed size' component.
Ability to Pin components, so that drop-targets can flow around them without re-ordering / moving them.
This feature may not be worth the effort unless and until a much larger number of dashboard components are available/visible, or as or in a second iteration.
Ability to Remove components from the dashboard
This will need a method to 'add components' (that are not already instantiated on the dashboard)
The text was updated successfully, but these errors were encountered:
For reference: I started discussion #376 for making ThirdStats UI more flexible for additional content. Making at least the chart widgets in the content area movable would be a great feature. So keeping this in mind.
Is your feature request related to a problem? Please describe.
Users value and prioritize different pieces of information in different ways, which can also change over time. Distributed software cannot predict or know these subjective values/priorities, but it can provide generic abilities such that users can specify them
The ability tweak or otherwise customise an application allows users to:
Describe the solution you'd like
The ability to Move components (drag-and-drop) all "sections" (component, graph, whatever) of the dashboard so as to suit my individual priorities and preferences, including:
Each graph
ThirdStats Logo
Statistics Summary Bar
Dashboard Settings Bar
Representative Examples
Describe alternatives you've considered
Additional context
Add a 'move' icon in a similar location to 'expand chart area' icon for each component
Expand chart area
icon is actually more commonly used as amove
icon.Expand chart area
icon to double-arrow (rather than quad arrow), OR use left (<) and right (>) chevrons, as the present expand chart area icon 'hides' the histogramProposed Expand: OR
Proposed Collapse: OR
Consider additional abilities
Ability to Resize components
Ability to Pin components, so that drop-targets can flow around them without re-ordering / moving them.
This feature may not be worth the effort unless and until a much larger number of dashboard components are available/visible, or as or in a second iteration.
The text was updated successfully, but these errors were encountered: