Enlightenment CVS committal
Author : dresb
Project : e17
Module : docs
Dir : e17/docs/devwithedje/xml
Modified Files:
bookoverview.xml foundations_at_practice.xml
interacting_with_the_objects.xml intro_to_edje.xml
intro_to_gui.xml
Added Files:
introduction_to_widgets.xml
Log Message:
fixed several errors and began a new chapter.
===================================================================
RCS file: /cvs/e/e17/docs/devwithedje/xml/bookoverview.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -3 -r1.1 -r1.2
--- bookoverview.xml 15 Jan 2008 02:33:41 -0000 1.1
+++ bookoverview.xml 20 Jan 2008 14:23:53 -0000 1.2
@@ -53,46 +53,67 @@
<formalpara>
<title>III. The foundations in practice</title>
- This is a practical example of the simplest approach to setting up an Evas
- canvas for display.
+ A practical example of setting up an Evas canvas with the simplest
+ approach, Ecore_Evas.
</formalpara>
<para>
<emphasis>III.I Working with the canvas</emphasis>
- Another example dealing with the inclusion of an Edje object.
+ Including new Edje objects inside the previously setup canvas can be
+ explained with this simple example.
</para>
<para>
<emphasis>III.II Interacting with the objects</emphasis>
- A practical guide through both Edje and plain Ecore's event system.
+ There are different channels for the application to interact with the
+ interface. For the sake of brevity I will include an example of each one to
+ serve as an introduction for the pratical examples to come in the next
+ chapters.
</para>
<!-- New Chapter -->
<formalpara>
<title>IV. Introduction to widgets</title>
- A simple description of what a widget is and what it is useful for along
with
- the limitations presented by common toolkits.
+ Interfaces need to resolve two problems, presenting information to users
+ and taking orders from them. The past chapters presented enough information
+ to solve the first. In the following chapters we will review the second.
+ The widget iself can be seen as a small application inside our interfaces.
+ As an example let's examine the structure of a common widget, the combox.
</formalpara>
<para>
<emphasis>IV.I. The common widget design</emphasis>
- A generic vision of the way the different toolkits design the structure of
- widgets with the corresponding diagram.
+ Revisar el diseño de los widget combox en varias librerias, mostrar las
+ pattern usadas y concluir porque MVC es la mejor (si es que lo es).
</para>
<para>
<emphasis>IV.II. Widget design with Edje</emphasis>
- An explanation about where does Edje fits in the structure mentioned
before,
- and the shortcuts it provides.
+ If the Model View Controller pattern is the choice for developing
+ a widget the place Edje ocuppies becomes quite clear. Mostrar el papel
+ que ocupa Edje, Ecore_Evas y Ecore_ en cada parte del diseño del widget.
+</para>
+
+<para>
+ <emphasis>IV.III. The Enlightenment Widget Library</emphasis>
+ Añadir una introduccion a EWL y añadir mi vision sobre como debeira ser
+ usado en conjunto con Edje destacando claramente que es una opinion
+ personal.
+</para>
+
+<para>
+ <emphasis>IV.III. The Enlightenment ToolKit</emphasis>
+ Añadir una introduccion a ETK y añadir mi vision sobre como debeira ser
+ usado en conjunto con Edje destacando claramente que es una opinion
+ personal.
</para>
<!-- New Chapter -->
<formalpara>
- <title>V. Implementing a widget with Edje</title>
- A brief resume of the previous chapter and the introduction of names
specific
- to Evas, Ecore_Evas and Edje.
+ <title>V. Implementacion del widget</title>
+ Presentar estrucutura inicial del codigo paralelizandola con IV.II
</formalpara>
<para>
===================================================================
RCS file: /cvs/e/e17/docs/devwithedje/xml/foundations_at_practice.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -3 -r1.1 -r1.2
--- foundations_at_practice.xml 15 Jan 2008 02:33:41 -0000 1.1
+++ foundations_at_practice.xml 20 Jan 2008 14:23:53 -0000 1.2
@@ -22,14 +22,14 @@
button.file_set("theme.edj","button")
</programlisting>
- Altough the difference between the code snippets could be written off
- as "sintactic sugar" it serves to demonstrate the structure the EFL C
- API follow. If we dissected the last function call we could split it
- into three groups. First, the class of the object to manipulate,
- <code>edje_object</code>, second, the method to call
<code>file_set</code>
- and third the pointer to the object instance <code>(button,</code>
- along with the parameters <code>"theme.edj","button")</code>. In
- more generic terms:
<code>class_method(instance,parameters)</code>.</para>
+ The differences between the code snippets could be written off as
+ "sintactic sugar" it serves to demonstrate the structure which the
+ EFL C API follows. If we dissected the last function call we could
+ split it into three groups. First, the class of the object to
+ manipulate, <code>edje_object</code>, second, the method to call
+ <code>file_set</code> and third the pointer to the object instance
+ <code>(button,</code> along with the parameters
<code>"theme.edj","button")</code>
+ . In more generic terms:
<code>class_method(instance,parameters)</code>.</para>
<para>The first source snippet in the following tutorial is, of course, the
first exception. The following function calls deal with the library
===================================================================
RCS file: /cvs/e/e17/docs/devwithedje/xml/interacting_with_the_objects.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -3 -r1.2 -r1.3
--- interacting_with_the_objects.xml 17 Jan 2008 00:07:49 -0000 1.2
+++ interacting_with_the_objects.xml 20 Jan 2008 14:23:53 -0000 1.3
@@ -4,7 +4,7 @@
<para>To understand how to interact with Edje or any other Evas object we
need to review the basics of how the main loop manager handles
events. Ecore maintains a list of pointers to functions to be called
- when a signal from a given type is received. These functions
+ when a signal of a given type is received. These functions
are known as signal "handlers".</para>
<para>By default, Ecore awareness is limited to system singals like HUP or
@@ -26,8 +26,9 @@
int
good_bye(void *data, int type, void *event)
{
- //This removes the handler for no practical reason but showoff the API
- if (ecore_event_handler_del(close)) printf("Handler deleted\n");
+ //Removing handler for no reason other than API showoff
+ if (ecore_event_handler_del(close))
+ printf("Handler deleted\n");
printf("Good bye! \n");
ecore_main_loop_quit();
@@ -37,7 +38,8 @@
...
int main() {
...
- close =
ecore_event_handler_add(ECORE_EVENT_SIGNAL_EXIT,good_bye,"data");
+ close = ecore_event_handler_add(ECORE_EVENT_SIGNAL_EXIT,
+ good_bye,"data");
...
ecore_main_loop_begin();
...
@@ -46,7 +48,7 @@
This example moves the library shutdown procedure from the main
function to the "good_bye" function. Then before the main loop is
initiated we add the handler for this signal type. The last parameter
- its a pointer to any kind of data you want to pass to the handler
+ it's a pointer to any kind of data you want to pass to the handler
function, in this case is just a string containing "data".</para>
<para>Interaction with the interface works in a similar way. The Edje
@@ -58,18 +60,22 @@
<programlisting role="C">
...
void
- colorize(void *data, Evas_Object *o, const char *emission, const char
*source)
+ colorize(void *data, Evas_Object *o, const char *emission,
+ const char *source)
{
Evas_Coord x,y;
evas_pointer_canvas_xy_get(evas,&x,&y);
if(x > 255) x = 255;
- if(y > 255) y = 255;
- edje_color_class_set("main color", 190, x, y, 255, 255, 255, 255, 255,
255, 255, 255, 255);
+ if(y > 255) y = 255; //R, G, B, A,
+ edje_color_class_set("main color", 190, x, y, 255,
+ 255, 255, 255, 255,
+ 255, 255, 255, 255);
}
...
int main() {
...
- edje_object_signal_callback_add(edje, "mouse,move", "*", colorize,
"data");
+ edje_object_signal_callback_add(edje, "mouse,move", "*",
+ colorize,"data");
...
ecore_main_loop_begin();
...
===================================================================
RCS file: /cvs/e/e17/docs/devwithedje/xml/intro_to_edje.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -3 -r1.1 -r1.2
--- intro_to_edje.xml 15 Jan 2008 02:33:41 -0000 1.1
+++ intro_to_edje.xml 20 Jan 2008 14:23:53 -0000 1.2
@@ -167,7 +167,7 @@
<para>The normal process to get a canvas up and running can be
bothersome. Evas supports multiple rendering engines, like the
- softare, xrender and opengl flavors of X11 and framebuffer
+ software, xrender and opengl flavors of X11 and framebuffer
devices. But before any rendering can be done the developer has
to complete an Evas_Engine_Info structure with the required
information about the target engine. This forces the developer to
@@ -185,7 +185,7 @@
<para>It's small and lean, designed to work on embedded
systems all the way to large and powerful multi-cpu
- workstations. It serialises all system signals,
+ workstations. It serializes all system signals,
events etc. into a single event queue, that is easily
processed without needing to worry about concurrency.
A properly written, event-driven program using this
===================================================================
RCS file: /cvs/e/e17/docs/devwithedje/xml/intro_to_gui.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -3 -r1.2 -r1.3
--- intro_to_gui.xml 17 Jan 2008 00:07:49 -0000 1.2
+++ intro_to_gui.xml 20 Jan 2008 14:23:53 -0000 1.3
@@ -23,7 +23,7 @@
is known as the Event loop (or main loop).</para>
<figure>
- <title>The averange GUI application</title>
+ <title>The average GUI application</title>
<mediaobject><imageobject>
<imagedata
fileref="img/graphical_application_components.png" format="png" ScaleFit="1"
width="100%"></imagedata>
</imageobject></mediaobject>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-cvs mailing list
enlightenment-cvs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-cvs
