Re: GDP question about piano templates dynamics
On 6/29/08, Andrew Hawryluk [EMAIL PROTECTED] wrote: Well, at least that explains what the New_fingering_engraver is! As long as the engraver is under construction, is it easy to make the skyline 'disappear' between dynamic marks so that it behaves more like the figured bass engraver (see image)? Currently the entire row of dynamic marks are shifted vertically to avoid a collision that can't happen. This isn't so much related to the engraver as it is to the way we combine and calculate skylines. This is related to bug 584, and I hope to fix it in the not-too-distant future. Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP question about piano templates dynamics
2008/6/25 Graham Percival [EMAIL PROTECTED]:
Neil,
If you're not busy finishing the markup stuff, could you take a
look at this?
I don't think it's a good idea to implement a PianoDynamics context
until it's working properly; while the centring works fine, there are
problems with the horizontal alignment because the dynamics aren't in
the same voice context as the notes (see Issue 620). In addition, the
New_dynamic_engraver isn't quite ready to be used here, since there
are some callback changes required to prevent warning messages.
BTW, why *aren't* the markup docs finished yet? I mean, a whole
bunch of Font stuff aren't done. All the \bigger \smaller \teeny
etc can use practically the same example;
\markup{ one \command two}
I know it's not exciting work, but that's life doing docs. Just
grab a bottle of wine or bag of candy[1] and get it over with. I
bet you could finish 95% of \markup commands in an hour,
I wish that were the case; got any tips on working faster (without
causing massive breakage)? :)
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP question about piano templates dynamics
I will leave the Piano docs as they are with respect to dynamics and
the templates, at least for now. In the meanwhile, I am looking
forward to the New_dynamic_engraver very much!
Andrew
On Sat, Jun 28, 2008 at 9:02 AM, Neil Puttock [EMAIL PROTECTED] wrote:
2008/6/25 Graham Percival [EMAIL PROTECTED]:
Neil,
If you're not busy finishing the markup stuff, could you take a
look at this?
I don't think it's a good idea to implement a PianoDynamics context
until it's working properly; while the centring works fine, there are
problems with the horizontal alignment because the dynamics aren't in
the same voice context as the notes (see Issue 620). In addition, the
New_dynamic_engraver isn't quite ready to be used here, since there
are some callback changes required to prevent warning messages.
BTW, why *aren't* the markup docs finished yet? I mean, a whole
bunch of Font stuff aren't done. All the \bigger \smaller \teeny
etc can use practically the same example;
\markup{ one \command two}
I know it's not exciting work, but that's life doing docs. Just
grab a bottle of wine or bag of candy[1] and get it over with. I
bet you could finish 95% of \markup commands in an hour,
I wish that were the case; got any tips on working faster (without
causing massive breakage)? :)
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP question about piano templates dynamics
2008/6/28 Neil Puttock [EMAIL PROTECTED]: I wish that were the case; got any tips on working faster (without causing massive breakage)? :) Similarly, I'm looking for tips on how to write sensible docs on hairy stuff such as 1.8 Text :) (I've just seen Nicolas has made my font-size docs nearly obsolete less than an hour ago; I'm both thrilled and desperate.) Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP question about piano templates dynamics
On Sat, 28 Jun 2008 19:43:44 +0200
Valentin Villenave [EMAIL PROTECTED] wrote:
2008/6/28 Neil Puttock [EMAIL PROTECTED]:
I wish that were the case; got any tips on working faster (without
causing massive breakage)? :)
Focus. Let's say that you're working on \underline:
- does this command take 1 argument or more? It's one. So copy
the previous one-argument example:
\markup {
one \\bold two
}
and change the \\bold to \\underline. Boom, example done. Next
command. Assuming that you keep that previous example in your
copy buffer, the entire command can be done in 30 seconds.
- go through the entire list, just taking care of simple stuff.
Don't play with examples. For example, you noticed that the
\box command looks ugly if you don't \override the padding. Don't
fix that stuff yet. Just go through the list making the examples.
- if there's a command with multiple arguments, dump a FIXME
there. And then move on. Don't think about it.
- once you've gone through the list, start compiling the docs and
go get coffee. When you come back, hopefully they'll be done.
skim through the html pages; if you see something ugly (like
\box), *then* go back and fiddle with the example.
This is how you can cover 90% of the docs in an hour. It's dull,
it's repetitive, but it gets stuff done.
Then you do the same thing for multi-argument commands. Now the
.scm file is a mixture of finished and unfinished commands, but
you don't need to search for commands to fill in -- you just
search for FIXME. Here's your basic example:
\markup {
\command {
one
two
}
}
If you can shove a markup command into the above format, do it and
stop thinking about it. If you can't, leave the FIXME alone and
move on to the next one. Again, DON'T THINK ABOUT IT.
- compile docs, get coffee, fix remaining.
At this point there's probably about 10 commands left. They'll
require special attention, though, reading source code, asking on
-devel, whatever. But that's fine... it's a short list. The end
is in sight. You might be able to farm out one or two of these to
other people if it's too hard (this is a general tip, I don't
think it'll apply to you).
Also, I'm much happier, because the docs look pretty complete; I
can see that there's only a few things left. If you fell off the
edge of the Earth, I know that I can finish the remaining commands
myself.
Similarly, I'm looking for tips on how to write sensible docs on hairy
stuff such as 1.8 Text :)
Here, the big question is figuring out what you don't need to
discuss. At the moment, you're thinking about explaining all the
different text alignment commands, because they aren't in the
appendix. Once Neil has added all those examples -- and these
definitely do fall into the trivial multi-arg commands category,
and therefore only take an hour -- I suspect that we'll find that
you don't need to discuss them.
Basically, stop thinking about explaining everything there is to
do about text. Instead, think about explain enough abotu text
so that users can understand the \markup command reference in the
appendix.
Again, this is much easier if you can actually *see* what the
command reference looks like... but if you can't, you just need to
imagine it. That's what I have to do all the time, with the
possibility of snippets, new texi2html output, deciding what to
cover in the LM vs. the NR, etc.
(I've just seen Nicolas has made my font-size docs nearly obsolete
less than an hour ago; I'm both thrilled and desperate.)
If your font-size docs were written properly, it should only take
a few minutes to update them.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP question about piano templates dynamics
Neil,
If you're not busy finishing the markup stuff, could you take a
look at this?
BTW, why *aren't* the markup docs finished yet? I mean, a whole
bunch of Font stuff aren't done. All the \bigger \smaller \teeny
etc can use practically the same example;
\markup{ one \command two}
I know it's not exciting work, but that's life doing docs. Just
grab a bottle of wine or bag of candy[1] and get it over with. I
bet you could finish 95% of \markup commands in an hour, and that
would really help Valentin working on the NR. In this
wine-fueled[2] doc bonanza, skip over anything tricky like
\draw-line.
[1] whatever appeals to you. I'd take the candy, but you may
have more mature taste than me. :)
[2] just make sure it compiles before you commit to git.
Cheers,
- Graham
On Sun, 22 Jun 2008 20:58:47 -0600
Andrew Hawryluk [EMAIL PROTECTED] wrote:
I'm working on the Piano section of the GDP and had a question. The
notation manual includes a template for piano music with centered
dynamics, and there was some discussion a while back about including a
PianoDynamics context in LilyPond itself:
http://lists.gnu.org/archive/html/lilypond-devel/2008-02/msg00072.html
http://code.google.com/p/lilypond/issues/detail?id=581
Is this still being considered for inclusion? If so, I'll modify the
piano docs to match, and I could also test the proposed context
against some typographically challenging piano music to make sure we
haven't missed anything obvious.
Andrew
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP question about piano templates dynamics
2008/6/25 Graham Percival [EMAIL PROTECTED]: Neil, BTW, why *aren't* the markup docs finished yet? Neil has been working on quite a few other (useful) things lately, and has been particularly helpful with LSR stuff I used to (not very well) do before. As for me, I'm really busy these days (preparing my pupil's concert, etc) but I'll be ready to finish both NR1.8 and B6 next week. Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
GDP question about piano templates dynamics
I'm working on the Piano section of the GDP and had a question. The notation manual includes a template for piano music with centered dynamics, and there was some discussion a while back about including a PianoDynamics context in LilyPond itself: http://lists.gnu.org/archive/html/lilypond-devel/2008-02/msg00072.html http://code.google.com/p/lilypond/issues/detail?id=581 Is this still being considered for inclusion? If so, I'll modify the piano docs to match, and I could also test the proposed context against some typographically challenging piano music to make sure we haven't missed anything obvious. Andrew ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
