|
| 1 | +This is a fork of the ropensci/plotly HtmlWidget for use in Displayr. The repository has been modified to be an node package and use the rhtmlBuildUtils framework. This was done in order to run unit tests on the widget js code, which has been modified by Displayr. The integration with rhtmlBuildUtils is incomplete, and only the building and unit testing of widget js code is supported. Features from rhtmlBuildUtils such as visual regression testing, linting and the internal web server are absent. |
1 | 2 |
|
2 | | -<!-- README.md is generated from README.Rmd. Please edit that file --> |
3 | | - |
4 | | -<img src="man/figures/plotly.png" width="200" /> |
5 | | - |
6 | | -[](https://travis-ci.org/ropensci/plotly) |
8 | | -[](https://cran.r-project.org/package=plotly) |
10 | | -[](https://www.rpackages.io/package/plotly) |
12 | | -[](https://www.rpackages.io/package/plotly) |
13 | | - |
14 | | -An R package for creating interactive web graphics via the open source |
15 | | -JavaScript graphing library |
16 | | -[plotly.js](https://github.com/plotly/plotly.js). |
17 | | - |
18 | | -## Installation |
19 | | - |
20 | | -Install from CRAN: |
21 | | - |
22 | | -``` r |
23 | | -install.packages("plotly") |
24 | | -``` |
25 | | - |
26 | | -Or install the latest development version (on GitHub) via devtools: |
27 | | - |
28 | | -``` r |
29 | | -devtools::install_github("ropensci/plotly") |
30 | | -``` |
31 | | - |
32 | | -## Getting started |
33 | | - |
34 | | -### Web-based ggplot2 graphics |
35 | | - |
36 | | -If you use [ggplot2](https://github.com/tidyverse/ggplot2), `ggplotly()` |
37 | | -converts your static plots to an interactive web-based version\! |
38 | | - |
39 | | -``` r |
40 | | -library(plotly) |
41 | | -g <- ggplot(faithful, aes(x = eruptions, y = waiting)) + |
42 | | - stat_density_2d(aes(fill = ..level..), geom = "polygon") + |
43 | | - xlim(1, 6) + ylim(40, 100) |
44 | | -ggplotly(g) |
45 | | -``` |
46 | | - |
47 | | - |
48 | | - |
49 | | -By default, `ggplotly()` tries to replicate the static ggplot2 version |
50 | | -exactly (before any interaction occurs), but sometimes you need greater |
51 | | -control over the interactive behavior. The `ggplotly()` function itself |
52 | | -has some convenient “high-level” arguments, such as `dynamicTicks`, |
53 | | -which tells plotly.js to dynamically recompute axes, when appropriate. |
54 | | -The `style()` function also comes in handy for *modifying* the |
55 | | -underlying trace |
56 | | -attributes (e.g. [hoveron](https://plotly.com/r/reference/#scatter-hoveron)) used to generate the plot: |
57 | | - |
58 | | -``` r |
59 | | -gg <- ggplotly(g, dynamicTicks = "y") |
60 | | -style(gg, hoveron = "points", hoverinfo = "x+y+text", hoverlabel = list(bgcolor = "white")) |
61 | | -``` |
62 | | - |
63 | | - |
64 | | - |
65 | | -Moreover, since `ggplotly()` returns a plotly object, you can apply |
66 | | -essentially any function from the R package on that object. Some useful |
67 | | -ones include `layout()` (for [customizing the |
68 | | -layout](https://plotly-r.com/improving-ggplotly.html#modifying-layout)), |
69 | | -`add_traces()` (and its higher-level `add_*()` siblings, for example |
70 | | -`add_polygons()`, for [adding new |
71 | | -traces/data](https://plotly-r.com/improving-ggplotly.html#leveraging-statistical-output)), |
72 | | -`subplot()` (for [combining multiple plotly |
73 | | -objects](https://plotly-r.com/arranging-views.html#arranging-plotly-objects)), |
74 | | -and `plotly_json()` (for inspecting the underlying JSON sent to |
75 | | -plotly.js). |
76 | | - |
77 | | -The `ggplotly()` function will also respect some “unofficial” |
78 | | -**ggplot2** aesthetics, namely `text` (for [customizing the |
79 | | -tooltip](https://plotly-r.com/controlling-tooltips.html#tooltip-text-ggplotly)), |
80 | | -`frame` (for [creating |
81 | | -animations](https://plotly-r.com/animating-views.html)), |
82 | | -and `ids` (for ensuring sensible smooth transitions). |
83 | | - |
84 | | -### Using plotly without ggplot2 |
85 | | - |
86 | | -The `plot_ly()` function provides a more direct interface to plotly.js |
87 | | -so you can leverage more specialized chart types (e.g., [parallel |
88 | | -coordinates](https://plotly.com/r/parallel-coordinates-plot/) or |
89 | | -[maps](https://plotly.com/r/maps/)) or even some visualization that the |
90 | | -ggplot2 API won’t ever support (e.g., surface, |
91 | | -[mesh](https://plotly.com/r/3d-mesh/), |
92 | | -[trisurf](https://plotly.com/r/trisurf/), etc). |
93 | | - |
94 | | -``` r |
95 | | -plot_ly(z = ~volcano, type = "surface") |
96 | | -``` |
97 | | - |
98 | | - |
99 | | - |
100 | | -## Learn more |
101 | | - |
102 | | -To learn more about special features that the plotly R package provides (e.g., [client-side linking](https://plotly-r.com/client-side-linking.html), [**shiny** integration](https://plotly-r.com/linking-views-with-shiny.html), [editing and generating static images](https://plotly-r.com/publish.html), [custom events in JavaScript](https://plotly-r.com/javascript.html), and more), see <https://plotly-r.com>. You may already be familiar with existing plotly documentation (e.g., <https://plotly.com/r/>), which is essentially a language-agnostic how-to guide for learning plotly.js, whereas <https://plotly-r.com> is meant to be more wholistic tutorial written by and for the R user. The package itself ships with a number of demos (list them by running `demo(package = "plotly")`) and shiny/rmarkdown examples (list them by running `plotly_example("shiny")` or `plotly_example("rmd")`). [Carson](https://cpsievert.me) also keeps numerous [slide decks](https://talks.cpsievert.me) with useful examples and concepts. |
103 | | - |
104 | | -## Contributing |
105 | | - |
106 | | -Please read through our [contributing |
107 | | -guidelines](https://github.com/ropensci/plotly/blob/master/CONTRIBUTING.md). |
108 | | -Included are directions for opening issues, asking questions, |
109 | | -contributing changes to plotly, and our code of |
110 | | -conduct. |
111 | | - |
112 | | ------ |
113 | | - |
114 | | - |
| 3 | +Changes to widget js code should be made in [theSrc/tasks](theSrc/tasks) and `gulp compileWidgetEntryPoint` needs to be called to compile the code and write it to [inst/htmlwidgets](inst/htmlwidgets). |
0 commit comments