Re: cap in path routine

[josé henrique padovani]

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?

For 1), we could use the PostScript naming convention, though it is
somewhat difficult to remember.  The SVG naming convention is easier
to understand, but more wordy.

For 2), I don't really know at the moment.  :-)

I think it would be best to find a "general" solution that will work
for all routines capable of supporting linecap settings (for example,
'draw-line and 'polygon).

Any thoughts (about syntax, or otherwise)?

Thanks,
Patrick

  

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 #&key linecap linejoin)

....
What do you think?

-- 
http://zepadovani.info