denemo-devel
[Top][All Lists]
Advanced

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

Re: [Denemo-devel] Lyrics


From: Nils Gey
Subject: Re: [Denemo-devel] Lyrics
Date: Thu, 25 Jun 2009 01:29:46 +0200

I really really like the new system. This is such a huge improvement. 
Multiline-box, a frame instead of a floating window: great!
I said this very often and again: This frame should be always there (hide on 
click a button maybe) and should also be the place where all logs and errors 
should be written to, including the ones from the console. Maybe tabbed, too. 
Lilypond output, errors and warnings and of course new tabs on the fly for 
functions like the new lyrics-systems!

Great work!

Bugs:

"Fi -- nal" is rendered on two notes in lilypond, which is correct, but on 
three in Denemo. " -- ", including leading and tailing whitespace, is not its 
own syllabe but the connector in lilypond.  (but " - " is its own syllabe.)

Vers one is shown twice/n-times where n is the number of verses. In 
lilypond-view only the first verse is shown multiple times.

If you have verse 1, 2 and 3 and delete number two the remaining ones in the 
tab are still 1 and 3 and not 1 and 2. Don't know if this has any influence on 
the lilypond output. If you save, quit and reload its verse 1 and 2 then.  So 
this should not be a problem.

Nils

On Wed, 24 Jun 2009 21:00:21 +0100
Richard Shann <address@hidden> wrote:

> On Wed, 2009-06-24 at 20:28 +0100, Richard Shann wrote:
> > On Wed, 2009-06-24 at 16:38 +0100, Richard Shann wrote:
> > > I have now checked in a major upgrade to the lyrics. All of the old
> > > lyrics handling has gone, replaced by text editors for each verse on
> > > each staff.
> > > The rationale should be obvious: lyrics are much easier to type in, &
> > > adjust the syllabification of, by inserting the LilyPond characters (_ -
> > > space etc) than typing one syllable at a time into a dialog box and
> > > checking check boxes.
> > > 
> > > There are some things missing.
> > >       * No printing of the multiple verses.
> > done
> > >       * No delete a verse
> done
> > >       * Slurs are not respected
> > done
> > >       * The tabs for verses are labelled as Page nnn
> > done
> > 
> > Richard
> > 
> > >       * Empty verses won't print
> > >       * Short verses are displayed with repeated last word.
> fixed
> 
> > > These should all be easy enough to fix. I just got nervous sitting on so
> > > much unpublished code.
> > > There may be other things that need fixing, as I don't know much about
> > > lyrics. Please add to the list if need be.
> > > 
> > > Richard
> > > 
> > > 
> > > 
> > > On Tue, 2009-06-23 at 20:03 +0100, Richard Shann wrote:
> > > > On Tue, 2009-06-23 at 12:17 +0100, Richard Shann wrote:
> > > > > On Tue, 2009-06-23 at 08:20 +0100, Richard Shann wrote:
> > > > > > I propose to replace the measures field of the DenemoStaff with a
> > > > > > field
> > > > > > called bars. This would point to a GList of DenemoMeasure which 
> > > > > > would
> > > > > > have a field called measure containing a list of DenemoObject.
> > > > > > Then all the code referring to the staff->measures will need to 
> > > > > > refer
> > > > > > to
> > > > > > ((DenemoMeasure*)staff->bars->data)->measure->data and all the
> > > > > > creation
> > > > > > and destruction of the measures field will need to be re-written to
> > > > > > create/destroy a DenemoMeasure.
> > > > > 
> > > > > The lilypond parser presents a challenge:
> > > > Actually, the problem is worse than that: the assumption that the
> > > > measures are a list of lists is implicit almost everywhere in the code -
> > > > it would not be enough just to identify where the measures field is used
> > > > as pointers to it are passed around & the same assumption made in the
> > > > receiving functions.
> > > > So I will work around the problem,
> > > > 
> > > > Richard
> > > > 
> > > > 
> > > > 
> > > > >  I propose to create a field
> > > > > staff->lilymeasures to take over the role of the current 
> > > > > staff->measures
> > > > > field for the lilypond input phase, moving the data into the 
> > > > > staff->bars
> > > > > field before the parser returns.
> > > > > 
> > > > > Richard
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Denemo-devel mailing list
> > > > > address@hidden
> > > > > http://lists.gnu.org/mailman/listinfo/denemo-devel
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Denemo-devel mailing list
> > > > address@hidden
> > > > http://lists.gnu.org/mailman/listinfo/denemo-devel
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Denemo-devel mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/denemo-devel
> > 
> > 
> > 
> > _______________________________________________
> > Denemo-devel mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/denemo-devel
> 
> 
> 
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel
> 


-- 
Nils Gey <address@hidden>




reply via email to

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