teal Addin - allow users to pick modules, based on which default app templates and project structure will be created

[kumamiao]

Please see details on the linked draft proposal below

Draft proposal

Issues:

• Research rhino for teal skeleton  #58
• Research Rstudio tools for teal skeleton #59
• Solution for modules-marketplace #51
• Research Github Template for teal skeleton #66
• Research cookiecutter for a teal app template #67
• Make teal.marketplace #53
• Filter and search feature for the modules marketplace #52
• Make button to get skelleton #54
• Make UI prototype for teal_marketet_module #55
• Improve UI for modules selection #56

Later we can improve:

• arguments customization
• data customization

Note: Be aware that app.R might grow too big, consider splitting into several files sourced in app.R (data.R, args.R, etc.)

[Polkas]

We should consider an update of our template for NEST apps, to take advantage from last shiny/rstudio improvements.
Here we could find 3 different templates (3 branches) https://github.com/rstudio/shiny-testing-gha-example/tree/minimal for shiny app.

This is mainly a research task.
The goal is to assess the value added for the end user, more precisely if this RStudio proposition could be helpful.
After the research an update could be done.
Definitely part of this item assume we are already open source.

Important topics to explore:

• template button functionality - USE THIS TEMPLATE (button)
  
• tests dir structure
• R dir automatically consumed, when run and deploy the app

[pawelru]

Few open-source initiatives that are very close to what we want to achieve:

• https://github.com/ThinkR-open/golem
• https://github.com/Appsilon/rhino
• https://github.com/devOpifex/leprechaun

[gogonzo]

Issue for a design

[kpagacz]

Here's my doc for specifying functional requirements: https://docs.google.com/document/d/1QvHhGiC94mx2xJ7pTEmGF14_YRbKiZ0eM1xpbQC0Ifg/edit

Some draw.io: https://drive.google.com/file/d/1nwxnceqxTLhosX4deLfvqd9RuYO75yxz/view?usp=sharing

[kpagacz]

https://www.figma.com/file/LZTe9lIfuQbDAwd9NuZSPL/TealDesigner?node-id=0%3A1

[Polkas]

https://app.diagrams.net/#G1P904WifNz_HnyTZyjUxYRYnbOBbJYBIT

https://docs.google.com/document/d/1Vys4wmUtAsbuUG84Y76oSWX2Ie4KwrauBktk-ju3X1Y/edit

[kpagacz]

Here are my notes from the meeting.

Dawid: 
* had a comment about scraping parameter descriptions from the Roxygen descriptions and showing them in the GUI of the designer


Pawel:
* wanted to open for modules not only from NEST
* wanted to decouple arguments specification from the rest of NEST, specifically the data extract specs and similar (Konrad: I do not know how feasible it is)
* specifying arguments is too much - do not create them at all

People seem to like the idea of module listings

Maciej:

tmc_n <- asNamespace("teal.modules.clinical")

lapply(ls(tmc_n)[grep("tm_", ls(tmc_n))], function(x) tmc_n[[x]])
modules_names <- ls(tmc_n)[grep("tm_", ls(tmc_n))]
tm_formals <- lapply(modules_names, function(x) formals(tmc_n[[x]]))
names(tm_formals) <- modules_names
tm_formals

and possibly docs/roxygen2 processing

[kpagacz]

I am closing this one.