kicad-developers team mailing list archive

[Maciej Sumiński <maciej.suminski@xxxxxxx>]

Hi Chris,

Have a look at the last summary, commented by Wayne [1] and a few
reports tagged as such [2]. Perhaps we need to have a software renderer
that offers decent speed, then we can either use wxDC or try to boost
Cairo GAL performance (I have done some minor improvements [3], but
probably they need to be rebased).

I agree that coding with dual canvases in mind is challenging at times,
as it is easy to break either one or the other. Currently I am stuck
with undo buffer refactoring, putting extra effort to modify the code
and without adding regressions in the legacy canvas.

Any help in this field would be appreciated.

Regards,
Orson

1.
https://www.mail-archive.com/kicad-developers@xxxxxxxxxxxxxxxxxxx/msg19323.html
2. https://bugs.launchpad.net/kicad/+bugs?field.tag=missing-gal-tool
3. http://bazaar.launchpad.net/~orsonmmz/+junk/cairo_fast/revision/4454

On 06/16/2016 03:30 AM, Chris Pavlina wrote:
> Other than a decently efficient fallback backend for systems that can't handle
> OpenGL+GAL, do we have an official list of things we need to be implemented in
> GAL before legacy can be taken out? I really want to keep working on the UI
> cleanup, but having dual canvases is quite the roadblock to doing that
> correctly. So far I've been handling the easy bits (legacy things that can be
> taken out to achieve parity with GAL), but I'd like to contribute some time to
> adding the missing bits to GAL.
>

Attachment: signature.asc
Description: OpenPGP digital signature