Development

A place to gather miscellaneous development notes.

• See also: HOWTO contribute
• See also: Doxygen code documentation
• See also: Eclipse/CDT with Rosegarden
• See also: UnitTesting

These are short explanations that have come up on the Rosegarden developers' mailing list at one time or another, sometimes with a bit more detail added in the wiki.

See also the rosegarden-devel archives.

• Manipulating the document

• Loading the Studio or other partial documents from XML
• Keeping GUI elements updated

• Instruments and Devices

• Making strings translatable

These are either topics that have come up on the mailing list, or things that originally appeared as open-ended feature requests on our trackers.

See also Summer code.

These need to be simmered down into a single unified Theory of Notation Editing.

• Notation editor improvement thoughts
• Score layout, not just notation layout
• Notation layout, staff types etc

• Making a noise by default

• Ramblings about scripting
• A Vision

There are several plain-text documents found in the Rosegarden source code repository (browse).

These ones are either vaguely interesting, or at least not hopelessly out of date:

• Code formatting guidelines
• Overall code structure (out of date with respect to code file locations and build structure)
• Creating Events and their properties
• Pitch and time units for Events
• Iterating over Events in segments and compositions

• Menu layout explanation
• Saving toolbar state

• Triplet/tuplet event storage properties
• Notation event grouping terminology
• Notation layout procedure

• Recording from multiple MIDI ports (but not onto multiple tracks simultaneously - this document predates that work)