Patrick McCarty | 1 Mar 08:26 2009
Picon

Re: Various SVG issues

On Sat, Feb 28, 2009 at 3:09 PM, Valentin Villenave
<v.villenave <at> gmail.com> wrote:
> 2009/2/28 Patrick McCarty <pnorcks <at> gmail.com>:
>
>> Can you open an issue on the bug tracker for this?  I might have more
>> things to add as I discover more.
>
> Look Patrick, I'm sorry but I just can't add this.
>
> No, really. I have just opened another issue that says *exactly* the
> things you told us.
>
> By the way, would you happen to know the guy who gave me the details I
> added to the tracker? He's called Patrick McSomething -- heck, what's
> his name already?
> http://code.google.com/p/lilypond/issues/detail?id=755
>
> :)
>
> (Yeah, I know what you'll think: "man, this guy has a long way to go
> before becoming a new G. Percival")

I tried to think of a clever response, but failed.  :-)

Thanks,
Patrick
Patrick McCarty | 1 Mar 09:10 2009
Picon

Re: SeparationItem #'padding not working anymore?

On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
<v.villenave <at> gmail.com> wrote:
> 2009/2/2 Joe Neeman <joeneeman <at> gmail.com>:
>> On Fri, 2009-01-30 at 12:21 -0600, Jonathan Kulp wrote:
>>> Ok Graham.  I've been trying for 20 minutes and can't figure how to use
>>> PaperColumn to change spacing, though.  Joe, could you send me a snippet
>>> that shows how to use this?
>>
>> This is very embarrassing, I'm just testing the fix:
>>
>> spacing-spanner.cc:306:
>> set_column_rods (cols, 0.1); // FIXME: padding
>
> Greetings Joe,
>
> where are we now? Does this SeparationItem thingy deserve an issue in
> the tracker?

I don't think it deserves an issue.

We have two options:

1) Remove SeparationItem from LilyPond's source
(scm/define-grobs.scm).  Then we would need a convert-ly rule.
2) Keep SeparationItem, even though it is never used.

I guess it all depends on whether SeparationItem will ever be used
again in the future.

-Patrick
(Continue reading)

Mats Bengtsson | 1 Mar 09:17 2009
Picon
Picon

Re: SeparationItem #'padding not working anymore?

Quoting Patrick McCarty <pnorcks <at> gmail.com>:

> On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
> <v.villenave <at> gmail.com> wrote:
>> 2009/2/2 Joe Neeman <joeneeman <at> gmail.com>:
>>> On Fri, 2009-01-30 at 12:21 -0600, Jonathan Kulp wrote:
>>>> Ok Graham.  I've been trying for 20 minutes and can't figure how to use
>>>> PaperColumn to change spacing, though.  Joe, could you send me a snippet
>>>> that shows how to use this?
>>>
>>> This is very embarrassing, I'm just testing the fix:
>>>
>>> spacing-spanner.cc:306:
>>> set_column_rods (cols, 0.1); // FIXME: padding
>>
>> Greetings Joe,
>>
>> where are we now? Does this SeparationItem thingy deserve an issue in
>> the tracker?
>
> I don't think it deserves an issue.
>
> We have two options:
>
> 1) Remove SeparationItem from LilyPond's source
> (scm/define-grobs.scm).  Then we would need a convert-ly rule.
> 2) Keep SeparationItem, even though it is never used.
>
> I guess it all depends on whether SeparationItem will ever be used
> again in the future.
(Continue reading)

Patrick McCarty | 1 Mar 09:44 2009
Picon

Re: SeparationItem #'padding not working anymore?

On Sun, Mar 1, 2009 at 12:17 AM, Mats Bengtsson
<mats.bengtsson <at> ee.kth.se> wrote:
> Quoting Patrick McCarty <pnorcks <at> gmail.com>:
>
>> On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
>> <v.villenave <at> gmail.com> wrote:
>>>
>>> Greetings Joe,
>>>
>>> where are we now? Does this SeparationItem thingy deserve an issue in
>>> the tracker?
>>
>> I don't think it deserves an issue.
>>
>> We have two options:
>>
>> 1) Remove SeparationItem from LilyPond's source
>> (scm/define-grobs.scm).  Then we would need a convert-ly rule.
>> 2) Keep SeparationItem, even though it is never used.
>>
>> I guess it all depends on whether SeparationItem will ever be used
>> again in the future.
>
> The main thing is that the documentation is modified to show a solution that
> works, i.e. that gives the same result as you previously could obtain
> setting SeparationItem #'padding = ...

Ah, yes.  I forgot that the documentation was not updated to reflect the change.

Joe added a regtest called spacing-paper-column-padding.ly that
(Continue reading)

Jonathan Kulp | 1 Mar 14:24 2009
Picon

Re: SeparationItem #'padding not working anymore?

Patrick McCarty wrote:
> On Sun, Mar 1, 2009 at 12:17 AM, Mats Bengtsson
> <mats.bengtsson <at> ee.kth.se> wrote:
>> Quoting Patrick McCarty <pnorcks <at> gmail.com>:
>>
>>> On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
>>> <v.villenave <at> gmail.com> wrote:
>>>> Greetings Joe,
>>>>
>>>> where are we now? Does this SeparationItem thingy deserve an issue in
>>>> the tracker?
>>> I don't think it deserves an issue.
>>>
>>> We have two options:
>>>
>>> 1) Remove SeparationItem from LilyPond's source
>>> (scm/define-grobs.scm).  Then we would need a convert-ly rule.
>>> 2) Keep SeparationItem, even though it is never used.
>>>
>>> I guess it all depends on whether SeparationItem will ever be used
>>> again in the future.
>> The main thing is that the documentation is modified to show a solution that
>> works, i.e. that gives the same result as you previously could obtain
>> setting SeparationItem #'padding = ...
> 
> Ah, yes.  I forgot that the documentation was not updated to reflect the change.
> 
> Joe added a regtest called spacing-paper-column-padding.ly that
> demonstrates the new behavior.
> 
(Continue reading)

ian | 1 Mar 14:44 2009
Picon

Re: [frogs] Re: Doc - explaining layout dimensions

Hi all,

Graham Percival wrote:
> On Sat, Feb 28, 2009 at 09:05:26AM -0700, Carl D. Sorensen wrote:
>> I think that Graham wants to draw a distinction between Frogs, whose primary
>> purpose is to fix bugs in the code, and documentation developers, whose
>> primary purpose is to improve the documentation.
>
> Yes, absolutely!  Jonathan Kulp is handling (or learning how to
> handle) normal doc updating tasks.  I'm not certain if he signed
> up as a Frog; if he did, this would contribute to this confusion.
>
> If he *is* a Frog, I'd cautiously recommend that he stops being a
> Frog and concentrates on doc-maintenance.  It's not like we don't
> have enough doc tasks to occupy one full-time volunteer!
>

OK: how about nick-naming the apprentice documenters like Newts (that way, we all still count as pond-life {:===:}.

>
> Granted, this may require a bit more oversight from me, and this
> isn't likely to happen for another two weeks... *sigh* ok,
> realistically not until the end of April... and even then,
> possibly not until June.  :|
>
> I have tomorrow off, though, and should only need to spend about
> four hours on work emails.  So I'll try to have a lilypond splurge
> of my own, to match Valentin's.  :)
>
>> To a certain extent I created some confusion between the two, because my
(Continue reading)

Graham Percival | 1 Mar 15:11 2009
Picon

Re: SeparationItem #'padding not working anymore?

On Sun, Mar 01, 2009 at 07:24:53AM -0600, Jonathan Kulp wrote:
> 2. Doc policy discourages (forbids?) the use of  <at> example, which is  
> currently how this issue is addressed in NR 4.5.1 "known issues and  
> warnings."  It would be easy enough to change the  <at> example currently  
> there to show the NonMusicalPaperColumn override, but this would  
> perpetuate a breach of doc policy.

Go ahead and keep the  <at> example; NR 4 still needs to start its
rewrite.  This goes for anything else you see in NR 3 and
upwards... I don't see this situation changing until the summer.

Cheers,
- Graham
Jonathan Kulp | 1 Mar 15:51 2009
Picon

Re: SeparationItem #'padding not working anymore?

Patch attached.

Jon

On Sun, Mar 1, 2009 at 8:11 AM, Graham Percival <graham <at> percival-music.ca>wrote:

> On Sun, Mar 01, 2009 at 07:24:53AM -0600, Jonathan Kulp wrote:
> > 2. Doc policy discourages (forbids?) the use of  <at> example, which is
> > currently how this issue is addressed in NR 4.5.1 "known issues and
> > warnings."  It would be easy enough to change the  <at> example currently
> > there to show the NonMusicalPaperColumn override, but this would
> > perpetuate a breach of doc policy.
>
> Go ahead and keep the  <at> example; NR 4 still needs to start its
> rewrite.  This goes for anything else you see in NR 3 and
> upwards... I don't see this situation changing until the summer.
>
> Cheers,
> - Graham
>

--

-- 
Jonathan Kulp
http://www.jonathankulp.com
Attachment (spacing.patch): text/x-patch, 1621 bytes
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
(Continue reading)

Trevor Daniels | 1 Mar 16:38 2009
Picon

Re: SeparationItem #'padding not working anymore?


Mats Bengtsson wrote Sunday, March 01, 2009 8:17 AM

> Quoting Patrick McCarty <pnorcks <at> gmail.com>:
>
>> On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
>> <v.villenave <at> gmail.com> wrote:
>>> 2009/2/2 Joe Neeman <joeneeman <at> gmail.com>:
>>>> On Fri, 2009-01-30 at 12:21 -0600, Jonathan Kulp wrote:
>>>>> Ok Graham.  I've been trying for 20 minutes and can't figure 
>>>>> how to use
>>>>> PaperColumn to change spacing, though.  Joe, could you send me 
>>>>> a snippet
>>>>> that shows how to use this?
>>>>
>>>> This is very embarrassing, I'm just testing the fix:
>>>>
>>>> spacing-spanner.cc:306:
>>>> set_column_rods (cols, 0.1); // FIXME: padding
>>>
>>> Greetings Joe,
>>>
>>> where are we now? Does this SeparationItem thingy deserve an 
>>> issue in
>>> the tracker?
>>
>> I don't think it deserves an issue.
>>
>> We have two options:
>>
(Continue reading)

Trevor Daniels | 1 Mar 17:12 2009
Picon

Re: SeparationItem #'padding not working anymore?

Thanks Jon. Pushed to git.

Trevor

----- Original Message ----- 
From: "Jonathan Kulp" <jonlancekulp <at> gmail.com>
To: "Graham Percival" <graham <at> percival-music.ca>
Cc: "Joe Neeman" <joeneeman <at> gmail.com>; "Lilypond bug" 
<bug-lilypond <at> gnu.org>; "Mats Bengtsson" <mats.bengtsson <at> ee.kth.se>
Sent: Sunday, March 01, 2009 2:51 PM
Subject: Re: SeparationItem #'padding not working anymore?

> Patch attached.
>
> Jon
>
> On Sun, Mar 1, 2009 at 8:11 AM, Graham Percival 
> <graham <at> percival-music.ca>wrote:
>
>> On Sun, Mar 01, 2009 at 07:24:53AM -0600, Jonathan Kulp wrote:
>> > 2. Doc policy discourages (forbids?) the use of  <at> example, which 
>> > is
>> > currently how this issue is addressed in NR 4.5.1 "known issues 
>> > and
>> > warnings."  It would be easy enough to change the  <at> example 
>> > currently
>> > there to show the NonMusicalPaperColumn override, but this 
>> > would
>> > perpetuate a breach of doc policy.
>>
(Continue reading)


Gmane