One can get engine names with ecore_evas_engines_get() and present
them to its users (from --help, for example) and then give that name
to ecore_evas_new(), that accepts the name, geometry and extra options
as a string.
As I don't have all the engines here, I might have missed something
from those, tested here:
- software_x11
- xrender_x11
- opengl_x11
- directfb
- buffer
SVN revision: 35919
after a make maintainer-clean, with xlib or xcb. e17 also has no problem.
Please report any problem. Thanks
* put xlib and xcb specific code in their own directories inside ecore_x
* fix xcb logic check in autotools and ecore_evas
* update configure.in for detection of ecore_evas with xlib and xcb support,
update ecore_evas accordingly. Note that e17 needs a little fix after that,
it will come in a few minutes
SVN revision: 35188
Added Ecore_IMF module. This module enables different input methods to be
used with Ecore. Input methods modules can be created using the Ecore_IMF
interface.
Added ecore_evas_window_get method to allow input methods to request
the window related to a given Ecore_Evas when available.
SVN revision: 32775
WARNING: this breaks the API, if you rely on ecore_evas_cursor_get(), you
need to get the "Evas_Object *" instead of the filename.
Now the code is smaller and we can handle any object, including Edje.
Patch by Cedric BAIL.
SVN revision: 31818
* add _window_get() functions
* add minimal fullscreen support (not completely finished yet, but should work)
* remove CR character in ecore_evas_win32.c
SVN revision: 31790
Re-apply the previously reverted patch and add (I think) the correct
fix for ecore-config. I haven't tested this extensively, but edje
builds okay with it, so hopefully it's right.
----------------------------------------------------------------------
SVN revision: 28755
to do ssl and al fo ecorE_evas stuff
BUt ecore_* may not be BUILT with that support
so the api stub exists
but it may just return NULL. theres calls to query for support here.
SVN revision: 11957