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
Note: maybe it would be better to put yes in the .pc file
instead of static. I don't see any advantage having that
information in the pc file.
SVN revision: 62412
(based on patch from Boris Faure)
NB: This is untested/unsupported code. Ymmv, but using/compiling
ecore_x with versions of xcb > 0.3.6 is not supported yet (until such
time that standard distros support 0.3.8 out of the box).
SVN revision: 61971
Thread safety is disabled by default.
Enable it with --enable-thread-safety
Should cover timers, events, animators, idlers and fd handlers.
Tested with Enlightenment and elementary_test.
Signed-off-by: Mike McCormack <mj.mccormack@samsung.com>
SVN revision: 61851
near finished yet). Add working OpenGL for XCB engine.
NB: wrt Opengl...Raster, this is the env var/dlsym version you
requested this morning ;)
NB: Basically what happens is, if you know you do not ever want/use
opengl, you can export ECORE_X_NO_XLIB env variable, and ecore_x will
use pure xcb to establish it's X connection. However, if you do use
OpenGL and this env var is not exported, then ecore_x(cb) will use
XOpenDisplay to init the connection.
SVN revision: 61724
NB: IF you are going to try this, build evas with
`--enable-software-xcb` AND build ecore with `--enable-ecore-x-xcb
--disable-ecore-evas-opengl-x11`.
NB: OpenGL does NOT work with the xcb stuff yet. E itself does NOT
work with this yet either (still have to commit those changes).
SVN revision: 61385
glib only allows millisecond resolution in g_main_loop.
To avoid this limitation, use timerfd to wake up the main loop.
Signed-off-by: Mike McCormack <mj.mccormack@samsung.com>
SVN revision: 61079
Subject: [E-devel] XRender engine causes ecore build failure
while building ecore. The problem is that this engine was removed from evas
but not yet completely from ecore. I was on IRC with Vincent Torri (vtorri)
and Daniel Juyung Seo (SeoZ) and the consensus was to remove the code for the
XRender engines, both the Xlib and XCB versions.
There is a switch over the different engine types, where there are still a few
places left where XRender is handled, grep for "xrender" or "XRENDER" and you
will find them. The question is whether to just return NULL in order to signal
that this engine is not supported or to remove the whole thing. The latter
could break binary compatibility, therefore I left those stubs in.
SVN revision: 60502
The ecore_con module needed a port of the local connections
with named pipes. The other connections (TCP, UDP) are using
BSD sockets, which are also used on Windows.
No abstract sockets on Windows.
NB: Should I backport that commit to 1.0 ?
SVN revision: 59385
Use isfinite() if available, otherwise use finite() on
compilers != vc++, otherwise use _finite()
and a bit of formatting too (i know, it's bad)
SVN revision: 58566
Gustavo Sverzut Barbieri
Iván Briano
Youness Alaoui
Vincent Torri
Christopher Michael
Cedric BAIL
Mike McCormack
Naruto TAKAHASHI
Rafael Antognolli
Ulrich Eckhardt
Carsten Haitzler
Sebastian Dransfeld
Eric Schuele
Michael Jennings