Pages for both Etcher and Ebits, including a screenshot..........

Still preliminary, but they should be a good starting point for both
pgaes.


SVN revision: 5648

e/data/ebits.html

@@ -1,8 +1,18 @@
 @top@
 @start@
 <p class="contenttitle">Ebits</p>
-<p>Ebits is a library that can be used to apply theming to your application.  Ebit files containing image and theming data can be used to spruce up any application.</p>
-<p>Ebit file are created using <a href="etcher.html">Etcher</a>.</p>
+<p>Theme-ing has come a long way.  At one point in time (and in some cases still) themeablility was mearly the ability to change th
+e default colors of the interface.  Later came the idea of replacing default objects with new modified ones.  But Enlightenment has
+ always been on the front lines, defining with each update what it is to theme.  Through this journey its come to be that the theme
+ is an integral part of the windowing enviroment, and is becoming more and more complex all the time.  A common method of modern th
+eming is to provide a pool of images which are then "bound" together in a configuration to define size, padding, location, state an
+d so on.  However this has become increasingly complex to manage, not to mention that theme-ing is no longer just something for "ey
+e candy", but integral to the feel of your application.  The solution was <a href="ebits.html">Ebits</a>, which allows us a method 
+to bind every kind of information possible for a theme into singular file.  This information includes size, position, context, stat
+e, cursors, fonts, and a whole lot more.  These files are created with <a href="etcher.html">Etcher</a>.</p
+
+<p>On of the reasons Ebits is so functional is due to its input file format, bit db's.  Ebit files are actually <a href="edb.html">Edb's</a> which can contain both binary and ascii data.  Each Ebits file (named <i>file</i>.bits.db) contains all the images and configuration data for that bit.  This removes the need for the specialized tarballs of old, and add alot of flexablility that wouldn't exsists with it being built on <a href="edb.html">Edb</a>.
+
 <p>Ebits developers include: The Rasterman, Carlos Puchol, and Mark Bainter.  Their contact details can be found on the 
 <a href="team.html">team page</a>.</p>
 @end@

e/data/etcher.html

@@ -1,6 +1,16 @@
 @top@
 @start@
 <p class="contenttitle">Etcher</p>
-<p>Empty page.</p>
+<p>Theme-ing has come a long way.  At one point in time (and in some cases still) themeablility was mearly the ability to change the default colors of the interface.  Later came the idea of replacing default objects with new modified ones.  But Enlightenment has always been on the front lines, defining with each update what it is to theme.  Through this journey its come to be that the theme is an integral part of the windowing enviroment, and is becoming more and more complex all the time.  A common method of modern theming is to provide a pool of images which are then "bound" together in a configuration to define size, padding, location, state and so on.  However this has become increasingly complex to manage, not to mention that theme-ing is no longer just something for "eye candy", but integral to the feel of your application.  The solution was <a href="ebits.html">Ebits</a>, which allows us a method to bind every kind of information possible for a theme into singular file.  This information includes size, position, context, state, cursors, fonts, and a whole lot more.  These files are created with <a href="etcher.html">Etcher</a>.</p>
+
+<p><img src="img/etcher.png"></p>
+
+<p>Using Etcher we can sew various images together, and then define how all these images fit together.  Please understand that Etcher is <b>not</b> a drawing program.  To begin in Etcher you should create a number of graphics in your favorite graphics application, such as <a href="http://www.gimp.org">The GIMP</a>.  To create a window theme (or <b>bit</b>) we should, in our graphics app, create images to be used for the title bar, the iconize button, the close button, and various window borders.  Then we can open Etcher and import these images.  By placing the images around the workspace you can define how the images should fit together, how they should move together, and how they should react.  We can go so far as to define clicked states, selected states, unselected states, and more.  Once you have the bit set up the way you think you'd like it you can save it to a <b>bit.db</b> file.  These bit.db files can be used by any application that uses the Ebits library.</p>
+
+<p>With Ebits and Etcher, the possibilities for a unique look and feel for your application are limited to your imagination, not a color spectrum.</p>
+
+<p>Etcher's primary developers are The Rasterman and Christian "cK" Kreibich.  Their contact details can be found on the 
+<a href="team.html">team page</a>.</p>
+
 @end@
 @bottom@

