Get_R(app_dir = "my/app/path", R_version = "2.2.1")Ĭreate_bat(app_name = "My AppName", app_dir = "my/app/path")Ĭreate_config(app_name = "My AppName", R_version = "2.2.1", app_dir = "my/app/path", Alternatively, you can provide instructions directly to those support functions like this: # Copy installation scripts (JavaScript, icons, infobefore.txt, package_manager.R, launch_app.R)Ĭopy_installation(app_dir = "my/app/path") You can (and probably should) specify most things there and they will get passed on. Privilege = "high", # Admin only installationĭefault_dir = "pf") # Install app in to Program FilesĬreate_app passes its arguments to most of the other support functions in RInno. Include_R = TRUE, # Download R and install it with your app, if necessary Remotes = c("talgalili/installr", "daattali/shinyjs"), # GitHub packages Pkgs = c("jsonlite", "shiny", "magrittr", "xkcd"), # CRAN-like repo packages If you would like to create a custom installer from within R, you can slowly build up to it with create_app, like this: create_app( ![]() All other user_browser options will be deprecated in future releases. Likewise, the Electron app will need to be recompiled to capture any manual changes to files in app_dir.Įlectron is now used to render the shiny app’s UI. The Inno Setup Script (ISS), app_name.iss, will look for default.ico and try to use it until you update the script or call create_app with the new icon’s file name (i.e. create_app(info_after = "infobefore.txt")) for those files have not changed. For example, you can replace the default/setup icon at, or you can customize the pre-/post- install messages, infobefore.txt and infoafter.txt. You can perform minor customizations before you call compile_iss. The main components are a file called “app_name.iss” and the “nativefier-app” directory. # Example app included with RInno packageĬreate_app(app_name = "Your appname", app_dir = "app")Ĭreate_app creates an installation framework in your app’s directory, app_dir. Once you have developed a shiny app, you can build an installer with create_app followed by compile_iss. RInno only requires a high-level understanding of what you’d like to accomplish. You don’t need to remember the 100+ places impacted by changing app_dir. DesktopDeployR requires many manual adjustments and a deep understanding of the entire framework to use, but RInno can be learned incrementally and changes automatically flow down stream. However, RInno also supports GitHub package dependencies, continuous installation (auto-update on start up), and it is easier to manage with create_app, the main RInno function. And similar to Dr. Lee Pang’s DesktopDeployR project, RInno provides a framework for managing software dependencies and error logging features. ![]() If a user does not have R installed, the RInno installer can be configured to ask them to install R along with a shiny app, include_R = TRUE. RInno is designed to be simple to use (two lines of code at a minimum), yet comprehensive. RInno makes it easy to install local shiny apps by providing an interface between R, Inno Setup, an installer for Windows programs (sorry Mac and Linux users), and Electron, a modern desktop framework used by companies like Github, Slack, Microsoft, Facebook and Docker.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |