[Rosegarden-devel] Fwd: Re: Trying to add Preview with LilyPond into NotationView (again)

[Chris C. <ca...@al...>]

[resending bounced email from last week]

----------  Forwarded Message  ----------

Subject: Re: [Rosegarden-devel] Trying to add Preview with LilyPond into 
NotationView (again)
Date: Wednesday 25 July 2007 15:50
From: Chris Cannam <ca...@al...>
To: "Heikki Johannes Junes" <hj...@gm...>
Cc: ros...@li...

On Sunday 22 July 2007 22:18, Heikki Johannes Junes wrote:
> 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
> ?

Normally I would move it to the obsolete/ subdirectory and leave it there --
unless it had very little of interest in it, in which case I'd delete it.

However, to address both questions in your email at once, it may be worth
keeping this branch around for further work.  For example, making Lilypond
the default printing mode.  Perhaps the Lilypond options dialog could become
a general printing options dialog, with the very first option in it being
whether to use Lilypond or built-in printing -- assuming we didn't decide to
remove the built-in printing capability completely.  My feeling, as I use the
Lilypond output a bit more, is that it probably should be the default but
there probably are some cases where built-in printing would be useful too.

If we did that, then I guess the notation view would probably want Print
(defaulting to Lilypond) and Print Preview (defaulting via Lilypond), but not
Export to Lilypond which would continue to be a document-level File
operation.


Chris

-------------------------------------------------------