On Thu, Nov 11, 2021 at 1:48 AM Jean Abou Samra wrote:
>
>
> > First one would be to add, with small fonts, at the bottom of the
> > page, a list of the pairs (as links): class/interface -
> > overriden/implemented property, inside an expandible panel (hidden by
> > default).
> > In this way, IF
Le 11/11/2021 à 13:24, Paolo Prete a écrit :
This appears to me as an additional issue instead a *must do*.
Formatting as pdf (or plain text) an API doc with an OO paradygm and
plenty of links is IMHO meaningless. I give you a personal advice:
don't spend your time in the creation of this kin
On Thu, Nov 11, 2021 at 2:50 PM Jean Abou Samra wrote:
> Le 11/11/2021 à 13:24, Paolo Prete a écrit :
> >
> > This appears to me as an additional issue instead a *must do*.
> > Formatting as pdf (or plain text) an API doc with an OO paradygm and
> > plenty of links is IMHO meaningless. I give you
Le 11/11/2021 à 15:12, Paolo Prete a écrit :
I see, but my advice included your Scheme example, which is formatted
as plain text as well.
IMHO, a tool that formats on the fly, as a tree or list on the
standard output in plain text, a sum of cross links, would be actually
unusable in practical c
On 2021-11-11 5:50 am, Jean Abou Samra wrote:
Le 11/11/2021 à 13:24, Paolo Prete a écrit :
This appears to me as an additional issue instead a *must do*.
Formatting as pdf (or plain text) an API doc with an OO paradygm and
plenty of links is IMHO meaningless. I give you a personal advice:
do
Hi Paolo (et al.),
For what it’s worth, I can already see how Jean’s "IR Grob Formatting” snippet
will be invaluable to me as both a [power] user and a [beginning] developer.
I’m going to play around with it to see exactly what output format will be the
most helpful — it will probably be two di
Le 11/11/2021 à 15:41, Aaron Hill a écrit :
If it helps to have a data point, I exclusively use the PDF manuals
for my reference (apart from searching the code base directly).
Yeah, I know that some people prefer PDFs. Personally,
it would not even have crossed my mind to search for
documentati
On Thu, Nov 11, 2021 at 3:39 PM Jean Abou Samra wrote:
> Le 11/11/2021 à 15:12, Paolo Prete a écrit :
> > I see, but my advice included your Scheme example, which is formatted
> > as plain text as well.
> > IMHO, a tool that formats on the fly, as a tree or list on the
> > standard output in plai
From: Paolo Prete
Date: Thursday, November 11, 2021 at 9:07 AM
To: Jean Abou Samra
Cc: Carl Sorensen , Kieren MacMillan
, Lilypond-User Mailing List
Subject: Re: How to increase the distance between the last note of a measure
and the following bar line
On Thu, Nov 11, 2021 at 3:39 PM Jea
Le 11/11/2021 à 17:11, Carl Sorensen a écrit :
*From: *Paolo Prete
*Date: *Thursday, November 11, 2021 at 9:07 AM
*To: *Jean Abou Samra
*Cc: *Carl Sorensen , Kieren MacMillan
, Lilypond-User Mailing List
*Subject: *Re: How to increase the distance between the last note of a
measure and the
Sorry, I sent a previous message only to Carl instead to the ML. Here are
the following messages:
On Thu, Nov 11, 2021 at 5:28 PM Carl Sorensen wrote:
>
>
>
>
> *From: *Paolo Prete
> *Date: *Thursday, November 11, 2021 at 9:17 AM
> *To: *Carl Sorensen
> *Subject: *Re: How to increase the dista
On Thu, Nov 11, 2021 at 5:33 PM Jean Abou Samra wrote:
>
>
> The standard autodocumentation tools wouldn't help
> much either.
>
> - The bulk of the work is extracting information from
>LilyPond's internals. Take predicates. Their mapping
>to names is maintained in the code, so we would h
>>> This appears to me as an additional issue instead a *must do*.
>>> Formatting as pdf (or plain text) an API doc with an OO paradygm
>>> and plenty of links is IMHO meaningless. I give you a personal
>>> advice: don't spend your time in the creation of this kind of
>>> document; what now seem
From: Paolo Prete
Date: Thursday, November 11, 2021 at 11:06 AM
To: Jean Abou Samra
Cc: Carl Sorensen , Kieren MacMillan
, Lilypond-User Mailing List
Subject: Re: How to increase the distance between the last note of a measure
and the following bar line
On Thu, Nov 11, 2021 at 5:33 PM Je
On Thu, Nov 11, 2021 at 7:30 PM Carl Sorensen wrote:
>
>
>
> The thought of having to make a “TimeSignature_wrap”, as opposed to a
> “Grob_wrap”, is antithetical to the LilyPond core principles. We insist
> that, as much as possible, internals documentation be created from
> executable code, rat
Le 11/11/2021 à 20:15, Paolo Prete a écrit :
On Thu, Nov 11, 2021 at 7:30 PM Carl Sorensen wrote:
The thought of having to make a “TimeSignature_wrap”, as opposed
to a “Grob_wrap”, is antithetical to the LilyPond core
principles. We insist that, as much as possible, internals
d
Hi Jean,
> At this point, what is needed is input on
> precise ways to structure the information.
Agreed.
I’m getting close to an offer for [power] users… =)
Stay tuned!
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email:
How can I obtain an an acciaccatura-style (slashed) grace stem with
\afterGrace? Much searching has failed to find an answer. Help appreciated!
Thanks,
Stan
\version "2.23.3"
\include "english.ly"
\relative c
{\clef bass
<<{ 2 \afterGrace 3/4 2 8( | 1) }
\\
{2 \afterGrace
On Thu, Nov 11, 2021 at 3:24 PM Stan Sanderson wrote:
>
> How can I obtain an an acciaccatura-style (slashed) grace stem with
> \afterGrace? Much searching has failed to find an answer. Help appreciated!
> Thanks,
> Stan
>
> \version "2.23.3"
> \include "english.ly"
> \relative c
> {\clef bass
Hi Stan,
Am 12.11.21 um 00:17 schrieb Stan Sanderson:
How can I obtain an an acciaccatura-style (slashed) grace stem with
\afterGrace? Much searching has failed to find an answer. Help appreciated!
Thanks,
Stan
\version "2.23.3"
\include "english.ly"
\relative c
{\clef bass
<<{ 2 \af
Wow- 28 minutes from problem to solution! Thank you again to Lukas and Knute.
-Stan
> On Nov 11, 2021, at 5:49 PM, Knute Snortum wrote:
>
> On Thu, Nov 11, 2021 at 3:24 PM Stan Sanderson wrote:
>>
>> How can I obtain an an acciaccatura-style (slashed) grace stem with
>> \afterGrace? Much sear
21 matches
Mail list logo
