Re: cap in path routine

[Patrick McCarty]

2010/6/6 josé henrique padovani <address@hidden>:
> Em 06/06/10 15:33, Patrick McCarty escreveu:
>> Looking into this more, I see two issues:
>>
>> 1) What names should we use for the different linecap options?
>> 2) Where should these values be specified?
>>
>> Any thoughts (about syntax, or otherwise)?
>
> well.. I think that would be good to preserve the ps-like words (simply to
> avoid confusion between svg and
> ps syntaxes)
>
> It would be nice to add both "setlinecap" and "setlinejoin" to the 'path
> defs...
> They could be added as optional arguments (not sure about the guile syntax
> as I am more
>
> (use-modules (ice-9 optargs)) ;; is this module already loaded by LilyPond?
> (define* (path thickness exps #:optional cap join )
>
>  ...)
>
> or, using keywords (more elegant?)... and then if linecap or linejoin are
> not supplied
> by the user they can have their actual default values... (maybe path could
> be extendend in this way?)
>
> (use-modules (ice-9 optargs)) ;; is this module already loaded by LilyPond?
> (define my-proc (lambda* (thickness exps #&amp;key linecap linejoin)
>
> ....
> What do you think?

This looks like an easy way of implementing these extra configurable options.

I've already started fiddling with the 'path routines, and I'll let
you know when I have worked everything out.

Thanks,
Patrick