MainPageContainer: MainPageContainer

In mjhelf/METABOseek: Metaboseek platform

MainPageContainer

Description

Container for modules in the Metaboseek main page

Usage

MainPageContainer(
  input,
  output,
  session,
  values = reactiveValues(projectData = values$projectData, featureTables =
    values$featureTables, MSData = values$MSData, GlobalOpts = values$GlobalOpts)
)

MainPageContainerUI(id)

Arguments

input	arguments necessary for use with callModule()
output	arguments necessary for use with callModule()
session	arguments necessary for use with callModule()
values	a reactiveValues object that in effect gives read and write access to external objects
id	id to be used to define a namespace via NS() (must match id in callModule() for the server Module)

Value

The server module for this container returns nothing

Functions

• MainPageContainer: server logic module, to be called with callModule()

• MainPageContainerUI: returns the shiny UI elements for the Metaboseek main page

MseekContainers

Containers are used to keep the code organised and can be characterized as Modules which contain other Modules, but do not contain add any functionality themselves. They should not contain any observers and are only here to pass values into modules, or provide ways for individual Modules to interact with each other.

See Also

values for a description of the values object

• General Information: MseekContainers

• Specific containers: MseekContainer, MainPageContainer

• More on Shiny modules: http://shiny.rstudio.com/articles/modules.html

Examples

## Not run: 
ui <- function(request){
MseekContainerUI("Mseek")
}
server <- function(input, output, session) {
   callModule(MseekContainer, "Mseek")
}
Create Shiny app ----
shinyApp(ui, server)

## End(Not run)

mjhelf/METABOseek documentation built on April 27, 2022, 5:13 p.m.