e/pages/ebits.html

@@ -144,8 +144,18 @@
   <td class="content" valign="top" align="center" width="100%">
 
 <p class="contenttitle">Ebits</p>
-<p>Ebits is a library that can be used to apply theming to your application.  Ebit files containing image and theming data can be used to spruce up any application.</p>
-<p>Ebit file are created using <a href="etcher.html">Etcher</a>.</p>
+<p>Theme-ing has come a long way.  At one point in time (and in some cases still) themeablility was mearly the ability to change th
+e default colors of the interface.  Later came the idea of replacing default objects with new modified ones.  But Enlightenment has
+ always been on the front lines, defining with each update what it is to theme.  Through this journey its come to be that the theme
+ is an integral part of the windowing enviroment, and is becoming more and more complex all the time.  A common method of modern th
+eming is to provide a pool of images which are then "bound" together in a configuration to define size, padding, location, state an
+d so on.  However this has become increasingly complex to manage, not to mention that theme-ing is no longer just something for "ey
+e candy", but integral to the feel of your application.  The solution was <a href="ebits.html">Ebits</a>, which allows us a method 
+to bind every kind of information possible for a theme into singular file.  This information includes size, position, context, stat
+e, cursors, fonts, and a whole lot more.  These files are created with <a href="etcher.html">Etcher</a>.</p
+
+<p>On of the reasons Ebits is so functional is due to its input file format, bit db's.  Ebit files are actually <a href="edb.html">Edb's</a> which can contain both binary and ascii data.  Each Ebits file (named <i>file</i>.bits.db) contains all the images and configuration data for that bit.  This removes the need for the specialized tarballs of old, and add alot of flexablility that wouldn't exsists with it being built on <a href="edb.html">Edb</a>.
+
 <p>Ebits developers include: The Rasterman, Carlos Puchol, and Mark Bainter.  Their contact details can be found on the 
 <a href="team.html">team page</a>.</p>
 </td>

e/pages/etcher.html

@@ -144,7 +144,17 @@
   <td class="content" valign="top" align="center" width="100%">
 
 <p class="contenttitle">Etcher</p>
-<p>Empty page.</p>
+<p>Theme-ing has come a long way.  At one point in time (and in some cases still) themeablility was mearly the ability to change the default colors of the interface.  Later came the idea of replacing default objects with new modified ones.  But Enlightenment has always been on the front lines, defining with each update what it is to theme.  Through this journey its come to be that the theme is an integral part of the windowing enviroment, and is becoming more and more complex all the time.  A common method of modern theming is to provide a pool of images which are then "bound" together in a configuration to define size, padding, location, state and so on.  However this has become increasingly complex to manage, not to mention that theme-ing is no longer just something for "eye candy", but integral to the feel of your application.  The solution was <a href="ebits.html">Ebits</a>, which allows us a method to bind every kind of information possible for a theme into singular file.  This information includes size, position, context, state, cursors, fonts, and a whole lot more.  These files are created with <a href="etcher.html">Etcher</a>.</p>
+
+<p><img src="img/etcher.png"></p>
+
+<p>Using Etcher we can sew various images together, and then define how all these images fit together.  Please understand that Etcher is <b>not</b> a drawing program.  To begin in Etcher you should create a number of graphics in your favorite graphics application, such as <a href="http://www.gimp.org">The GIMP</a>.  To create a window theme (or <b>bit</b>) we should, in our graphics app, create images to be used for the title bar, the iconize button, the close button, and various window borders.  Then we can open Etcher and import these images.  By placing the images around the workspace you can define how the images should fit together, how they should move together, and how they should react.  We can go so far as to define clicked states, selected states, unselected states, and more.  Once you have the bit set up the way you think you'd like it you can save it to a <b>bit.db</b> file.  These bit.db files can be used by any application that uses the Ebits library.</p>
+
+<p>With Ebits and Etcher, the possibilities for a unique look and feel for your application are limited to your imagination, not a color spectrum.</p>
+
+<p>Etcher's primary developers are The Rasterman and Christian "cK" Kreibich.  Their contact details can be found on the 
+<a href="team.html">team page</a>.</p>
+
 </td>
 <td class="border-r" width="25"><img src="img/empty.gif" height="1" width="25" alt=""></td>
 </tr>