Right now, we use hardcoded pixel offsets for everything, which is clearly an awful approach.

Something like https://github.com/dylanede/cassowary-rs should be investigated further.

Partially implemented in ac62e85. Design will probably be iterated further.

To have any practical use, we clearly need to be able to save and restore projects.

I've been thinking about perhaps embedding alacritty once they support embedding. But perhaps writing an Xi frontend would be better. Anything beats rolling our own text boxes - the quick implementation I have now will probably not be extended to multiline in favor of embedding something that is externally maintained and comfortable to use for long periods of time.

Currently, gfx_text is used, but it is very inflexible. gfx_glyph is lower level but should satisfy flexibility needs.

Bitmap fonts / pixel perfect TTF is not supported in gfx_glyph as well as gfx_text. We can live without.

To begin with, dynamic reloading should perhaps be avoided, but we should certainly be able to load new modules at runtime. Or at least at startup, but from a shared library.

I think that http://gluon-lang.org/ would make a good language for live coding. It has excellent rust interop and the operator overloading we need to live coding smooth.

Once we have #2, text editing, this is probably the next step.

I hope to have a simple way to transparently write modules in gluon. Only the most performance critical modules will need to be written in rust directly.

Using Future combinators can be quite unwieldy (see audio io for example) so writing modules is currently awkward. Data must be moved between processing stages explicitly in the current model. Async/await should improve this.

Ideally I think the module could be polled repeatedly until it is closed, in contrast to how the module is currently polled infinitely by the executor until it decides to stop itself. Maybe some kind of custom executor could handle that.

I don't know if headless mode is ever going to be a thing, but regardless it should be possible to do save/load, module creation/deletion, connection, etc without explicitly going through the GUI. Maybe via some kind of generic frontend trait. This will aid with testing and hopefully improve readability.

• Audio IO
• Buffer size change
• STFT
• Slider/knob
• Plotter
• Multiplexing
• Mixer