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
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.
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
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
Am 16.12.2013 04:31, schrieb Graham Percival:
On Mon, Dec 16, 2013 at 11:29:44AM +0800, Graham Percival wrote:
Urs Liska u...@openlilylib.org writes:
I don't want to imagine what happens if I propose my rewrite of the
Features page (http://www.openlilylib.org/lilyweb/features.html).
A
Carl Peterson carlopeter...@gmail.com writes:
On Dec 16, 2013 12:16 AM, Graham Percival gra...@percival-music.ca
wrote:
On Sun, Dec 15, 2013 at 01:23:51PM +0100, Urs Liska wrote:
It was consensus that new users should actively be encouraged to
download one of the complete environments,
Am 16.12.2013 10:25, schrieb David Kastrup:
Just thinking out loud here...would it be worth looking into tweaking the
.htaccess file to do OS-based redirection on the download page, like many
sites do? That way, if someone requests download.html, they are redirected
to download-win.html if the
Am 15.12.2013 19:48, schrieb David Kastrup:
Urs Liska u...@openlilylib.org writes:
...
Viewed from the very narrow perspective of the actual patch there
isn't much I can argue against People should read Text Input and if
they don't we can't help them/we should help them find that page or
this
Am 16.12.2013 04:29, schrieb Graham Percival:
I don't want to imagine what happens if I propose my rewrite of the
Features page (http://www.openlilylib.org/lilyweb/features.html).
A rewrite of a single page has less impact than changing the
intended flow of a new reader through the website.
Am 16.12.2013 06:15, schrieb Graham Percival:
On Sun, Dec 15, 2013 at 01:23:51PM +0100, Urs Liska wrote:
Am 15.12.2013 06:47, schrieb Graham Percival:
2) they noticed the existing, read the text input page, but were
still confused. Solution: improve the text input page.
I think the only
Am 16.12.2013 07:46, schrieb Paul Morris:
Graham Percival-3 wrote
Maybe another whole page about sample
usage, or something like that?
Maybe this should even be split: One dedicated page explaining the
concept of IDEs, similar to the Text Input page but less elaborate,
and another page that
Am 16.12.2013 07:53, schrieb David Kastrup:
Paul Morris p...@paulwmorris.com writes:
Here's how I would reword the warning to make it as concrete and simple as
possible:
Note: With LilyPond you write and edit music by typing text with your
keyboard, not by dragging notes around with a mouse.
Urs Liska u...@openlilylib.org writes:
Based on my patch:
LilyPond is a **command line application** and does not constitute a
working environment. Apart from LilyPond itself you'll need a suitable
editor. ...
The problem I'm running into is that I see a conflict between being
accurate and
On Mon, Dec 16, 2013 at 4:25 AM, David Kastrup d...@gnu.org wrote:
Carl Peterson carlopeter...@gmail.com writes:
Just thinking out loud here...would it be worth looking into tweaking the
.htaccess file to do OS-based redirection on the download page, like many
sites do? That way, if someone
Am 15.12.2013 06:47, schrieb Graham Percival:
On Sat, Dec 14, 2013 at 09:46:54AM +, lilyli...@googlemail.com wrote:
On 2013/12/14 03:51:33, Graham Percival wrote:
Umm, isn't the whole point of this to be a warning? Why are you
removing the
warning CSS tag?
It's the whole point of
Urs,
On 15/12/13 12:23, Urs Liska wrote:
I'm worried about the opposition even my first modest suggestions raise.
There will be patches with more involved changes to come. And if each
tiny bit is discussed to death from exactly the developer's
perspective that seems part of the problem,
Am 15.12.2013 14:14, schrieb James:
Urs,
On 15/12/13 12:23, Urs Liska wrote:
I'm worried about the opposition even my first modest suggestions raise.
There will be patches with more involved changes to come. And if each
tiny bit is discussed to death from exactly the developer's
perspective
Urs Liska u...@openlilylib.org writes:
I know that and I fully agree that it's important to be somewhat
strict about what comes into LilyPond or its parts.
Yes and no. One wants to avoid unpleasant surprises.
And I also see that not _each_ of my patches is objected against.
Well, it's
On Sun, Dec 15, 2013 at 07:48:28PM +0100, David Kastrup wrote:
Urs Liska u...@openlilylib.org writes:
But it's actually quite off-putting when you prepare a patch that is
more or less based on a broad (and astonishingly productive)
discussion on lilypond-user, and then (after two steps of
On Mon, Dec 16, 2013 at 11:29:44AM +0800, Graham Percival wrote:
Urs Liska u...@openlilylib.org writes:
I don't want to imagine what happens if I propose my rewrite of the
Features page (http://www.openlilylib.org/lilyweb/features.html).
A rewrite of a single page has less impact than
On Sun, Dec 15, 2013 at 01:23:51PM +0100, Urs Liska wrote:
Am 15.12.2013 06:47, schrieb Graham Percival:
2) they noticed the existing, read the text input page, but were
still confused. Solution: improve the text input page.
I think the only issue with text input might be that it isn't
On Dec 16, 2013 12:16 AM, Graham Percival gra...@percival-music.ca
wrote:
On Sun, Dec 15, 2013 at 01:23:51PM +0100, Urs Liska wrote:
It was consensus that new users should actively be encouraged to
download one of the complete environments, namely Frescobaldi or
Denemo, which would then
-based music engraver; it is more similar to a
programming language than a graphical score editing program. Before
downloading LilyPond, please read about our Text input.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Web-Download-Add-introductory-text-issue
Paul Morris p...@paulwmorris.com writes:
Here's how I would reword the warning to make it as concrete and simple as
possible:
Note: With LilyPond you write and edit music by typing text with your
keyboard, not by dragging notes around with a mouse.
It's not just simple, but wrong. The
On Mon, Dec 16, 2013 at 07:53:38AM +0100, David Kastrup wrote:
Note: LilyPond is a text-based music engraver; it is more similar to a
programming language than a graphical score editing program. Before
downloading LilyPond, please read about our Text input.
Which is not helping much. It
to concisely and clearly convey both the overall
text-editing user experience and the need for a separate editor that would
be even better.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Web-Download-Add-introductory-text-issue-40510046-tp155657p155928.html
Sent from
On Mon, Dec 16, 2013 at 12:42:16AM -0500, Carl Peterson wrote:
Just thinking out loud here...would it be worth looking into tweaking the
.htaccess file to do OS-based redirection on the download page, like many
sites do?
That's possible, but having the unified landing page lets us
https://codereview.appspot.com/40510046/diff/40001/Documentation/web/download.itexi
File Documentation/web/download.itexi (left):
https://codereview.appspot.com/40510046/diff/40001/Documentation/web/download.itexi#oldcode35
Documentation/web/download.itexi:35: @warningTextBased
On 2013/12/14
On Sat, Dec 14, 2013 at 09:46:54AM +, lilyli...@googlemail.com wrote:
On 2013/12/14 03:51:33, Graham Percival wrote:
Umm, isn't the whole point of this to be a warning? Why are you
removing the
warning CSS tag?
It's the whole point of this patch to raise this information to the
Incorporated most of the comments.
Will upload new patch set in a minute
https://codereview.appspot.com/40510046/diff/20001/Documentation/web/download.itexi
File Documentation/web/download.itexi (right):
https://codereview.appspot.com/40510046/diff/40001/Documentation/web/download.itexi
File Documentation/web/download.itexi (left):
https://codereview.appspot.com/40510046/diff/40001/Documentation/web/download.itexi#oldcode35
Documentation/web/download.itexi:35: @warningTextBased
Umm, isn't the
Reviewers: ,
Description:
Web: Download: Add introductory text
This addresses the initial issue discussed on lilypond-user:
too many people don't understand what they download and get
stuck on not being able to open the LilyPond program.
Add a text that explains the compiled approach and makes
A couple of nitpicks, otherwise LGTM.
https://codereview.appspot.com/40510046/diff/1/Documentation/web/download.itexi
File Documentation/web/download.itexi (right):
https://codereview.appspot.com/40510046/diff/1/Documentation/web/download.itexi#newcode57
Documentation/web/download.itexi:57:
Overall this is a bit too chatty for my liking. I have tried to give
some constructive suggestions but please make sure that you follow the
doc guidelines and use the appropriate Texinfo commands (as applicable).
It fails make at the moment (I will see why from my patchy and update
the Tracker
34 matches
Mail list logo
