EWS is a new Ecor_Evas engine that builds on top of other engines. It
will create a backing store Ecore_Evas and ecore_evas_ews_new()
windows are created in it as images, but transparent to the outside
users (similar to buffer's ecore_evas_object_image_new()).
It provides a basic windowing system, with a known background object
that can be changed to your pleasure, and issue Ecore_Events to notify
of new windows and changes like movement, etc. Then you can write a
simple window manager based on it. (See example, Elementary will
contain one as well).
Backing store is determined by your best engine (as in
ecore_evas_new()) or specified with ecore_evas_ews_engine_set() or
environment variable $ECORE_EVAS_EWS (format:
engine-name❌y:w:h:options). The size can be set with
ecore_evas_ews_setup().
SVN revision: 63848
It has some issues that need debugging, I'm not sure if Ecore_Thread doesn't
like having stuff done before the main loop is running and valgrind was also
complaining about some invalid reads in ecore_thread.c, but at least the
example is there for people to look at and report problems, things not clear
or just about anything that may come up from it.
SVN revision: 61293
It exemplifies the difference between ecore_time_get(), ecore_time_unix_get()
and ecore_loop_time_get(). A description of this example is also provided.
SVN revision: 60557
Gustavo Sverzut Barbieri
Gustavo Lima Chaves
Jonas M. Gastal
Iván Briano
Rafael Antognolli
Mike McCormack