KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#ai
#dsh-plugin
#deepseek-harness
#open-source
#cli
#claude-code
#codex
#developer-tools
#react
#windows
shinySignals
★ 31
Open GitHub ↗
No description available.
Download README (.md)
Explore Similar Repositories
lancache
:
Game Update Caching for LAN Parties
Statusbar-Download-Progress
:
Xposed module for showing download progress bar in status bar
whisper
:
Stream audio from browser to server
weechat-twitch
:
Checks status of streams using twitch api
aspnetmvc-for-osx
:
Fully working, runnable and clean ASP.NET MVC 5 project for Xamarin Studio and MONO on Mac OSX.
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
shinySignals
?
Download (.md)
# shinySignals [](https://travis-ci.org/hadley/shinySignals) Shiny is a reactive programming framework, but it focusses mainly on the nuts and bolts of generating interactive analysis apps. shinySignals is an attempt to port more functional programming tools that compute on signals (reactives). Currently, shinySignals only implements the [Signal](http://library.elm-lang.org/catalog/elm-lang-Elm/0.12.3/Signal) and [Time](http://library.elm-lang.org/catalog/elm-lang-Elm/0.12.3/Time) libraries from the [Elm programming language](http://elm-lang.org). It's expected that this package will grow over time to include useful techniques from other FRP frameworks, and to include uniquely R-like features. ## Installation shinySignals is currently only available on github. Run the following code to install it: ```R # install.packages("devtools") devtools::install_github("hadley/shinySignals") ``` ## Elm Compared to the Elm API, the main change is that the key signal always comes first. This leads to a more natural style of composition using `%>%`: ```R library(shinySignals) fps(30) %>% count() step <- reactive({fps(30); sample(c(-1, 0, 1), 1)}) walk <- step %>% reducePast(`+`, 0) ```