http://www.rosegardenmusic.com/wiki/ 2012-05-17T03:41:17+00:00 http://www.rosegardenmusic.com/wiki/ http://www.rosegardenmusic.com/wiki/lib/tpl/rosegarden/images/favicon.ico text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:1.6.0?rev=1286188529&do=diff Aim To release Rosegarden 1.6.0 by end of September 2007 - Failed! To release Rosegarden 1.6.0 by end of October 2007- Released 1.6.0-pre1 (string freeze) in November 2, 2007! New aim: To release Rosegarden 1.6.0 few weeks after that ... Finally succeeded! text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:1.7.0?rev=1286188529&do=diff Plans * Making a noise by default * First Impressions and How to Improve Them * Different fonts in LilyPond (#1811129) * Consider merging notation command registration overhaul from Chris's kiftsgate branch? * Documentation revise. New features: track headers New features: segment sync and transpose stuff text/html 2010-07-23T17:38:13+00:00 http://www.rosegardenmusic.com/wiki/dev:1.7.3?rev=1279906693&do=diff ROSEGARDEN 1.7.3 RELEASED The Rosegarden team is proud to announce the release of version 1.7.3 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. http://www.rosegardenmusic.com/ This is primarily a bug fix/maintenance release. It addresses some critical track-related crashes that have been affecting users over the last couple of releases, and introduces assorted other minor fixes, such as improved multi-track recording for transposing instruments. It also inclu… text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:1.7.4?rev=1286188529&do=diff ROSEGARDEN 1.7.4 RELEASED The Rosegarden team is proud to announce the release of version 1.7.4 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. http://www.rosegardenmusic.com/ This release introduces [EDIT] We hope for this to be the final release of the KDE/Qt3-based Rosegarden. All work on this line of code has been suspended, and all of our effort is going into the new Qt4-based Rosegarden “Thorn” which we hope to release at some point in 2009. Unless we … text/html 2009-05-10T16:31:50+00:00 http://www.rosegardenmusic.com/wiki/dev:1.7.x_faq?rev=1241973110&do=diff General questions Do I have to be using a particular desktop environment (KDE or whatever)? No. Rosegarden uses the KDE libraries for various common controls, but you can run it under any window manager or graphical environment you like with no change in functionality. text/html 2008-09-04T01:47:54+00:00 http://www.rosegardenmusic.com/wiki/dev:1.8.0?rev=1220492874&do=diff ROSEGARDEN 1.7.2 RELEASED 2008-09-03/9-3-2008 The Rosegarden team is proud to announce the release of version 1.7.2 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. http://www.rosegardenmusic.com/ This is a maintenance release that follows close on the heels of 1.7.1. It includes some comparatively small but really interesting new features and usability improvements, which mostly concern lyrics, and a new lead sheet LilyPond export mode that lets you make lead … text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:10.02-beta_guide?rev=1286188529&do=diff Watch this space. I haven't made it quite this far yet. text/html 2010-01-27T15:51:57+00:00 http://www.rosegardenmusic.com/wiki/dev:10.02?rev=1264607517&do=diff The Rosegarden team is proud to announce the release of version 10.02 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. This release marks five years to the day since the release of 1.0 (which would be be called 05.02 using our current numbering scheme). Rosegarden has come a very long way in only five years! text/html 2010-03-11T16:53:41+00:00 http://www.rosegardenmusic.com/wiki/dev:10.04?rev=1268326421&do=diff The Rosegarden team is proud to announce the release of version 10.04 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> This release marks 10 years since the creation of our project at SourceForge. Rosegarden itself has been around in one form or another since 1993, but the current codebase has survived longer than any previous incarnation of the project. Rosegarden has overcome many obstacles in the last 10 years, including… text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:10.06?rev=1286188529&do=diff The Rosegarden team is proud to announce the release of version 10.06 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> This is a maintenance release. Bug Fixes * New Features Available Languages The following translations are complete and up to date for this release: text/html 2010-10-25T23:20:00+00:00 http://www.rosegardenmusic.com/wiki/dev:10.10?rev=1288048800&do=diff The Rosegarden team is proud to announce the release of version 10.10 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> This is a substantial bug-fix release, with fixes in almost every area of the application. text/html 2011-02-04T00:34:46+00:00 http://www.rosegardenmusic.com/wiki/dev:11.02?rev=1296779686&do=diff The Rosegarden team is proud to announce the release of version 11.02 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> This is a bug fix release that addresses a few of those annoying problems that hang around for the longest time, because they are rather complicated to fix. The most notable of these is that nine years after the first complaints, we have FINALLY found some sensible way to handle tied notes in the matrix and no… text/html 2011-05-15T04:33:21+00:00 http://www.rosegardenmusic.com/wiki/dev:11.06?rev=1305434001&do=diff The Rosegarden team is proud to announce the release of version 11.06 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> With this release, the Glasgow Pitch Tracker fork of Rosegarden finally merges into the new codebase, and into mainline Rosegarden. We on the core development team have done basically nothing of interest for this release cycle, and everything here was accomplished by contributors from the community. text/html 2011-11-05T04:53:57+00:00 http://www.rosegardenmusic.com/wiki/dev:11.11?rev=1320468837&do=diff The Rosegarden team is proud to announce the release of version 11.11 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. A long time in the making, this release combines a number of bug fixes with two major sub-projects that happened to come together right at the same time, and several completely new features as well. It is probably our most substantial offering since the landmark 10.02. text/html 2012-05-08T19:56:35+00:00 http://www.rosegardenmusic.com/wiki/dev:12.04?rev=1336506995&do=diff The Rosegarden team is proud to announce the release of version 12.04 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> Ted Felix and Tom “Tehom” Breton did the biggest part of the work that went into this release. Ted is a masochist who enjoys the challenge of cleaning up Rosegarden's enormous and complicated code in order to make it less buggy, and much more sensible. Tehom is a visionary who comes up with crazy complicated … text/html 2009-03-08T18:59:04+00:00 http://www.rosegardenmusic.com/wiki/dev:2.0?rev=1236538744&do=diff ROSEGARDEN 2.0.0 (to be) RELEASED IMPORTANT: THIS HAS NOT HAPPENED YET This page is only a working area for making notes about what is being done for the 2.0 release, so that we don't forget anything when the code is finally ready to be released -- which will not be for some time yet. text/html 2009-12-18T06:22:38+00:00 http://www.rosegardenmusic.com/wiki/dev:9.x?rev=1261117358&do=diff IMPORTANT: THIS HAS NOT HAPPENED YET This page is only a working area for making notes about what is being done for the 10.02 release, so that we don't forget anything when the code is finally ready to be released -- which will not be for some time yet. text/html 2008-07-28T14:19:10+00:00 http://www.rosegardenmusic.com/wiki/dev:a_programme_for_tedium?rev=1217254750&do=diff Or “A Program For Tediumme”. How to help out with the dull, mechanical part of converting to Qt4. Working environment Here's how to check out, update, and test-build the “Qt4 Mechanised Conversion” branch. First you'll need the Qt4 and KDE4 headers. Here on Ubuntu 8.04 this one line seems to be enough: text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:a_vision?rev=1286188529&do=diff Mail archive link - See also - “Having visions is easy” On Sunday 19 Feb 2006 00:38, Luis Garrido wrote: > So what is your vision, then? I'm not sure I have a "vision", or at least not one that I understand how to realise, which is probably why it isn't very well expressed in Rosegarden. Traditional notation is a very useful thing in music learning, in exchanging and publishing certain sorts of music in certain ways, and in musicological contexts. MIDI and the like are very useful not just … text/html 2009-10-23T15:34:15+00:00 http://www.rosegardenmusic.com/wiki/dev:after_thorn?rev=1256312055&do=diff We're leaving a lot of messy things behind in the interest of getting the job done. These items (at least the items I have in mind as I'm creating this list) are pretty ugly in code terms, but don't affect end users much, if at all, and they require more fiddling than clean code justifies in the short term. text/html 2009-11-25T22:07:55+00:00 http://www.rosegardenmusic.com/wiki/dev:branching?rev=1259186875&do=diff To branch or not to branch? The decision whether to branch or not is not really something that follows a strict formula, but you should consider doing your work in a branch if it: * involves disabling a lot of code in order to work through a problem step by step until it is finally solved * is an experimental idea that might not be an improvement, or might not be workable after all * is something big and new that might require design modification before everyone can agree on including it… text/html 2009-11-30T04:24:52+00:00 http://www.rosegardenmusic.com/wiki/dev:bugs_todo?rev=1259555092&do=diff Fix as many of these as possible before Abraham Darby, but not before Thorn. * Show annotations/LilyPond directives is broken in the notation editor, and I'm just leaving it broken. It needs some fairly heavy sorting, and there are more important things to fix first. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:candidates_for_future_symbols?rev=1286188529&do=diff Symbols are a new thing that have subordering and duration like text events, for example performance directions, tempo indications, and other such that are no-ops from a sequencer perspective, but will display suitable glyphs on the staff instead of arbitrary or canned texts. The first three of these are the segno, coda, and breath mark, which aim to be a 1:1 replacement for the LilyPond directive Text tool based hacks that have been working and exportable for some time. text/html 2008-07-27T03:37:57+00:00 http://www.rosegardenmusic.com/wiki/dev:cases_that_we_know_require_hand_coding?rev=1217129877&do=diff Cases we know require hand coding * QComboBox::text() becomes itemText(), but I'm sure the word “text” appears umpty scadillion times, and I'm immediately relegating these cases to hand correction * QRegExp no longer has search() and searchRev(), which have been replaced with text/html 2009-11-25T22:40:34+00:00 http://www.rosegardenmusic.com/wiki/dev:code_consistency?rev=1259188834&do=diff We try to maintain code consistency with several methods. Some of the methods are very general while the others are specific only to the Rosegarden project. A note on this page: this page is ment to be incomplete and subject to change. Design patterns The guide lines below are mostly justifiable text/html 2010-12-17T01:27:33+00:00 http://www.rosegardenmusic.com/wiki/dev:coding_style?rev=1292549253&do=diff Rosegarden house style is as follows, in approximately descending order of importance: * Class names are UpperCamelCase, method names are lowerCamelCase, non-public member variables are m_prefixedCamelCase, slot names start with “slot”. * Indentation is by four spaces at a time. There should be no tab characters anywhere in Rosegarden source code. The indentation should look the same regardless of whether you read it in an IDE, in a terminal window with “cat” or “vi”, in Emacs, or quoted… text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:comment_codes?rev=1286188529&do=diff * indicates code that has been temporarily disabled in order to get a file to compile. use very sparingly! //&&& * indicates places in the code where the person doing the porting wasn't completely certain about the right thing to do, and made a best guess. If these guesses are incorrect, there could be problems after the code is running, and these comments are the first place to look for solutions to weird problems. //@@@ text/html 2009-08-15T17:16:11+00:00 http://www.rosegardenmusic.com/wiki/dev:config_groups_config_groups?rev=1250356571&do=diff Rosegarden currently uses a mixture of idioms after the conversion to use QSettings for storing user preferences. The first type of code looks like: QSettings.settings; settings.beginGroup("Lazy Options Directly in a String"); ... The second type of code looks like: text/html 2011-07-27T08:43:42+00:00 http://www.rosegardenmusic.com/wiki/dev:contributing?rev=1311756222&do=diff (still needs more editing, but I'm leaving it alone for now) There are numerous ways to contribute to Rosegarden. You may * Create a patch (described in this page) * Report a bug * Create a feature request (Please understand that some good requests everyone likes have still been on the waiting list for several years.) text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:creating_events.txt?rev=1286188529&do=diff From email, 2002 01 04 To create a new sort of event, you just create an Event with a type name that hasn't been used before, and to add properties, you just use a new property name. (We have a big potential problem with namespacing property names, as there's no central registry of names that have been used. I've been considering adding something that might help, because we do actually intern PropertyName strings, we just don't yet complain about duplicates definitions -- but it won't prevent… text/html 2009-09-20T20:24:02+00:00 http://www.rosegardenmusic.com/wiki/dev:development?rev=1253478242&do=diff A place to gather miscellaneous development notes. * See also: HOWTO contribute * See also: A getting started page for new project members * See also: Future Plans * See also: Doxygen code documentation * See also: Eclipse/CDT with Rosegarden * See also: UnitTesting text/html 2009-07-29T15:28:22+00:00 http://www.rosegardenmusic.com/wiki/dev:device_management_and_replacing_auto-connect?rev=1248881302&do=diff Device Management (in Thorn), and Replacing the Unwanted Auto-Connect Rosegarden 1.7.x has quite a strange device management system, in which devices (meaning: virtual things within the Rosegarden document, that can be connected to external MIDI hardware ports or software programs) are created “on demand” by Rosegarden itself, connected up automatically, and so on. text/html 2008-09-08T14:12:15+00:00 http://www.rosegardenmusic.com/wiki/dev:directories_compiled?rev=1220883135&do=diff Lately, I've been looking at problems on a per-directory level. Some are easier than others in general. Unsurprisingly, our first 100% directory is base. * base/ (except base/test, which has some obscure public vs. private friend class problem that doesn't look related to QT4 at all; I'm just skipping it, because base/test can totally wait until much later) * src/misc text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:doxygen?rev=1286188529&do=diff There is apparently somebody out there bored enough to publish our Doxygenized code for the entire world to see. This makes it that much more important that we update and clean up our Doxygen-targeted internal comment documentation. Please have a look at the existing Doxygen-based docs, and then look at the doxygen style info page for help figuring out how to clean up the existing mess, and extend it into something vastly more useful going forward. text/html 2012-04-29T18:02:44+00:00 http://www.rosegardenmusic.com/wiki/dev:eclipse?rev=1335722564&do=diff Get Rosegarden Source From SVN To get started we'll need the source code for Rosegarden. We can get a copy of it from sourceforge using subversion (svn). Since we are going to use the source with Eclipse, we'll need to make sure that we set up the directories in a way that will make Eclipse happy. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:eclipsecdt?rev=1286188529&do=diff Eclipse has been a popular IDE for Java developers for a long time, but it also provides an excellent environment for other languages. CDT is the Eclipse IDE for C/C++ developers. This document is a quick tutorial to set up a working development environment for Rosegarden using Eclipse CDT on Linux. text/html 2009-12-06T05:28:26+00:00 http://www.rosegardenmusic.com/wiki/dev:file_format_version?rev=1260077306&do=diff I just caught myself in an error, and I made the mistake because I can't ever really remember there being any guidance on what to do about the file format version number. I had to go do a bit of digging to figure this out. It seems past time to establish some formal policy on this one, so the mistakes of the past can be avoided in the future. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:first_impressions_and_how_to_improve_them?rev=1286188529&do=diff How does Rosegarden appear when first installed and run on a new Linux distribution? I've been so used to fixing problems “in the distribution” with Studio to Go that I no longer really remember what the normal first time user experience on a non-audio-focused distribution is like. However, I do remember that it used to be pretty lousy; that's one reason STG exists in the first place. So, I downloaded Ubuntu 7.10 and gave it a try. (I just used Ubuntu because it's popular and it isn't KDE-based… text/html 2009-11-25T22:25:05+00:00 http://www.rosegardenmusic.com/wiki/dev:future_plans?rev=1259187905&do=diff 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. They won't all necessarily happen; they're just ideas. * See also: Summer code, Code Consistency * See also: Plans for 9.x text/html 2009-03-06T02:44:04+00:00 http://www.rosegardenmusic.com/wiki/dev:help_with_config_page?rev=1236307444&do=diff This is the heart of the whole thing, and until we solve this, everything else is completely irrelevant. I have a decent roadmap to follow rearranging the GUI, thanks to Luis Garrido, but it seems completely pointless to me to fix the GUI while the whole configuration dialog itself remains broken. One way or another, this problem needs to be solved up front. text/html 2012-03-29T03:24:21+00:00 http://www.rosegardenmusic.com/wiki/dev:how_a_note_becomes_a_sound?rev=1332991461&do=diff How a note becomes a sound in Rosegarden. A note is a type of Event. All events live in Segments. There are two kinds of segments, internal and audio. Events live in the internal kind of Segment. The first steps towards becoming a sound occur even before you tell Rosegarden to play. As soon as a document is loaded, Rosegarden creates (among other things) a SequenceManager and a RosegardenSequencer, which we'll get to later. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:includes?rev=1286188529&do=diff This needs to link in from some best practices thing for developers that hasn't been written yet. As I've gone through the Qt4 port, I'm enforcing these standards as I come to includes that need to be diddled. I think we should follow the same pattern everywhere for consistency. Do we still have templates somewhere? If so, we should update them to reflect this. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:instruments_and_devices?rev=1286188529&do=diff Problem description We would like a way to insert MIDI program changes in the middle of tracks. This is a common feature in many sequencer programs, but it is not currently supported by RG. Also, the “import MIDI files” function can't be properly fixed now to process MIDI files having PC events in the middle of the tracks. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:keeping_gui_elements_updated?rev=1286188529&do=diff Mail archive link Keeping GUI elements updated, e.g. notifying the NotationView if a segment has changed, is done through the RefreshStatus class. This class holds a set of 'observer IDs'. Every Segment carries a RefreshStatus, and every edit part displaying one has an observer ID. Whenever a change is made in a segment, its RefreshStatus is set to 'has changed' for all observer IDs. Then each observer, whenever it's refreshed, checks its status ID to see if the segment it displays has chan… text/html 2009-06-27T23:05:59+00:00 http://www.rosegardenmusic.com/wiki/dev:layout_code?rev=1246143959&do=diff When doing new work in Rosegarden, it is perfectly acceptable to use Qt Designer if you prefer. One good example of a new Designer-based dialog is the MIDI device manager. However, most of our layout code is hand-written Qt, and most of us have seemed to prefer this approach over the years, so we will probably go on having a high proportion of hand-written layout code. text/html 2011-03-11T21:25:13+00:00 http://www.rosegardenmusic.com/wiki/dev:linked_segments?rev=1299878713&do=diff Linked Segments What is it? The ability to have segments linked together. In its simplest form, linked segments would appear identical - the events in one would appear to be the same as the events in the others to which it was linked. Edits to a linked segment would be reflected in its siblings. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:loading_the_studio_or_other_partial_documents_from_xml?rev=1286188529&do=diff Mail archive link Unlike our XML export code, which is located within the particular class being exported, we only have one single large XML import class (RoseXmlHandler, in src/document/) which reads a complete document in one go. In cases where we only need to import part of a document -- for example, when importing a .rgd device file, which consists of just the studio element from a .rg file -- we do it by importing the file as if it were a complete document, into a new RosegardenGUIDoc o… text/html 2008-08-03T05:08:47+00:00 http://www.rosegardenmusic.com/wiki/dev:making_a_noise_by_default?rev=1217740127&do=diff Making a noise by default The most common source of problems for new users of Rosegarden is still a straightforward inability to get any sound out of it. There are two parts to this problem, plus a third related problem: * “Notes” in Rosegarden are MIDI only by default and are not synthesised within the program, so the user needs to run a separate synth or load a plugin and use it explicitly. * To make use of a plugin, or anything else that involves RG actually making the sound, JACK need… text/html 2009-05-04T02:56:36+00:00 http://www.rosegardenmusic.com/wiki/dev:making_strings_translatable?rev=1241405796&do=diff THIS DOCUMENT IS OBSOLETE AND NEEDS TO BE EDITED HEAVILY OR REPLACED ======Making strings translatable====== =====A few quick notes===== Please note that the base/ directory does not use QString, and so cannot be translated with the KDE tools. If you think a string needs to be there that absolutely must be translated, the mailing list is the best place to work this out. Unfortunately, someone has made the decision that American English be the default language for KDE apps, so all inter… text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:manipulating_the_document?rev=1286188529&do=diff It's usually neatest to wrap manipulations to the document in a 'Command' (src/commands/*). Commands know how to undo themselves. When you add a command to the history (e.g. via 'RosegardenGUIDoc::getCommandHistory()->addCommand(my_command);'), the command will be executed and added to the undo history. text/html 2009-12-22T04:11:48+00:00 http://www.rosegardenmusic.com/wiki/dev:michael?rev=1261455108&do=diff This is a place for me to jot down things I want to remember, in a place where I can remember where I put them. Parts vs. Score I don't have any specific thoughts about how to tackle this, but we really need some way to print parts vs. printing the entire score. Tempo indications and other such directives are per segment, but many should be present in individual parts if they're printed separately. We can make nice looking scores complete with brackets now, but there isn't any simple, conven… text/html 2009-06-12T14:06:59+00:00 http://www.rosegardenmusic.com/wiki/dev:midi_control_interface_draft?rev=1244815619&do=diff . Ideas * Allow external control for the transport using normal MIDI CCs * Allow the mixer to be controled using CCs * Allow selecting segments in the arranger using 2 CCs (vertical and horizontal) - is that really useful ? * Allow selecting the current track over CCs, maybe dis/enable record state * Allow to record Controler movements, in order to articulate midi tracks: expression, velo, portamento, modulation, etc.. text/html 2009-11-30T04:22:48+00:00 http://www.rosegardenmusic.com/wiki/dev:missing_slots?rev=1259554968&do=diff We need to investigate all of these and either restore the missing slots or remove the useless cruft calling slots that no longer exist for good reason. AudioInstrumentParameterPanel * AudioInstrumentParameterPanel::updateAllBoxes() in src/gui/editors/parameters/AudioInstrumentParameterPanel.cpp:81 text/html 2009-09-01T02:33:04+00:00 http://www.rosegardenmusic.com/wiki/dev:new_developers?rev=1251772384&do=diff You've been referred to this page because you've been granted commit access to our Subversion repository. Rosegarden is a large and complex project, and we depend on volunteers like you to make it happen. Thanks for participating in Rosegarden development, and welcome to the team! text/html 2012-01-09T00:56:23+00:00 http://www.rosegardenmusic.com/wiki/dev:next_version?rev=1326070583&do=diff The Rosegarden team is proud to announce the release of version xx.xx of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. <http://www.rosegardenmusic.com/> With this release... Bug Fixes * New Features * ... Active translators for this release: * D. Michael McIntyre * Yves Guillemot text/html 2011-01-24T01:22:54+00:00 http://www.rosegardenmusic.com/wiki/dev:notation_cleanup?rev=1295832174&do=diff Start Date: 01/23/2011 End Date: 03/07/2011 (Projected) Primary Developer: Julie Swango (msjulie_s@yahoo.com) The intent of this branch is to clean up several aspect of the Notation Editor to allow consistent entering and editing of notation. There will be spill over to the Matrix / Percussion Editor as well, but it is not the primary focus of this branch. text/html 2009-01-16T23:59:02+00:00 http://www.rosegardenmusic.com/wiki/dev:notation_crash_discussion?rev=1232150342&do=diff We're up to 9736 now, and I have the impression that other people are at least able to start digging into the notation editor's problems. It still crashes here. * Create one bar segment * Open segment in notation editor * Long pause, some draw action, and then kaboom text/html 2010-01-05T10:34:57+00:00 http://www.rosegardenmusic.com/wiki/dev:notation_editor_improvement_thoughts?rev=1262687697&do=diff Notation editor improvement thoughts This page started out as Bug #1310257 - Notation editor has limitations and may confuse. See also Notation layout, staff types etc - excerpts from another discussion about notation editor reworking. See also Score layout, not just notation layout. text/html 2010-10-17T03:20:36+00:00 http://www.rosegardenmusic.com/wiki/dev:notation_layout_staff_types_etc?rev=1287285636&do=diff Notation layout, staff types etc Mail archive thread link (a long discussion about potential future changes) See also Notation editor improvements. See also Score layout, not just notation layout. Note: this is not a description of code actually in Rosegarden, it's part of a discussion about future work. That particular discussion didn't really go anywhere, but it's possible material for later. text/html 2009-09-05T16:26:43+00:00 http://www.rosegardenmusic.com/wiki/dev:notation_toolbar_2?rev=1252168003&do=diff Revision 2.1 -- 08/29/2009 This page is a reference for the branch/obsolete/notation_toolbar_2 branch. NOTE: This branch was not intended as a rewrite of the entire notation view interface but is limited to a few very focused aspects related to notation entry which requires a rewrite of the NoteInserter and RestInserter classes. text/html 2010-01-21T16:23:42+00:00 http://www.rosegardenmusic.com/wiki/dev:notes_on_porting_to_qt4?rev=1264091022&do=diff See also: * Porting from Qt3 to Qt4 * Porting from KDE3 to KDE4 * Cases we know will require hand editing of the code * Porting RG, qt3->qt4 *Examples* * List of current and completed developer tasks for RG Qt4 port * Comments on dialogs and the buttons in them text/html 2008-08-31T19:49:43+00:00 http://www.rosegardenmusic.com/wiki/dev:notes_on_porting_to_qt4_examples?rev=1220212183&do=diff This may be a help, for new contributors to the qt4/kde4 port of rosegarden. It may also serve to see, what could be replaced with “search'n replace scripts”. If possible, avoid to use the Q3Support and includes. Use the new Qt4 classes instead. Reason: Q3Support doesn't work as well, as it one might expect and we need to move to Qt4 anyway. text/html 2011-01-26T00:12:59+00:00 http://www.rosegardenmusic.com/wiki/dev:overall_code_structure?rev=1296000779&do=diff DISCLAIMER: I am not myself a RG developer, so any hardcore Rosegardener's comments, additions or corrections to this document will be very welcome. It would be also nice if the doxy output was published somewhere in the web site so it could be referenced from the wiki. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:preferences_restructuring?rev=1286188529&do=diff Which options are too obvious; which are not obvious enough; which are about right? Key: Too obvious, not obvious enough, about right General/Presentation This is one of the worst config tabs, and it's the first one you see! * Note name style (definitely) text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:qt4-graphicsview-branch-new-plings?rev=1286188529&do=diff src/gui/editors/matrix/MatrixView.h 68: virtual void initStatusBar() { }//!!! 69: virtual void updateViewCaption() { }//!!! 70: virtual timeT getInsertionTime() { return 0; }//!!! src/gui/editors/matrix/MatrixView.cpp 466: // emit usedSelection();//!!! src/gui/editors/matrix/OldMatrixView.cpp 75: //!!!#include "gui/general/ActiveItem.h" 282: //!!! if (isDrumMode()) m_staffs[i]->setX(resolution); 581: //!!! addPropertyViewRuler(BaseProperties::VELOCITY); 1010: … text/html 2010-01-12T21:25:28+00:00 http://www.rosegardenmusic.com/wiki/dev:qt4_bug_tracker?rev=1263331528&do=diff Rosegarden 10 Fake Bug Tracker We're just using this wiki page as a tracker for now. To report a bug, just jot something down, preferably at the top of the stack, using docuwiki numbered list syntax (like the existing examples.) To claim a bug, tack your initials after it in brackets, like [dmm] or [cc] text/html 2009-11-16T03:21:36+00:00 http://www.rosegardenmusic.com/wiki/dev:qt4_feature_review?rev=1258341696&do=diff This is intended to be complementary to the Fake Bug Tracker. This was a good idea Chris had, but let's take it to the next level. For the first phase, we're going to go through every menu in Rosegarden item by item, and create a structure following this pattern: text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:ramblings_about_scripting?rev=1286188529&do=diff Mail archive link We have a few shreds of DCOP support for calling basic menu functions (loading a file, playing from a given time etc), but not really for any editing. Some of the menu options we have already might have been easier to build if there had been a script-style interface to make them from. It needn't even necessarily have involved a scripting language -- just an interface that works at a slightly higher level than our basic data structures, allowing the author to avoid worrying … text/html 2009-04-16T16:10:34+00:00 http://www.rosegardenmusic.com/wiki/dev:regression_snapshots?rev=1239898234&do=diff Committed revision 9957. Committed revision 10014. Committed revision 10127. Committed revision 10211. text/html 2008-11-23T19:59:23+00:00 http://www.rosegardenmusic.com/wiki/dev:rg_qt4_action_management?rev=1227470363&do=diff A plan for managing construction and property setup on QActions for menus and toolbars There are three “developer roles” here which can readily be done by different people with very little interaction -- so I suggest we do that, unless we can't find three, erm, “volunteers”. text/html 2011-11-22T09:09:50+00:00 http://www.rosegardenmusic.com/wiki/dev:rg_qt4_dialogs?rev=1321952990&do=diff Comments on our use of dialogs, with regard to the Qt4 port (Michael wrote) > I don't care about KDialog vs. QDialog though, and if possible, could we get > rid of all the stupid [redacted] Apply buttons except for the ones that actually > make sense? KDE3 is full of Apply buttons that are totally stupid, just like > Windows. I know dozens of people who think they have to click Apply and then > OK instead of just clicking the [redacted] OK button. It drives me nuts, and > we're full … text/html 2009-01-06T12:46:54+00:00 http://www.rosegardenmusic.com/wiki/dev:rg_qt4_task_list?rev=1231246014&do=diff See also: * Thoughts on porting to Qt4/KDE4 * Directories that compile 100% * Managing construction and property setup for menu actions etc Summary This page is for the developers involved in the Rosegarden QT4 port. The intent is to track each developers current task and to log their accomplishments. Let's hope this works easily for everyone involved. text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:score_layout_not_just_notation_layout?rev=1286188529&do=diff Score layout, not just notation layout Text initially excerpted from RFE #1559811 - more staff grouping options. See also Notation editor improvement thoughts. See also Notation layout, staff types etc. CC: We don't have any staff groupings natively in Rosegarden. The main reason for this is not that the brackets or whatever are hard to represent internally or to draw, but that I failed to come up with a good way for the user to describe what groupings they wanted in the first place. text/html 2009-09-28T16:24:16+00:00 http://www.rosegardenmusic.com/wiki/dev:slog_endgame?rev=1254155056&do=diff The end is closer every day. After months of slogging, we finally have something tangible, and quite broken. Rosegarden 2.0 is primarily a Qt4 application, but it still depends on KDE4 for i18n() is now a Qt4 application, but still uses some Qt3-compatibility classes, such as Q3Canvas to defer those major rewrite until after the obligatory rewrites have been accomplished. text/html 2009-05-11T03:59:07+00:00 http://www.rosegardenmusic.com/wiki/dev:style_bugs?rev=1242014347&do=diff regression_snapshots Outstanding Issues * Progress dialogs are coming out solid black. Progress dialogs are still broken to the point where they're random and useless, so I haven't bothered to try to iron this out at all. I haven't tried to style the actual progress bars themselves yet either, but that needs to be done eventually. text/html 2009-11-16T22:48:12+00:00 http://www.rosegardenmusic.com/wiki/dev:summer_code?rev=1258411692&do=diff This page collects small development projects for Rosegarden in the spirit of Google's Summer of Code (although without the funding! Some institutes may proved funding for students who would program open source applications in summer time -- you may pick up projects from here!). text/html 2008-08-15T13:18:04+00:00 http://www.rosegardenmusic.com/wiki/dev:svn_post_1.7.0?rev=1218806284&do=diff (Redundant page deleted.) text/html 2009-02-14T20:29:47+00:00 http://www.rosegardenmusic.com/wiki/dev:the_merge?rev=1234643387&do=diff It's nearly time to merge all the changes that went into 1.7.3 after the fork that became the qt4 branch. OLD TRUNK: stable_1_7/ NEW TRUNK: trunk/ <= qt4/ <= qt4-graphicsview Bugs * Assigning a port (connection) to a record-device re-sets the Recording-Enabled status of all record-devices to “No” text/html 2009-12-05T02:36:34+00:00 http://www.rosegardenmusic.com/wiki/dev:thorn_matrix_review?rev=1259980594&do=diff This is a continuation of the notation review, using what started as aveverum.rg but is highly mangled now. I've grabbed a random swipe of segments top open in a multi-segment matrix view. BUG Shift+click on the piano keyboard to select all notes of that pitch. Shift+click and drag to sweep select. Neither of these works. MUST FIX! text/html 2009-11-30T04:52:50+00:00 http://www.rosegardenmusic.com/wiki/dev:thorn_notation_review?rev=1259556770&do=diff BUG You should be able to click on a note to select it, then start dragging it around. Likewise clefs, and probably myriad other things. This is all broken too. [This looks like it's probably related to a couple fixes ago, my hack that said PLEASE REVIEW! on it. It's more bogus w and h variables, seems like to me. I haven't given up any hope of sorting this one, but it's not the best use of my time if there's any remote possibility Chris might steal enough time to have a look himself.] text/html 2012-04-29T21:52:25+00:00 http://www.rosegardenmusic.com/wiki/dev:tnp?rev=1335736345&do=diff Goal To implement a consistent notification mechanism whereby Boundary (User Interface) objects make changes directly to Entity (Document) objects and use a notification (Observer) mechanism within the Entities to inform the rest of the system of changes. text/html 2009-03-08T04:29:08+00:00 http://www.rosegardenmusic.com/wiki/dev:tooltips?rev=1236486548&do=diff After some discussion on the devel list, we've decided we need a lot more tooltips. I want to add more tooltips, and make better, more useful tooltips taking advantage of Qt4's rich text capabilities. I got this little project started by adding a mostly complete set of tooltips to the SPB today. In particular, there's a fancy new tooltip, we'll call it the “drool tip,” hanging off the repeat button in the SPB. text/html 2009-03-06T02:42:38+00:00 http://www.rosegardenmusic.com/wiki/dev:transport_focus?rev=1236307358&do=diff Update: Chris added to another, related, report: Chris: Looks like Qt::Tool is not the proper window type for this window, regardless of how nicely it works for me! Try replacing Qt::Tool at TransportDialog.cpp:59 with some other flag, or combination of flags, from <http://doc.trolltech.com/4.4/qt.html#WindowType-enum> and see what serves best. --cc) text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:units.txt?rev=1286188529&do=diff Performance pitch Events store pitch values in simple integers. These are fixed-frequency pitches in the MIDI pitch scale, independent of clef and key. Adding 12 to a pitch increments it by one octave; pitch 60 is the treble-clef middle C. (Previous rewrites have considered using double the MIDI pitch so as to allow quarter-tones; this time let's go for the simpler option as if we ever want quarter-tones we can always code them using special Event properties.) text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:unittesting?rev=1286188529&do=diff Unit tests are useful to call code in isolation during development (so you don't need to start the entire GUI to test every change), and for regression tests. A couple of unit tests for Rosegarden have been written in src/test. Building Enable WANT_TEST in ccmake and build the codebase as usual text/html 2009-09-04T18:56:27+00:00 http://www.rosegardenmusic.com/wiki/dev:using_git?rev=1252090587&do=diff Before continuing to read this page, you have two options: * If you are happy with using svn, stop reading here. * If you would like to experiment with git, continue reading. This page has been benefited a lot from the following pages: * Effectively Using Git With Subversion text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:wiki-convert?rev=1286188529&do=diff Pleasantly ugly script to convert from SourceForge wiki format (WikiSpaces) to Dokuwiki #!/usr/bin/perl while (<>) { my $h='H_E_A_D_I_N_G'; s/^====(.*)====$/$h$h$h$1$h$h$h/; s/^===(.*)===$/$h$h$h$h$1$h$h$h$h/; s/^==(.*)==$/$h$h$h$h$h$1$h$h$h$h$h/; s/^=(.*)=$/$h$h$h$h$h$h$1$h$h$h$h$h$h/; s/$h/=/g; if (/\[\[code[^\]]*\]\]/) { if ($incode) { s/\[\[code\]\]/<\/code>/; $incode=0; } else { s/\[\[code\]\]/<code>/; s/\[\[code( format=\"([^\"]*)\")?\]\]/<c… text/html 2010-10-04T10:35:29+00:00 http://www.rosegardenmusic.com/wiki/dev:working_with_multiple_installed_build_versions?rev=1286188529&do=diff Lifted straight out of an old post on the devel list: running multiple Rosegarden builds: msg#00002 Subject: running multiple Rosegarden builds List-id: <rosegarden-devel.lists.sourceforge.net> I know that the subject of how to install and run different builds of Rosegarden at once comes up occasionally. It's not hard to do; here's what I do. Now that I actually have more than about ten gig of disk space in my development machine, I'm finally keeping more than one Rosegarden source tree ac…