Future Roadmap

0.4.x

  • Allow user adjusting note color (done)
  • Store fragment metadata in another database table; beyond future management interface, this is useful for determining which post / comment links to which image, and perhaps clear all orphaned images
  • Filter user supplied content for deviation of page / staff size from hardcoded ones, and selectively drop them
  • Warn if user turn on visual editing, that can damage score fragments! (still unknown whether visual editing toggling is the culprit, will investigate later)
  • Allow ‘hooking’ / filtering of each notation. The primary goal is: add / remove include file would automatically add / drop support for certain notation (mostly done)
  • Allow empty cache dir / url settings, which should be treated as WP default (done)
  • Shortcode
    • Use native shortcode API instead of home-brew regular expression matching (done)
    • Allow [score lang="..."] shortcode as well, and possibly convert existing ones to new format (now accepts [score lang=""] and [scorerender lang=""])
  • ImageMagick version check
  • Check prerequisites during plugin activation, and deactivate if requirements are not satisfied

Future Ideas

  • Management interface
    • Pre-render image in management or post / page authoring page, in individual post or comment level
    • Admin page for basic management of fragment images, such as deleting individual cached images and finding out which image belongs to which post
    • Better error handling, possibly showing error message and debugging output in management interface
  • MIDI output (currently possible for Lilypond, Mup and Abc)
  • Use stub image before rendering finished, otherwise page loading can possibly take extremely long time to finish (especially true for Lilypond)
  • Multi-page score sheet generation (this is probably too much for a mere WordPress plugin though)
  • Is it possible to use file selection dialog to select program and paths?
  • After changing image maximum width, should all cached images be invalidated?
  • chroot support for lilypond (I think not many people manage this one?)
  • Notation support:

Leave a Reply

Powered by WP Hashcash