From: Heikki J. J. <hj...@gm...> - 2007-07-19 23:01:01
Attachments:
rg_hjj_20070720.diff
|
Hi! I again tried to add command "Preview with LilyPond" into NotationView. Again, I am stuck in the fact that the menu item does not show up. What is wrong in the attached patch? -- Heikki |
From: Chris C. <ca...@al...> - 2007-07-20 09:24:34
|
On Friday 20 July 2007 00:00, Heikki Johannes Junes wrote: > I again tried to add command "Preview with LilyPond" into > NotationView. Again, I am stuck in the fact that the menu item does > not show up. What is wrong in the attached patch? It looks as simple as the <Action> XML element in notation.rc being outside the <Menu> element that's supposed to contain it. I created a branch called lilypond_everywhere to test this on (I don't know about you and others here, but I have no problem having any number of branches "on the go" at the same time), and have committed your patch to it, with the action element moved to what appears to be the right place. It does seem to work for me. Incidentally, the progress reporting in lilypondview doesn't seem to be working for me -- it stays at 0% until Lilypond is completely finished. It's not immediately obvious to me what the problem is -- perhaps I'll have a look into it. Chris |
From: Heikki J. J. <hj...@gm...> - 2007-07-20 22:24:44
|
2007/7/20, Chris Cannam <ca...@al...>: > On Friday 20 July 2007 00:00, Heikki Johannes Junes wrote: > > I again tried to add command "Preview with LilyPond" into > > NotationView. Again, I am stuck in the fact that the menu item does > > not show up. What is wrong in the attached patch? > > It looks as simple as the <Action> XML element in notation.rc being outside > the <Menu> element that's supposed to contain it. You're right. I have tried this also... > I created a branch called lilypond_everywhere to test this on (I don't know > about you and others here, but I have no problem having any number of > branches "on the go" at the same time), and have committed your patch to it, > with the action element moved to what appears to be the right place. It does > seem to work for me. ...until it worked also for me. I am not sure whether it was - "make uninstall", or - "sudo rm -rf `locate -i rosegarden | grep -v workspace`", or - "make clean" which helped to have the updated menus correctly. -- Heikki |
From: Chris C. <ca...@al...> - 2007-07-20 12:53:38
|
On Friday 20 July 2007 10:25, Chris Cannam wrote: > Incidentally, the progress reporting in lilypondview doesn't seem to be > working for me -- it stays at 0% until Lilypond is completely finished. > It's not immediately obvious to me what the problem is -- perhaps I'll have > a look into it. I've committed what I think is a fix, to that branch (lilypond_everywhere). I've also made a couple of other changes, including picking up the actual installed Lilypond version for the default language version in Rosegarden's Lilypond export dialog. Please test & report (& fix/unfix as appropriate)! Chris |
From: Heikki J. J. <hj...@gm...> - 2007-07-22 21:18:56
|
2007/7/20, Chris Cannam <ca...@al...>: > On Friday 20 July 2007 10:25, Chris Cannam wrote: > > Incidentally, the progress reporting in lilypondview doesn't seem to be > > working for me -- it stays at 0% until Lilypond is completely finished. > > It's not immediately obvious to me what the problem is -- perhaps I'll have > > a look into it. > > I've committed what I think is a fix, to that branch (lilypond_everywhere). > > I've also made a couple of other changes, including picking up the actual > installed Lilypond version for the default language version in Rosegarden's > Lilypond export dialog. Please test & report (& fix/unfix as appropriate)! > > Chris Seems like the default LilyPond version 2.6 is changed to the actual present version 2.10, so, picking up the actual installed Lilypond version indeed works. I have finished working with branch "lilypond_everywhere" and it is time to merge the changes to trunk. Now there is "Preview with LilyPond". Should there also be "Export to LilyPond" ? What happens to a branch after it has been merged to trunk and there is no more use for the branch ? Will such a branch be cut off and thrown away ? -- Heikki |
From: Chris C. <ca...@al...> - 2007-07-20 16:08:56
|
btw, a Lilypond question: Why does it always seem to spread out the staffs so as to take the full height of the page, even if it means leaving a large gap in the middle? Example: Load stormy-riders.rg. Say File -> Preview with Lilypond; A4 paper; font size 13 (so that two whole lines fit on the page); OK. The first page looks just about OK, but the second and subsequent pages have 11 small staffs bunched up at the top, 11 staffs bunched up right at the bottom, with hardly any margin below them -- and about three inches of blank space in the middle. It doesn't look right at all. This is with Lilypond 2.10.something. Chris |
From: Heikki J. J. <hj...@gm...> - 2007-07-20 23:31:58
|
2007/7/20, Chris Cannam <ca...@al...>: > > btw, a Lilypond question: Why does it always seem to spread out the staffs so > as to take the full height of the page, even if it means leaving a large gap > in the middle? > > Example: Load stormy-riders.rg. Say File -> Preview with Lilypond; A4 paper; > font size 13 (so that two whole lines fit on the page); OK. The first page > looks just about OK, but the second and subsequent pages have 11 small staffs > bunched up at the top, 11 staffs bunched up right at the bottom, with hardly > any margin below them -- and about three inches of blank space in the middle. > It doesn't look right at all. This is with Lilypond 2.10.something. > > > Chris > The following helps: see what is written about ragged-bottom in http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Page-formatting.html and add \paper { ragged-bottom=##t } after \header-block and before \score -block. With the default "ragged-bottom=##f" the pages becomes "vertically justified". Maybe vertical justifying of systems in a page is as beautiful as horizontal justifying of staffs on lines. Who knows? Changing this setting could be added as an advanced option in the export dialog. I would create a tab named Advanced options for it and current Extra options. There would then be two tabs: Basic options and Advanced options. I have earlier couple times been trying to learn how to introduce tabs in LilyPond export dialog---it is not as easy as adding just a widgets, which is the reason why I have been pending this improvement. -- Heikki |