|Age||Commit message (Collapse)||Author|
Since we're now going to be shipping some eo classes as stable,
there is no point in keeping the eo api behind a macro, and it
should be enabled by default. Another case is beta classes, but
those are behind the EFL_BETA_API_SUPPORT guard.
This also changes includes around the place where things are
clearly broken (such as an included header needing something
from another header but that other header being guarded, notably
efl_ui_widget.h needing focus manager but focus manager being
behind beta in Elementary.h)
Reviewers: zmike, cedric, bu5hm4n, stefan_schmidt, segfaultxavi
Reviewed By: cedric, segfaultxavi
Subscribers: segfaultxavi, #reviewers, #committers
Differential Revision: https://phab.enlightenment.org/D8322
For clarity, since there are all kinds of maps, including a navigation map
Also, corrected some misspellings.
Test Plan: make && make check && make examples all work
Reviewers: cedric, zmike, bu5hm4n
Reviewed By: cedric
Subscribers: Jaehyun_Cho, #reviewers, #committers
Maniphest Tasks: T7564
Differential Revision: https://phab.enlightenment.org/D7974
Reviewers: cedric, devilhorns
Differential Revision: https://phab.enlightenment.org/D5103
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D5075
This is more in line with the other "absolute" APIs.
This implements an entirely new API model for Evas Map by relying
on high-level transformations on the object rather than an external
Evas_Map structure that needs to be constantly updated manually.
The implementation relies on Evas_Map.
To rotate an object all you need to do now is
efl_gfx_map_rotate(obj, 45.0, NULL, 0.5, 0.5);
Or with a C++ syntax:
obj.rotate(45.0, NULL, 0.5, 0.5);
Or even simply (with default arguments):
The map transformation functions are:
- translate (new!)
For people browing through the examples, having the opening statement be
concise and consistent will help them more quickly find what they're
Signed-off-by: Bryce Harrington <firstname.lastname@example.org>
Some of the examples had identical opening statements (e.g. the image
object examples). I've tried to give each a unique description defining
what they are demonstrating, but you may want to doublecheck I got these
correct. Of particular note, to me evas-images5.c looks like just a
fixup to evas-images4.c, so I'm not sure what makes these two distinct.
Subscribers: cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D4861
Signed-off-by: Cedric BAIL <email@example.com>
Those are copy & paste & eo-ified versions of the legacy
samples. I did not touch the other legacy APIs, only maps.