Urs Liska writes:
> Hi David,
>
> Am Sonntag, den 23.02.2020, 22:12 +0100 schrieb David Kastrup:
>> Urs Liska writes:
>>
>> > Hi all,
>> >
>> > as a starting point for a - hopefully - comprehensive documentation
>> > effort I have finally updated https://openlilylib.org with a
>> > completely
Hi David,
Am Sonntag, den 23.02.2020, 22:12 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Hi all,
> >
> > as a starting point for a - hopefully - comprehensive documentation
> > effort I have finally updated https://openlilylib.org with a
> > completely
> > new website, which I'd like
Hi Simon,
Am Sonntag, den 23.02.2020, 18:42 +0100 schrieb Simon Albrecht:
> Hi Urs,
>
> this looks great! As often, I can’t offer much more than applause
> and
> some nitpicking…
Well, that's useful too.
>
> On the ‘About LilyPond’ I’d rather write “GNU LilyPond is a music
> notation
Urs Liska writes:
> Hi all,
>
> as a starting point for a - hopefully - comprehensive documentation
> effort I have finally updated https://openlilylib.org with a completely
> new website, which I'd like to have some feedback about and
> contributions for.
>
> There are several parts to that
On 02/22, Urs Liska wrote:
> Am Freitag, den 21.02.2020, 18:52 -0800 schrieb ma...@masonhock.com:
> > Do you want something similar [Sphinx][1] or [Doxygen][2]?
>
> Yes, something similar, but IISC these tools (which I had of course
> taken notice of earlier) are limited to their set of
Hi Urs,
this looks great! As often, I can’t offer much more than applause and
some nitpicking…
On the ‘About LilyPond’ I’d rather write “GNU LilyPond is a music
notation program /strongly inspired by/ traditional craftsmanship”.
After all, the process of working with LilyPond doesn’t
Am Freitag, den 21.02.2020, 18:52 -0800 schrieb ma...@masonhock.com:
> On 02/20, Urs Liska wrote:
> > What I really *want* to have but have no idea so far how to achieve
> > is
> > additional code/API documentation retrieved from the actual source
> > files. There should be a tool to retrieve that
On 02/20, Urs Liska wrote:
> What I really *want* to have but have no idea so far how to achieve is
> additional code/API documentation retrieved from the actual source
> files. There should be a tool to retrieve that from comments (or actual
> signatures?), resulting in either HTML or Markdown
Hi Joram,
thanks for the ffecback.
Am Donnerstag, den 20.02.2020, 23:33 +0100 schrieb Noeck:
> Dear Urs,
>
> it’s great that you found time for that. It looks nice and I think
> MkDocs is a good choice (would have been my first choice, too).
>
> While speaking about documentation, I very much
Dear Urs,
it’s great that you found time for that. It looks nice and I think
MkDocs is a good choice (would have been my first choice, too).
While speaking about documentation, I very much like this approach:
https://www.divio.com/blog/documentation/
Some nitpicks from me:
- Should everyone
Hi all,
as a starting point for a - hopefully - comprehensive documentation
effort I have finally updated https://openlilylib.org with a completely
new website, which I'd like to have some feedback about and
contributions for.
There are several parts to that effort, most of which are essentially
11 matches
Mail list logo
