waffle

Name day + Name days in Sweden + today.

The Unforking of KDE’s KHTML and WebKit. Ars Technica’s Linux weblog looks at how Apple and KDE have resolved their previous differences with patch-acceptance worries by working towards reconciling the codebases.

Good stuff on one of the two best rendering engines on Earth.

Checkers solved - the necessary handful of all 500 billion billion possible states have been isolated and an unbeatable AI has been constructed.

After about spending 10 effective hours getting a SnapBack arrow path out of Photoshop (no, not Illustrator, because I regularly don’t need it), I have a few tips for myself and for others:

• Do not write an AppleScript at 2AM to kinda-sorta generate NSBezierPath incantations from Photoshop’s vended data - it will turn out reasonably useless because the incantations will not generate the exact correct path but instead somehow fudge the curves, something you do not want to particularly investigate further.
• Do not write a test application having text boxes bound to the individual x or y point values of the destination or control points of the curve parts of the paths based on what you got from the previous step in some sort of attempt to fix the essentially almost-there data. You will mess around for a few minutes and then sob violently.
• Do not extend the test application from the previous step with steppers (up-down controls). You will mess around for another three minutes and acquire a strong urge to hit yourself in the head with a spade.

• Do draw the shape in a new Photoshop document, Save As as a “Photoshop EPS”, preserve vector data, open this EPS document up in the competent text editor of your choice, search for newpath in this wondrous file, grab everything from that point until closepath, copy and paste it into a new text document and then follow these instructions to acquire a functional line of NSBezierPath incantations (this is script-like grunt work but can be performed by hand; I do not have a script to hand out at this time):

  1. Start from the top. Ignore the newpath line.
  2. For each line that doesn’t say closepath:
     • If the line ends with an m and holds two floating-point values, write [bp moveToPath:NSMakePoint(X,Y)]; where X is the first floating-point value and Y is the second.
     • If the line ends with an l and holds two floating-point values, write [bp lineToPath:NSMakePoint(X,Y)]; where X is the first floating-point value and Y is the second.
     • If the line ends with a v and holds four floating-point values, write [bp curveToPath:NSMakePoint(X,Y) controlPoint1:NSMakePoint(X1,Y1) controlPoint2:NSMakePoint(X2,Y2)]; where X and Y are the last two floating-point values, X1 and Y1 are the floating-point values you last wrote out as part of an earlier X,Y instruction in a previous step (the ‘current point’, as it were) and X2 and Y2 are the first two floating-point values.
     • If the line ends with a y and holds four floating-point values, write [bp curveToPath:NSMakePoint(X,Y) controlPoint1:NSMakePoint(X1,Y1) controlPoint2:NSMakePoint(X,Y)]; where X and Y are the first two floating-point values and X1 and Y1 are the last two floating-point values.
     • If the line ends with a c and holds six floating-point values, write [bp curveToPath:NSMakePoint(X,Y) controlPoint1:NSMakePoint(X1,Y1) controlPoint2:NSMakePoint(X2,Y2)]; where X and Y are the last two floating-point values, X1 and Y1 are the first two floating-point values and X2 and Y2 are the two middle floating-point values.
  3. You’re done. Add to this only an initialization of a new NSBezierPath at the top (NSBezierPath *bp = [[NSBezierPath alloc] init];) and any drawing instructions on the bottom.

So. You may get the impression that I’m taking this “resolution-independent” thing seriously. You may be right.