freenode/#clim - IRC Chatlog
Search
15:08:55
loke
beach: I'm trying to understand the basics of cluffer. I read the documentation, but I'm having some troubles.
15:24:49
beach
I don't see any problem right away, and I don't have time to investigate today. In just a few minutes, I will serve dinner to my (admittedly small) family. I'll try to remember to look at it first thing tomorrow morning.
15:47:32
loke
beach: FYI, I changed cluffer-standard-{line,cursor} to cluffer-simple-* and it worked.
16:10:47
jackdaniel
because it doesn't map over a line, but over parameters (from which you may infere overcut points)
16:19:09
jackdaniel
or to put it the other way around: it computes the parameter which is the argument to a function from overcut points between the polygon and a line (note, unbounded line, not a segment)
16:30:06
ck_
jackdaniel: my point was more that 'overcut' is probably not the term you wanted. But ok, sure.
16:32:58
jackdaniel
ck_: do you have another suggestion then? intersection (in our case) is too ambigous (and whole function is used in the other "intersection" context, where we mean intersection of a path and an area)
16:35:07
jackdaniel
n.b if we take meaning "to cut excessively" it makes actually sense, because we also cut beyond the segment (but on the same line ;)
17:37:51
ck_
jackdaniel: aha, all right. I had 'overcut' filed mentally as something exclusively to do with woodwork.
17:40:01
ck_
still, translating map-over-schnitt-gerade/polygon as map-over-overcuts-line/polygon is a distortion of meaning, and (for me) the latter is not understandable by name alone. That's all I wanted to say in the first place.
17:58:39
jackdaniel
ck_: I'm not overly attached to the name, if you could propose better alternative I can rename it
17:59:34
jackdaniel
s/could/can/ with a stipulation, that the word "intersection" is ambigous in this context
18:39:29
jackdaniel
just in case it stays as it is I've added a comment above the function explaining the used term