Can be automatic
Can define conditions for showing inputs
(see daneApp and Conectando caminos)

Chrome:
Tooltip overflows behind panel.

Firefox
Tooltip not workin. Label aligned right - should be left.

"Summarize" no content but this shows

How to make in yaml one o more dependences, before I can write:

agg:
  show: true
  depends_on: 
    ftype:
      one_of: [CatNum, Cat]
    viz:
      one_of:[bar, pie]
  input_info:
    input_type: selectizeInput

we want the name, label to be translated but to get the id when chosen by the user

output_parmesan("controls",
parmesan = i_(parmesan, lang()),
input = input,
output = output)
has a weird behaviour: it duplicates the sections' titles and doesn't translate them

library(shinypanels)

styles <- "
.info-tool {
 display: flex;
}


.tooltip-inf {
 cursor: pointer;
 position: relative;
 margin-left: 3px;
}

.tooltip-inf .tooltiptext {
  visibility: hidden;
  width: 170px;
  higth: auto;
  background-color: #fafafa;
  color: #9FBD36;
  position: absolute;
  z-index: 9999;
  top: 0;
  padding: 1rem;
  border: 1px solid #ccc;
  font-weight: 400;
  letter-spacing: normal;
  font-size: 0.75rem;
}

.tooltip-inf:hover .tooltiptext {
  visibility: visible;
}
"

ui <- panelsPage( styles = styles,
                  panel(title = "example", 
                        head = NULL,
                        body = uiOutput('ejemplo')
                  )
)

server <- function(input, output, session) {
  
  output$ejemplo <- renderUI({
    div(
    HTML('<div class= "info-tool"> Plot type  <div class="tooltip-inf"> 
    <i class="fa fa-info-circle"></i><span class="tooltiptext">
    Its a tootip information </span</div></div></div>'),
    radioButtons('plot_type',  ' ', c("ggplot", "hgchmagic")))
})

}

shinyApp(ui, server)

In Yaml one option with:

library:
show: true
tooltip_info: Its a tootip information
input_type: radioButtons
input_params:
label: Library
choices:
highcharter:
- Interactive
ggplot:
- Static
inline: true

ALSO happens with everything that is translated in particular the data input from the user...

if the user of an app have altered the initial values of the parameters and then changes the language they are re-rendered and so the current configuration of the parameters is lost

this could be fixed i guess by passing to the update parameter (selected, value, ...) the current value of the input--- that is, all inputs would have to have the corresponding reactive called in the yaml file...
for example
name_column:
show: true
input_type: selectInput
input_params:
label: name_column
choices: data_input_names()
selected: input$name_column
update_param: selected

the only problem with this is that firtsly input$name_column is going to be null, so what we really want is something like
ifelse(is.null(input$name_column), "...", input$name_column)

Add package namespace when input functions are called (especially when not from shiny).

This is because the golem package requires all functions within packages to be called with namespace.

Avoid this:

parmesan_env <- new.env()
# (...)
reactive({...}, env = parmesan_env)

For example, if you have "highlight", the inputs in CatNum are "highlight_color" and "highligh_var", but in CatCatNum this options are disables, so this section title "highlight" should not appear in the panel.

xxxInput
 is not a registered input.

On parmesan load

Improve:
Currently inputs with dependencies must be rendered before dependants in another output

Make parmesan work with other environment but the current one.

E.g. get parmesan_output to work within a function inside the server function of a shiny app.

for example 'order' depend of ftype and choices are the data categories

Using weird as parameter should throw an informative error

  input_type: textInput
  input_params:
    label: Title
    weird: "My text"

parmesan_render_ui and parmesan_config functions have the config_path parameter in common and its default value is config_path = NULL an config_path = "parmesan" respectively. Because parmesan_render_ui calls parmesan_config in its body this parameter should have the same default value for both functions, i.e. "parmesan"

Now you can use equals but there are situations out of it's scope:
a parameter F that depends on a slider; if the slider value is less than one, F exists, is shown, if not then it is not shown.

por example

colors:
  label: colors
  section_info:
    icon: info-circle
    text: colors_info
  inputs:
    - palette_colors
    - background_color
summarize: 

parmesan_render_ui function fails when a dependant parameter and the parameter in which it depends sit in the same section

Esto solo pasa cuando se agrega la internacionalización

tooltip:
  show: true
  input_type: textInput
  input_params:
    label: tooltip
    value: 
  input_info:
    icon: info-circle
    text: tooltip_info()

tooltip_info() is ready as text and no the info into reactive

My layout .yaml

titles:
  label: Titles
  inputs:
    - title
    - subtitle
    - caption
colors:
  label: Colors
  inputs:
    - palette_colors

inputs:

---
title:
  show: true
  input_type: textInput
  input_params:
    label: Title
    value:
subtitle:
  show: true
  input_type: textInput
  input_params:
    label: Subtitle
    value:
caption:
  show: true
  input_type: textInput
  input_params:
    label: caption
    value: 
palette_colors:
  show: true
  input_type: colorPaletteInput
  input_params:
    label: palette_colors
    colors:
    - "#FA0A0A"
    - "#4354A3"
    - "#3298A0"
    - "#563208"
    - "#cd5490"
    - "#5689c4"

In R (server):

library(shinypanels)
library(parmesan)
library(shi18ny)
library(shinyinvoer)

ui <- panelsPage(
  panel(title = "Options",
        color = "chardonnay",
        width = 350,
        body = uiOutput("controls"))
)

server <- function(input, output, session) {

  parmesan <- parmesan_load("parmesan")
  
  output$controls <- renderUI({
  #  render_section(parmesan = parmesan)
    render_section("all_controls_here", parmesan = parmesan)
  })
  
}

Result:

colors section is ignored

Selectize vs. radiobuttons
numericInput vs. sliderInput
?