Re: [oll-user] Learning manuals vs. reference documentation | lilydoc

[Janek W. <lem...@gm...>]

Hi,

2013/4/12 Urs Liska <ul...@op...>

> Am Freitag, den 12.04.2013, 18:45 +0200 schrieb Janek Warchoł:
> > This looks like a good idea.  However, i have limited experience with
> > such systems, so i don't have more thoughts on this topic.
>
> We should probably look at two or three languages (e.g. Java and Python)
> and collect ideas about their syntay (i.e. how to document the source
> files).
> Then we should discuss our special cases - because this is another field
> where we are facing the hybrid nature of LilyPond files as source code
> and documents.
>

ok.  however, i'm afraid i won't have enough time for this anywhere soon :(


> For our immediate need we could stick to documenting the source code,
> but for a real lilyDoc library we should also strive for documenting the
> content.
> For example it would be a real improvement if we could enter critical
> remarks directly in the source code and let a script harvest and output
> them. This would an extremely cool feature when talking with
> musicologists.
> If I could for example enter the latex code for critical remarks
> directly in the source, then I'd have 2way point-and-click at hand, i.e.
> I could enter the remarks in the environment where I inspect and correct
> the score. Afterwards a script would parse the files, sort the remarks
> and spit out the (nearly finished) critical report. Cool!
>

Awesome :)

Janek
-------------- next part --------------
An HTML attachment was scrubbed...