TOAD & Fischland on Mac OS X

I've created a Taskboard at Trello for the program. (And "Neutra" might be the new name for "Fischland".)

TOAD & Fischland on Mac OS X

I'm making plans to clean up the code, starting with TFigureTool.

One thing, which came to my mind, is that I have this clever (too clever?) design, where TActions (closures) can be added anywhere into the window (interactor) tree and then the next menu bar up the window tree will automagically provide entries to invoke those actions. But I am not using the same technique to connect the buttons in the toolbar with TFigureTools. So that needs to change.

And since I forgot how I implemented the menu bar 17 years ago, I drew the following diagram with TOAD & Fischland... converted it to SVG with Affinity Designer (for the time being)...

TOAD & Fischland on Mac OS X

Text can now be attached to figures and it can be bold, in italics and underlined. It doesn't wrap yet inside the figure, but it moves along with the figure it is attached to.

The program can now be used to draw a diagram of itself, I have an idea of all the features I need (a mixture of Illustrator, CorelDraw, Manga Studio, OmniGraffle, ...) so I should now be able to come up with a reasonable design.

TOAD & Fischland on Mac OS X

The past year had been quite busy and I finally came around to do some coding again and began writing a feature to connect figures with lines. This is something I wanted to implement in Workflow, but I considered that should get the design right in Fischland first before reimplementing parts of it in JavaScript.


I had a look at Jira's Kanban board a week ago and while it is what everybody else seems to implement as an electronic Kanban board, one can't do Kanban with it like Henrik Kniberg did in Lean from the trenches.

And I don't think much has changed since Kniberg's Jira rant: "I don't hate many things. But Jira... it's like a cancer that sucks the soul out of companies. Even w Greenhopper. #uxfail" (Greenhopper being the Kanban board Jira bought.)

So I had some ideas how Kniberg's physical Kanban boards could be turned into code and began porting some of the TOAD/Fischland design to JavaScript 6 for a little web application:

As the time of writing, one can only resize the two rectangles.


Path Offset

Extending Philip J. Schneider's classic “An Algorithm for Automatically Fitting Digitized Curves” from two to four dimensions lets it handle pressure and rotation quite well.

Path Offset

I move an ellipse (light green) along a Bézier curve (black) and let it intersect (red) with a single normal (dark green) on that curve.

The dark blue curve represents the distance of each ellipse, the light blue curve is it's 1st derivative. Which is a polynomial of degree 18. (Thanks to the trial version of Mathematica for figuring that out.)

Which I could tackle with Newton-Horner.

And then I would have still to include rotation and pressure (scaling)...

Or I just take, say, a hundred samples, and take the maximum/minimum as start for the Newton method.

    Path Offset

    Inkscape uses an algorithm based on Dynadraw for it's calligraphic pencil tool. Which seems to extrude a scaled and rotated line along a path.

    The algorithm others and I've been using uses an ellipse instead of a line. Which I prefer because it's closer to a real nib pen.

    But my code doesn't output béziers yet, so I began playing with Tiller-Hanson's bézier offset algorithm.

    But I'm not quite sure how to handle a rotated ellipse with a path offset algorithm.

    Boolean Operations on Polygons

    It's getting somewhere. Curves are now also split on vertical extrema and the sweep buffer sorting should work for curves and lines with no more than one intersection. As far as I see, getting rid of that limit plus curves intersecting with curves might be only remaining issues.

    Boolean Operations on Polygons

    Got it. My mistake. I assumed that splitting curves at their horizontal extrema would be enough. But in the case below the green curve ended up above the blue curve in the sweep line buffer. That's because SweepComp is using the end points of the curve (red line) and then of course the green line ends up above the blue one.
    I could solve that by also splitting curves at the vertical extremas (orange line)... or by using the left point's control point?


    Subscribe to RSS - blogs