Phase 1: All Critical Functionality. about meerk40t

[tatarize]

• Phase 0 complete.
• Require Travis CI
• Document API source elements
• Coverage test suite path.
• Coverage test suite speedcode.
• Limited test suite K4Controller (cannot test actual USB interactions).
• Coverage test suite LhymicroWriter

A lot of people use the Whisperer methodology of editing a project elsewhere and reloading the project. As such, the project need to permit that to happen with robustness.

• Must render text elements. #61
• Must have a working dxf reader. #41
• Must have preset color / settings values. #36
• Must load images from SVG.
• Must permit the scaled and altered images to convert to a raster image for processing.
• Must have proper widgeting scale and rotate ability.
• Should make a better method for querying and selecting the specific K40 device.
• Should have multi-language support. #27 (It does not need to have translations)

[tatarize]

The main dialog is primarily concerned with vector, raster, and text elements. These are the core classes to be used.

Each of these classes can map to a several functions. Rasters should have operations like #88 #87 #24, etc or anything other people come up with, where the core classes (the data) are the same but how these are made and converted and rendered differently. For example, you could do all raster operations on a vector, if it is converted to a raster image, though vectors have other operations like engrave and cut, where the distinction is in the functionality. Cuts are processed specially for jobs such that the cut operations are put last and optimized inner to outer. Additionally processing must be done for operations like rotary engraving where scaling for the rotary must be done. Also, for images which are not real pixels but mere affine transformations of pixels.