Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-24 Thread Chris Cannam
On Mon, Aug 24, 2009 at 7:04 PM, D. Michael McIntyre wrote: > There's a process here, with a lot of red tape and hoops involved in getting > something like this through "committee." Well, we like to sit around arguing over the fine points and a lot of possible ideas end up running out of steam bec

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-24 Thread D. Michael McIntyre
On Monday 24 August 2009, Chris Cannam wrote: > Can I just speak up in support of the "branching and vetting" process > for this? I'm feeling a bit defensive, I feel should apologize for putting you on the defensive with all my talk of "rigmarole" and the "barriers of our conservatism" in this.

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-24 Thread Chris Cannam
On Mon, Aug 24, 2009 at 4:32 AM, D. Michael McIntyre wrote: > This really worked out well, I think.  An obscure release note bullet point > well earned all around. Yes, definitely. Thank you for all that work. Can I just speak up in support of the "branching and vetting" process for this? I'm f

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread D. Michael McIntyre
On Sunday 23 August 2009, Julie S wrote: > No, I wasn't wanting you to hurry up. I just feel bad for having to drop the ball. We finally get everybody else talking at the same time for once, and I'm not at the party. Story of my life. > Sorry you don't have weekends off. It's a small matter.

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Julie S
Dear Michael, No, I wasn't wanting you to hurry up. I just wanted you to have the last say so in it, since you did most of the work. Sorry you don't have weekends off. Sincerely, Julie S. -- Let Crystal Repor

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread D. Michael McIntyre
On Sunday 23 August 2009, Julie S wrote: > Other than that, I think this is ready to go. You're still steaming along. It's kind of funny to see all this going on and people sort of waiting on me to hurry up and speak up while I was working. It's as if people expected me to have a weekend off

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread D. Michael McIntyre
On Sunday 23 August 2009, Julie S wrote: > I'm happy to see it merge back into trunk at this point, if you have no > reservations. I see people have been saying merge merge merge all day. As it happened, I completed the merge just before work today, but I ran out of time. I'm sure it's fine,

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Julie S
Dear Brett and Yves. Thanks for the good report. now keyboard duration shortcuts update the toolbar as expected. Let's merge this thing as soon as Michael give the consenting nod. Great work everyone. I think there may be some stuff to clean up concerning the old tool bar stuff, but Michael

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Brett McCoy
I gave the notation_toolbar branch a spin this morning, I like it, much cleaner and less cluttered than the old toolbar. -- Brett "In the rhythm of music a secret is hidden; If I were to divulge it, it would overturn the world."

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Yves Guillemot
Le dimanche 23 août 2009 23:19:12, Julie S a écrit : > You will need to: > make qrc Thanks Julie, It is what I missed. The tool bar works really fine now. Yves -- Let Crystal Reports handle the reporting - Free Cry

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Julie S
Dear Yves, you need the latest svn: Checked out revision 10745 You will need to: make qrc to get the correct toolbars There is only 1 tool bar now. Sincerely, Julie S. -- Let Crystal Reports handle the repor

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Julie S
Dear Chris, Welcome back. Don't bother to recompile. It's working rather well. There is a toolbar update issue I'm working on until I hear from Michael about merging. It is all good stuff and can be merged at any time, just waiting on some final consensus from Michael. But I think we are pr

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Chris Cannam
Cor, lumme... I go offline for a couple of days and the list gets all excitable again. I'd have suggested merging first and worrying about the details later, but if the branch is now working in a superior fashion, it's all good in the end. Is it worth my updating the branch and rebuilding (on thi

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Julie S
Dear Heikki, you wrote: > At least (this is not answer to your question) I would > like "LilyPond" style for the duration shortcuts: > (1) pressing a number makes the the dot always to > disappear > (2) pressing period makes the dot to appear again. > > > E.g. '4' and '.' > > This way you wi

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Heikki Johannes Junes
2009/8/23 Julie S > Dear Michael, > > Glad to hear your system is up and going. I just took the last round of > 9.04 updates and had the same problem as you. A reboot cured it. > > Let's talk shop a bit -- open for all: > > * branches/notation_toolbar: > > I'm happy to see it merge back into tr

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-23 Thread Julie S
Dear Michael, Glad to hear your system is up and going. I just took the last round of 9.04 updates and had the same problem as you. A reboot cured it. Let's talk shop a bit -- open for all: * branches/notation_toolbar: I'm happy to see it merge back into trunk at this point, if you have no

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread D. Michael McIntyre
On Saturday 22 August 2009, Julie S wrote: > Sounds good. I'll jump on it tomorrow afternoon. It turns out to be more complicated than I would have thought. The shortcuts are assigned directly to, eg. "duration_crotchet" and all of these (included the dotted permutations, etc.) are connect()e

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread Julie S
Dear Michael, You wrote: > I'd vote that way. 4 in dot mode is 4. else 4. > > Be my guest to implement that if you have time today. > I'm going to blow > things off for a bit longer while I enjoy a belly full of > beef. > > Your fix works fine, and the Monobar(tm) appears to be > viable now.

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread D. Michael McIntyre
On Saturday 22 August 2009, Julie S wrote: > When in rest mode Triplet Inert Mode is disabled. Is this correct? My > initial thought is that it is incorrect. Some veteran input is required > here. It wasn't disabled before, but probably should have been. I don't have a copy of Classic to com

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread Julie S
Dear Rg Team: More thoughts for mono_toolbar(tm) and related issues: Triplet Insert Mode: When in rest mode Triplet Inert Mode is disabled. Is this correct? My initial thought is that it is incorrect. Some veteran input is required here. Using RG 1.7.3 as a guide, it sho

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread D. Michael McIntyre
On Saturday 22 August 2009, Julie S wrote: > The floating mono_toolbar(tm) still shows, if undocked, still shows itself > after the notation window is closed. So do all the other toolbars. This isn't my bug. Probably has something to do with all the dtors that aren't called when you'd expect th

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread Julie S
Dear RG Team, Please check the notation_toolbar branch now powered by monotoolbar(tm) technology -- patent pending. Just kidding. Michael was inches from having it going, just needed a little push to make it go. Great work Michael. Quite excellent. "One toolbar to rule them all." -- Lord

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread Julie S
Dear Michael, Concerning the monobar: I do apologize. I did not research this idea entirely, and spoke with more authority than I had knowledge to wield. But There really is some hope here. You wrote: > The problem is you can't ->show() and ->hide() the > BUTTONS. Just the whole > TOOLBAR.

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread D. Michael McIntyre
On Saturday 22 August 2009, Julie S wrote: > One avenue to explore is 1 toolbar with all of the buttons on it, and see > if we can hide/un-hide the buttons based on the mode(s) we are in. That > would solve much of this and still allow each button to have "simple" > actions. . OK, we have on

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread Brian Clem
> > I'm taking it pretty badly, I must say. It would have been a lot cleaner > if > everybody just embraced "four corners" because they loved it. Now I feel > like > I really should pursue this further, and yet I'm strongly inclined to throw > it > all away and just tell you all to blow it out yo

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread D. Michael McIntyre
On Saturday 22 August 2009, Julie S wrote: > Well, that is okay, but we still have issues to resolve. If we can't > resolve these, then we probably should keep 4 corners because it works. If you all completely hated the new approach, I could live with that, and just dump it all as a failed exp

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-22 Thread Julie S
Hello RG Team: More thoughts on the latest notation_toolbar rev 10737. I liked the dropping of the shift Y. Good work there. I like the new location of the dot/non-dot and rest/note mode icons. I like the new toggling icons and the gold plus / minus and arrow. That help to indicate action in

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread D. Michael McIntyre
On Friday 21 August 2009, D. Michael McIntyre wrote: > It doesn't behave well, and isn't a very good strategy, but it's > interesting nonetheless. It behaves better now. The "switch to notes" icons on the rests toolbars are greyed out. Probably always were, but now it's visible. Not the same o

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread D. Michael McIntyre
On Friday 21 August 2009, D. Michael McIntyre wrote: > This is an interesting conundrum, and not so easy to solve. > > I'll have to chew on this. I wonder if you can findAction->setPixmap() or > something? I think I have it worked out both ways. A pair of separate named actions that just call

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread D. Michael McIntyre
On Friday 21 August 2009, Chris Cannam wrote: > I worry that the two new buttons to switch the toolbar mode are not > obvious enough for the first time user, though. OK. > I hate to say it, but what this probably calls for is a sort of > Sibelius-style button grid with toggle controls at the to

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Julie S
Dear Michael, More thoughts on the toolbar stuff. Sticky / non-sticky: I think we should leave it like it is (sticky). It appears all of the other mode options, rest / note mode, accidentals, are all sticky. So to do that for the dot would break from our existing interfac

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread D. Michael McIntyre
On Friday 21 August 2009, Julie S wrote: > But without the purple marker everything acted as if it were in chord mode. True, but I'm ignoring that for now as it's irrelevant to the discussion at hand. > I don't care for the y / shift-y aspect to togle note / rest mode. I can agree, though the

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread D. Michael McIntyre
On Friday 21 August 2009, Yves Guillemot wrote: > The use of shift is surprising : why not to use Y and dot alone, as toggles > ? The keyboard shortcuts are Heikki's scheme, not mine. I'd agree with the rest of you on this, I think. > I noticed something strange : if the toolbar has been moved,

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Yves Guillemot
Le vendredi 21 août 2009 04:13:34, D. Michael McIntyre a écrit : > > The new scheme puts notes, dotted notes, rests and dotted rests onto > separate, otherwise identical toolbars, and adds two (hopefully > self-evident) action controls. These two new controls are used to pick > which of the four t

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Julie S
ted toolbar. And I like the auto swap of the rest / note toolbar. Those are the features I suggest we keep. Sorry, I should have referenced the text I was thinking of. Sincerely, Julie S. --- On Fri, 8/21/09, Chris Cannam wrote: > From: Chris Cannam > Subject: Re: [Rosegarden-devel] P

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Chris Cannam
On Fri, Aug 21, 2009 at 2:57 PM, Julie S wrote: > But without the purple marker everything acted as if it were in chord mode.   > There was no easy way to advance to the next location via keyboard and > inserting a note did not advance the marker.  Hmmm...  I guess that purple > thing was good fo

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Julie S
Hello RG team, Well, I have a mixed bag to report. But I am not a heavy notation input user. inserting in general: I like the keyboard input, which was available in a similar fashion in the classic branch. But without the purple marker everything acted as if it were in chord mode. There was

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Chris Cannam
On Fri, Aug 21, 2009 at 3:13 AM, D. Michael McIntyre wrote: > It works fine here.  Very clean and snappy.  Is it an improvement? I think it probably is, at least when you know the keyboard shortcuts. It's very natural to use the . key instead of the mouse to toggle between the toolbars, as a firs

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-21 Thread Chris Cannam
On Fri, Aug 21, 2009 at 6:16 AM, Jani Frilander wrote: > Sounds good, since I almost never personally use dotted notes. Instead I use > a lot of tuplets. > > Could you post a screenshot, because I'm too lazy to recompile? I don't think a screenshot will really help all that much, since the differe

Re: [Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-20 Thread Jani Frilander
Sounds good, since I almost never personally use dotted notes. Instead I use a lot of tuplets. Could you post a screenshot, because I'm too lazy to recompile? -Jani -- Let Crystal Reports handle the reporting - Free Cryst

[Rosegarden-devel] Pivotal Decision: the future of toolbar-based notation entry

2009-08-20 Thread D. Michael McIntyre
Heikki jumped into some refactoring work to clean up the duration-related menus in the notation editor, and related keyboard shortcuts. Now you use Shift+Y to switch to inserting rests, Y to switch to inserting notes, and . to toggle between dots and no dots. This coupled with I II III-based (