Re: [Denemo-devel] Lyrics

[Richard Shann]

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
>       * 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.
> 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