Thoughts on reusable shiny modules

[Karthik Rajendran]

How do people share shiny modules for common use cases? (both universally re-usable ones or domain-specific)

I've not been following developments in the shiny community very closely, but I used shiny apps extensively in my last role and I had created a package of modules (mostly for myself) so that I can reuse common functionality especially in a data-science context.  I especially found the debug (develop-within-the-app) module helpful, although perhaps there are better ways to accomplish what I was trying now.

Link to the package repository: https://github.com/rajkar86/shinypipe

- Just curious. Would people find any of these modules helpful?

- More generally, is there value in encouraging sharing modules, and building upon them?

 

Thanks in advance!

Karthik

[Jonathan Cummings]

I don't know it there is a standard or common way to share modules, but I appreciate that yours are available on github. I think the debug module will be useful to me and that there is value in sharing and building on what others have developed.

Thanks for sharing.

[Justin BEM]

Modules can be bundle as R packages ...

[Karthik Rajendran]

Yes, that's what I attempted to do in the package that I shared before. But I don't see that as an active way that people actually use to share modules.

I don't know if there is any good list of packages that are meant to share shiny modules either.

Karthik

--
You received this message because you are subscribed to the Google Groups "Shiny - Web Framework for R" group.
To unsubscribe from this group and stop receiving emails from it, send an email to shiny-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/shiny-discuss/fd9c38c7-ed21-4926-8737-a91cf381cbb2n%40googlegroups.com.

[Justin BEM]

See DTedit package it a good example of shiny module sharing 

--

Justin Bem
Tél 00 241 02 28 02 37
BP 2180 Libreville