tedsinger / stui Goto Github PK

Every command generates some javascript as text. This should be easy to test by separating the JS generation from w.Dispatch(etc etc).
First, I'd like to have a test that parses the JS and confirms that it is valid. Then I can start fuzzing the inputs.

In the case where an element used to match a selector, but doesn't anymore because something else moved, events on that element will still trigger any subscriptions on that selector. See listenAndApply in main.go

The intended behavior is for subscriptions to work like global CSS styles - automatically keeping up-to-date on every redraw

currently /tmp/stui is the default. multiple programs will clash

Dynamic languages can churn through deeply nested JSON in half of a line of code. But statically-typed languages have to endure a lot of boilerplate/reflection. I'd like to provide language-native header files for parsing and forming messages.

Protocol Buffers? Cap'n Proto? Flatbuffers? SOAP?

Replace Elem message component spec with jsonml.org

Some inconsistencies to resolve:
Commands have long names, events have short names.
Commands are in TitleCase, while events are in lowercase.

Styles currently assume that all values are strings. Is this correct?