lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] Issue 3705 in lilypond: Patch: Commits (in reverse chron


From: lilypond
Subject: [Lilypond-auto] Issue 3705 in lilypond: Patch: Commits (in reverse chronological order):
Date: Fri, 06 Dec 2013 19:09:27 +0000

Status: Started
Owner: address@hidden
Labels: Type-Enhancement Patch-new

New issue 3705 by address@hidden: Patch: Commits (in reverse chronological order):
http://code.google.com/p/lilypond/issues/detail?id=3705

Commits (in reverse chronological order):

font: abstract stuff away, unify, format

* move common elements to separate input files,
* move brace-drawing procedure to separate file,
* rename feta-alphabet to feta-alphabet-generic
  to conform to the convention,
* rename feta-generic to feta-other-generic
  (because this file is not for the whole font,
  but just some glyphs that aren't in their own
  subfonts); similarly parmesan-generic,
* remove feta-test-generic.mf and other testing
  files that were just polluting the code,
* put testing code in one place,
* remove spurious filename comments,
* unify formatting and indentation.


font: clean up staffline-display in testing mode

Previous testing code was a mix of hideous copy&paste with
non-obvious passing glyph outlines around, which attempted
to produce additional glyphs in testing mode, so that there
would be both on-staffline and on-staffspace variations.

That code was completely unreadable and unmaintainable.

Instead i've introduced a global variable that determines
how the stafflines will be printed relative to the glyphs.
To see alternative configuration, just change that value.


font: rename draw_staff to draw_staff_if_debugging

Previous name was confusing: the stafflines are actually
not drawn unless 'test' is set to non-zero value.


feta accidentals: split into several files

http://codereview.appspot.com/38530043

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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