lilypond-user
[Top][All Lists]
Advanced

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

Re: maintaining advanced power-user Scheme functions


From: Phil Holmes
Subject: Re: maintaining advanced power-user Scheme functions
Date: Mon, 19 Aug 2013 09:15:54 +0100

----- Original Message ----- From: "Janek Warchoł" <address@hidden>
To: "Thomas Morley" <address@hidden>
Cc: "lilypond-user" <address@hidden>; "Phil Hézaine" <address@hidden>; "David Nalesnik" <address@hidden>; "LilyPond Developmet Team" <address@hidden>
Sent: Sunday, August 18, 2013 9:46 PM
Subject: Re: maintaining advanced power-user Scheme functions


After some thinking, i came to the conclusion that LSR should be redesigned.
Fristly, it should be a git repository, to make collaboration easy -
when something's a git repository, i have a habit of contributing
stuff there on every opportunity, because even if i do something wrong
i can undo this.

I'd guess you're in a minority of about 1% of users who would prefer using git to using a web interface. The current web interface allows you to copy-and-paste code directly in, or alternatively to type it directly in. Both are simple and quick. To use git propoerly requires installing a new program and learning how to use it. Remember yesterday when you recommended a whole book about how it's used? If that doesn't put off casual contributors, nothing will. I started work on LilyPond by adding regtests to the LSR. If git had been required, I wouldn't have done so.

Secondly, i think that it shouldn't depend on any particular lilypond
version - in fact, it shouldn't actually run any lilypond in my
opinion.  I believe that LSR should hold both snippets' code and their
output, with lilypond version clearly stated, and thus allow to post
snippets for any lilypond version.  It would just be a collection of
snippets.

The benefit of it running LilyPond is that it shows the result of the code on the fly - no need to create and upload images. This is another significant benefit.

I could elaborate on this topic, but as i don't have time to actually
do something about it it probably wouln't make sense (unless someone
wanted to lead such a change - then i would gladly help).

best,
Janek

It doesn't need much changing - the main problem is maintaining the web site.


--
Phil Holmes



reply via email to

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