WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=3f0d8bf8876dc0df3bf057961882f1ca0637d512
commit 3f0d8bf8876dc0df3bf057961882f1ca0637d512
Author: Andrew Williams <a...@andywilliams.me>
Date: Wed Jan 3 05:16:41 2018 -0800
Wiki page unified-and-legacy.md changed with summary [promotion from
playground] by Andrew Williams
---
pages/develop/unified-and-legacy.md.txt | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/pages/develop/unified-and-legacy.md.txt
b/pages/develop/unified-and-legacy.md.txt
new file mode 100644
index 000000000..39aa47043
--- /dev/null
+++ b/pages/develop/unified-and-legacy.md.txt
@@ -0,0 +1,20 @@
+# Unified and Legacy APIs together
+
+The 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.
+
+## Object Compatibility
+
+Our main approach to ensure compatibility is making sure that our legacy API
can work with Unified EFL objects.
+That means that an Eo* created with the new Unified API will work with the
equivalent APIs from the legacy API.
+
+For example:
+
+ * Efl_Canvas objects can be passed to evas_object_* methods
+ * Efl_Canvas_Layout objects can be passed to edje_object_* methods
+ * Efl_Ui objects work with elm_object_* methods
+
+Also the eina and eo namespaces are retained over these versions so you can
continue to pass Eina_Bool or Eo* where you previously did.
+
+## Combined Releases
+
+For 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.
--
