summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorXavi Artigas <xavierartigas@yahoo.es>2018-08-21 03:29:12 -0700
committerapache <apache@e5-web1.enlightenment.org>2018-08-21 03:29:12 -0700
commit83c867428a884a2e0a633f4bc5f918467cc3a974 (patch)
tree5227e4b1ecab6b05f93835331007ed12e1994e69 /pages
parent1dec9516e9071e00444350f553379a4034656d24 (diff)
Wiki page unified-and-legacy.md changed with summary [Formatting and typos] by Xavi Artigas
Diffstat (limited to 'pages')
-rw-r--r--pages/develop/unified-and-legacy.md.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/pages/develop/unified-and-legacy.md.txt b/pages/develop/unified-and-legacy.md.txt
index 39aa47043..4d4b8de7f 100644
--- a/pages/develop/unified-and-legacy.md.txt
+++ b/pages/develop/unified-and-legacy.md.txt
@@ -1,19 +1,19 @@
1# Unified and Legacy APIs together 1# Unified and Legacy APIs together
2 2
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. 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 interchangeable.
4 4
5## Object Compatibility 5## Object Compatibility
6 6
7Our main approach to ensure compatibility is making sure that our legacy API can work with Unified EFL objects. 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. 8That means that an `Eo *` created with the new Unified API will work with the equivalent APIs from the legacy API.
9 9
10For example: 10For example:
11 11
12 * Efl_Canvas objects can be passed to evas_object_* methods 12 * `Efl_Canvas` objects can be passed to `evas_object_*` methods
13 * Efl_Canvas_Layout objects can be passed to edje_object_* methods 13 * `Efl_Canvas_Layout` objects can be passed to `edje_object_*` methods
14 * Efl_Ui objects work with elm_object_* methods 14 * `Efl_Ui` objects work with `elm_object_*` methods
15 15
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. 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.
17 17
18## Combined Releases 18## Combined Releases
19 19