-
Notifications
You must be signed in to change notification settings - Fork 1
/
i-rstudio-addins.Rmd
56 lines (41 loc) · 1.89 KB
/
i-rstudio-addins.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
---
title: "Using `SpaDES.addins` with RStudio"
author:
- "Alex M. Chubaty"
date: '`r strftime(Sys.Date(), "%B %d %Y")`'
output:
rmarkdown::html_vignette:
fig_width: 7
number_sections: yes
self_contained: yes
toc: yes
vignette: >
%\VignetteIndexEntry{Using SpaDES.addins with RStudio}
%\VignetteDepends{SpaDES.addins}
%\VignetteKeyword{cache}
%\VignetteEncoding{UTF-8}
%\VignetteEngine{knitr::rmarkdown}
editor_options:
chunk_output_type: console
---
# Using RStudio addins
RStudio addins provide a graphical interface for performing common tasks.
After installing the `SpaDES.addins` package, go to the Addins menu in the RStudio IDE to see the list of available addins provided by this package.
![](figures/screenshot_menu.png)
You can assign keyboard shortcuts to any of these addins if you wish.
See https://rstudio.github.io/rstudioaddins/#running-addins.
## `SpaDES` module directory
The default module directory is a temporary one, and can be changed using `SpaDES.core::setPaths()`.
See `?SpaDES.core::setPaths` for details.
We recommend using a single local directory for your `SpaDES` modules.
Thus, only a single module directory is specified when using these addins.
# `SpaDES` module development
## Copy an existing module
The simplest way to get started on developing a `SpaDES` module, is to start from an existing module.
Anytime you wish to modify an existing module, we suggest working from a copy, rather than modifying the existing module directly.
To copy an existing module, simply invoke the *SpaDES: copy module* addin from the RStudio Addins menu.
![](figures/screenshot_copy_module.png)
## Create a new `SpaDES` module from a template
![](figures/screenshot_new_module.png)
# `SpaDES` package development (advanced)
More advanced users planning on contributing code to the `SpaDES` ecosystem of packages, can make use of additional package development tools.