forked from enlightenment/efl
efl: Modified section names as doxygen reuses titles for same named sections in different pages.
SVN revision: 81279
This commit is contained in:
parent
93cdccf144
commit
d41d76ca38
|
@ -13,7 +13,7 @@
|
|||
|
||||
Please see the @ref authors page for contact details.
|
||||
|
||||
@section intro Introduction
|
||||
@section ecore_main_intro Introduction
|
||||
|
||||
Ecore is a library of convenience functions. A brief explanation of how to use
|
||||
it can be found in @ref Ecore_Main_Loop_Page.
|
||||
|
@ -36,7 +36,7 @@
|
|||
|
||||
For more info on Ecore usage, there are these @ref ecore_examples.
|
||||
|
||||
@section compiling How to compile using Ecore?
|
||||
@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:
|
||||
|
||||
|
@ -44,7 +44,7 @@
|
|||
gcc *.c $(pkg-config ecore ecore-$x ecore-$y [...] --cflags --libs)
|
||||
@endverbatim
|
||||
|
||||
@section install How is it installed?
|
||||
@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
|
||||
|
@ -71,7 +71,7 @@ sudo make install
|
|||
/**
|
||||
* @page Ecore_Main_Loop_Page The Ecore Main Loop
|
||||
*
|
||||
* @section intro What is Ecore?
|
||||
* @section Ecore_Main_Loop_Page_intro What is Ecore?
|
||||
*
|
||||
* Ecore is a clean and tiny event loop library with many modules to do lots of
|
||||
* convenient things for a programmer, to save time and effort. It's small and
|
||||
|
@ -141,7 +141,7 @@ sudo make install
|
|||
*
|
||||
*
|
||||
*
|
||||
* @section work How does Ecore work?
|
||||
* @section Ecore_Main_Loop_Page_work How does Ecore work?
|
||||
*
|
||||
* Ecore is very easy to learn and use. All the function calls are designed to
|
||||
* be easy to remember, explicit in describing what they do, and heavily
|
||||
|
|
|
@ -12,14 +12,14 @@
|
|||
|
||||
@section toc Table of Contents
|
||||
|
||||
@li @ref intro
|
||||
@li @ref example
|
||||
@li @ref compiling
|
||||
@li @ref install
|
||||
@li @ref next_steps
|
||||
@li @ref intro_example
|
||||
@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 intro What is Eet?
|
||||
@section eet_main_intro What is Eet?
|
||||
|
||||
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,7 +40,7 @@
|
|||
encoded in a platform independent way and can be written and read by any
|
||||
architecture.
|
||||
|
||||
@section example A simple example on using Eet
|
||||
@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
|
||||
|
@ -56,7 +56,7 @@
|
|||
|
||||
@include eet-basic.c
|
||||
|
||||
@section compiling How to compile using Eet ?
|
||||
@section eet_main_compiling How to compile using Eet ?
|
||||
|
||||
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
|
||||
|
@ -87,7 +87,7 @@
|
|||
is only guaranteed to make Eet add it's own requirements.
|
||||
|
||||
|
||||
@section install How is it installed?
|
||||
@section eet_main_install How is it installed?
|
||||
|
||||
Simple:
|
||||
|
||||
|
@ -99,7 +99,7 @@
|
|||
make install
|
||||
@endverbatim
|
||||
|
||||
@section next_steps Next Steps
|
||||
@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
|
||||
|
@ -114,7 +114,7 @@
|
|||
parse your data structures automatically. Just create your
|
||||
descriptors and let Eet do the work for you.
|
||||
|
||||
@section intro_example Introductory Examples
|
||||
@section eet_main_intro_example Introductory Examples
|
||||
|
||||
@ref eet_examples
|
||||
|
||||
|
|
|
@ -100,7 +100,7 @@
|
|||
*
|
||||
* @defgroup Eina_Containers_Group Containers
|
||||
*
|
||||
* @section Intro Introduction
|
||||
* @section eina_main_Intro Introduction
|
||||
* Containers are data types that hold data and allow iteration over
|
||||
* their elements with an @ref Eina_Iterator_Group, or eventually an
|
||||
* @ref Eina_Accessor_Group.
|
||||
|
@ -109,7 +109,7 @@
|
|||
* of this is that they @b don't check the validity of data structures given to
|
||||
* them(@ref Eina_Magic_Group).
|
||||
*
|
||||
* @section Choice Choosing container type
|
||||
* @section eina_main_Choice Choosing container type
|
||||
*
|
||||
* The choice of which container to use in each situation is very important in
|
||||
* achieving good performance and readable code. The most common container types
|
||||
|
@ -133,7 +133,7 @@
|
|||
* @warning These are general considerations, every situation is different,
|
||||
* don't follow these recommendations blindly.
|
||||
*
|
||||
* @section Creation Creating custom container types
|
||||
* @section eina_main_Creation Creating custom container types
|
||||
*
|
||||
* @note Before creating a custom container check if one of the existing ones
|
||||
* doesn't suit your needs. For example, while there is no stack type @ref
|
||||
|
|
|
@ -11,15 +11,15 @@
|
|||
|
||||
@section toc Table of Contents
|
||||
|
||||
@li @ref intro
|
||||
@li @ref work
|
||||
@li @ref compiling
|
||||
@li @ref install
|
||||
@li @ref next_steps
|
||||
@li @ref intro_example
|
||||
@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 intro What is Evas?
|
||||
@section evas_main_intro What is Evas?
|
||||
|
||||
Evas is a clean display canvas API for several target display systems
|
||||
that can draw anti-aliased text, smooth super and sub-sampled scaled
|
||||
|
@ -42,7 +42,7 @@
|
|||
back-ends, letting it display on several display systems, making it
|
||||
portable for cross-device and cross-platform development.
|
||||
|
||||
@subsection intro_not_evas What Evas is not?
|
||||
@subsection evas_main_intro_not_evas What Evas is not?
|
||||
|
||||
Evas is not a widget set or widget toolkit, however it is their
|
||||
base. See Elementary (http://docs.enlightenment.org/auto/elementary/)
|
||||
|
@ -58,7 +58,7 @@
|
|||
Ecore_Evas (http://docs.enlightenment.org/auto/ecore/).
|
||||
|
||||
|
||||
@section work How does Evas work?
|
||||
@section evas_main_work How does Evas work?
|
||||
|
||||
Evas is a canvas display library. This is markedly different from most
|
||||
display and windowing systems as a canvas is structural and is also a
|
||||
|
@ -184,7 +184,7 @@
|
|||
scrollbars, sliders, push buttons etc.
|
||||
|
||||
|
||||
@section compiling How to compile using Evas ?
|
||||
@section evas_main_compiling How to compile using Evas ?
|
||||
|
||||
Evas is a library your application links to. The procedure for this is
|
||||
very simple. You simply have to compile your application with the
|
||||
|
@ -218,7 +218,7 @@
|
|||
example is only guaranteed to make Evas add it's own requirements.
|
||||
|
||||
|
||||
@section install How is it installed?
|
||||
@section evas_main_install How is it installed?
|
||||
|
||||
Simple:
|
||||
|
||||
|
@ -230,7 +230,7 @@
|
|||
make install
|
||||
@endverbatim
|
||||
|
||||
@section next_steps Next Steps
|
||||
@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
|
||||
|
@ -265,7 +265,7 @@
|
|||
ends to be a widget, providing some intelligence (thus the name)
|
||||
to Evas objects -- like a button or check box, for example.
|
||||
|
||||
@section intro_example Introductory Example
|
||||
@section evas_main_intro_example Introductory Example
|
||||
|
||||
@include evas-buffer-simple.c
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue