Enlightenment CVS committal
Author : sleuth
Project : web
Module : e
Dir : web/e/pages
Modified Files:
faq.html
Log Message:
Little FAQ proofreading.
Kevin Brosius <cobraATcompuserveDOTcom>
===================================================================
RCS file: /cvsroot/enlightenment/web/e/pages/faq.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -3 -r1.42 -r1.43
--- faq.html 15 Oct 2003 08:20:11 -0000 1.42
+++ faq.html 18 Oct 2003 17:21:52 -0000 1.43
@@ -171,8 +171,8 @@
</td></tr></table><table width="100%"><tr><td class="newsbody">
The Enlightenment Project is known for its window manager, but even more powerful
are the tools used to build that window manager. Enlightenment DR15 and DR16 were
-based around the Imlib library created by Rasterman to provide greater flexability,
-speed and functionlity over the conventional image libraries of the time. As the
+based around the Imlib library created by Rasterman to provide greater flexibility,
+speed and functionality over the conventional image libraries of the time. As the
window manager has grown, so has its need for more powerful libraries to draw on.
In DR17s development cycle more than 14 libraries have been created, and 9 are
currently grouped together to form the basis of the applications and window manager
@@ -189,18 +189,18 @@
Oct 27th 2000. At that time work was already well underway toward DR17, Imlib2 1.0
was released
on Oct 16th 2000 and EVAS v0.0.1 was released on Oct 24th 2000. Since that time the
EFL has
grown into a mature suite of libraries which are now capable of supporting the
applications and
-window manager for Enlightenments DR17 release. In the interum we saw alot of people
and code come
-and go. GEVAS was a created to use EVAS with GTK, Eprog simplified EVAS, Ebits
became the theming
+window manager for Enlightenments DR17 release. In the interim we saw a lot of
people and code come
+and go. GEVAS was a created to use EVAS with GTK, Eprog simplified EVAS, Ebits
became the themeing
and interface library for E applications, Etcher and Ebony were created as tools for
creating Ebit themes
and backgrounds, EFSD was written to support the file management for E which grew out
of a prototype (EFM)
that worked with DR16, not to mention an advanced prototype of the window manager
itself! But as
the code matured and we moved closer to what we wanted DR17 to become it became clear
that many of
-the componants had already been pushed beyond their initial design and it was clear
that they would need
-to be replaced. The debates raged on whether to release what was there or start
rewritting
-in order to get things done right the first time. As it should be, Raster descided
he would not release
-code that would just need to be immediately replace and that we'd need to get it
right. And so
+the components had already been pushed beyond their initial design and it was clear
that they would need
+to be replaced. The debates raged on whether to release what was there or start
rewriting
+in order to get things done right the first time. As it should be, Raster decided he
would not release
+code that would just need to be immediately replaced and that we'd need to get it
right. And so
EVAS 0.6.0 gave way to a rewrite known for a short time as EVAS2, later renamed back
to EVAS 1.0. Ebits
-gave way to it's rewrite renamed to Edje, which ment that applications using Ebits
were no longer needed (Etcher and
+gave way to it's rewrite renamed to Edje, which meant that applications using Ebits
were no longer needed (Etcher and
Ebony). EET was developed to more efficiently handle many of the tasks Edb was being
used for, namely
packing theme data and images. And other libraries such as EWL and Etox went along
for the ride evolving
with EVAS. Ecore was built to tie everything together and thus displaced Eprog. And
now that the
@@ -208,13 +208,13 @@
</p>
<p>
-We know it has been a long frustrating wait for users and we appreciate everyones
patiences. Enlightenment
+We know it has been a long frustrating wait for users and we appreciate everyones
patience. Enlightenment
has a long proud history of producing the best ahead-of-it's-time eye-candy on the
planet that is emulated
for years to come, and we have no desire to release a half assed product just to make
people happy for 2 or 3
-days untill they start complaining. The results will be well worth the wait. And if
your a developer
-there is plenty of toys for you to play with now. If you aren't a developer you'll
find no better or more
+days until they start complaining. The results will be well worth the wait. And if
you're a developer
+there are plenty of toys for you to play with now. If you aren't a developer you'll
find no better or more
inviting place to start learning than with the EFL. The work being done to make the
next generation of the Enlightenment
-Window Manager will bring alot more than just some pretty borders around your Eterm,
it will drive
+Window Manager will bring a lot more than just some pretty borders around your Eterm,
it will drive
the development of graphical applications industry wide for several years to come.
</p>
</td></tr></table>
@@ -222,14 +222,14 @@
<p><table width="100%"><tr><td class="newstitle">
Is the EFL portable?
</td></tr></table><table width="100%"><tr><td class="newsbody">
-Extremely! Primary developement of the Enlightenment Foundation Libraries is
currently
+Extremely! Primary development of the Enlightenment Foundation Libraries is
currently
being done on Linux/X86. Other platforms that are currently in use for development
include Linux/PPC, Linux/Sparc, Solaris/Sparc, FreeBSD, and OSX. PDAs can use the EFL
on Qtopia (Zaurus) and most iPaq Linux distributions.
</td></tr></table>
<p><table width="100%"><tr><td class="newstitle">
-What is the diffrence between E 17 and DR17 or 0.17? What does DR mean?
+What is the difference between E 17 and DR17 or 0.17? What does DR mean?
</td></tr></table><table width="100%"><tr><td class="newsbody">
DR stands for Development Release. The current stable window manager can be called
any of the following, E 0.16.5, E 16.5 or DR16.5 it's all the same thing. Which you
@@ -267,15 +267,15 @@
I'm tired of the old themes! Isn't there anything new?
</td></tr></table><table width="100%"><tr><td class="newsbody">
The Enlightenment Project currently has 2 <a href="team.html">team themers</a> who
have been providing
-new <b>origonal</b> themes for DR16. <a
href="http://pixelhead.lostmypants.net/";>Pixelhead</a>
-and <a href="http://tokyo.cored.org/";>Tokyo</a>. Both have been created themes that
will make your friends
-who stopped using E a long time ago drewl with envy. Enlightenment is still the king
of the eye-candy universe.
+new <b>original</b> themes for DR16. <a
href="http://pixelhead.lostmypants.net/";>Pixelhead</a>
+and <a href="http://tokyo.cored.org/";>Tokyo</a>. Both have been creating themes that
will make your friends
+who stopped using E a long time ago drool with envy. Enlightenment is still the king
of the eye-candy universe.
</td></tr></table>
<p><table width="100%"><tr><td class="newstitle">
Is there a manual or HOWTO on building themes?
</td></tr></table><table width="100%"><tr><td class="newsbody">
-Yes, a basic set of documentents can be found thanks to Tokyo and the
+Yes, a basic set of documents can be found thanks to Tokyo and the
<a href="www.etherdoxproject.org">EtherDox Project</a> setup by Peter "monkiboi"
Watts.
Pixelhead has also written a document on
<a href="http://pixelhead.lostmypants.net/dr16borders.html";>creating DR16 borders</a>
that is very good.
@@ -294,7 +294,7 @@
</td></tr></table><table width="100%"><tr><td class="newsbody">
We're not exactly sure why, but Freshmeat renames (theme).etheme's to (theme).tar.gz
or (theme).tgz.
In most cases you simply need to rename the file from XXX.tgz to XXX.etheme and copy
it into your
-themes directory. There are one or two themes out there that actually are
distrubuted as tarballs because
+themes directory. There are one or two themes out there that actually are
distributed as tarballs because
they require special fonts, so when you untar those themes you should get an etheme,
a font, and possibly a README.
If you unpack and get a directory named after the theme then just rename it.
</td></tr></table>
@@ -311,10 +311,10 @@
<p><table width="100%"><tr><td class="newstitle">
Is DR16 still in development?
</td></tr></table><table width="100%"><tr><td class="newsbody">
-Yes! DR16 went thru a long hybernation as it's developers devoted all their
-efforts toward DR17. While there were still room for improvement in
+Yes! DR16 went thru a long hibernation as it's developers devoted all their
+efforts toward DR17. While there was still room for improvement in
DR16 the primary focus shifted and DR16 was left without an owner or maintainer.
-Patches were commited from time to time, but it wasn't untill the first half
+Patches were commited from time to time, but it wasn't until the first half
of 2003 that Kim Woelders (kwo) took up the call to become the DR16 owner and
began devoting time to working on improvements and bug fixes. DR16.6 is drawing
close toward release as he continues to work on it.
@@ -463,6 +463,7 @@
FAM is the File Alteration Monitor, a server which reports
file modification events to clients. Imon is a Linux kernel patch
to improve performance, using it is highly recommended.
+Without Imon, FAM can run in polling mode, but performance is slower.
Read more about it at <a href="http://oss.sgi.com/projects/fam";>SGI</a>.
</td></tr></table>
@@ -503,7 +504,7 @@
When run with hardware acceleration Evas uses the GL libraries on your
system; this means that if you have Mesa installed then Evas will use
the Mesa GL liberties. Mesa however only provides software acceleration
-and therefore will run slow compared to Evas's in-built software mode. If
+and therefore will run slow compared to Evas's built-in software mode. If
you have a video card that supports hardware acceleration then you should
attempt to get the manufacturers own GL drivers for your computer and
install them making sure that none of the Mesa libraries are left behind
@@ -539,8 +540,8 @@
</td></tr></table><table width="100%"><tr><td class="newsbody">
When used in software mode, Evas will use a lot of CPU. In hardware
mode however it depends on your OpenGL drivers. What a lot of drivers
-do is limit buffer buffer swaps to vertical blanking gaps only. This
-means that the buffers wont be swapped until the vertical blanking gap
+do is limit buffer swaps to vertical blanking gaps only. This
+means that the buffers won't be swapped until the vertical blanking gap
is reached, however since there is no method of using interrupts under
Linux/X the GL drivers have to poll in a tight loop waiting for the gap.
Also if the GL libraries are accessing the GFX hardware directory then if the
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
enlightenment-cvs mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-cvs
