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
These functions are not contemplated by examples because there is no
meaningfull example(just setting the flags doesn't won't help developers
in understading how to use them) and because their behavior is dependant
on the windowing system.
SVN revision: 62056
This common interface allows engines to provide whole screen
information to users.
Right now just X is implemented and it queries the size of the default
screen. I hope this is fine.
SVN revision: 59761
* Remove vim modelines:
find . -name '*.[chx]' -exec sed -i '/\/\*$/ {N;N;/ \* vim:ts/d}' \{\} \;
find . -name '*.[chx]' -exec sed -i '/\/[\*\/] *vim:/d' \{\} \;
* Remove leading blank lines:
find . -name '*.[cxh]' -exec sed -i '/./,$!d'
If you use vim, use this in your .vimrc:
set ts=8 sw=3 sts=8 expandtab cino=>5n-3f0^-2{2(0W1st0
SVN revision: 50816
Subject: [E-devel] 8bpp xcb evas engine
Hi all,
I've implemented the 8bpp grayscale evas engine. It is based on the 16bpp
engine. It would be nice if someone could review the code and maybe commit
into svn. The patches against evas and ecore are attached.
SVN revision: 50561
I’ve prepared basic patch to add support for custom malloc/free functions for
buffer management. (with changes to api from raster to addd void *data param
to alloc/free callbacks and naming and ordering changes).
SVN revision: 49044
I am attaching another patches for transparent window.
1. Use RGB Visual.
2. Set destination_alpha in ecore_evas for alpha composite in evas.
3. add Function
- Ecore_Evas_Engine_Func->fn_transparent_set
- ecore_evas_transparent_set , ecore_evas_transparent_get
- elm_win_transparent_set, elm_win_transparent_get
SVN revision: 46106
looks broken to me. sdl looks like it could be much more complete - like
multiple sdl windows/instances.
anyway - allow rendering to be manual.
SVN revision: 44938
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
fix doc
* ecore_file/Makefile.am:
add Windows cflags
* ecore_file/ecore_file_private.h:
move Evil.h so that EAPI is correctly defined
* ecore_wince:
make window_new windowed by default. other backend that gdi might have problems.
add title_set and fullscreen_set functions.
do not use aygshell features anymore for fullscreen (it's not free and not always available)
include missing config.h
* ecore_evas:
move Evas.h and Ecore_Getopt.h so that EAPI is correctly defined
add title_set and fullscreen_set functions.
SVN revision: 38540
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
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
Gustavo Sverzut Barbieri
Gustavo Lima Chaves
Jonas M. Gastal
Doyun Kang
Vincent Torri
Carsten Haitzler
Cedric BAIL
Lucas De Marchi
Alexander Kerner
Brett Nash
Lukasz Wrzosek
이상진
xcomputerman
Miculcy Brian
doursse