Closed rpodcast closed 8 years ago
I'm looking forward to seeing all the neat things created by the folks that were lucky enough to attend the conference. I'll be happy to add that to the DESCRIPTION
. Thanks for the report. Probably time to revisit this nifty little htmlwidget
also...
Actually, I did not complete my htmlwidget
checklist on this one. The DESCRIPTION
is a mess. I'll need to get on my development machine to make sure that I don't screw something up. Ok if I complete first thing in the morning?
Thanks @timelyportfolio! Yeah it's no rush, whenever you get to it. The bigger app I'm working on has a lot more on the to-do list. BTW keep me posted when you want to chat for a future episode of the podcast!
@thercast hopefully 44c3775dcaf39bc66f3dc4a201569044d2bbbef6 fixes. Thanks for the issue. Loved the podcast with Dean. Ready when you are.
:thumbsup: success! The app deployed flawlessly this time. This little widget will go a long way to help improve the user experience of my apps going forward. I'll be in touch next week about the future episode.
Greetings, I'm getting back to creating a Shiny app that's composed with the new modules framework while incorporating
sweetalertR
. It was fairly easy to adapt your example from issue 1 and I put the snippet below. My question is regarding deploying this app on the new RStudio Connect beta service (it's like a supercharged Shiny server and works similarly as their Shinyapps.io service for deployment). Basically I'm getting an error every time complaining that thehtmlwidgets
package is not available when it gets to the installation ofsweetalertR
:I tried this deployment out with another Shiny app that uses the [visNetwork]() widget and during that deployment the
htmlwidgets
package was installed correctly before trying to installvisNetwork
and I'm guessing that's because thevisNetwork
package importshtmlwidgets
. Sorry for the long wall of text again, but would it be possible to declarehtmlwidgets
in the imports field of the DESCRIPTION file? I'd be glad to put in a pull request if it helps.Test app code: