>> > > I did this once for GLCanvas, and don't want to repeat that again :) > The Balloon canvas and its uses is too damn focused on blitting, which makes > it too hard to provide a backend which doing most things on GPU. > If you want to go into vector world, you should keep a distance from > any blitting operations. > Simply because they are ineffective, CPU hungry and don't scale well.
In that case what would be the next generation API (call it Athens) that would make ROME getting better and that your code would propose an API compliant interface? You could that way have a class that implements the Athens interface and the system gets improved and you would not depend on Athens. Because we should not neglect that without common API change and adaptation is and will be a pain. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
