path: root/pages
diff options
authorAndrew Williams <>2018-01-03 05:16:41 -0800
committerapache <>2018-01-03 05:16:41 -0800
commit3f0d8bf8876dc0df3bf057961882f1ca0637d512 (patch)
tree455b57bba5ba250a9f34534834b9803dd0466fe7 /pages
parent7e84a79ca856cd54f582a71c40d8c59dffdff153 (diff)
Wiki page changed with summary [promotion from playground] by Andrew Williams
Diffstat (limited to 'pages')
1 files changed, 20 insertions, 0 deletions
diff --git a/pages/develop/ b/pages/develop/
new file mode 100644
index 0000000..39aa470
--- /dev/null
+++ b/pages/develop/
@@ -0,0 +1,20 @@
1# Unified and Legacy APIs together
3The process of moving an application from our old stable API to the new Unified EFL may take some time. Enlightenment is probably the largest EFL application so we know how complicated this could be! To ease the transition we are ensuring that the APIs are interchangable.
5## Object Compatibility
7Our main approach to ensure compatibility is making sure that our legacy API can work with Unified EFL objects.
8That means that an Eo* created with the new Unified API will work with the equivalent APIs from the legacy API.
10For example:
12 * Efl_Canvas objects can be passed to evas_object_* methods
13 * Efl_Canvas_Layout objects can be passed to edje_object_* methods
14 * Efl_Ui objects work with elm_object_* methods
16Also the eina and eo namespaces are retained over these versions so you can continue to pass Eina_Bool or Eo* where you previously did.
18## Combined Releases
20For the foreseeable future all EFL releases will contain both the Legacy and the Unified APIs meaning that you can upgrade once you feel that our new APIs are ready for your usage. The benefits of moving over should be compelling, but as usage varies between apps we will continue to support the legacy API for all our users.