Snippets!

A quick update on what we've been up to recently.

Just yesterday, Vladimir Savic completed the first set of new icons he's been working on for OpenoctaveMidi, and he's done a grand job. The new icons look great as a set, and Vladimir's keen eye for detail shows, in the elegance of the design, and the unobtrusive nature of the pics.

Thanks Vlamidir for a good job well done!

The Denemo team have been at it again. Jeremiah, Richard, and Nils continue their breakneck pace, and there have been several important bugs fixed, and improvements in the structure and framework of the app. As the default choice of notation programme for the OpenOctave Project, we're naturally pleased with the developments, and features, and we'd like to thank the Denemo team for their continued hard work, and a great working partnership. Makes it lot easier when we're all facing in the same direction!

Chris and I continue to work on the auto script for the project, and are testing quite a few apps to determine their potential for inclusion. Stay tuned as we'll post on our results, and how they fit into the OpenOctave Project workflow, from beginning to end.

Some really quick thanks and mention for Fons who helped with a better understanding of the workings of Aeolus, his pipe organ app. I'm going to practise with this a bit more, and post a quick blog about Aeolus, and it's use in the OpenOctave Project in the near future.

 A quick reminder to users. When you use any programmes within a distro environment, it's important , if you have any issues or questions, to go to the distro forums or support areas first. They're responsible for the format and packaging of an application in their distro, not the original developers. If there's a problem, like an application segfaults, not starting correctly, or behaving in an unstable fashion, the responsibility for fixing this lays with the distro packager responsible. (And we ask that you treat these people politely, as they're volunteering their time to maintain packages)   Distros often impose other conditions that the original developer can't see, or have any control over, so please, help our community, and go to the right place, in the first place.

Thanks!