[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] A Transformation of how Denemo is perceived.

From: Federico Bruni
Subject: Re: [Denemo-devel] A Transformation of how Denemo is perceived.
Date: Tue, 25 Sep 2012 20:49:31 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.6esrpre) Gecko/20120817 Icedove/10.0.6

Il 25/09/2012 20:18, Richard Shann ha scritto:
Denemo set out to be a GUI front end to LilyPond back in 1999.
With the increasing power of computers I have realised that it no longer
needs to be thought of in that way. It is now possible to think of
Denemo as a program with two windows, one showing the music entry system
the other the final printed score. By running LilyPond in the background
the typeset score can pretty much keep up with typing music in,
especially with single movement works. Even when it does not keep up, by
the time you look across to see how things are progressing it is

Premise: I'm not a Denemo user.
IIUC, a typical Denemo user works with music-entry view and lilypond-input: that would be the "front-end concept".

You propose to have music-entry + printed score (and keep lilypond-input as optional). The good point is that you'll see the nice output _while_ you enter the notes.

So Denemo becomes a program which differs from the conventional wysywyg
programs only in how you edit the music - you can even click on a note
in the typeset version and edit it directly using pc-keyboard or midi
Of course, the option of editing the LilyPond text is still there, but
most users will never do that.

Are you sure?
I think that it's the main feature of Denemo, because I see it as a sort of trade-off for people who don't like text input but still want to have full control over the score output (and you probably have to tweak the lilypond input in this case).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]