![]() |
![]() |
![]() |
adg-1 reference manual | ![]() |
---|
The following list is roughly in reversed implementation order. All the improvements must be reflected in the demo programs, where applicable.
This is the collection of TODOs that could be applied also after the 1.0.0 version has been released. They are usually non-blocking and hard to implement.
angle
and size
, rotate the
path by half angle
in both directions, cut it with a circle centered
at the end of the director path with radius size
and close the
resulting path (eventually filling it).The commits in the 0.7 branch should be atomics, that is a succesfull built will be added as a prerequisite for each commit, so bisecting with "git bisect" is usable. The API should be considered almost frozen, new additions are still accepted tough. This is a testing branch: the target is to reach a sufficient quality level to make a 1.0.0 release.
These releases should reach the wider audience, according to a niche project such as the ADG canvas. This means to build releases also for different platforms, such as *BSD, OpenSolaris and Windows.
The target of the 0.6 branch is to clean up the code and stabilize the API: the 0.7.0 release will probably be a beta release.
The target of the 0.5 branch is to provide a usable canvas: with usable it is meant a canvas that can generate fairly completed drawings. The 0.5.x releases leading up to 0.6.0 should add all the missing features needed to generate this drawing.
The target of the 0.4 branch is to build the base of the canvas: few user visible changes but a quite stable base code. All the main infrastructures should be in place.
The target for the 0.3 branch is to give a shape to the project: build system, docs and a bunch of (probably temporary) basic classes should be enough to give a direction.