Skip to content

Milestones

List view

  • Ability to test is one thing, automated execution is another. The goal of this milestone is to have automated testing on push/pull request.

    No due date
    0/2 issues closed
  • For the time being, the GUI is usable, but not overly pretty. The color choosers look a little helpless, ROI selection is single-shot, wireframe colors are not automatically adjusted. There is exactly one menu, adding an unnecessary click to get to the commands. There are no icons for them. Image sizes have gone wild. It's not fully clear whether shell mode should be left in. It's not clear either whether it should be mandatory (likely shouldn't), and what consequences that has for the OpenCV requirement. Shell mode doesn't draw helper lines. Shell mode also doesn't provide a means of configuring them. Shell mode doesn't allow a way to modify colors. Anything the UI is enhanced with in the meantime that is technically doable from shell will also be missing from shell mode. Potentially it makes sense to refactor the code such that there is a common middle layer for options and distribution of the same data according to the same logic from different user interfaces to different technology-centered implementations.

    No due date
    3/7 issues closed
  • Custom-shape pixelation is also useful for cross-stitching. However, the requirements are slightly different. - Cross-stitching is usually done with a much larger amount of individual colors. For those, the current color display is no longer viable. - Shapes and sizes follow a different naming. There is no such thing as a gauge. - There are various stitch shapes. Therefore, simple rectangles may not be sufficient. Instead, some brush-like customizable shape may come in more handy. - It is possible that a different type of representation makes more sense - this may require further investigation as to how cross-stitching patterns are written down, in particular for non-cross stitches.

    No due date
    0/2 issues closed
  • - There is a test harness of some kind that can verify the actual transformation code. - Corner cases for the transformation algorithms are identified. - There are tests in place that verify that all corner cases (as well as good cases and plain-and-straightforward failures) behave correctly.

    No due date
    7/8 issues closed