WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=9fa31cf71c27224d6325f8a94232db100b3952bc
commit 9fa31cf71c27224d6325f8a94232db100b3952bc
Author: Xavi Artigas <xavierarti...@yahoo.es>
Date: Tue Jul 23 02:28:22 2019 -0700
Wiki page start.md changed with summary [Improve Unified and Legacy
consistency] by Xavi Artigas
---
pages/develop/start.md.txt | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/pages/develop/start.md.txt b/pages/develop/start.md.txt
index 5f010d10d..eef397e4b 100644
--- a/pages/develop/start.md.txt
+++ b/pages/develop/start.md.txt
@@ -5,23 +5,23 @@
# Developing with the Enlightenment Foundation Libraries (EFL) #
-The Enlightenment Foundation Libraries (EFL) are designed to build on top of
each other in layers, steadily becoming higher level yet allowing access to
each individual level as they go. Whether you're looking for the types of
low-level helpers contained in the ``Eina`` library or the high-level
abstractions of Elemetary you'll find a wealth of assistance within EFL.
+The Enlightenment Foundation Libraries (EFL) are designed to build on top of
each other in layers, steadily becoming higher level yet allowing access to
each individual level as they go. Whether you're looking for the types of
low-level helpers contained in the ``Eina`` library or the high-level
abstractions of ``Elementary`` you'll find a wealth of assistance within EFL.
More information on EFL can be found on the [About EFL page](/about-efl),
including a breakdown of its various features and components.
-## Current vs. Beta ##
+## Legacy vs. Unified APIs ##
-The documentation on this section of the website is written with a focus on
the next-generation release, currently in beta. While this means that the
documentation is only partial in places, it will get you started with the very
latest revision of EFL and all the new and improved features it brings.
+The documentation on this section of the website is written with a focus on
the next-generation API called **Unified API**, currently rolling out of the
beta stage. While this means that the Unified documentation is only partial in
places, it will get you started with the very latest revision of EFL and all
the new and improved features it brings.
-Documentation on the current version of EFL can be found in the [Legacy
section](legacy/). When working through the documentation on the site, keep in
mind that if a document is located in ``/develop/legacy`` it is referring to
the current release of EFL; if it is located in any other section of
``/develop`` it is referring to the beta release. It is possible to use both
APIs in the same application, information about that is in the [Unified and
Legacy](/develop/unified-and-legacy.md) page.
+Documentation on the **Legacy API** of EFL can be found in the [Legacy
section](legacy/). It is possible to use both APIs in the same application,
although not recommended. Information about that is in the [Unified and
Legacy](/develop/unified-and-legacy.md) page.
-Information on porting software between the current and beta releases of EFL
can be found as part of the [Programming Guides](#Programming_Guides) section.
+Information on porting existing software to the Unified API can be found as
part of the [Programming Guides](#Programming_Guides) section.
## Languages ##
-Developers working with the Enlightenment Foundation Libraries can do so in a
variety of languages. Each of the following documentation categories is split
by language: at present the majority include documentation only for the C
language, with documentation for additional languages to follow.
+Developers working with the Enlightenment Foundation Libraries can do so in a
variety of languages. Each of the following documentation categories is split
by language: at present the majority include documentation only for the C and
C# languages, with documentation for additional languages to follow.
-In all cases, the language to which a particular document applies will be
indicated in the page location: a document in ``/develop/tutorials/c`` will be
for the C language, whereas ``/develop/tutorials/python`` offers alternatives
for Python developers.
+In all cases, the language to which a particular document applies will be
indicated in the page location: a document in ``/develop/tutorials/c`` will be
for the C language, whereas ``/develop/tutorials/csharp`` offers alternatives
for C# developers.
A full list of the languages available is available on the landing page for
each section.
@@ -41,9 +41,9 @@ The [Programming Guides](guides/start.md) are designed to
provide informative ma
## API Reference Documentation ##
-A reference to the features and functions of the beta-release API can be found
in the [API Reference section](api/).
+A reference to the features and functions of the Unified API can be found in
the [API Reference section](api/).
-Those working on the current-release API can find the equivalent documentation
in the [Legacy API Reference section](legacy/api/c/).
+The Legacy API equivalent documentation in the [Legacy API Reference
section](legacy/api/c/).
Please note that, in both cases, the reference documentation is currently
available exclusively for the C programming language.
--
