Lomse roadmap

This is a working document describing the high-level development plans for the Lomse library. The library aims not only at supporting renderization and playback but also at music score interactive edition. My objective is to build something similar to the Scintilla editing component, but for music scores. So I will continue Lomse development with that objective.

The Lomse library is now the core engine for the LenMus Phonascus music learning program. I use Phonascus as a test bed for the library, and this helps me to have some feedback about its usability, deficiencies, and needs. And also guides the definition of the roadmap and the short term objectives.

Short term objectives

The following list is in no particular order:

• Complete renderization support needed for current Phonascus 4.2 version. This task is practically finished. Done.
• I would like to start adding support for edition. It is important to have some scores edition facilities so that I can include advanced exercises in Phonascus.
• I have to improve all Lomse event generation and handling architecture. I'm thinking on creating a handling loop in another thread, but I have to study the issue in depth.
• I would like to move LDP to XML format in a zip archive container. This would allow me to pack images, fonts and other content. And to have a more powerful format, integrating the two currently existing formats: scores (.lms files) and eBooks (.lmb files). Done.
• I would like to add support for importing/exporting MusicXML files. This is not complex, as it is basically, building a parser. But will require some time (six months?). So after having done some experiments to validate ideas, it is a task I always postpone.

Please feel free to send me your comments, suggestions or questions about the Lomse roadmap. I would prefer to receive this feedback from the Lomse mail list. Thank you

If any one would like to join this project, you are welcome. I'm currently the only developer, so I would like to find one or two committed developers to create a core team. If you are interested and would like to take this project as your own project, you are welcome. The project has no commercial aim, so do not expect any money. I do this in my free time, for learning and for creating useful free software for the community. And costs me money!.

Last updated: 2012/07/20