Re: Issue 1364 in lilypond: Enhancement: Dynamics should be printed *above* vocal staves

[lilypond]

Comment #4 on issue 1364 by v.villenave: Enhancement: Dynamics should be  
printed *above* vocal staves
http://code.google.com/p/lilypond/issues/detail?id=1364

I'm not sure I agree.  The whole point of LilyPond has always been to  
provide the user with a nearly-ideal output out-of-the-box.  Predefined  
tweaks are indeed quite easy to enter, however these are but workarounds:  
an ideal output should require no manual tweak whatsoever.

Wilbert: you may be used to workarounds, and most of us probably are (I  
aren't: I've published a 400-pages opera where all dynamics were at their  
default position, between the staves and the lyrics!).  But please think  
of "future generations" of users: a few years ago, every LilyPond user was  
required to use manual overrides to avoid vertical collisions (as explained  
in NR 4.4.4); nowadays these collisions are automatically handled and  
nobody would complain about that (in fact, new users don't even suspect how  
imperfect the default output used to look!).

I think it all comes down to how complicated this would be to implement.   
If it *is* very complicated, adds quite a lot of calculations and  
eventually makes LilyPond more bloated, then fine, let's just stick with  
\dynamicsUp.  If (as I suspect, since the code for alignAboveContext  
already exists) it's simple enough, then we should at least consider it.