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
Would it be possible to expose parts of the internals of GWSDAT to allow for their easy embedding within other shiny apps or Rmd docs?
Two obvious use cases are a shiny dashboard showing a bunch of metrics for a site including one groundwater tab that embedded the GWSDAT "Analyse" tab. Since the dashboard would be for a particular site, the data set would always be the same the ability to manage data sources would not be needed. A second use case would be an Rmd document that included an embedded shiny component that showed (for example), just the "Spatial Image" frame with the time series slider.
The disadvantage, of course, is that it would make internal re-factoring harder.
The text was updated successfully, but these errors were encountered:
This is an excellent suggestion and something I've already been looking in to. However, there is a technical challenge...
I don't think its possible to create a single standard Rmd report which will fit everybody's needs. My personal view is that an Rmd report will only be used if it can be customised by the users, i.e. the premise here is that you can get a template with some basic visualisations/animations etc from GWSDAT which the user can further edit to their own needs. Here in lies the problem..
Would it be possible to expose parts of the internals of GWSDAT to allow for their easy embedding within other shiny apps or Rmd docs?
Two obvious use cases are a shiny dashboard showing a bunch of metrics for a site including one groundwater tab that embedded the GWSDAT "Analyse" tab. Since the dashboard would be for a particular site, the data set would always be the same the ability to manage data sources would not be needed. A second use case would be an Rmd document that included an embedded shiny component that showed (for example), just the "Spatial Image" frame with the time series slider.
The disadvantage, of course, is that it would make internal re-factoring harder.
The text was updated successfully, but these errors were encountered: