Needs Triage (5)
Wed, Feb 14
Tue, Feb 13
Sun, Feb 11
Tue, Feb 6
There could be mouse-over or clickable question-mark buttons right next to the Python and LilyPond input tabs in CodeScoreView. The text should be something like:
Mon, Feb 5
I think it would be cool to show a simple example of how code can be leveraged to generate a score. Like this (which works), run in the Python/Verovio side-by-side view. It's also cool that it shows you can import stuff.
Just a couple of thoughts in no particular order:
- Make English the default language.
- If a natural language field doesn't have a natural language specified, assume it's the default.
- If the requested language is not available, fill in that item with the default language.
- Two ideas on how Lychee could choose a starting language for the user. Either just make it in the default language unless the user explicitly changes it, or have it based on the ip address of the user.
- This would be a great way for new people to contribute to nCoda. It would be nice if there were some sort of form that people could side-by-side translate to fill in all the words and sentences we need.
- This stack overflow question has two interesting answers. One referencing what Qt does, the other suggesting that every user-facing text snippet could be passed through a tr() function that could retroactively include support for languages when we get there.
I realize that the alpha release is predominantly coder-oriented, but I still think we should move away from coder jargon as much as possible in client-facing text. So let's get rid of the word repository. Since we have relatively limited functionality for the alpha release, we should use this text to tell people to do the main thing that they would want to (and can) do which is to create a new piece. Here's what I propose:
Sun, Feb 4
What we promise for the MVP is everything that appears in the test plan.