Currently, kiva.agg is the only Kiva backend which implements the draw_marker_at_points method correctly. This is mostly OK, because 99% of the time that's the only backend an application uses.
However, given #414 and our desire to live in a future without kiva.agg, it would be useful have an implementation of draw_marker_at_points, written in a fast language, that could draw to any buffer of bytes that was passed to it. Chaco scatter plot renderers would benefit considerably if they can keep their fast drawing path.
draw_marker_at_points has built-in limitations in its only existent implementation (no rotation allowed, line widths aren't scaled), so it might be OK to keep those limitations if it means we get a solution sooner.
Currently,
kiva.aggis the only Kiva backend which implements thedraw_marker_at_pointsmethod correctly. This is mostly OK, because 99% of the time that's the only backend an application uses.However, given #414 and our desire to live in a future without
kiva.agg, it would be useful have an implementation ofdraw_marker_at_points, written in a fast language, that could draw to any buffer of bytes that was passed to it. Chaco scatter plot renderers would benefit considerably if they can keep their fast drawing path.draw_marker_at_pointshas built-in limitations in its only existent implementation (no rotation allowed, line widths aren't scaled), so it might be OK to keep those limitations if it means we get a solution sooner.