between all ecore graphic engine to ease porting of application and reduce the amount of
specific code per engine. This patch does just that.
All your application should continu to work has previously, if it's not the case
please report any new behaviour regarding mouse and keyboard.
SVN revision: 39505
* fix requirements
* fix configuration on mac os x (problem with automake 1.9) and
add missing values/macro for quartz support
* small typo in ecore_evas_win32 api
* use m4 api in m4 files
SVN revision: 39471
* add vim header
* include config.h when necessary
* fix the order of some include
* move the standard header in ecore_private.h to the source files
I have recompiled all the efl and e17, and e17 seems to work fine with these changes.
If you encounter problems with that commit, let me know.
SVN revision: 38864
We usually want to create an Ecore_Evas and attach an object to it, be
it the background, your smart object that will manage the scene (ie:
edje) and this is replicated everywhere. Not anymore!
ecore_evas_new() and ecore_evas_object_associate() will behave much
like regular toolkits "window-new()" and "window-main-child-add()",
actually it was based on elm_win.c and hopefully we can remove that,
or most of that code and replace with this helper.
I'll add an Evas smart object to handle stacks of objects, that is, it
will be a clipped smart object that on resize it will resize every
child to the same size. This means we can associate this stack object
and add a background and then your stuff on top of it.
SVN revision: 37010
Problem: ecore reference count can drop to zero before
_ecore_evas_async_events_fd is deleted, ecore_shtudown() will finish
all fd handlers and then we would delete a now invalid pointer.
SVN revision: 36055
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
* remove printfs that clutter output
* add efreet file type check - only parse regular files
* chekc mmap returns correctly for MAP_FAILED results
* edje has some stubs for adding script-only objecvts - but nothing useful
right now
SVN revision: 34689
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