version | 11.0.1 |
license | MIT |
native-modules | False |
elm-version | 0.18.0 <= v < 0.19.0 |
Tag | 11.0.1 |
Committed At | 2018-07-10 14:58:28 UTC |
elm-lang/websocket | 1.0.2 <= v < 2.0.0 | 1.0.2 |
elm-lang/http | 1.0.0 <= v < 2.0.0 | 1.0.0 |
elm-lang/html | 2.0.0 <= v < 3.0.0 | 2.0.0 |
elm-lang/dom | 1.1.1 <= v < 2.0.0 | 1.1.1 |
elm-lang/core | 5.1.1 <= v < 6.0.0 | 5.1.1 |
elm-community/string-extra | 1.4.0 <= v < 2.0.0 | 1.5.0 |
elm-community/list-extra | 6.1.0 <= v < 7.0.0 | 6.1.0 |
billstclair/elm-websocket-framework package at elm-lang.org
A websocket-based client/server framework written almost entirely in Elm.
This package is the client side. The server side is in billstclair/elm-websocket-framework-server.
You design your protocol, write JSON encoders and decoders for it, the server logic to use it to transform state, and the client logic to provide a user interface, and this package does the rest.
The server side depends on Node.js and RGBboy/websocket-server.
For single-player use, and development, you can wrap your server-side code for client use, in elm-reactor
if you want, then switch easily to using a real remote server.
I have used this basic technology for both my Spokes and Archmage games. I made the Archmage version by copying and modifying the Spokes version. Now that I want a server for JSMaze, it's time to wrap it as a package, embodying my experience in a form everyone can use.
See the README in the Example directory for instructions on building and running the examples.
Happy Hacking!
Bill St. Clair 31 March 2018