2016-04-06 10:07 GMT+02:00 Igor Stasenko <siguctua@gmail.com>:

On 6 April 2016 at 10:35, Nicolai Hess <nicolaihess@gmail.com> wrote:

I made some fixes for AthensBalloon (not all are integrated yet, some parts are just experimental and needs more tests), the idea is to have

AthensBalloon at least not crash or throwing�� errors, even if not all features are supported.

Much, much, much appreciated. The whole point of existence of Balloon backend for Athens was to use it as a proving ground that Athens can stay backend neutral, and its API allows to stay it like that.

From that perspective, any feature that offered by any backend should find its way via API, but not thrown into play just because we can.

Cool. I played with AthensBalloon a way back; but some stuff wasn't working. Good to know it has improved, and this is within Athens objective to be backend-neutral.

��

As i mentioned before, if we would be making Cairo wrapper, then there no reason to call it Athens. It could be something like 'CairoPharo'.��

��

And i kept mentioned over and over again on all presentations related to Athens, that it is not Cairo.

But at the moment, no one cares about non-cairo-athens. All users just directly use AthensCairoCanvas/AthensCairoSurface.

I had a bug report for discussion about how to make some kind of factory that would create the appropriate Athens backend.

Is there still some interest on AthensBalloon or to make athens more independent from cairo?

��

��

It always been. But didn't have much time to make that happen.��

For instance, i dream to make an OpenGL backend for Athens.. but i had no chance to put my hands on that topic so far.

It is interesting to know, because this means you probably already have an idea about how to implement that :)

Regards,

Thierry