Some examples need ecore, ecore-evas and edje to demonstrate its
functionality. If --enable-build-examples is used, these dependencies are
required. This commit disables the examples build if they are not found
in the system.
TODO: improve efl_examples.m4 and use it in evas build too - I'll work on
that soon.
SVN revision: 60609
Also remove references to examples that don't exist anymore.
More examples are going to be explained, and removing them from Ecore.h
will improve the readability of that file. This is the same that was
done to Elementary.
I'm going to move all the examples reference to this file, and should
have them being pointed by functions that use them too.
SVN revision: 60598
To: enlightenment-devel@lists.sourceforge.net
Subject: Re: [E-devel] E SVN: raster trunk/edje/src/lib
Date: Wed, 22 Jun 2011 15:32:41 +0200 (CEST)
On Wed, 22 Jun 2011, Enlightenment SVN wrote:
[...]
i would have prefered a beautiful colored spank message with ERR
Vincent
SVN revision: 60591
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
This work was first started by Vincent Torri and Nicolas Aguirre.
I took the necessary time to make it work and included inside
emotion with Samsung sponsorship.
This code is not yet completly clean and fast, but it work and
make it possible to add more speed improvement later. This was
a needed infrastructure work.
SVN revision: 60532
Subject: [E-devel] [PATCH] Add Ecore_IMF API to set the attirbute of
input panel
For supporting virtual keyboard, I'd like to add
ecore_imf_context_input_panel_enabled_set/get APIs. The detail description of
each API is included in the patch file as doxygen format.
If input panel is in 'enabled' status, the immodule will request to
show the input panel automatically When the input widget such as entry is
clicked or has focus. In some case, application programmers want to control
the input panel manually (not automatically), so I implement this API.
SVN revision: 60504
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
Cedric BAIL
Michael Jennings
Rafael Antognolli
Christopher Michael
Jonas M. Gastal
Vincent Torri
Carsten Haitzler
Bruno Dilly
Gustavo Lima Chaves
Iván Briano
Tom Hacohen
Jihoon Kim
Ulrich Eckhardt
Lucas De Marchi
ChunEon Park