[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: improving LilyPond useability
From: |
Renato |
Subject: |
Re: improving LilyPond useability |
Date: |
Mon, 2 Dec 2013 17:49:42 +0100 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 2 Dec 2013 15:06:13 -0000
"Phil Burfitt" <address@hidden> wrote:
> So often people after buying a new shiny thingy, open the box, plug
> it in, and only after numerous failed attempts to get it to work,
> decide to read the manual
Well they'd hit the same wall with Latex, it doesn't "do" anything by
default, yet still it's the undisputed standard for scientific
typesetting. I'd say that lilypond is more or less as good as Latex
(which is not perfect, it *is* rather messy at times), the great
difference is there is much more interest in Latex so there is
excellent documentation and a lot of community activity.
Now, one could make the argument that the crowd Lilypond has to appeal
to (musicians) is in general far less accostumed to command line
programs rather then Latex's crowd (scientist); I'd argue back that
Lilypond doesn't really "have to appeal" to someone who doesn't see the
advantages of WYSIWYM vs. WYSIWYG and doesn't take the time to learn
it. I mean, lilypond is text-editor + command-line by design, you don't
really get around these programs without reading docs (and you
shouldn't try to make it easy).
So I think "improving lilypond's usability" should boil down to:
1) better language functionality (personally I haven't used lilypond
all that much so I can't really point out any show-stopper there)
2) better docs
and nothing else
my 2 cents,
cheers
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJSnLowAAoJEBz6xFdttjrf7EMIAIEuDvT36WaQ8MwA60TqinFK
rIngCy9PfVVqVYKS/YgiP3DkV5/GWapEx36HKJkJmZrmYL46Xfs4i0G1Rw+3CqIi
3zOqA8kg4N0iQvrfbuzf7f3GQENN26lFdLVT2RCtm8qMnA+GT9JfzCavXTZPNdvQ
8/PXoAaHE1AAZFcFmTI63+WMHfGGKexLCvlKbLNRCRUojJAKNAjtHg+uXIbDkuRM
dzY6oWKPBdkPGn5C2Bvn60MfuolC7/k4EtvvGFNPqeVETYHY+Vzl5LMe86zVuBKX
OlH0p9AHxeav21uRPLvkZdNDRjZYk5CyEFz2jwGstax9Dg2nir+waMJzDUtGcOo=
=BMq3
-----END PGP SIGNATURE-----
- Re: improving LilyPond useability, (continued)
- Re: improving LilyPond useability, Noeck, 2013/12/03
- Re: improving LilyPond useability, Jacques Menu, 2013/12/04
- Re: improving LilyPond useability, Janek Warchoł, 2013/12/05
- Re: improving LilyPond useability, Urs Liska, 2013/12/05
- Re: improving LilyPond useability, David Kastrup, 2013/12/05
- Re: improving LilyPond useability, Janek Warchoł, 2013/12/05
- Re: improving LilyPond useability, Colin Campbell, 2013/12/05
- Re: improving LilyPond useability, Noeck, 2013/12/05
- Re: improving LilyPond useability, Urs Liska, 2013/12/05
- Re: improving LilyPond useability, Janek Warchoł, 2013/12/05
Re: improving LilyPond useability,
Renato <=
Re: improving LilyPond useability, Renato, 2013/12/02
Re: improving LilyPond useability, David Kastrup, 2013/12/03
Re: improving LilyPond useability, renato, 2013/12/03
Re: improving LilyPond useability, David Kastrup, 2013/12/03
Re: improving LilyPond useability, Phil Burfitt, 2013/12/03
RE: improving LilyPond useability, Daniel Rosen, 2013/12/02