enlightenment/www-content
enlightenment
/
www-content
6
0
Fork 2
Code Issues Pull Requests Projects Releases Wiki Activity

Wiki page about-enlightenment.md changed with summary [] by Raster

This commit is contained in:
Carsten Haitzler 2021-12-27 12:33:52 -08:00 committed by www-data
parent 0f881ccd41
commit e58105022d
1 changed files with 15 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
pages/about-enlightenment.md.txt
View File

@ -138,17 +138,28 @@ The underlying philosophy behind Enlightenment is that users should be given as
### Efficiency ###
Enlightenment is designed for efficiency, without sacrificing looks or functionality. The theme files are binary blobs but can be dissected to reveal tools such as *edje_decc*. The same holds true for configuration (*.eet*) files.
Enlightenment is designed for efficiency, without sacrificing looks or functionality. The theme files are binary blobs but can be dissected to reveal tools such as *edje_decc*. The same holds true for configuration (*.cfg*) files that are actually eet archives with serialized data structures.
Emphasis is placed on runtime speed and efficiency over forcing users to edit the configuration over and over prior to running a program. Most Enlightenment options can easily be configured through a GUI although there are also tools for importing and editing text files for dedicated programmers.
Emphasis is placed on runtime speed and efficiency over forcing users to edit the configuration. Most Enlightenment options can easily be configured through a GUI although there are also tools for importing and editing text files for dedicated programmers.
Enlightenment also has advanced error detection routines. When problems are detected, users are offered the choice either to debug or to restart from where they left off without losing any data. If you've installed *gdb* and activated debug options, Enlightenment also saves a crash log file to *~/.e-crashdump.txt*.
Enlightenment is also designed to run on a variety of platforms from budget smartphones to multi-core servers with two screens. The development process is designed to accommodate older and slower machines as well as the most recent. For this reason, compositing in Enlightenment is still very efficient even without a GPU.
Enlightenment is also designed to run on a variety of platforms from budget smartphones to multi-core servers with two screens. The development process is designed to accommodate older and slower machines as well as the most recent. For this reason, compositing in Enlightenment is still very efficient even without a GPU.
A quick comparison of memory usage between major desktops on Linux shows Enlightenment at the bottom of the footprint. Keep in mind that it is also a full compositing desktop, thus adding a large extra footprint just for that. The below is the memory usage above a basic empty Xorg session (which would be a base footprint to get anything displayed that every environment needs) (measured on Arch Linux on 27/12/2021). All environments are freshly logged in on a freshly booted VM, with their default configuration with the user's home directory opened up in the native file manager and one native terminal emulator window opened up.
| Software | Version | Memory | Compositing |
|---------------|---------|--------|-------------|
| LXDE | | 111M | No |
| Enlightenment | 0.25 | 124M | Yes |
| LXQT | | 157M | No |
| XFCE | 4.16 | 225M | Yes |
| GNOME | 41.0 | 425M | Yes |
| KDE | 5.23 | 475M | Yes |
### Libraries ###
Over 80% of the Enlightenment Project's code has its own stand-alone libraries, which allows it to function as much more than a simple window manager. Developers emphasise building libraries first over adding single features. This provides valuable resources for other developers who may want to reuse those libraries for other projects.
Over 80% of the Enlightenment Project's code is in its own stand-alone libraries, which allows it to function as much more than a simple window manager. Developers emphasize building libraries first over adding single features. This provides valuable resources for other developers who may want to reuse those libraries for other projects.
## Porting ##