♩ ScoreRender ♫

0.3.x

• Implement lilypond-book syntax support
• chroot support for lilypond
• Implement Philip’s Music Writer notation support (done!)
• Better Windows support (done!)
• Test if cache directory corresponds to cache URL (done!)
• Access control based on author capability (specifically, ‘unfiltered_html’ capability) (done!)
• Warn if user turn on visual editing, that can damage score fragments!

0.4.x

• Admin page for basic management of fragment images, such as deleting individual cached images and finding out which image belongs to which post
• Store fragment metadata in another database table
• Filter user supplied content for deviation of page / staff size from hardcoded ones, and selectively drop them

Future Ideas

• Implement MusiXTeX, PMX and M-Tx notation support (postponed because TeX does not allow setting staff width)
• Implement MusicXML support (this one can be difficult)
• Better error handling (error message and debugging), perhaps using AJAX if possible?
• Pre-render image in management or post / page authoring page
• Allow people to choose whichever color they want for notes and background (Built-in alpha channel support in PHP is not there yet, not to mention PHP GD support under some Linux distro is braindead)
• Multi-page score sheet generation (this is probably too much for a mere WordPress plugin though)
• Allow ‘hooking’ / filtering of each notation. The primary goal is: add / remove include file would automatically add / drop support for certain notation.
• Is it possible to use file selection dialog to select program and paths?
• After changing image maximum width, should all cached images be invalidated?