efl/docs: clean-up and make it more uniform.

now unified docs are bit more uniform in their start pages, overall
improved but much to do :-(



SVN revision: 81851

10 files changed, 399 insertions, 205 deletions

diff --git a/src/lib/ecore/Ecore.h b/src/lib/ecore/Ecore.h
index 448e1aca1f..34210f932e 100644
--- a/src/lib/ecore/Ecore.h
+++ b/src/lib/ecore/Ecore.h
@@ -8,10 +8,14 @@
 
    @page ecore_main Ecore
 
-   @version 1.7
-   @date 2000-2012
+   @date 2000 (created)
 
-   Please see the @ref authors page for contact details.
+   @section toc Table of Contents
+
+   @li @ref ecore_main_intro
+   @li @ref ecore_main_compiling
+   @li @ref ecore_main_next_steps
+   @li @ref ecore_main_intro_example
 
    @section ecore_main_intro Introduction
 
@@ -36,35 +40,49 @@
 
    For more info on Ecore usage, there are these @ref ecore_examples.
 
-   @section ecore_main_compiling How to compile using Ecore?
-   pkgconfig (.pc) files are installed for every ecore module.
-   Thus, to compile using any of them, you can use something like the following:
-
-@verbatim
-gcc *.c $(pkg-config ecore ecore-$x ecore-$y [...] --cflags --libs)
-@endverbatim
-
-   @section ecore_main_install How is it installed?
-
-   Suggested configure options for ecore for a Linux desktop X display
-   with OpenGL and Software support, communication (networking) and
-   IPC (inter process communication):
-
-@verbatim
-./configure \
-    --enable-ecore-con \
-    --enable-ecore-ipc \
-    --enable-ecore-file \
-    --enable-ecore-input \
-    --enable-ecore-input-evas \
-    --enable-ecore-x \
-    --enable-ecore-evas \
-    --enable-ecore-evas-software-buffer \
-    --enable-ecore-evas-software-x11 \
-    --enable-ecore-evas-opengl-x11
-make
-sudo make install
-@endverbatim
+   @section ecore_main_compiling How to compile
+
+   Ecore is a library your application links to. The procedure for
+   this is very simple. You simply have to compile your application
+   with the appropriate compiler flags that the @p pkg-config script
+   outputs. Note that each module is separate in pkg-config. For
+   example using @ref Ecore_Evas_Group:
+
+   Compiling C or C++ files into object files:
+
+   @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags ecore ecore-evas`
+   @endverbatim
+
+   Linking object files into a binary executable:
+
+   @verbatim
+   gcc -o my_application main.o `pkg-config --libs ecore ecore-evas`
+   @endverbatim
+
+   See @ref pkgconfig
+
+   @section ecore_main_next_steps Next Steps
+
+   After you understood what Ecore is and installed it in your system
+   you should proceed understanding the programming interface. We'd
+   recommend you to take a while to learn @ref Eina as it is very
+   convenient and optimized, and Ecore uses it extensively.
+
+   Recommended reading:
+
+   @li @ref Ecore_Timer_Group
+   @li @ref Ecore_Idle_Group
+   @li @ref Ecore_FD_Handler_Group
+   @li @ref Ecore_Event_Group
+   @li @ref Ecore_Exe_Group
+
+   @section ecore_main_intro_example Introductory Examples
+
+   @include ecore_timer_example.c
+
+   More examples can be found at @ref ecore_examples.
+
 
  */
 
diff --git a/src/lib/edbus/EDBus.h b/src/lib/edbus/EDBus.h
index 36cdf2e245..9145c93937 100644
--- a/src/lib/edbus/EDBus.h
+++ b/src/lib/edbus/EDBus.h
@@ -1,14 +1,23 @@
 /**
  * @page edbus_main EDBus
  *
- * @section edbus_intro_sec Introduction
+ * @date 2012 (created)
+ *
+ * @section toc Table of Contents
+ *
+ * @li @ref edbus_main_intro
+ * @li @ref edbus_main_compiling
+ * @li @ref edbus_main_next_steps
+ * @li @ref edbus_main_intro_example
+ *
+ * @section edbus_main_intro Introduction
  *
  * EDBus is a wrapper around the
  * <a href="http://www.freedesktop.org/wiki/Software/dbus">dbus</a>
  * library, which is a message bus system. It also implements a set of
  * specifications using dbus as interprocess communication.
  *
- * @section edbus_modules_sec Modules
+ * @subsection edbus_modules_sec Modules
  *
  * <ul>
  * <li> @ref EDBus_Core
@@ -27,50 +36,42 @@
  * <li> @ref EDBus_Basic
  * </ul>
  *
- * @section edbus_examples_sec Examples
+ * @section edbus_main_compiling How to compile
+ *
+ * EDBus is a library your application links to. The procedure for this is
+ * very simple. You simply have to compile your application with the
+ * appropriate compiler flags that the @c pkg-config script outputs. For
+ * example:
  *
- * Here some EDBus examples:
+ * Compiling C or C++ files into object files:
  *
- * @li @ref banshee.c
- * @li @ref client.c
- * @li @ref complex-types.c
- * @li @ref complex-types-client-eina-value.c
- * @li @ref complex-types-server.c
- * @li @ref connman-list-services.c
- * @li @ref ofono-dial.c
- * @li @ref server.c
- * @li @ref simple-signal-emit.c
+ * @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags edbus2`
+   @endverbatim
  *
- * @example banshee.c
- * Access Banshee music player and send commands to it.
+ * Linking object files into a binary executable:
  *
- * @example client.c
- * Client to test various call message types against a provided server
- * (@ref server.c)
+ * @verbatim
+   gcc -o my_application main.o `pkg-config --libs edbus2`
+   @endverbatim
  *
- * @example complex-types.c
- * Client to test complex types (arrays, structs, dicts) against a
- * provided server (@ref complex-types-server.c)
+ * See @ref pkgconfig
  *
- * @example complex-types-client-eina-value.c
- * Client to test complex types (arrays, structs, dicts) against a
- * provided server (@ref complex-types-server.c) returning them as
- * @ref Eina_Value.
+ * @section edbus_main_next_steps Next Steps
  *
- * @example complex-types-server.c
- * Server to test complex types (arrays, structs, dicts).
+ * After you understood what EDBus is and installed it in your system
+ * you should proceed understanding the programming interface.
  *
- * @example connman-list-services.c
- * Client to list networks/services from connman.
+ * Recommended reading:
+ * @li @ref EDBus_Core for library init, shutdown and getting a connection.
+ * @li @ref EDBus_Proxy to easily bind a client object to an interface.
+ * @li @ref EDBus_Object_Mapper to monitor server objects and properties.
  *
- * @example ofono-dial.c
- * Client to ask oFono to dial.
+ * @section edbus_main_intro_example Introductory Example
  *
- * @example server.c
- * Server to reply to @ref client.c requests.
+ * @include ofono-dial.c
  *
- * @example simple-signal-emit.c
- * Server that registers a service interface and emits simple signals.
+ * More examples can be found at @ref edbus_examples.
  */
 #ifndef EDBUS_H
 #define EDBUS_H
diff --git a/src/lib/eet/Eet.h b/src/lib/eet/Eet.h
index 9b2fd1b9a4..693b839056 100644
--- a/src/lib/eet/Eet.h
+++ b/src/lib/eet/Eet.h
@@ -3,23 +3,18 @@
 
    These routines are used for Eet Library interaction
 
-   @page eet_main Eet Library Documentation
+   @page eet_main Eet
 
-   @version 1.7.0
-   @date 2000-2012
-
-   Please see the @ref authors page for contact details.
+   @date 2000 (created)
 
    @section toc Table of Contents
 
    @li @ref eet_main_intro
-   @li @ref eet_main_example
    @li @ref eet_main_compiling
-   @li @ref eet_main_install
    @li @ref eet_main_next_steps
    @li @ref eet_main_intro_example
 
-   @section eet_main_intro What is Eet?
+   @section eet_main_intro Introduction
 
    It is a tiny library designed to write an arbitrary set of chunks of data
    to a file and optionally compress each chunk (very much like a zip file)
@@ -40,23 +35,7 @@
    encoded in a platform independent way and can be written and read by any
    architecture.
 
-   @section eet_main_example A simple example on using Eet
-
-   Here is a simple example on how to use Eet to save a series of strings to a
-   file and load them again. The advantage of using Eet over just
-   fprintf() and
-   fscanf() is that not only can these entries be strings, they need no special
-   parsing to handle delimiter characters or escaping, they can be binary data,
-   image data, data structures containing integers, strings, other data
-   structures, linked lists and much more, without the programmer having to
-   worry about parsing, and best of all, Eet is very fast.
-
-   This is just a very simple example that doesn't show all of the capabilities
-   of Eet, but it serves to illustrate its simplicity.
-
-   @include eet-basic.c
-
-   @section eet_main_compiling How to compile using Eet ?
+   @section eet_main_compiling How to compile
 
    Eet is a library your application links to. The procedure for this is very
    simple. You simply have to compile your application with the appropriate
@@ -74,38 +53,14 @@
    gcc -o my_application main.o `pkg-config --libs eet`
    @endverbatim
 
-   You simply have to make sure that pkg-config is in your shell's PATH (see
-   the manual page for your appropriate shell) and eet.pc in /usr/lib/pkgconfig
-   or its path is in the PKG_CONFIG_PATH environment variable. It's that simple
-   to link and use Eet once you have written your code to use it.
-
-   Since the program is linked to Eet, it is now able to use any advertised
-   API calls to serialize your data.
-
-   You should make sure you add any extra compile and link flags to your
-   compile commands that your application may need as well. The above example
-   is only guaranteed to make Eet add it's own requirements.
-
-
-   @section eet_main_install How is it installed?
-
-   Simple:
-
-   @verbatim
-   ./configure
-   make
-   su -
-   ...
-   make install
-   @endverbatim
+   See @ref pkgconfig
 
    @section eet_main_next_steps Next Steps
 
