jaredforth / lilypond-rs

A Rust wrapper and types for GNU LilyPond

jaredforth.com

~ software engineer creating usable, accessible, humane, & ethical technology ~

lilypond-rs's Issues

Library Design

Hello again! (And happy holidays!) I haven't been as active as I would have liked lately, but I'm about to have some time that I plan to spend working on the project.

With that in mind, I was hoping to ask about the design and roadmap for the library. I don't really have much experience or training in program design, and am therefore somewhat at a loss for where to begin.

For my purposes, I'll be using this library to write a command-line application with subcommands for common computer-assisted composition tasks. I would therefore want the library to implement MIDI/integer-based data types, an interface between these and lilypond types, and various transformations to be performed on both, but I worry this might be out of scope. Whether or not these are appropriate, what features should the library have?

Also, how much needs to be covered on the notation side? It seems that the goal would be to compile from internal data, which I think would require structures as complicated as voices, staves, and maybe even scores? I think chords would also be useful to implement.

Finally, what general (or Rust-specific) design decisions should be made? Should struct members be public, or private with get methods? How should errors be handled (i.e. panic!, Option, or Result)? I may be forgetting several things, and it's been a while since I've studied the code, but these are the two that come to mind most immediately.

Apologies for the wall of text and the barrage of questions. If it's not too much trouble, I'd love to hear thoughts on this!

how to use this?

Hey, i am making a scripting language for writing and playing music.
I wanted to be able to export lilypond files.
I was looking for Rust bindings and this is the only thing i found.
However, it doesn't seem to provide any functionality yet.