Skip to content

Commit c2588c4

Browse files
committed
Update README
1 parent 80109da commit c2588c4

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -204,12 +204,12 @@ w.layout.display = "none"
204204
Yes! In fact this a crucial aspect to how packages like `{ipyleaflet}` work. In
205205
`{ipyleaflet}`'s case, each [individual marker is a widget](https://ipyleaflet.readthedocs.io/en/latest/layers/circle_marker.html) which gets attached to a `Map()` via `.add_layer()`.
206206

207-
### Does `{shinywidgets}` work with `shiny static`?
207+
### Does `{shinywidgets}` work with Shinylive?
208208

209-
Shiny's `shiny static` CLI command allows some Shiny apps to be statically served (i.e.,
210-
run entirely in the browser). [py-shinylive](https://github.com/rstudio/py-shinylive)
211-
(the Python package behind `shiny static`) does have some special support for
212-
`{shinywidgets}` and it's dependencies, which should make most widgets work out-of-the-box.
209+
Shinylive allows some Shiny apps to be statically served (i.e., run entirely in the
210+
browser). [py-shinylive](https://github.com/rstudio/py-shinylive) does have some special
211+
support for `{shinywidgets}` and it's dependencies, which should make most widgets work
212+
out-of-the-box.
213213

214214
In some cases, the package(s) that you want to use may not come pre-bundled with
215215
`{shinywidgets}`; and in that case, you can [include a `requirements.txt`

0 commit comments

Comments
 (0)