summaryrefslogtreecommitdiff
path: root/pages/about-efl.txt
diff options
context:
space:
mode:
authorapache <apache@e5-web1.enlightenment.org>2015-04-07 19:53:56 -0700
committerapache <apache@e5-web1.enlightenment.org>2015-04-07 19:53:56 -0700
commit55b9febfb0695f785f5d6231ee5e348fa11b7249 (patch)
treeab9ac3afdd680529f8fb85f9da9798a395638a1a /pages/about-efl.txt
parent334508f1da15abd40e59fb43e952dd7c4660874f (diff)
Wiki page about-efl changed with summary [] by chris
Diffstat (limited to 'pages/about-efl.txt')
-rw-r--r--pages/about-efl.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/pages/about-efl.txt b/pages/about-efl.txt
index c194c3b..e7078e1 100644
--- a/pages/about-efl.txt
+++ b/pages/about-efl.txt
@@ -12,16 +12,16 @@ yourself. Elementary is about as high up as you get, while you still
12access layers below it for day to day things as there is no need for 12access layers below it for day to day things as there is no need for
13it to wrap things that work perfectly well as-is. 13it to wrap things that work perfectly well as-is.
14 14
15All of EFL exposes its APIs by default in C, with sseveral bindings 15All of EFL exposes its APIs by default in C, with several bindings
16available. We are now also working on supporting bindings for various 16available. We are now also working on supporting bindings for various
17language as first-class-citizens in EFL by auto-generating the 17language as first-class-citizens in EFL by auto-generating the
18bindings directly from our new object orientation infrastrucutre for 18bindings directly from our new object orientation infrastructure for
19C. We stick to C mostly because the libraries have been around for a 19C. We stick to C mostly because the libraries have been around for a
20long time, were originally written in C and the developers who write 20long time, were originally written in C and the developers who write
21the libraries perfer C. We add OO features in C with tools and 21the libraries prefer C. We add OO features in C with tools and
22infrastructure where needed. Also moving from C would limit the 22infrastructure where needed. Also moving from C would limit the
23audience. C programmrs won't be able to access a C++ API (whereas a 23audience. C programmers won't be able to access a C++ API (whereas a
24C++ programemr can access both C and C++). That is partly why we aim 24C++ programmer can access both C and C++). That is partly why we aim
25to auto-generate bindings so programmers of various languages can get 25to auto-generate bindings so programmers of various languages can get
26native-like APIs for their chose language from the same core EFL API 26native-like APIs for their chose language from the same core EFL API
27set. 27set.
@@ -38,9 +38,9 @@ components are:
38|Efreet |Freedesktop.org standards handling | 38|Efreet |Freedesktop.org standards handling |
39|Eldbus |D-Bus glue and handling | 39|Eldbus |D-Bus glue and handling |
40|Embryo |Tiny VM and compiler based on Pawn | 40|Embryo |Tiny VM and compiler based on Pawn |
41|Eeze |Device enumation and access library | 41|Eeze |Device enumeration and access library |
42|Emotion |Video decode wrapping, glue and abstraction | 42|Emotion |Video decode wrapping, glue and abstraction |
43|Ethumb |Thhumbnailing handler | 43|Ethumb |Thumbnailing handler |
44|Ephysics |Physics (bullet) wrapper and Evas glue | 44|Ephysics |Physics (bullet) wrapper and Evas glue |
45|EIO |Asynchronous I/O handling | 45|EIO |Asynchronous I/O handling |
46|Evas Generic Loaders |Extra image loaders for complex image types | 46|Evas Generic Loaders |Extra image loaders for complex image types |