currently using conditionalPanel() in app_ui.R which seems unsustainable and limiting. renderUI({}) will allow them to be built dynamically on fly. Also if done correctly, will allow more modular app design (i.e I want an intro module) with values accessed by downstream modules ("num_windows").
However, will likely be a bit of work as I will need to create modules that wrap multiple sub-modules, also will likely need to transition from having all calculations essentially fluid/non-stop to adding an action button for calculations. The action button necessity was likely inevitable and should only improve app maintenance and UI in the long run.
Going to try to document and work through the development here.
[x] #6
[ ] transition historical analysis to action button approach. i think the action button will help as it will allow the user to view historical analysis OR NOT before generating next window
[ ] implement renderUI({}) mapping
[ ] merge renderUI branch into window-modules branch
currently using
conditionalPanel()
inapp_ui.R
which seems unsustainable and limiting.renderUI({})
will allow them to be built dynamically on fly. Also if done correctly, will allow more modular app design (i.e I want an intro module) with values accessed by downstream modules ("num_windows").However, will likely be a bit of work as I will need to create modules that wrap multiple sub-modules, also will likely need to transition from having all calculations essentially fluid/non-stop to adding an action button for calculations. The action button necessity was likely inevitable and should only improve app maintenance and UI in the long run.
Going to try to document and work through the development here.
action button
approach. i think the action button will help as it will allow the user to view historical analysis OR NOT before generating next windowrenderUI({})
mappingwindow-modules
branch