-   After you understood what Eet is and installed it in your system you
-   should proceed understanding the programming interface. We'd recommend
-   you to take a while to learn Eina
-   (http://docs.enlightenment.org/auto/eina/) as it is very convenient
-   and optimized, and Eet provides integration with it.
+   After you understood what Eet is and installed it in your system
+   you should proceed understanding the programming interface. We'd
+   recommend you to take a while to learn @ref Eina as it is very
+   convenient and optimized, and Eet provides integration with it.
 
    Recommended reading:
 
@@ -116,7 +71,21 @@
 
    @section eet_main_intro_example Introductory Examples
 
-   @ref eet_examples
+   Here is a simple example on how to use Eet to save a series of strings to a
+   file and load them again. The advantage of using Eet over just
+   fprintf() and
+   fscanf() is that not only can these entries be strings, they need no special
+   parsing to handle delimiter characters or escaping, they can be binary data,
+   image data, data structures containing integers, strings, other data
+   structures, linked lists and much more, without the programmer having to
+   worry about parsing, and best of all, Eet is very fast.
+
+   This is just a very simple example that doesn't show all of the capabilities
+   of Eet, but it serves to illustrate its simplicity.
+
+   @include eet-basic.c
+
+   More examples can be found at @ref eet_examples.
 
    @todo Document data format for images and data structures.
 
diff --git a/src/lib/eina/Eina.h b/src/lib/eina/Eina.h
index 2205811131..280cc9a7be 100644
--- a/src/lib/eina/Eina.h
+++ b/src/lib/eina/Eina.h
@@ -46,10 +46,16 @@
 /**
  * @page eina_main Eina
  *
- * @version 1.7
- * @date 2008-2012
+ * @date 2008 (created)
  *
- * @section eina_intro_sec Introduction
+ * @section toc Table of Contents
+ *
+ * @li @ref eina_main_intro
+ * @li @ref eina_main_compiling
+ * @li @ref eina_main_next_steps
+ * @li @ref eina_main_intro_example
+ *
+ * @section eina_main_intro Introduction
  *
  * The Eina library is a library that implements an API for data types
  * in an efficient way. It also provides some useful tools like
@@ -90,8 +96,45 @@
  * @li @ref Eina_Rectangle_Group rectangle structure and standard manipulation methods.
  * @li @ref Eina_Safety_Checks_Group extra checks that will report unexpected conditions and can be disabled at compile time.
  * @li @ref Eina_String_Group a set of functions that manages C strings.
- * 
- * Please see the @ref authors page for contact details.
+ *
+ * @section eina_main_compiling How to compile
+ *
+ * Eina is a library your application links to. The procedure for this is
+ * very simple. You simply have to compile your application with the
+ * appropriate compiler flags that the @c pkg-config script outputs. For
+ * example:
+ *
+ * Compiling C or C++ files into object files:
+ *
+ * @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags eina`
+   @endverbatim
+ *
+ * Linking object files into a binary executable:
+ *
+ * @verbatim
+   gcc -o my_application main.o `pkg-config --libs eina`
+   @endverbatim
+ *
+ * See @ref pkgconfig
+ *
+ * @section eina_main_next_steps Next Steps
+ *
+ * After you understood what Eina is and installed it in your system
+ * you should proceed understanding the programming interface.
+ *
+ * Recommended reading:
+ *
+ * @li @ref Eina_Data_Types_Group to find about implemented types and
+ *     how to use them.
+ * @li @ref Eina_Tools_Group to find about helper tools provided by eina.
+ *
+ * @section eina_main_intro_example Introductory Example
+ *
+ * @include eina_list_01.c
+ *
+ * More examples can be found at @ref eina_examples.
+ *
  *
  * @defgroup Eina_Data_Types_Group Data Types
  * @ingroup Eina
diff --git a/src/lib/eio/Eio.h b/src/lib/eio/Eio.h
index 6e24be8acd..494bc889c6 100644
--- a/src/lib/eio/Eio.h
+++ b/src/lib/eio/Eio.h
@@ -87,7 +87,16 @@ extern "C" {
 /**
  * @page eio_main Eio
  *
- * @section eio_intro_sec Introduction
+ * @date 2012 (created)
+ *
+ * @section toc Table of Contents
+ *
+ * @li @ref eio_main_intro
+ * @li @ref eio_main_compiling
+ * @li @ref eio_main_next_steps
+ * @li @ref eio_main_intro_example
+ *
+ * @section eio_main_intro Introduction
  *
  * The Eio library is a library that implements an API for asynchronous
  * input/output operation. Most operation are done in a separated thread
@@ -101,9 +110,45 @@ extern "C" {
  * Linux, BSD, Opensolaris and Windows (XP and CE). It is heavily
  * based on @ref Ecore_Main_Loop_Group.
  *
- * @section eio_main_intro_example Introductory Examples
+ * @section eio_main_compiling How to compile
+ *
+ * Eio is a library your application links to. The procedure for this is
+ * very simple. You simply have to compile your application with the
+ * appropriate compiler flags that the @c pkg-config script outputs. For
+ * example:
+ *
+ * Compiling C or C++ files into object files:
+ *
+ * @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags eio`
+   @endverbatim
+ *
+ * Linking object files into a binary executable:
+ *
+ * @verbatim
+   gcc -o my_application main.o `pkg-config --libs eio`
+   @endverbatim
+ *
+ * See @ref pkgconfig
+ *
+ * @section eio_main_next_steps Next Steps
+ *
+ * After you understood what Eio is and installed it in your system
+ * you should proceed understanding the programming interface.
+ *
+ * Recommended reading:
+ *
+ * @li @ref Eio_Helper for common functions and library initialization.
+ * @li @ref Eio_Map to manipulate files asynchronously (mmap).
+ * @li @ref Eio_Xattr to access file extended attributes (xattr).
+ * @li @ref Eio_Monitor to monitor for file changes (inotify).
+ * @li @ref Eio_Eet to access Eet files asynchronously.
+ *
+ * @section eio_main_intro_example Introductory Example
+ *
+ * @include eio_file_ls.c
  *
- * @ref eio_examples
+ * More examples can be found at @ref eio_examples.
  *
  * @{
  */
diff --git a/src/lib/embryo/Embryo.h b/src/lib/embryo/Embryo.h
index 1f14e12383..e9020d4ced 100644
--- a/src/lib/embryo/Embryo.h
+++ b/src/lib/embryo/Embryo.h
@@ -3,16 +3,18 @@
  
 These routines are used for Embryo.
 
-@page embryo_main Embryo Library Documentation
+@page embryo_main Embryo
 
-@image html  e_big.png
+@date 2004 (created)
+@note based on Compuphase (http://www.compuphase.com) PAWN language.
 
-@version 1.7.0
-@author Carsten Haitzler <raster\@rasterman.com>
-@author Compuphase http://www.compuphase.com
-@date 2004-2012
+@section toc Table of Contents
 
-@section intro What is Embryo?
+@li @ref embryo_main_intro
+@li @ref embryo_main_compiling
+@li @ref embryo_main_next_steps
+
+@section embryo_main_intro Introduction
 
 Embryo is a tiny library designed to interpret limited Small programs
 compiled by the included compiler, @c embryo_cc.  It is mostly a cleaned
@@ -26,16 +28,40 @@ For more information about the Pawn language, see
 @latexonly http://www.compuphase.com/pawn/pawn.htm @endlatexonly
 For the basics about the Small language, see @ref Small_Page.
 
-@section How_to_Use How to Use Embryo?
+@section embryo_main_compiling How to compile
+
+Embryo is a library your application links to. The procedure for this
+is very simple. You simply have to compile your application with the
+appropriate compiler flags that the @p pkg-config script outputs. For
+example:
+
+Compiling C or C++ files into object files:
+
+@verbatim
+gcc -c -o main.o main.c `pkg-config --cflags embryo`
+@endverbatim
+
+Linking object files into a binary executable:
+
+@verbatim
+gcc -o my_application main.o `pkg-config --libs embryo`
+@endverbatim
+
+See @ref pkgconfig
+
+@section embryo_main_next_steps Next Steps
+
+After you understood what Embryo is and installed it in your system you
+should proceed understanding the programming interface.
+
+Recommended reading:
+
+@li @ref Embryo_Program_Creation_Group to create Embryo from memory or file.
+@li @ref Embryo_Func_Group to expose functions to Embryo.
+@li @ref Embryo_Program_VM_Group to push pop virtual machine.
+@li @ref Embryo_Run_Group to run it.
 
-To use Embryo in your code, you need to do at least the following:
 
-@li Include @ref Embryo.h.
-@li Load the Embryo program using one of the 
-    @ref Embryo_Program_Creation_Group.
-@li Set up the native calls with @ref embryo_program_native_call_add.
-@li Create a virtual machine with @ref embryo_program_vm_push.
-@li Then run the program with @ref embryo_program_run.
 
 @todo Clean up compiler code.
 @todo Proper overview of the operation of the interpreter, that is how
diff --git a/src/lib/eo/Eo.h b/src/lib/eo/Eo.h
index ffb46fbeac..976328a130 100644
--- a/src/lib/eo/Eo.h
+++ b/src/lib/eo/Eo.h
@@ -64,11 +64,62 @@ enum _Eo_Op_Type
 typedef enum _Eo_Op_Type Eo_Op_Type;
 
 /**
- * @defgroup Eo Eo Generic Object System
+ * @page eo_main Eo
+ *
+ * @date 2012 (created)
+ *
+ * @section toc Table of Contents
+ *
+ * @li @ref eo_main_intro
+ * @li @ref eo_main_compiling
+ * @li @ref eo_main_next_steps
+ * @li @ref eo_main_intro_example
+ *
+ * @section eo_main_intro Introduction
  *
  * The Eo generic object system. It was designed to be the base object
  * system for the EFL.
+
+ * @section eo_main_compiling How to compile
+ *
+ * Eo is a library your application links to. The procedure for this is
+ * very simple. You simply have to compile your application with the
+ * appropriate compiler flags that the @c pkg-config script outputs. For
+ * example:
+ *
+ * Compiling C or C++ files into object files:
+ *
+ * @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags eo`
+   @endverbatim
+ *
+ * Linking object files into a binary executable:
+ *
+ * @verbatim
+   gcc -o my_application main.o `pkg-config --libs eo`
+   @endverbatim
+ *
+ * See @ref pkgconfig
+ *
+ * @section eo_main_next_steps Next Steps
+ *
+ * After you understood what Eo is and installed it in your system
+ * you should proceed understanding the programming interface.
+ *
+ * Recommended reading:
+ *
+ * @li @ref Eo_Class_Base
+ * @li @ref Eo_Class
+ * @li @ref Eo_Events
+ * @li @ref Eo_Composite_Objects
+ *
+ * @section eo_main_intro_example Introductory Example
+ *
+ * @ref Eo_Tutorial
+
+ *
  *
+ * @addtogroup Eo
  * @{
  */
 
diff --git a/src/lib/escape/Escape.h b/src/lib/escape/Escape.h
index c8f6267ec3..210bc872a1 100644
--- a/src/lib/escape/Escape.h
+++ b/src/lib/escape/Escape.h
@@ -20,18 +20,51 @@
 
 /**
  * @page escape_main Escape
- * @date 2011
+ * @date 2011 (created)
  *
- * @section intro_sec Introduction
+ * @section toc Table of Contents
+ *
+ * @li @ref escape_main_intro
+ * @li @ref escape_main_compiling
+ * @li @ref escape_main_next_steps
+ *
+ * @section escape_main_intro Introduction
  *
  * The Escape library is a library that acts implements some of the missing
  * function from the PS3 GameOS system that are needed for the proper
  * functioning of the EFL.
  *
- * @section escape_sec Escape API Documentation
+ * @section escape_main_compiling How to compile
+ *
+ * Escape is a library your application links to. The procedure for
+ * this is very simple. You simply have to compile your application
+ * with the appropriate compiler flags that the @p pkg-config script
+ * outputs. For example:
+ *
+ * Compiling C or C++ files into object files:
+ *
+ * @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags escape`
+   @endverbatim
+ *
+ * Linking object files into a binary executable:
+ *
+ * @verbatim
+   gcc -o my_application main.o `pkg-config --libs escape`
+   @endverbatim
+ *
+ * See @ref pkgconfig
+ *
+ * @section escape_main_next_steps Next Steps
+ *
+ * After you understood what Escape is and installed it in your system
+ * you should proceed understanding the programming interface.
  *
- * Take a look at the documentation of @ref mmap/munmap.
+ * Recommended reading:
  *
+ * @li @ref Escape_Libgen_Group
+ * @li @ref Escape_Unistd_Group
+ * @li @ref Escape_Mman
  */
 
 #include "escape_libgen.h"
diff --git a/src/lib/evas/Evas.h b/src/lib/evas/Evas.h
index bf58ec5c2b..2b82d9e8a0 100644
--- a/src/lib/evas/Evas.h
+++ b/src/lib/evas/Evas.h
@@ -1,25 +1,18 @@
 /**
    @page evas_main Evas
 
-   @version 1.7
-   @date 2000-2012
-
-   Please see the @ref authors page for contact details.
-   @link Evas.h Evas API @endlink
-
-   @link Evas.h Evas API @endlink
+   @date 2000 (created)
 
    @section toc Table of Contents
 
    @li @ref evas_main_intro
    @li @ref evas_main_work
    @li @ref evas_main_compiling
-   @li @ref evas_main_install
    @li @ref evas_main_next_steps
    @li @ref evas_main_intro_example
 
 
-   @section evas_main_intro What is Evas?
+   @section evas_main_intro Introduction
 
    Evas is a clean display canvas API for several target display systems
    that can draw anti-aliased text, smooth super and sub-sampled scaled
@@ -46,7 +39,7 @@
 
    Evas is not a widget set or widget toolkit, however it is their
    base. See Elementary (http://docs.enlightenment.org/auto/elementary/)
-   for a toolkit based on Evas, Edje, Ecore and other Enlightenment
+   for a toolkit based on Evas, Edje, @ref Ecore and other Enlightenment
    technologies.
 
    It is not dependent or aware of main loops, input or output
@@ -54,8 +47,8 @@
    Evas. Similarly, it will not create windows or report windows updates
    to your system, rather just drawing the pixels and reporting to the
    user the areas that were changed. Of course these operations are quite
-   common and thus they are ready to use in Ecore, particularly in
-   Ecore_Evas (http://docs.enlightenment.org/auto/ecore/).
+   common and thus they are ready to use in @ref Ecore, particularly in
+   @ref Ecore_Evas_Group.
 
 
    @section evas_main_work How does Evas work?
@@ -184,7 +177,7 @@
    scrollbars, sliders, push buttons etc.
 
 
-   @section evas_main_compiling How to compile using Evas ?
+   @section evas_main_compiling How to compile
 
    Evas is a library your application links to. The procedure for this is
    very simple. You simply have to compile your application with the
@@ -203,42 +196,17 @@
    gcc -o my_application main.o `pkg-config --libs evas`
    @endverbatim
 
-   You simply have to make sure that @c pkg-config is in your shell's @c
-   PATH (see the manual page for your appropriate shell) and @c evas.pc
-   in @c /usr/lib/pkgconfig or its path in the @c PKG_CONFIG_PATH
-   environment variable. It's that simple to link and use Evas once you
-   have written your code to use it.
-
-   Since the program is linked to Evas, it is now able to use any
-   advertised API calls to display graphics in a canvas managed by it, as
-   well as use the API calls provided to manage data.
-
-   You should make sure you add any extra compile and link flags to your
-   compile commands that your application may need as well. The above
-   example is only guaranteed to make Evas add it's own requirements.
-
-
-   @section evas_main_install How is it installed?
-
-   Simple:
-
-   @verbatim
-   ./configure
-   make
-   su -
-   ...
-   make install
-   @endverbatim
+   See @ref pkgconfig
 
    @section evas_main_next_steps Next Steps
 
-   After you understood what Evas is and installed it in your system you
-   should proceed understanding the programming interface for all
+   After you understood what Evas is and installed it in your system
+   you should proceed understanding the programming interface for all
    objects, then see the specific for the most used elements. We'd
-   recommend you to take a while to learn Ecore
-   (http://docs.enlightenment.org/auto/ecore/) and Edje
-   (http://docs.enlightenment.org/auto/edje/) as they will likely save
-   you tons of work compared to using just Evas directly.
+   recommend you to take a while to learn @ref Ecore, Edje
+   (http://docs.enlightenment.org/auto/edje/) and Elementary
+   (http://docs.enlightenment.org/auto/elementary/) as they will
+   likely save you tons of work compared to using just Evas directly.
 
    Recommended reading:
 
@@ -268,6 +236,9 @@
    @section evas_main_intro_example Introductory Example
 
    @include evas-buffer-simple.c
+
+   More examples can be found at @ref evas_examples.
+
  */
 
 #ifndef _EVAS_H
diff --git a/src/lib/evil/Evil.h b/src/lib/evil/Evil.h
index 191aae9c12..0aad5f0613 100644
--- a/src/lib/evil/Evil.h
+++ b/src/lib/evil/Evil.h
@@ -9,10 +9,16 @@
 /**
  * @page evil_main Evil
  * @author Vincent Torri
- * @version 1.7.0
- * @date 2008-2012
+ * @date 2008 (created)
  *
- * @section intro_sec Introduction
+ * @section toc Table of Contents
+ *
+ * @li @ref evil_main_intro
+ * @li @ref evil_main_ack
+ * @li @ref evil_main_compiling
+ * @li @ref evil_main_next_steps
+ *
+ * @section evil_main_intro Introduction
  *
  * The Evil library is an evil library that ports some evil Unix
  * functions to the Windows (XP or above, or Mobile) platform. The
@@ -28,7 +34,7 @@
  * cygwin. To compare the size of the DLL themselves, Evil is around
  * 33 KB and cygwin DLL is around 800 KB.
  *
- * @section acknowledgments_sec Acknowledgments
+ * @section evil_main_ack Acknowledgments
  *
  * This library has receive some from people interested in the EFL or
  * not. Among them, evil thanks to Lars Munch, Raoul Hecky, Nicolas
@@ -36,15 +42,46 @@
  * Vixie, Daniel Stenberg, who helped the author of the library in
  * different fields (code and tests).
  *
- * @section license_sec license
+ * @section evil_main_compiling How to compile
+ *
+ * Evil is a library your application links to. The procedure for
+ * this is very simple. You simply have to compile your application
+ * with the appropriate compiler flags that the @p pkg-config script
+ * outputs. For example:
+ *
+ * Compiling C or C++ files into object files:
+ *
+ * @verbatim
+   gcc -c -o main.o main.c `pkg-config --cflags evil`
+   @endverbatim
+ *
+ * Linking object files into a binary executable:
+ *
+ * @verbatim
+   gcc -o my_application main.o `pkg-config --libs evil`
+   @endverbatim
+ *
+ * See @ref pkgconfig
+ *
+ * @section evil_main_next_steps Next Steps
  *
- * The Evil library is distributes under a modified BSD license. See
- * the files COPYING and COPYING-PLAIN in the top level directory for
- * the full license text.
+ * After you understood what Evil is and installed it in your system
+ * you should proceed understanding the programming interface.
  *
- * @section reference_sec Reference API
+ * Recommended reading:
  *
- * Use the horizontal menu above to navigate into the reference API
+ * @li @ref Evil_Mman
+ * @li @ref Evil_Libgen_Group
+ * @li @ref Evil_Unistd_Group
+ * @li @ref Evil_Dlfcn
+ * @li @ref Evil_Pwd_Group
+ * @li @ref Evil_Stdio_Group
+ * @li @ref Evil_Main_Group
+ * @li @ref Evil_Inet_Group
+ * @li @ref Evil_Dirent_Group
+ * @li @ref Evil_String_Group
+ * @li @ref Evil_Stdlib_Group
+ * @li @ref Evil_Time_Group
  */
 
 /**