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
The idea is to introduce progressively the concept of widget. Widgets would another category of module that would work a standalone and would focus on a very specific item. It could be a linechart, a piechart, a single map. To work as standalone, the overall app should search for a URL param 'module' id/name, and if available, the app would work as 'fluid' (for embedded mode) instead of dashboard (relates to CALR-19). In this way the app could be embedded in Calipseo with a single widget context, instead of a dashboard context including many widget.
The granularity of a widget may vary. A Widget could be actually built on top of a module that has more or less features / UIs and is more and less complex. Whatever module initially mapped to a dashboard 'page' could be considered as widget, but a widget could be managed in the source code and loaded ONLY in a embedded mode, and not necessarily used in the dashboard. In other words, similarly as the shiny-calipseo app allows to display different country dashboard contexts, it may allow to display different module contexts.
For example, we could think of a single widget that displays countings of vessels licenses status. It would be set as module, not necessarily available in the dashboard, but loadable by targeting it through shiny app URL; to embedd it in the Calipseo webapp.
The idea is to introduce progressively the concept of
widget
. Widgets would another category of module that would work a standalone and would focus on a very specific item. It could be a linechart, a piechart, a single map. To work as standalone, the overall app should search for a URL param 'module' id/name, and if available, the app would work as 'fluid' (for embedded mode) instead of dashboard (relates to CALR-19). In this way the app could be embedded in Calipseo with a single widget context, instead of a dashboard context including many widget.The granularity of a widget may vary. A Widget could be actually built on top of a module that has more or less features / UIs and is more and less complex. Whatever module initially mapped to a dashboard 'page' could be considered as widget, but a widget could be managed in the source code and loaded ONLY in a embedded mode, and not necessarily used in the dashboard. In other words, similarly as the shiny-calipseo app allows to display different country dashboard contexts, it may allow to display different module contexts.
For example, we could think of a single widget that displays countings of vessels licenses status. It would be set as module, not necessarily available in the dashboard, but loadable by targeting it through shiny app URL; to embedd it in the Calipseo webapp.
cc [~[email protected]] related to CALR-19
The text was updated successfully, but these errors were encountered: