Add "Editing" page/node

Add "Editing" page/node




Web:Text input: Remove LilyKDE image in closing

As there is a dedicated page about editing now I think this
image here isn't needed anymore.
There are already so many nice images on that page.
And it's very outdated BTW (a discontinued program).

Web: Rewrite Closing of "Text input"

Discussion indicated that "Text input" - while very good in
itself - isn't sufficient to let all readers get the idea
of "editing and compiling".
Therefore I added a new page discussing that concept.

This commit rewrites the closing of "Text input" to make
that clear and @ref to the new page.

Web:Introduction: Add link to new Editing node


Web:Editing: Add new flow-chart

Attention: This image isn't present in lilypond-extra yet.
So outside of my dev computer this won't compile correctly.

Web: Add node "Editing"

As discussed on lilypond-devel I wrote a page discussing the concept
of editing and compiling itself.
While this factually is self-evident it seems that we need this
extra effort in getting potential users on the right track.

[uliska, 2014-02-07 12:28:01]

This has been waiting for some time, but is in line with stuff I did earlier and
was also discussed earlier.

A new page/node making the relation between input file, _any_ editor and
_dedicated_ editor more explicit, hopefully being a step to reduce confusion for
potential new users.

[PhilEHolmes, 2014-02-07 14:29:15]

An initial comment:

https://codereview.appspot.com/60530047/diff/1/Documentation/web/introduction...
File Documentation/web/introduction.itexi (left):

https://codereview.appspot.com/60530047/diff/1/Documentation/web/introduction...
Documentation/web/introduction.itexi:78: 
If I build the web page, this added menu item appears as a different colour, and
if I check the source, it fails to have the correct color as its class.  I'm
wondering whether 8 items is regarded as the maximum: I know GP was always
_very_ _very_ anti adding extra width to the menu.  Would it be possible to have
a menu item called editing, and easier editing as part of that?

Apart from noting that the patch has 2 whitespace errors, I'll wait until we can
resolve that before I review the patch further.

[uliska, 2014-02-07 14:45:28]

On 2014/02/07 14:29:15, PhilEHolmes wrote:
> An initial comment:
> 
>
https://codereview.appspot.com/60530047/diff/1/Documentation/web/introduction...
> File Documentation/web/introduction.itexi (left):
> 
>
https://codereview.appspot.com/60530047/diff/1/Documentation/web/introduction...
> Documentation/web/introduction.itexi:78: 
> If I build the web page, this added menu item appears as a different colour,
and
> if I check the source, it fails to have the correct color as its class.  

I'm sorry, but I don't have a clue where to define such a thing. IISC in the
itexi file there is only the @menu section which simply lists items without
assigning any class or other value?

> I'm
> wondering whether 8 items is regarded as the maximum: I know GP was always
> _very_ _very_ anti adding extra width to the menu.  

I can't imagine that, considering that Manuals has 14, Community 12 menu items.

> Would it be possible to have
> a menu item called editing, and easier editing as part of that?

I don't think so.
Easier Editing will remain a place to jump to directly, even if you know what
the concept of a compiled system is. (Maybe it will be renamed as one of the
upcoming steps.) 
The new page is explicitly intended for people who don't find their way around
all this nerdy stuff. I don't
think it's a good idea to put those two together.

> 
> Apart from noting that the patch has 2 whitespace errors, 

I'lss look into it.

> I'll wait until we can
> resolve that before I review the patch further.

[uliska, 2014-02-07 15:33:19]

Add pictures, fix whitespace errors

[uliska, 2014-02-07 15:35:27]

On 2014/02/07 15:33:19, uliska wrote:
> Add pictures, fix whitespace errors

As said earlier, I don't know how the colors of menu items are managed.
So without more input I can't do anything about that.

[uliska, 2014-02-07 15:52:51]

Fix color coding of menu

[PhilEHolmes, 2014-02-08 14:42:23]

Some proposed changes that help to make it easier to read, I hope.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
File Documentation/web/introduction.itexi (right):

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1190: and how you actually @emph{work} with
these text files you may
Think it's simpler and better to say:

"But if you don't have a clear idea yet how you actually @emph{work} with these
text files"

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1202: LilyPond isn't one monolithic program
as you may be used
one -> a single

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1203: from graphical notation tools. 
Instead it is a system with
graphical music notation tools.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1204: several independent parts.  This may
seem irritating at first,
"This may seem irritating at first," -> "This may not be what you're used to,"

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1213: of other options, including MIDI.
"there is a variety of other options" is grammatically correct, but sounds odd
to a native.  "there are a variety of other options" sounds better. 
Alternatively "a variety of other options are available, including MIDI" avoids
the issue.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1219: support you in working with LilyPond
files.
This would read better as:

It can be unnecessarily difficult editing LilyPond input with a plain text
editor, but fortunately there are a number of tools that actively support
working with LilyPond files.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1236: automatic command completion that
helps you remembering
remembering -> remember

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1237: the available commands and reduces
misspelling errors at the
misspelling -> spelling

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1240: While these are quite basic tools
some programs offer you a
"While these are quite basic tools some programs offer" -> "Some other programs
offer"

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1241: complete editing environment for
working with LilyPond score.
score -> scores

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduc...
Documentation/web/introduction.itexi:1242: They may include templates and entry
palettes, may support
"may support" -> "support"