I sorted out the annoying "Why didn't Rosegarden ask me if I wanted to save before just quitting like that?!" bug today, which was pretty high on my list of must fix problems. (I also added a little * to the title bar to show when the document thinks it has been modified. Why didn't we do that sooner? I remember talking about it ages ago.)
The new project packager finally made it through a complete cycle of stress tests without falling on its face. I haven't heard whether Ilan had similar results, but I sure hope so after all the misery I've experienced trying to keep that pile of crap straight. I think what we're coming down to before we can seriously consider a release are these main areas: 1) The bank editor. Immanuel Litzroth emailed me some while ago talking about how he was going to get down to work on that. I remain hopeful, but I'm starting to get itchy. I can only ignore this for another week or so before it's time to panic. 2) The matrix. There is a lot of stuff not hooked up yet, see http://rosegardenmusic.com/wiki/dev:missing_slots for some clues. The main things I worry about are the status bar, which notation has proven will be rather tricky to get put back into place (having to figure out which bits of what to stuff into which piece of the completely new structure), and getting some kind of next/previous segment functionality in here, which I think is supposed to be Alt+PgUp/PgDwn from notation. (Up/down staff have no meaning here.) 2) Notation. There is a lot of stuff not hooked up yet, as above. The main things I worry about here at this particular moment are again the up/down staff and next/previous segment whatzits I'm really quite dependent on Chris Cannam to sort out and get associated with working shortcuts. Then the status bar, which I will only puzzle out for myself if I really must resort to that. I think these two things will cover a lot of ground once the follow-on effects of clearing these obstacles trickle out. Then of course notation needs to have rulers too, and while we're at it, we need to disable the damn things in all except the default layout mode, and finally kill a bug from 2003 or so. 3) Control Rulers. Chris Fryer has made enormous progress on these, and they are getting to a pretty release-worthy state in the matrix. They need to work in the notation view as well. We really need a "open ruler n" function, because everything to date has just worked on pitch bend. Given some of the false assumptions Chris has had in the past (eg. that these rulers only existed in the matrix), and how long we've gone without this being implemented, I wonder if he understands this necessity. (No stone throwing, I'm just starting to wonder.) I've already put in about 30 hours since Saturday, and if we had three of me we could get this together before Halloween. Since we don't, I think we're screwed on an October alpha unless we just want it to be some kind of technology demo. -- D. Michael McIntyre ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
