Databases
StackOverflow2013
Postsdbo
POManaging External Assets in R Package
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POManaging External Assets in R Package
    primarykey
    data
    text
    <p>I am writing an R package called <code>slidify</code> which makes it easy to generate reproducible HTML5 slides from R Markdown files. The package makes use of <code>css</code> and <code>js</code> files from several existing HTML5 slide generation frameworks like <code>dzslides</code>, <code>deck.js</code> etc. Currently, I have organized the downloaded versions of these external assets in the <code>inst/libraries</code> folder of <code>slidify</code>, so that it is automatically available for users upon installation. While this approach is simple, there are some disadvantages:</p> <ol> <li><p>These frameworks are constantly updated on <code>github</code>. Under the current setup, I would have to push a new version of the package everytime any of these frameworks are updated.</p></li> <li><p>If I make any tweaks to the default <code>css</code> and <code>js</code> that come with these frameworks, then I need to merge the updates carefully so that I don't lose <code>slidify</code> specific customizations.</p></li> </ol> <p>I had a couple of thoughts on how to manage this.</p> <ol> <li><p>Don't package these libraries with <code>slidify</code>. Instead, provide a <code>function</code> that would allow users to add the frameworks they desire.</p></li> <li><p>Add these frameworks to the <code>inst\libraries</code> folder on <code>slidify</code>, but as <code>submodules</code>. Now, I have no idea if adding them as <code>submodules</code> would get them installed if someone were to use <code>devtools::install_github</code>.</p></li> </ol> <p><strong>So my question is, when writing an R package how can I manage external non-R dependencies which are updated constantly?</strong></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRamnath
    1. USRamnath
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POManaging External Assets in R Package
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POManaging External Assets in R Package
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POManaging External Assets in R Package
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI really like your question; tweaked the phrasing at the end to ward off "not constructive" votes.
      singulars
      1. POManaging External Assets in R Package
      1. USjoran
    2. COThanks for the edit. It makes the question cleaner.
      singulars
      1. POManaging External Assets in R Package
      1. USRamnath
    3. COOne possibility is to look at packages `xlsx` and `XLConnect`. Both depend on Java libraries. `xlsx` defines (and depends on) a stand-alone package `xlsxjars` that only contains the libraries. In this way, the downstream code is decoupled from the libraries.
      singulars
      1. POManaging External Assets in R Package
      1. USAndrie
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload