Menu

#817 Enhancement: new syntax for more flexible cresc/dim spanners

Verified
nobody
Enhancement
2010-08-17
2009-07-17
Anonymous
No

Originally created by: *anonymous

Originally created by: v.villenave
Originally owned by: reinhold...@gmail.com

Currently, dynamics have to be hardcoded to be attached _after_ the note
and not _before_. This implies that modifying or defining new dynamics
always requires some sort of a hack (for instance by using tweaks or
music-functions).

Neil and Reinhold have begun implementing a new framework for the
New_dynamic_engraver.

Please read the discussion on
http://lists.gnu.org/archive/html/lilypond-devel/2009-03/msg00007.html
continued on
http://lists.gnu.org/archive/html/lilypond-devel/2009-04/msg00124.html

the patch set is at Rietveld: http://codereview.appspot.com/39047/show
and comments are to be found on
http://lists.gnu.org/archive/html/lilypond-devel/2009-04/msg00136.html
continued on
http://lists.gnu.org/archive/html/lilypond-devel/2009-05/msg00015.html

Discussion

  • Google Importer

    Google Importer - 2009-08-21

    Originally posted by: reinhold...@gmail.com

    New patch implementing the backend (i.e. processing the properties):
    http://codereview.appspot.com/109072

    The definition of \cresc etc. is still unchanged

     
  • Google Importer

    Google Importer - 2009-10-10

    Originally posted by: reinhold...@gmail.com

    The patch for the backend is commited (snippet has been added showing how to define
    one's own commands or override the default \cresc, \dim, etc.).

     
  • Google Importer

    Google Importer - 2009-10-10

    Originally posted by: v.villenave

    Then this is only waiting for a major version bump to be fully taken advantage of,
    since it would imply a major syntax change.

    Labels: Syntax

     
  • Google Importer

    Google Importer - 2010-08-13

    Originally posted by: pnorcks@gmail.com

    I'm a little confused about the status of this issue...

    Reinhold committed his patch set from Comment 1, so should we close this issue?

    It's not clear to me whether there is further work left to do.  If so, we should probably open a new issue.

    Owner: reinhold.kainhofer
    Cc: -reinhold.kainhofer -n.puttock -pnorcks

     
  • Google Importer

    Google Importer - 2010-08-14

    Originally posted by: reinhold...@gmail.com

    The \cresc etc. commands have also been pushed, together with convert-ly rules. So, I would regard this issue to be fixed.

    What is missing is proper documentation (probably also adding the regtest cases as snippets, since they show some nice features, like the \mycresc function to allow arbitrary text...).

    Cheers,
    Reinhold

     
  • Google Importer

    Google Importer - 2010-08-14

    Originally posted by: percival.music.ca@gmail.com

    James Lowe is currently working on documentation for:
      dynamics-context-textspan.ly
      dynamics-custom-text-spanner-postfix.ly
      dynamics-hairpin-length.ly
      dynamics-text-spanner-postfix.ly
    as part of 989.  However, I'm not certain if these are absolutely necessary for 989 (after splitting off the post-2.13 stuff into 1217).  Also, I'm not certain if they should be snippets or part of the NR; I believe that he's working on getting them into the NR.

    If you could add a bit more information, or at least reassurance, to:
      http://wiki.lilynet.net/index.php/Regtests
    that would be nice.

     
  • Google Importer

    Google Importer - 2010-08-17

    Originally posted by: v.villenave

    Anyway, this issue can be closed indeed.

    Labels: fixed_2_13_4
    Status: Verified