WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=3850f793106ae9f84b37f398a4faad9a6060ef15
commit 3850f793106ae9f84b37f398a4faad9a6060ef15
Author: Henrik Danielsson <h.daniels...@gmail.com>
Date: Wed Apr 15 08:04:24 2015 -0700
Wiki page start changed with summary [Added missing "the" and a comma.] by
Henrik Danielsson
---
pages/start.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pages/start.txt b/pages/start.txt
index 618b85a..b35b55f 100644
--- a/pages/start.txt
+++ b/pages/start.txt
@@ -22,7 +22,7 @@ We still primarily support Linux for Enlightenment, but there
is some effort (ba
In the process of developing a Window Manager, A set of libraries were
developed in order to achieve that goal. These libraries are known collectively
as [[:about-efl|EFL]]. They cover a range of functionality from main-loop, to
graphics, scene graphs, networking, widgets, data storage, IPC and much more.
-We now are starting to pull in bindings support directly into EFL. We are
working on having bindings auto-generated for C++, Lua and Javascript
(v8/node.js). We also would like to pull in our Python bindings in future so we
can support as many languages as possible and keep them up to date.
+We now are starting to pull in bindings support directly into EFL. We are
working on having bindings auto-generated for C++, Lua and Javascript
(v8/node.js). We also would like to pull in our Python bindings in the future
so we can support as many languages as possible and keep them up to date.
For our libraries, our primary development environment is Linux, but we make
an effort to support the BSDs as fully as possible, as well as OSX and Windows.
@@ -38,7 +38,7 @@ We eat our own dog food. We use our libraries not just to
make [[:about-enlighte
We have some of the usual suspects like a [[:about-terminology|terminal
emulator]], a [[:about-rage|video player]], and even the start of an IDE.
-Even [[http://www.tizen.org|native Tizen applications]] use EFL for their
development because we have focused on remaining lean and still featureful.
Unlike many traditional toolkits, we have based ourselves around a scene graph
from the ground up, making EFL very different in nature, yet allowing us to
seamlessly switch from software rendering to OpenGL or any other mechanism that
can be put in a render engine for the canvas scene graph engine we call Evas as
well as layer widgets and o [...]
+Even [[http://www.tizen.org|native Tizen applications]] use EFL for their
development because we have focused on remaining lean and still featureful.
Unlike many traditional toolkits, we have based ourselves around a scene graph
from the ground up, making EFL very different in nature, yet allowing us to
seamlessly switch from software rendering to OpenGL or any other mechanism that
can be put in a render engine for the canvas scene graph engine we call Evas,
as well as layer widgets and [...]
{{:shot-edi.png?nolink&240 }}
--
