Enlightenment CVS committal
Author : xenith
Project : web
Module : e
Dir : web/e/data
RCS file: /cvsroot/enlightenment/web/e/data/faq-dr16.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -3 -r1.5 -r1.6
--- faq-dr16.html 1 Sep 2004 23:54:47 -0000 1.5
+++ faq-dr16.html 5 Sep 2004 07:20:27 -0000 1.6
@@ -109,8 +109,8 @@
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 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 was released
-Nov 5th 2003 and development on this series continues.
+began devoting time to working on improvements and bug fixes. DR16.7.1 was
+released on Aug 24, 2004 and development on this series continues.
RCS file: /cvsroot/enlightenment/web/e/data/faq-dr17.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -3 -r1.3 -r1.4
--- faq-dr17.html 1 Sep 2004 23:54:47 -0000 1.3
+++ faq-dr17.html 5 Sep 2004 07:20:27 -0000 1.4
@@ -26,7 +26,11 @@
Why has DR17 taken so long? The DR17 saga.
-The current stable release of the window manager is DR16.5, which was released to the world on 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.
+The current stable release of the window manager is DR16.7.1, which was released
+to the world on Aug 24th 2004. The last stable release was DR16.5, which was
+released to the world on 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.
<p>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 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 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.</p>
<p>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 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 back end is now roughly where it should be work on the replacement for the window manager can occur. </p>