Enlightenment CVS committal
Author : dj2
Project : e17
Module : docs
Dir : e17/docs/cookbook/xml/esmart
Modified Files:
esmart_container_intro.xml esmart_trans_intro.xml
Log Message:
- make a note that EXIT signal hander isn't strictly required if only the
call to ecore_main_loop_quit is being called.
===================================================================
RCS file:
/cvsroot/enlightenment/e17/docs/cookbook/xml/esmart/esmart_container_intro.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -3 -r1.2 -r1.3
--- esmart_container_intro.xml 4 Jul 2004 19:34:31 -0000 1.2
+++ esmart_container_intro.xml 10 Jul 2004 17:53:04 -0000 1.3
@@ -19,7 +19,7 @@
<para>
There is usually a desire while designing an apps UI to group common elements together
and have their layout depend on one another. To this end the Esmart Container
-libary has been created. It has been designed to handle the hard parts of the
+library has been created. It has been designed to handle the hard parts of the
layout, and in the cases where it does not do what you need, the layout portions of
the container are extensible and changeable.
</para>
@@ -222,7 +222,9 @@
</example>
<para>
Next we setup some generic callbacks to be used by the UI. This will be the exit,
destroy
-and resize callbacks. Again, the usual EFL style functions.
+and resize callbacks. Again, the usual EFL style functions. Although the exit
callback is not
+strictly necessary as Ecore itself will call
<function>ecore_main_loop_quit()</function> if
+no handler is registered for this callback.
</para>
<example>
@@ -360,7 +362,7 @@
<para>
Once the directions and alignment are set, the spacing and padding of the container
are
-specified. The padding specifes the space around the outside of the container taking
four
+specified. The padding specifies the space around the outside of the container taking
four
numeric parameters: left, right, top and bottom. The spacing parameter specifies
the space between elements in the container.
</para>
@@ -697,7 +699,7 @@
<para>
After the fonts are defined the main collections are defined. The first collection
is the main portion of the app itself, the "container_ex" group. This group
-specifes the main window of the app. As such it contains the parts for the
background,
+specifies the main window of the app. As such it contains the parts for the
background,
the header, and the header text. These parts are all fairly standard with some
(minimal)
alignment done between them.
</para>
@@ -815,7 +817,7 @@
<para>
The element group specifies how each element of the container is to be
displayed. You will notice that the names given here match up to the
-names seached for in the application code itself while creating the elements.
+names searched for in the application code itself while creating the elements.
</para>
<para>
===================================================================
RCS file: /cvsroot/enlightenment/e17/docs/cookbook/xml/esmart/esmart_trans_intro.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -3 -r1.2 -r1.3
--- esmart_trans_intro.xml 4 Jul 2004 19:34:31 -0000 1.2
+++ esmart_trans_intro.xml 10 Jul 2004 17:53:04 -0000 1.3
@@ -105,7 +105,9 @@
</programlisting>
</example>
<para>
-The exit and del callbacks are the generic ecore callbacks.
+The exit and del callbacks are the generic ecore callbacks. The exit callback isn't
strictly
+necessary, as Ecore will call <function>ecore_main_loop_quit()</function> if no
handler is
+registered, but is included to show how its done.
</para>
<example>
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
enlightenment-cvs mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-cvs
