https://github.com/jaredreisinger/fizmo-json
https://github.com/jaredreisinger/fizmo-json
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/jaredreisinger/fizmo-json
- Owner: JaredReisinger
- License: bsd-3-clause
- Created: 2018-02-16T04:18:43.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2018-03-07T23:20:46.000Z (over 8 years ago)
- Last Synced: 2025-02-10T05:26:13.492Z (over 1 year ago)
- Language: C++
- Size: 260 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# fizmo-json
A [Fizmo](https://github.com/chrender/fizmo) front-end meant for
bot-mediated streaming/flowing UIs, like
[xyzzybot](https://github.com/JaredReisinger/xyzzybot).
## Usage
## Background
In working on [xyzzybot](https://github.com/JaredReisinger/xyzzybot), I noticed
a conflict between the expectations that a Slack-based interface presented and
the affordances given by [RemGlk](https://github.com/erkyrath/remglk) and
[fizmo-remglk](https://github.com/chrender/fizmo-remglk). In particular, while
the Glk API seems ideal for "local" game interactions, it adds a lot of
complexity to the "remote" scenario. Further, Fizmo has its own engine/client
API, which means that it’s ripte for a scenario-specific front-end.