Re: Web: Download: Add introductory text (issue 40510046)
On Mon, Dec 16, 2013 at 01:50:53PM -0500, Carl Peterson wrote: (2) utilizing back-end scripting (PHP, etc.) to custom-serve the content based on the http header. We're using a donated web-server, and don't have root access. When (not if) PHP has another security hole, I don't think we want us to be responsible for somebody else's server getting hosed. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Download: Add introductory text (issue 40510046)
On Mon, Dec 16, 2013 at 01:27:05PM +0100, David Kastrup wrote:
Maybe interactive is a useful term? Like
LilyPond is not an interactive program: its sole task is translating
a textual description of music into typeset music. For creating that
textual description, an editor is required.
While any general-purpose text editor can be used for this task, some
applications are specifically tailored to working with LilyPond.
Yes, this is getting verbose again, but it's likely hard to whittle it
down significantly. At any rate, it might be a starting point regarding
the concepts and information we need to convey.
Three sentences is sufficently succinct, IMO. I have no problem
with a patch that changed the download warning macro into this.
(although the above would need to be reworded slightly to
accommodate the @refs{})
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Download: Add introductory text (issue 40510046)
Am 18.12.2013 11:33, schrieb Graham Percival:
On Mon, Dec 16, 2013 at 01:27:05PM +0100, David Kastrup wrote:
Maybe interactive is a useful term? Like
LilyPond is not an interactive program: its sole task is translating
a textual description of music into typeset music. For creating that
textual description, an editor is required.
While any general-purpose text editor can be used for this task, some
applications are specifically tailored to working with LilyPond.
Yes, this is getting verbose again, but it's likely hard to whittle it
down significantly. At any rate, it might be a starting point regarding
the concepts and information we need to convey.
Three sentences is sufficently succinct, IMO. I have no problem
with a patch that changed the download warning macro into this.
(although the above would need to be reworded slightly to
accommodate the @refs{})
- Graham
I suggest to wait with this too until it is clear which pages are
finally there to @ref to
Urs
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Download: Add introductory text (issue 40510046)
On Wed, Dec 18, 2013 at 5:30 AM, Graham Percival gra...@percival-music.ca wrote: On Mon, Dec 16, 2013 at 01:50:53PM -0500, Carl Peterson wrote: (2) utilizing back-end scripting (PHP, etc.) to custom-serve the content based on the http header. We're using a donated web-server, and don't have root access. When (not if) PHP has another security hole, I don't think we want us to be responsible for somebody else's server getting hosed. Indeed, I meant this paragraph to indicate two generally undesirable options for serving the content with the detected operating system info on top and all the other information rearranged on the same page, not as this is what we should do. Carl P. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 3720: Built-in templates for SATB vocal scores (issue 41990043)
Got a free moment.. 2013/12/15 Carl Peterson carlopeter...@gmail.com: I think I share in what I get to be the general sense of many of the comments that have been made thus far. There is a tradeoff between ease of default use and the customizability. To use a bad and probably over-generalized analogy, we're going from Linux (where you pretty much have to do it yourself, but you can make it do pretty much anything you want) to Mac (where everything is easy IF you are willing to work within the predefined templates, and anything else is almost impossible). We need something in between. I don't know that this is the route to go. If our goal is to get people using LP, I don't think that what we need is a function that hides basic structures from the users, where if they want to go beyond this, they have to move from two include commands to a whole new structure. I think what we need is a stripped-down choral/SATB layout that uses minimal overrides and extra code so that new users can copy-and-paste and start experimenting with. I believe we need to add an abstraction layer that would make it conceptually simpler to write \score blocks. Please take a look at https://github.com/openlilylib/snippets/tree/master/templates/predefined-instruments I believe that this is exactly what LilyPond needs to allow beginner users easily create score structures. Notice how much it shortens the \score definition. I don't quite understand why nobody seems interested in this... Janek PS this is not to say that i don't like Trevor's templates! I believe they are a useful addition. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Simplified version of Trevor Daniels' SATB framework. (issue 38720045)
This looks really good now. I've tried
out pretty well all the combinations and
I have only nitpicking comments to make!
One suggestion: what do you think about
making LyricsOne a synonym for Lyrics?
@Devon
How to proceed? The documentation in my
patch will need amending to correspond with
this improved template - I'm happy to do that
if you would like to guide this template
through review and into LP. Alternatively
I could adopt this template (with appropriate
credits to you) and incorporate it as a
replacement template together with doc changes
in my patch. Whichever you prefer.
Many thanks for turning my simple approach
into a properly engineered solution.
Trevor
https://codereview.appspot.com/38720045/diff/20001/ly/satb.ly
File ly/satb.ly (right):
https://codereview.appspot.com/38720045/diff/20001/ly/satb.ly#newcode15
ly/satb.ly:15: Tenor and bass (optionally on one staff)
Bass
https://codereview.appspot.com/38720045/diff/20001/ly/satb.ly#newcode37
ly/satb.ly:37: etc
Perhaps more explicitly:
etc - ...
VerseNine = \lyricmode { ... }
https://codereview.appspot.com/38720045/diff/20001/ly/satb.ly#newcode42
ly/satb.ly:42: PianoRHMusic = \relative { ... }
Follow with
PianoDynamics = { ... }
https://codereview.appspot.com/38720045/diff/20001/ly/satb.ly#newcode47
ly/satb.ly:47: All of the definitions are optional. Stavef with no music
will be
Staves
https://codereview.appspot.com/38720045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Simplified version of Trevor Daniels' SATB framework. (issue 38720045)
I'm not sure about using the default paper margins. The printed output goes very close to the left margin and the bottom of the bass staff is cut off on some pages. Either LP's defaults should be changed or we include the values I suggested originally in my templates in https://codereview.appspot.com/41990043/ . On balance I'd prefer to change them in the template, on the grounds that they are tailored for SATB layouts whereas the LP defaults may be more suited to other forms of music. Trevor https://codereview.appspot.com/38720045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Simplified version of Trevor Daniels' SATB framework. (issue 38720045)
On Wed, Dec 18, 2013 at 5:34 PM, tdanielsmu...@googlemail.com wrote: I'm not sure about using the default paper margins. The printed output goes very close to the left margin and the bottom of the bass staff is cut off on some pages. Either LP's defaults should be changed or we include the values I suggested originally in my templates in https://codereview.appspot.com/41990043/ . On balance I'd prefer to change them in the template, on the grounds that they are tailored for SATB layouts whereas the LP defaults may be more suited to other forms of music. I'm not sure I agree. I think for maximum utility, the template should define as little as possible regarding the physical dimensions of the page and margin, so that the user can use whatever style they want. For instance, I use a 1/4 inch margin on a half-letter format normally, but a 3/4 inch margin or so on a full letter size page. If the point is to simplify vocal scores, do the minimum required to produce the vocal score and leave the rest alone. Carl P. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Simplified version of Trevor Daniels' SATB framework. (issue 38720045)
Carl Peterson wrote Wednesday, December 18, 2013 10:54 PM I'm not sure I agree. I think for maximum utility, the template should define as little as possible regarding the physical dimensions of the page and margin, so that the user can use whatever style they want. But if the user is going to define his/her own \paper block the defaults will be overridden anyway - having them would do no harm nor cause more work for them. For instance, I use a 1/4 inch margin on a half-letter format normally, but a 3/4 inch margin or so on a full letter size page. If the point is to simplify vocal scores, do the minimum required to produce the vocal score and leave the rest alone. Well, the point is rather to enable the user to do the minimum required to produce a vocal score. LP already has an A4 default output, so setting margins by default to suit that, rather than _requiring_ a user to learn about \paper would definitely help newcomers. (The NR section on \paper is pretty daunting for a newcomer! And it's not even mentioned in the LM.) Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
