WWW-www.enlightenment.org pushed a commit to branch master. http://git.enlightenment.org/website/www-content.git/commit/?id=94ea8ed381dfcdb2114c4c843c4317a5529d9598
commit 94ea8ed381dfcdb2114c4c843c4317a5529d9598 Author: Xavi Artigas <[email protected]> Date: Tue Dec 5 06:02:15 2017 -0800 Wiki page porting-guide.md changed with summary [Added UI Sizing] by Xavi Artigas --- pages/develop/guides/c/porting-guide.md.txt | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/pages/develop/guides/c/porting-guide.md.txt b/pages/develop/guides/c/porting-guide.md.txt index 71bb70d2c..66548566a 100644 --- a/pages/develop/guides/c/porting-guide.md.txt +++ b/pages/develop/guides/c/porting-guide.md.txt @@ -4,12 +4,12 @@ # EFL C Porting Guide # -This document highlights the main differences between the original EFL API (henceforth the *Legacy API*) and the new EFL API based on Eo objects (dubbed *Unified API*). The Unified API was introduced in EFL 1.22, around December 2017. +This document highlights the main differences between the original EFL API (known from now on as *Legacy API*) and the new EFL API based on Eo objects (dubbed *Unified API*). The Unified API was introduced in EFL 1.22, around December 2017. -Both APIs can be used simultaneously but support for the Legacy version will be dropped in the future. As such any new code should use the Unified API. +Both APIs can be used simultaneously, but support for the Legacy one will be dropped in the future, and therefore usage of the Unified API is strongly recommended in new code. > **NOTE:** -> Currently the Legacy API has not been completely removed. Enabling the Unified API requires defining two compilation symbols, ``EFL_EO_API_SUPPORT`` and ``EFL_BETA_API_SUPPORT``, as you can see in the tutorials and examples. +> Meanwhile the Legacy API is not completely removed, enabling the Unified API requires defining two compilation symbols, ``EFL_EO_API_SUPPORT`` and ``EFL_BETA_API_SUPPORT``, as can be seen in the tutorials and examples. ## Main Loop ## @@ -21,7 +21,7 @@ Programming guides: [Unified EFL](/develop/guides/c/core/main-loop.md#Timers), [ * The timer callback is registered with ``efl_event_callback_add(timer_object, EFL_LOOP_TIMER_EVENT_TICK, ...)``. -* Timers are always periodic. The callback does not return ``ECORE_CALLBACK_RENEW`` or ``ECORE_CALLBACK_CANCEL`` any more. If you want a one-shot timer remove it from the callback after it has fired once. +* Timers are always periodic. The callback does not return ``ECORE_CALLBACK_RENEW`` or ``ECORE_CALLBACK_CANCEL`` anymore. If you want a one-shot timer, remove it from the callback after it has fired once. * ``ecore_timer_interval_set/get()`` -> ``efl_loop_timer_interval_set/get()`` @@ -57,4 +57,14 @@ Programming guides: [Unified EFL](/develop/guides/c/core/main-loop.md#Idlers), [ * ``ecore_idler_exiter_add()`` -> ``efl_event_callback_add(loop_object, EFL_LOOP_EVENT_IDLE_EXIT, ...)`` -* ``ecore_idler_*()`` methods should not be used in new code. \ No newline at end of file +* ``ecore_idler_*()`` methods should not be used in new code. + +## User Interface ## + +### Sizing ### + +Programming guides: [Unified EFL](/develop/guides/c/ui/sizing.md), [Legacy EFL](/develop/legacy/samples/elm_min_size_control) + +* ``evas_object_size_hint_min_set/get()`` -> ``efl_gfx_size_hint_min_set/get()`` + +* ``evas_object_size_hint_max_set/get()`` -> ``efl_gfx_size_hint_max_set/get()`` --
