Jason Tackaberry wrote: > On Sun, 2005-07-10 at 13:21 +0200, Dirk Meyer wrote: >> I now connected the expose to mevas. Maybe the window class should >> remeber the image and handle expose itself? Maybe not. The input > > Imlib2.Display supported that. But I think handling expose events > belongs at the canvas level.
Yes. Your updates look good. >> And when we have to kaa.evas, were do you put the "display" code for >> framebuffer and directfb? I guess inside evas is good idea. If I use >> evas with fb/dfb, I should need to install kaa.display at all. > > The short answer is because fb/dfb is "display stuff." For the same > reason the X11 stuff is in kaa.display, so should dfb stuff be. Evas's > support for these engines requires something glues the display to the > evas engine. Currently, that something is EvasWindow in kaa.display. > It should probably be called EvasX11Window. And dfb stuff would be > EvasDFBWindow. While speaking of kaa.display. Everything is in __init__.py right now. What about creating a file for each class? It will be easier to read and we have a directory for display, so why not use it? > Another thing I tried to do but didn't test was make kaa.display compile > without Imlib2 installed. It should be possible to use kaa.evas and > kaa.display without imlib2, for example. Agreed. Dischi -- If you can't beat your computer at chess, try kickboxing.
pgpL8HCLlgTZg.pgp
Description: PGP signature
