I think making it version independent might be easier to wish for than to
provide!
I believe the source code is available if you'd like to try getting it running
on alternative infrastructure and updating it:
http://lsr.dsi.unimi.it/download/
--
Phil Holmes
----- Original Message -----
From: Urs Liska
To: Janek Warchoł ; Phil Holmes
Cc: LilyPond Developmet Team ; Thomas Morley ; David Nalesnik ; lilypond-user
Sent: Monday, August 19, 2013 11:21 AM
Subject: Re: maintaining advanced power-user Scheme functions
One thing I'd definitely support about this is making LSR somewhat version
independent to allow one to have snippets requiring new lily versions.
Maybe providing several lily versions (not necessarily _all_ of course) and
use an appropriate one to compile the snippets. This would also allow us to
keep 'old' snippets without updating all to current lily syntax before being
able to upgrade the whole LSR.
Maybe something like running convert-ly over all snippets when a new stable
release comes out and leave snippets that can't be upgraded automatically for
older versions?
Urs
PS: I'd also second the idea of hosting lilypond on a more accessible server
(if that doesn't imply complicated side-effects). It is so easy to create a
fork and open a pull request, I'm sure such a step would increase the number of
contributions by people who can't or won't go through some undefined and
possibly complex process of 'becoming a developer'
"Janek Warchoł" <[email protected]> schrieb:
2013/8/19 Phil Holmes <[email protected]>:----- Original Message ----- From:
"Janek Warchoł"After some thinking, i came to the conclusion that LSR should
beredesigned.Fristly, it should be a git repository, to make collaboration easy
-when something's a git repository, i have a habit of contributingstuff there
on every opportunity, because even if i do something wrongi can undo this.I'd
guess you're in a minority of about 1% of users who would prefer usinggit to
using a web interface. The current web interface allows you tocopy-and-paste
code directly in, or alternatively
to type it directly in.Both are simple and quick. To use git propoerly
requires installing a newprogram and learning how to use it. Remember
yesterday when you recommendeda whole book about how it's used? If that
doesn't put off casualcontributors, nothing will. I started work on LilyPond
by adding regteststo the LSR. If git had been required, I wouldn't have done
so.A valid concern, but i have a counterargument: there is a webinterface for
git that allows you to copy-and-paste code directly in,or alternatively to type
it directly in. Both are quite simple andquick. This doesn't require
installing a new program and learning howto use it.It's github.I've just
checked and made a couple commits using that web interface.Plain and simple,
*with* all the advantages of git underneath. Ofcourse i may be biased, so i
invite you to check this with me. Ibelieve that i will
be able to explain everything that's needed in5-10 minutes. Would you like to
try?Actually, i believe that it would be good to have lilypond repositoryon
github, so that new contributors would be able to create patcheseasily. They
wouldn't have to install a virtual machine with Lilydev.Found a typo in
documentation? Create a fix and submit it in *2minutes.*Secondly, i think that
it shouldn't depend on any particular lilypondversion - in fact, it shouldn't
actually run any lilypond in myopinion. I believe that LSR should hold both
snippets' code and theiroutput, with lilypond version clearly stated, and thus
allow to postsnippets for any lilypond version. It would just
be a collection ofsnippets.The benefit of it running LilyPond is that it shows
the result of the codeon the fly - no need to create and upload images. This
is anothersignificant benefit.I'm not sure if i understand. Does LSR compile
snippets every time iopen its webpage?Anyway, i'm not saying that LSR shouldn't
be able to run LilyPond,just that it should not require this for operation.I
could elaborate on this topic, but as i don't have time to actuallydo something
about it it probably wouln't make sense (unless someonewanted to lead such a
change - then i would gladly help).It doesn't need much changing - the main
problem is
maintaining the website.What if the things i pointed out make it hard to
maintain?I'd just like to point this out:- with current system, i know that i'm
not going to help with updatingLSR. If i had more time, i'd gladly do that,
but i don't have.However, if it was independent from LilyPond version - i.e.
updatingone snippet means that the update becomes instantly visible,
becauseupdating isn't an all-or-nothing deal - i would gladly update
somesnippets from time to time, if it could be done "via git".- i have some
valuable snippets and templates myself, and i'd like toshare them, but i don't
see how they could fit with current LSRsystem.- i have 79 emails marked
"valuable snippet". Adding them to LSR (theway it works currently) would
require a lot of work, and i don't havetime for this. But if the LSR worked
another way, i could dosomething about it.If you'd
like to discuss this more, i think IRC could be a good idea(it's faster) - i'm
logged
in.best,Janek----------------------------------------------------------------------------lilypond-user
mailing
[email protected]https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
