The current default Dashboard schematic should be enhanced with a better change/aggregator pattern, such that the contained widgets collection have some basecommon functionality.
Use Case
Hello, this is a request to enhance the Dashboard Schematic Generation.
Since business mostly use dashboards for reporting fragments of information\visuals\charts\tables across the organization and always house that data inside widgets; these widgets always contain common basic plumbing that could be placed in a base class. However, that base is missing, if you could please enhance the Dashboard Schematic it would greatly benefit the developer community if a strategy/pattern was used in the dashboard component. These reports are data housed inside widgets form of charts, maps, tables etc. However, in this schematic there is no UI aggregation, or common base settings.
Dashboard
[ ] Typical dashboard is One (or many pages/tabs)
[ ] Each Dashboard houses widgets/containers
[ ] Be able to share change strategy with their contained widgets and other tabs
[ ] DI@Injectable Service to accept new or remove old widgets
Widgets -
[ ] Each of the widgets should extend from a base class
[ ] The widget should share/exchange some common data with other widgets
[ ] Widgets should have settings (an Icon gear, that can be extend, Print, Copy, Export, Import, Refresh etc.)
[ ] Some lifecycle that allows them to clean up or change within that dashboards context
Some places have layed out information on this, because it was lacking.
The current default Dashboard schematic should be enhanced with a better change/aggregator pattern, such that the
containedwidgets collection have somebasecommon functionality.Use Case
Hello, this is a request to enhance the Dashboard Schematic Generation.
Since business mostly use dashboards for reporting fragments of information\visuals\charts\tables across the organization and always house that data inside widgets; these widgets always contain common basic plumbing that could be placed in a base class. However, that base is missing, if you could please enhance the Dashboard Schematic it would greatly benefit the developer community if a strategy/pattern was used in the dashboard component. These reports are data housed inside widgets form of charts, maps, tables etc. However, in this schematic there is no UI aggregation, or common base settings.
Dashboard
@InjectableService to accept new or remove old widgetsWidgets -
Print, Copy, Export, Import, Refreshetc.)Some places have layed out information on this, because it was lacking.