summaryrefslogtreecommitdiff
path: root/legacy/ephysics/doc
diff options
context:
space:
mode:
authorBruno Dilly <bdilly@profusion.mobi>2012-06-26 22:36:12 +0000
committerBruno Dilly <bdilly@profusion.mobi>2012-06-26 22:36:12 +0000
commit28d9f92ef24a0d059470da7f1ef64be9542637d4 (patch)
treeb0e29f1104d72089295d5b6121cc09cf01c81a53 /legacy/ephysics/doc
parent3eaa894b6945756814045be4604e417387626fa7 (diff)
EPhysics: a new library comes to E world
It’s a wrapper between Bullet Physics and EFL to add physics effects in a simple way. More details on README, TODO, and edevelop mail list =) SVN revision: 72896
Diffstat (limited to 'legacy/ephysics/doc')
-rw-r--r--legacy/ephysics/doc/Doxyfile.in1515
-rw-r--r--legacy/ephysics/doc/Makefile.am35
-rw-r--r--legacy/ephysics/doc/e.css295
-rw-r--r--legacy/ephysics/doc/examples.dox208
-rw-r--r--legacy/ephysics/doc/foot.html18
-rw-r--r--legacy/ephysics/doc/head.html67
-rw-r--r--legacy/ephysics/doc/img/diagram_ephysics.pngbin0 -> 23499 bytes
-rw-r--r--legacy/ephysics/doc/img/e.pngbin0 -> 30052 bytes
-rw-r--r--legacy/ephysics/doc/img/edoxy.css486
-rw-r--r--legacy/ephysics/doc/img/foot_bg.pngbin0 -> 173 bytes
-rw-r--r--legacy/ephysics/doc/img/head_bg.pngbin0 -> 214 bytes
-rw-r--r--legacy/ephysics/doc/img/header_menu_background.pngbin0 -> 192 bytes
-rw-r--r--legacy/ephysics/doc/img/header_menu_background_last.pngbin0 -> 637 bytes
-rw-r--r--legacy/ephysics/doc/img/header_menu_current_background.pngbin0 -> 1200 bytes
-rw-r--r--legacy/ephysics/doc/img/header_menu_unselected_background.pngbin0 -> 1596 bytes
-rw-r--r--legacy/ephysics/doc/img/logo.pngbin0 -> 3825 bytes
16 files changed, 2624 insertions, 0 deletions
diff --git a/legacy/ephysics/doc/Doxyfile.in b/legacy/ephysics/doc/Doxyfile.in
new file mode 100644
index 0000000000..f6983317c4
--- /dev/null
+++ b/legacy/ephysics/doc/Doxyfile.in
@@ -0,0 +1,1515 @@
1# Doxyfile 1.6.1
2
3# This file describes the settings to be used by the documentation system
4# doxygen (www.doxygen.org) for a project
5#
6# All text after a hash (#) is considered a comment and will be ignored
7# The format is:
8# TAG = value [value, ...]
9# For lists items can also be appended using:
10# TAG += value [value, ...]
11# Values that contain spaces should be placed between quotes (" ")
12
13#---------------------------------------------------------------------------
14# Project related configuration options
15#---------------------------------------------------------------------------
16
17# This tag specifies the encoding used for all characters in the config file
18# that follow. The default is UTF-8 which is also the encoding used for all
19# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20# iconv built into libc) for the transcoding. See
21# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
23DOXYFILE_ENCODING = UTF-8
24
25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26# by quotes) that should identify the project.
27
28PROJECT_NAME = EPhysics
29
30# The PROJECT_NUMBER tag can be used to enter a project or revision number.
31# This could be handy for archiving the generated documentation or
32# if some version control system is used.
33
34PROJECT_NUMBER =
35
36# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37# base path where the generated documentation will be put.
38# If a relative path is entered, it will be relative to the location
39# where doxygen was started. If left blank the current directory will be used.
40
41OUTPUT_DIRECTORY = .
42
43# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44# 4096 sub-directories (in 2 levels) under the output directory of each output
45# format and will distribute the generated files over these directories.
46# Enabling this option can be useful when feeding doxygen a huge amount of
47# source files, where putting all generated files in the same directory would
48# otherwise cause performance problems for the file system.
49
50CREATE_SUBDIRS = NO
51
52# The OUTPUT_LANGUAGE tag is used to specify the language in which all
53# documentation generated by doxygen is written. Doxygen will use this
54# information to generate all constant output in the proper language.
55# The default language is English, other supported languages are:
56# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
57# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
58# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
59# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
60# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
61# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
62
63OUTPUT_LANGUAGE = English
64
65# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
66# include brief member descriptions after the members that are listed in
67# the file and class documentation (similar to JavaDoc).
68# Set to NO to disable this.
69
70BRIEF_MEMBER_DESC = YES
71
72# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
73# the brief description of a member or function before the detailed description.
74# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
75# brief descriptions will be completely suppressed.
76
77REPEAT_BRIEF = YES
78
79# This tag implements a quasi-intelligent brief description abbreviator
80# that is used to form the text in various listings. Each string
81# in this list, if found as the leading text of the brief description, will be
82# stripped from the text and the result after processing the whole list, is
83# used as the annotated text. Otherwise, the brief description is used as-is.
84# If left blank, the following values are used ("$name" is automatically
85# replaced with the name of the entity): "The $name class" "The $name widget"
86# "The $name file" "is" "provides" "specifies" "contains"
87# "represents" "a" "an" "the"
88
89ABBREVIATE_BRIEF =
90
91# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
92# Doxygen will generate a detailed section even if there is only a brief
93# description.
94
95ALWAYS_DETAILED_SEC = YES
96
97# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
98# inherited members of a class in the documentation of that class as if those
99# members were ordinary class members. Constructors, destructors and assignment
100# operators of the base classes will not be shown.
101
102INLINE_INHERITED_MEMB = NO
103
104# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
105# path before files name in the file list and in the header files. If set
106# to NO the shortest path that makes the file name unique will be used.
107
108FULL_PATH_NAMES = YES
109
110# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
111# can be used to strip a user-defined part of the path. Stripping is
112# only done if one of the specified strings matches the left-hand part of
113# the path. The tag can be used to show relative paths in the file list.
114# If left blank the directory from which doxygen is run is used as the
115# path to strip.
116
117STRIP_FROM_PATH = @top_srcdir@/ src/
118
119# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
120# the path mentioned in the documentation of a class, which tells
121# the reader which header file to include in order to use a class.
122# If left blank only the name of the header file containing the class
123# definition is used. Otherwise one should specify the include paths that
124# are normally passed to the compiler using the -I flag.
125
126STRIP_FROM_INC_PATH =
127
128# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
129# (but less readable) file names. This can be useful is your file systems
130# doesn't support long names like on DOS, Mac, or CD-ROM.
131
132SHORT_NAMES = NO
133
134# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
135# will interpret the first line (until the first dot) of a JavaDoc-style
136# comment as the brief description. If set to NO, the JavaDoc
137# comments will behave just like regular Qt-style comments
138# (thus requiring an explicit @brief command for a brief description.)
139
140JAVADOC_AUTOBRIEF = YES
141
142# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
143# interpret the first line (until the first dot) of a Qt-style
144# comment as the brief description. If set to NO, the comments
145# will behave just like regular Qt-style comments (thus requiring
146# an explicit \brief command for a brief description.)
147
148QT_AUTOBRIEF = NO
149
150# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
151# treat a multi-line C++ special comment block (i.e. a block of //! or ///
152# comments) as a brief description. This used to be the default behaviour.
153# The new default is to treat a multi-line C++ comment block as a detailed
154# description. Set this tag to YES if you prefer the old behaviour instead.
155
156MULTILINE_CPP_IS_BRIEF = NO
157
158# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
159# member inherits the documentation from any documented member that it
160# re-implements.
161
162INHERIT_DOCS = YES
163
164# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
165# a new page for each member. If set to NO, the documentation of a member will
166# be part of the file/class/namespace that contains it.
167
168SEPARATE_MEMBER_PAGES = NO
169
170# The TAB_SIZE tag can be used to set the number of spaces in a tab.
171# Doxygen uses this value to replace tabs by spaces in code fragments.
172
173TAB_SIZE = 4
174
175# This tag can be used to specify a number of aliases that acts
176# as commands in the documentation. An alias has the form "name=value".
177# For example adding "sideeffect=\par Side Effects:\n" will allow you to
178# put the command \sideeffect (or @sideeffect) in the documentation, which
179# will result in a user-defined paragraph with heading "Side Effects:".
180# You can put \n's in the value part of an alias to insert newlines.
181
182# Aliases
183ALIASES =
184
185# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
186# sources only. Doxygen will then generate output that is more tailored for C.
187# For instance, some of the names that are used will be different. The list
188# of all members will be omitted, etc.
189
190OPTIMIZE_OUTPUT_FOR_C = YES
191
192# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
193# sources only. Doxygen will then generate output that is more tailored for
194# Java. For instance, namespaces will be presented as packages, qualified
195# scopes will look different, etc.
196
197OPTIMIZE_OUTPUT_JAVA = NO
198
199# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
200# sources only. Doxygen will then generate output that is more tailored for
201# Fortran.
202
203OPTIMIZE_FOR_FORTRAN = NO
204
205# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
206# sources. Doxygen will then generate output that is tailored for
207# VHDL.
208
209OPTIMIZE_OUTPUT_VHDL = NO
210
211# Doxygen selects the parser to use depending on the extension of the files it parses.
212# With this tag you can assign which parser to use for a given extension.
213# Doxygen has a built-in mapping, but you can override or extend it using this tag.
214# The format is ext=language, where ext is a file extension, and language is one of
215# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,
216# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat
217# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
218# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
219
220EXTENSION_MAPPING =
221
222# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
223# to include (a tag file for) the STL sources as input, then you should
224# set this tag to YES in order to let doxygen match functions declarations and
225# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
226# func(std::string) {}). This also make the inheritance and collaboration
227# diagrams that involve STL classes more complete and accurate.
228
229BUILTIN_STL_SUPPORT = NO
230
231# If you use Microsoft's C++/CLI language, you should set this option to YES to
232# enable parsing support.
233
234CPP_CLI_SUPPORT = NO
235
236# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
237# Doxygen will parse them like normal C++ but will assume all classes use public
238# instead of private inheritance when no explicit protection keyword is present.
239
240SIP_SUPPORT = NO
241
242# For Microsoft's IDL there are propget and propput attributes to indicate getter
243# and setter methods for a property. Setting this option to YES (the default)
244# will make doxygen to replace the get and set methods by a property in the
245# documentation. This will only work if the methods are indeed getting or
246# setting a simple type. If this is not the case, or you want to show the
247# methods anyway, you should set this option to NO.
248
249IDL_PROPERTY_SUPPORT = NO
250
251# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
252# tag is set to YES, then doxygen will reuse the documentation of the first
253# member in the group (if any) for the other members of the group. By default
254# all members of a group must be documented explicitly.
255
256DISTRIBUTE_GROUP_DOC = NO
257
258# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
259# the same type (for instance a group of public functions) to be put as a
260# subgroup of that type (e.g. under the Public Functions section). Set it to
261# NO to prevent subgrouping. Alternatively, this can be done per class using
262# the \nosubgrouping command.
263
264SUBGROUPING = YES
265
266# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
267# is documented as struct, union, or enum with the name of the typedef. So
268# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
269# with name TypeT. When disabled the typedef will appear as a member of a file,
270# namespace, or class. And the struct will be named TypeS. This can typically
271# be useful for C code in case the coding convention dictates that all compound
272# types are typedef'ed and only the typedef is referenced, never the tag name.
273
274TYPEDEF_HIDES_STRUCT = NO
275
276# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
277# determine which symbols to keep in memory and which to flush to disk.
278# When the cache is full, less often used symbols will be written to disk.
279# For small to medium size projects (<1000 input files) the default value is
280# probably good enough. For larger projects a too small cache size can cause
281# doxygen to be busy swapping symbols to and from disk most of the time
282# causing a significant performance penality.
283# If the system has enough physical memory increasing the cache will improve the
284# performance by keeping more symbols in memory. Note that the value works on
285# a logarithmic scale so increasing the size by one will roughly double the
286# memory usage. The cache size is given by this formula:
287# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
288# corresponding to a cache size of 2^16 = 65536 symbols
289
290SYMBOL_CACHE_SIZE = 0
291
292#---------------------------------------------------------------------------
293# Build related configuration options
294#---------------------------------------------------------------------------
295
296# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
297# documentation are documented, even if no documentation was available.
298# Private class members and static file members will be hidden unless
299# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
300
301EXTRACT_ALL = YES
302
303# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
304# will be included in the documentation.
305
306EXTRACT_PRIVATE = NO
307
308# If the EXTRACT_STATIC tag is set to YES all static members of a file
309# will be included in the documentation.
310
311EXTRACT_STATIC = NO
312
313# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
314# defined locally in source files will be included in the documentation.
315# If set to NO only classes defined in header files are included.
316
317EXTRACT_LOCAL_CLASSES = YES
318
319# This flag is only useful for Objective-C code. When set to YES local
320# methods, which are defined in the implementation section but not in
321# the interface are included in the documentation.
322# If set to NO (the default) only methods in the interface are included.
323
324EXTRACT_LOCAL_METHODS = NO
325
326# If this flag is set to YES, the members of anonymous namespaces will be
327# extracted and appear in the documentation as a namespace called
328# 'anonymous_namespace{file}', where file will be replaced with the base
329# name of the file that contains the anonymous namespace. By default
330# anonymous namespace are hidden.
331
332EXTRACT_ANON_NSPACES = NO
333
334# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
335# undocumented members of documented classes, files or namespaces.
336# If set to NO (the default) these members will be included in the
337# various overviews, but no documentation section is generated.
338# This option has no effect if EXTRACT_ALL is enabled.
339
340HIDE_UNDOC_MEMBERS = NO
341
342# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
343# undocumented classes that are normally visible in the class hierarchy.
344# If set to NO (the default) these classes will be included in the various
345# overviews. This option has no effect if EXTRACT_ALL is enabled.
346
347HIDE_UNDOC_CLASSES = NO
348
349# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
350# friend (class|struct|union) declarations.
351# If set to NO (the default) these declarations will be included in the
352# documentation.
353
354HIDE_FRIEND_COMPOUNDS = NO
355
356# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
357# documentation blocks found inside the body of a function.
358# If set to NO (the default) these blocks will be appended to the
359# function's detailed documentation block.
360
361HIDE_IN_BODY_DOCS = YES
362
363# The INTERNAL_DOCS tag determines if documentation
364# that is typed after a \internal command is included. If the tag is set
365# to NO (the default) then the documentation will be excluded.
366# Set it to YES to include the internal documentation.
367
368INTERNAL_DOCS = NO
369
370# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
371# file names in lower-case letters. If set to YES upper-case letters are also
372# allowed. This is useful if you have classes or files whose names only differ
373# in case and if your file system supports case sensitive file names. Windows
374# and Mac users are advised to set this option to NO.
375
376CASE_SENSE_NAMES = YES
377
378# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
379# will show members with their full class and namespace scopes in the
380# documentation. If set to YES the scope will be hidden.
381
382HIDE_SCOPE_NAMES = NO
383
384# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
385# will put a list of the files that are included by a file in the documentation
386# of that file.
387
388SHOW_INCLUDE_FILES = NO
389
390# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
391# is inserted in the documentation for inline members.
392
393INLINE_INFO = YES
394
395# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
396# will sort the (detailed) documentation of file and class members
397# alphabetically by member name. If set to NO the members will appear in
398# declaration order.
399
400SORT_MEMBER_DOCS = YES
401
402# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
403# brief documentation of file, namespace and class members alphabetically
404# by member name. If set to NO (the default) the members will appear in
405# declaration order.
406
407SORT_BRIEF_DOCS = YES
408
409# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
410
411SORT_MEMBERS_CTORS_1ST = NO
412
413# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
414# hierarchy of group names into alphabetical order. If set to NO (the default)
415# the group names will appear in their defined order.
416
417SORT_GROUP_NAMES = YES
418
419# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
420# sorted by fully-qualified names, including namespaces. If set to
421# NO (the default), the class list will be sorted only by class name,
422# not including the namespace part.
423# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
424# Note: This option applies only to the class list, not to the
425# alphabetical list.
426
427SORT_BY_SCOPE_NAME = NO
428
429# The GENERATE_TODOLIST tag can be used to enable (YES) or
430# disable (NO) the todo list. This list is created by putting \todo
431# commands in the documentation.
432
433GENERATE_TODOLIST = YES
434
435# The GENERATE_TESTLIST tag can be used to enable (YES) or
436# disable (NO) the test list. This list is created by putting \test
437# commands in the documentation.
438
439GENERATE_TESTLIST = YES
440
441# The GENERATE_BUGLIST tag can be used to enable (YES) or
442# disable (NO) the bug list. This list is created by putting \bug
443# commands in the documentation.
444
445GENERATE_BUGLIST = YES
446
447# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
448# disable (NO) the deprecated list. This list is created by putting
449# \deprecated commands in the documentation.
450
451GENERATE_DEPRECATEDLIST= YES
452
453# The ENABLED_SECTIONS tag can be used to enable conditional
454# documentation sections, marked by \if sectionname ... \endif.
455
456ENABLED_SECTIONS =
457
458# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
459# the initial value of a variable or define consists of for it to appear in
460# the documentation. If the initializer consists of more lines than specified
461# here it will be hidden. Use a value of 0 to hide initializers completely.
462# The appearance of the initializer of individual variables and defines in the
463# documentation can be controlled using \showinitializer or \hideinitializer
464# command in the documentation regardless of this setting.
465
466MAX_INITIALIZER_LINES = 30
467
468# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
469# at the bottom of the documentation of classes and structs. If set to YES the
470# list will mention the files that were used to generate the documentation.
471
472SHOW_USED_FILES = YES
473
474# If the sources in your project are distributed over multiple directories
475# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
476# in the documentation. The default is NO.
477
478SHOW_DIRECTORIES = NO
479
480# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
481# This will remove the Files entry from the Quick Index and from the
482# Folder Tree View (if specified). The default is YES.
483
484SHOW_FILES = YES
485
486# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
487# Namespaces page.
488# This will remove the Namespaces entry from the Quick Index
489# and from the Folder Tree View (if specified). The default is YES.
490
491SHOW_NAMESPACES = YES
492
493# The FILE_VERSION_FILTER tag can be used to specify a program or script that
494# doxygen should invoke to get the current version for each file (typically from
495# the version control system). Doxygen will invoke the program by executing (via
496# popen()) the command <command> <input-file>, where <command> is the value of
497# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
498# provided by doxygen. Whatever the program writes to standard output
499# is used as the file version. See the manual for examples.
500
501FILE_VERSION_FILTER =
502
503# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
504# doxygen. The layout file controls the global structure of the generated output files
505# in an output format independent way. The create the layout file that represents
506# doxygen's defaults, run doxygen with the -l option. You can optionally specify a
507# file name after the option, if omitted DoxygenLayout.xml will be used as the name
508# of the layout file.
509
510LAYOUT_FILE =
511
512#---------------------------------------------------------------------------
513# configuration options related to warning and progress messages
514#---------------------------------------------------------------------------
515
516# The QUIET tag can be used to turn on/off the messages that are generated
517# by doxygen. Possible values are YES and NO. If left blank NO is used.
518
519QUIET = NO
520
521# The WARNINGS tag can be used to turn on/off the warning messages that are
522# generated by doxygen. Possible values are YES and NO. If left blank
523# NO is used.
524
525WARNINGS = YES
526
527# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
528# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
529# automatically be disabled.
530
531WARN_IF_UNDOCUMENTED = YES
532
533# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
534# potential errors in the documentation, such as not documenting some
535# parameters in a documented function, or documenting parameters that
536# don't exist or using markup commands wrongly.
537
538WARN_IF_DOC_ERROR = YES
539
540# This WARN_NO_PARAMDOC option can be abled to get warnings for
541# functions that are documented, but have no documentation for their parameters
542# or return value. If set to NO (the default) doxygen will only warn about
543# wrong or incomplete parameter documentation, but not about the absence of
544# documentation.
545
546WARN_NO_PARAMDOC = YES
547
548# The WARN_FORMAT tag determines the format of the warning messages that
549# doxygen can produce. The string should contain the $file, $line, and $text
550# tags, which will be replaced by the file and line number from which the
551# warning originated and the warning text. Optionally the format may contain
552# $version, which will be replaced by the version of the file (if it could
553# be obtained via FILE_VERSION_FILTER)
554
555WARN_FORMAT = "$file:$line: $text"
556
557# The WARN_LOGFILE tag can be used to specify a file to which warning
558# and error messages should be written. If left blank the output is written
559# to stderr.
560
561WARN_LOGFILE =
562
563#---------------------------------------------------------------------------
564# configuration options related to the input files
565#---------------------------------------------------------------------------
566
567# The INPUT tag can be used to specify the files and/or directories that contain
568# documented source files. You may enter file names like "myfile.cpp" or
569# directories like "/usr/src/myproject". Separate the files or directories
570# with spaces.
571
572INPUT = @srcdir@/examples.dox @top_srcdir@/src/lib
573
574# This tag can be used to specify the character encoding of the source files
575# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
576# also the default input encoding. Doxygen uses libiconv (or the iconv built
577# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
578# the list of possible encodings.
579
580INPUT_ENCODING = UTF-8
581
582# If the value of the INPUT tag contains directories, you can use the
583# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
584# and *.h) to filter out the source-files in the directories. If left
585# blank the following patterns are tested:
586# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
587# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
588
589FILE_PATTERNS =
590
591# The RECURSIVE tag can be used to turn specify whether or not subdirectories
592# should be searched for input files as well. Possible values are YES and NO.
593# If left blank NO is used.
594
595RECURSIVE = YES
596
597# The EXCLUDE tag can be used to specify files and/or directories that should
598# excluded from the INPUT source files. This way you can easily exclude a
599# subdirectory from a directory tree whose root is specified with the INPUT tag.
600
601EXCLUDE =
602
603# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
604# directories that are symbolic links (a Unix filesystem feature) are excluded
605# from the input.
606
607EXCLUDE_SYMLINKS = NO
608
609# If the value of the INPUT tag contains directories, you can use the
610# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
611# certain files from those directories. Note that the wildcards are matched
612# against the file with absolute path, so to exclude all test directories
613# for example use the pattern */test/*
614
615EXCLUDE_PATTERNS =
616
617# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
618# (namespaces, classes, functions, etc.) that should be excluded from the
619# output. The symbol name can be a fully qualified name, a word, or if the
620# wildcard * is used, a substring. Examples: ANamespace, AClass,
621# AClass::ANamespace, ANamespace::*Test
622
623EXCLUDE_SYMBOLS =
624
625# The EXAMPLE_PATH tag can be used to specify one or more files or
626# directories that contain example code fragments that are included (see
627# the \include command).
628
629EXAMPLE_PATH = @top_srcdir@/src/bin/
630
631# If the value of the EXAMPLE_PATH tag contains directories, you can use the
632# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
633# and *.h) to filter out the source-files in the directories. If left
634# blank all files are included.
635
636EXAMPLE_PATTERNS =
637
638# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
639# searched for input files to be used with the \include or \dontinclude
640# commands irrespective of the value of the RECURSIVE tag.
641# Possible values are YES and NO. If left blank NO is used.
642
643EXAMPLE_RECURSIVE = NO
644
645# The IMAGE_PATH tag can be used to specify one or more files or
646# directories that contain image that are included in the documentation (see
647# the \image command).
648
649IMAGE_PATH = img
650
651# The INPUT_FILTER tag can be used to specify a program that doxygen should
652# invoke to filter for each input file. Doxygen will invoke the filter program
653# by executing (via popen()) the command <filter> <input-file>, where <filter>
654# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
655# input file. Doxygen will then use the output that the filter program writes
656# to standard output.
657# If FILTER_PATTERNS is specified, this tag will be
658# ignored.
659
660INPUT_FILTER =
661
662# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
663# basis.
664# Doxygen will compare the file name with each pattern and apply the
665# filter if there is a match.
666# The filters are a list of the form:
667# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
668# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
669# is applied to all files.
670
671FILTER_PATTERNS =
672
673# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
674# INPUT_FILTER) will be used to filter the input files when producing source
675# files to browse (i.e. when SOURCE_BROWSER is set to YES).
676
677FILTER_SOURCE_FILES = NO
678
679#---------------------------------------------------------------------------
680# configuration options related to source browsing
681#---------------------------------------------------------------------------
682
683# If the SOURCE_BROWSER tag is set to YES then a list of source files will
684# be generated. Documented entities will be cross-referenced with these sources.
685# Note: To get rid of all source code in the generated output, make sure also
686# VERBATIM_HEADERS is set to NO.
687
688SOURCE_BROWSER = NO
689
690# Setting the INLINE_SOURCES tag to YES will include the body
691# of functions and classes directly in the documentation.
692
693INLINE_SOURCES = NO
694
695# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
696# doxygen to hide any special comment blocks from generated source code
697# fragments. Normal C and C++ comments will always remain visible.
698
699STRIP_CODE_COMMENTS = YES
700
701# If the REFERENCED_BY_RELATION tag is set to YES
702# then for each documented function all documented
703# functions referencing it will be listed.
704
705REFERENCED_BY_RELATION = YES
706
707# If the REFERENCES_RELATION tag is set to YES
708# then for each documented function all documented entities
709# called/used by that function will be listed.
710
711REFERENCES_RELATION = YES
712
713# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
714# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
715# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
716# link to the source code.
717# Otherwise they will link to the documentation.
718
719REFERENCES_LINK_SOURCE = YES
720
721# If the USE_HTAGS tag is set to YES then the references to source code
722# will point to the HTML generated by the htags(1) tool instead of doxygen
723# built-in source browser. The htags tool is part of GNU's global source
724# tagging system (see http://www.gnu.org/software/global/global.html). You
725# will need version 4.8.6 or higher.
726
727USE_HTAGS = NO
728
729# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
730# will generate a verbatim copy of the header file for each class for
731# which an include is specified. Set to NO to disable this.
732
733VERBATIM_HEADERS = YES
734
735#---------------------------------------------------------------------------
736# configuration options related to the alphabetical class index
737#---------------------------------------------------------------------------
738
739# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
740# of all compounds will be generated. Enable this if the project
741# contains a lot of classes, structs, unions or interfaces.
742
743ALPHABETICAL_INDEX = YES
744
745# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
746# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
747# in which this list will be split (can be a number in the range [1..20])
748
749COLS_IN_ALPHA_INDEX = 5
750
751# In case all classes in a project start with a common prefix, all
752# classes will be put under the same header in the alphabetical index.
753# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
754# should be ignored while generating the index headers.
755
756IGNORE_PREFIX =
757
758#---------------------------------------------------------------------------
759# configuration options related to the HTML output
760#---------------------------------------------------------------------------
761
762# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
763# generate HTML output.
764
765GENERATE_HTML = YES
766
767# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
768# If a relative path is entered the value of OUTPUT_DIRECTORY will be
769# put in front of it. If left blank `html' will be used as the default path.
770
771HTML_OUTPUT = html
772
773# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
774# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
775# doxygen will generate files with .html extension.
776
777HTML_FILE_EXTENSION = .html
778
779# The HTML_HEADER tag can be used to specify a personal HTML header for
780# each generated HTML page. If it is left blank doxygen will generate a
781# standard header.
782
783HTML_HEADER = @srcdir@/head.html
784
785# The HTML_FOOTER tag can be used to specify a personal HTML footer for
786# each generated HTML page. If it is left blank doxygen will generate a
787# standard footer.
788
789HTML_FOOTER = @srcdir@/foot.html
790
791# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
792# style sheet that is used by each HTML page. It can be used to
793# fine-tune the look of the HTML output. If the tag is left blank doxygen
794# will generate a default style sheet. Note that doxygen will try to copy
795# the style sheet file to the HTML output directory, so don't put your own
796# stylesheet in the HTML output directory as well, or it will be erased!
797
798HTML_STYLESHEET = @srcdir@/e.css
799
800# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
801# files or namespaces will be aligned in HTML using tables. If set to
802# NO a bullet list will be used.
803
804HTML_ALIGN_MEMBERS = YES
805
806# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
807# documentation will contain sections that can be hidden and shown after the
808# page has loaded. For this to work a browser that supports
809# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
810# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
811
812HTML_DYNAMIC_SECTIONS = NO
813
814# If the GENERATE_DOCSET tag is set to YES, additional index files
815# will be generated that can be used as input for Apple's Xcode 3
816# integrated development environment, introduced with OSX 10.5 (Leopard).
817# To create a documentation set, doxygen will generate a Makefile in the
818# HTML output directory. Running make will produce the docset in that
819# directory and running "make install" will install the docset in
820# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
821# it at startup.
822# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
823
824GENERATE_DOCSET = NO
825
826# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
827# feed. A documentation feed provides an umbrella under which multiple
828# documentation sets from a single provider (such as a company or product suite)
829# can be grouped.
830
831DOCSET_FEEDNAME = "Doxygen generated docs"
832
833# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
834# should uniquely identify the documentation set bundle. This should be a
835# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
836# will append .docset to the name.
837
838DOCSET_BUNDLE_ID = org.enlightenment.EPhysics
839
840# If the GENERATE_HTMLHELP tag is set to YES, additional index files
841# will be generated that can be used as input for tools like the
842# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
843# of the generated HTML documentation.
844
845GENERATE_HTMLHELP = NO
846
847# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
848# be used to specify the file name of the resulting .chm file. You
849# can add a path in front of the file if the result should not be
850# written to the html output directory.
851
852CHM_FILE =
853
854# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
855# be used to specify the location (absolute path including file name) of
856# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
857# the HTML help compiler on the generated index.hhp.
858
859HHC_LOCATION =
860
861# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
862# controls if a separate .chi index file is generated (YES) or that
863# it should be included in the master .chm file (NO).
864
865GENERATE_CHI = NO
866
867# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
868# is used to encode HtmlHelp index (hhk), content (hhc) and project file
869# content.
870
871CHM_INDEX_ENCODING =
872
873# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
874# controls whether a binary table of contents is generated (YES) or a
875# normal table of contents (NO) in the .chm file.
876
877BINARY_TOC = NO
878
879# The TOC_EXPAND flag can be set to YES to add extra items for group members
880# to the contents of the HTML help documentation and to the tree view.
881
882TOC_EXPAND = NO
883
884# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
885# are set, an additional index file will be generated that can be used as input for
886# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
887# HTML documentation.
888
889GENERATE_QHP = NO
890
891# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
892# be used to specify the file name of the resulting .qch file.
893# The path specified is relative to the HTML output folder.
894
895QCH_FILE =
896
897# The QHP_NAMESPACE tag specifies the namespace to use when generating
898# Qt Help Project output. For more information please see
899# http://doc.trolltech.com/qthelpproject.html#namespace
900
901QHP_NAMESPACE =
902
903# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
904# Qt Help Project output. For more information please see
905# http://doc.trolltech.com/qthelpproject.html#virtual-folders
906
907QHP_VIRTUAL_FOLDER = doc
908
909# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
910# For more information please see
911# http://doc.trolltech.com/qthelpproject.html#custom-filters
912
913QHP_CUST_FILTER_NAME =
914
915# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
916# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
917
918QHP_CUST_FILTER_ATTRS =
919
920# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
921# filter section matches.
922# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
923
924QHP_SECT_FILTER_ATTRS =
925
926# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
927# be used to specify the location of Qt's qhelpgenerator.
928# If non-empty doxygen will try to run qhelpgenerator on the generated
929# .qhp file.
930
931QHG_LOCATION =
932
933# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
934# top of each HTML page. The value NO (the default) enables the index and
935# the value YES disables it.
936
937DISABLE_INDEX = YES
938
939# This tag can be used to set the number of enum values (range [1..20])
940# that doxygen will group on one line in the generated HTML documentation.
941
942ENUM_VALUES_PER_LINE = 4
943
944# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
945# structure should be generated to display hierarchical information.
946# If the tag value is set to YES, a side panel will be generated
947# containing a tree-like index structure (just like the one that
948# is generated for HTML Help). For this to work a browser that supports
949# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
950# Windows users are probably better off using the HTML help feature.
951
952GENERATE_TREEVIEW = NO
953
954# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
955# and Class Hierarchy pages using a tree view instead of an ordered list.
956
957USE_INLINE_TREES = NO
958
959# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
960# used to set the initial width (in pixels) of the frame in which the tree
961# is shown.
962
963TREEVIEW_WIDTH = 250
964
965# Use this tag to change the font size of Latex formulas included
966# as images in the HTML documentation. The default is 10. Note that
967# when you change the font size after a successful doxygen run you need
968# to manually remove any form_*.png images from the HTML output directory
969# to force them to be regenerated.
970
971FORMULA_FONTSIZE = 10
972
973# When the SEARCHENGINE tag is enable doxygen will generate a search box for the HTML output. The underlying search engine uses javascript
974# and DHTML and should work on any modern browser. Note that when using HTML help (GENERATE_HTMLHELP) or Qt help (GENERATE_QHP)
975# there is already a search function so this one should typically
976# be disabled.
977
978SEARCHENGINE = NO
979
980#---------------------------------------------------------------------------
981# configuration options related to the LaTeX output
982#---------------------------------------------------------------------------
983
984# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
985# generate Latex output.
986
987GENERATE_LATEX = YES
988
989# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
990# If a relative path is entered the value of OUTPUT_DIRECTORY will be
991# put in front of it. If left blank `latex' will be used as the default path.
992
993LATEX_OUTPUT = latex
994
995# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
996# invoked. If left blank `latex' will be used as the default command name.
997
998LATEX_CMD_NAME = latex
999
1000# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1001# generate index for LaTeX. If left blank `makeindex' will be used as the
1002# default command name.
1003
1004MAKEINDEX_CMD_NAME = makeindex
1005
1006# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1007# LaTeX documents. This may be useful for small projects and may help to
1008# save some trees in general.
1009
1010COMPACT_LATEX = NO
1011
1012# The PAPER_TYPE tag can be used to set the paper type that is used
1013# by the printer. Possible values are: a4, a4wide, letter, legal and
1014# executive. If left blank a4wide will be used.
1015
1016PAPER_TYPE = a4wide
1017
1018# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1019# packages that should be included in the LaTeX output.
1020
1021EXTRA_PACKAGES =
1022
1023# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1024# the generated latex document. The header should contain everything until
1025# the first chapter. If it is left blank doxygen will generate a
1026# standard header. Notice: only use this tag if you know what you are doing!
1027
1028LATEX_HEADER =
1029
1030# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1031# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1032# contain links (just like the HTML output) instead of page references
1033# This makes the output suitable for online browsing using a pdf viewer.
1034
1035PDF_HYPERLINKS = YES
1036
1037# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1038# plain latex in the generated Makefile. Set this option to YES to get a
1039# higher quality PDF documentation.
1040
1041USE_PDFLATEX = YES
1042
1043# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1044# command to the generated LaTeX files. This will instruct LaTeX to keep
1045# running if errors occur, instead of asking the user for help.
1046# This option is also used when generating formulas in HTML.
1047
1048LATEX_BATCHMODE = NO
1049
1050# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1051# include the index chapters (such as File Index, Compound Index, etc.)
1052# in the output.
1053
1054LATEX_HIDE_INDICES = NO
1055
1056# If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.
1057
1058LATEX_SOURCE_CODE = NO
1059
1060#---------------------------------------------------------------------------
1061# configuration options related to the RTF output
1062#---------------------------------------------------------------------------
1063
1064# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1065# The RTF output is optimized for Word 97 and may not look very pretty with
1066# other RTF readers or editors.
1067
1068GENERATE_RTF = NO
1069
1070# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1071# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1072# put in front of it. If left blank `rtf' will be used as the default path.
1073
1074RTF_OUTPUT = rtf
1075
1076# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1077# RTF documents. This may be useful for small projects and may help to
1078# save some trees in general.
1079
1080COMPACT_RTF = NO
1081
1082# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1083# will contain hyperlink fields. The RTF file will
1084# contain links (just like the HTML output) instead of page references.
1085# This makes the output suitable for online browsing using WORD or other
1086# programs which support those fields.
1087# Note: wordpad (write) and others do not support links.
1088
1089RTF_HYPERLINKS = NO
1090
1091# Load stylesheet definitions from file. Syntax is similar to doxygen's
1092# config file, i.e. a series of assignments. You only have to provide
1093# replacements, missing definitions are set to their default value.
1094
1095RTF_STYLESHEET_FILE =
1096
1097# Set optional variables used in the generation of an rtf document.
1098# Syntax is similar to doxygen's config file.
1099
1100RTF_EXTENSIONS_FILE =
1101
1102#---------------------------------------------------------------------------
1103# configuration options related to the man page output
1104#---------------------------------------------------------------------------
1105
1106# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1107# generate man pages
1108
1109GENERATE_MAN = YES
1110
1111# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1112# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1113# put in front of it. If left blank `man' will be used as the default path.
1114
1115MAN_OUTPUT = man
1116
1117# The MAN_EXTENSION tag determines the extension that is added to
1118# the generated man pages (default is the subroutine's section .3)
1119
1120MAN_EXTENSION = .3
1121
1122# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1123# then it will generate one additional man file for each entity
1124# documented in the real man page(s). These additional files
1125# only source the real man page, but without them the man command
1126# would be unable to find the correct page. The default is NO.
1127
1128MAN_LINKS = YES
1129
1130#---------------------------------------------------------------------------
1131# configuration options related to the XML output
1132#---------------------------------------------------------------------------
1133
1134# If the GENERATE_XML tag is set to YES Doxygen will
1135# generate an XML file that captures the structure of
1136# the code including all documentation.
1137
1138GENERATE_XML = NO
1139
1140# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1141# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1142# put in front of it. If left blank `xml' will be used as the default path.
1143
1144XML_OUTPUT = xml
1145
1146# The XML_SCHEMA tag can be used to specify an XML schema,
1147# which can be used by a validating XML parser to check the
1148# syntax of the XML files.
1149
1150XML_SCHEMA =
1151
1152# The XML_DTD tag can be used to specify an XML DTD,
1153# which can be used by a validating XML parser to check the
1154# syntax of the XML files.
1155
1156XML_DTD =
1157
1158# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1159# dump the program listings (including syntax highlighting
1160# and cross-referencing information) to the XML output. Note that
1161# enabling this will significantly increase the size of the XML output.
1162
1163XML_PROGRAMLISTING = YES
1164
1165#---------------------------------------------------------------------------
1166# configuration options for the AutoGen Definitions output
1167#---------------------------------------------------------------------------
1168
1169# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1170# generate an AutoGen Definitions (see autogen.sf.net) file
1171# that captures the structure of the code including all
1172# documentation. Note that this feature is still experimental
1173# and incomplete at the moment.
1174
1175GENERATE_AUTOGEN_DEF = NO
1176
1177#---------------------------------------------------------------------------
1178# configuration options related to the Perl module output
1179#---------------------------------------------------------------------------
1180
1181# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1182# generate a Perl module file that captures the structure of
1183# the code including all documentation. Note that this
1184# feature is still experimental and incomplete at the
1185# moment.
1186
1187GENERATE_PERLMOD = NO
1188
1189# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1190# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1191# to generate PDF and DVI output from the Perl module output.
1192
1193PERLMOD_LATEX = NO
1194
1195# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1196# nicely formatted so it can be parsed by a human reader.
1197# This is useful
1198# if you want to understand what is going on.
1199# On the other hand, if this
1200# tag is set to NO the size of the Perl module output will be much smaller
1201# and Perl will parse it just the same.
1202
1203PERLMOD_PRETTY = YES
1204
1205# The names of the make variables in the generated doxyrules.make file
1206# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1207# This is useful so different doxyrules.make files included by the same
1208# Makefile don't overwrite each other's variables.
1209
1210PERLMOD_MAKEVAR_PREFIX =
1211
1212#---------------------------------------------------------------------------
1213# Configuration options related to the preprocessor
1214#---------------------------------------------------------------------------
1215
1216# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1217# evaluate all C-preprocessor directives found in the sources and include
1218# files.
1219
1220ENABLE_PREPROCESSING = YES
1221
1222# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1223# names in the source code. If set to NO (the default) only conditional
1224# compilation will be performed. Macro expansion can be done in a controlled
1225# way by setting EXPAND_ONLY_PREDEF to YES.
1226
1227MACRO_EXPANSION = NO
1228
1229# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1230# then the macro expansion is limited to the macros specified with the
1231# PREDEFINED and EXPAND_AS_DEFINED tags.
1232
1233EXPAND_ONLY_PREDEF = NO
1234
1235# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1236# in the INCLUDE_PATH (see below) will be search if a #include is found.
1237
1238SEARCH_INCLUDES = YES
1239
1240# The INCLUDE_PATH tag can be used to specify one or more directories that
1241# contain include files that are not input files but should be processed by
1242# the preprocessor.
1243
1244INCLUDE_PATH =
1245
1246# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1247# patterns (like *.h and *.hpp) to filter out the header-files in the
1248# directories. If left blank, the patterns specified with FILE_PATTERNS will
1249# be used.
1250
1251INCLUDE_FILE_PATTERNS =
1252
1253# The PREDEFINED tag can be used to specify one or more macro names that
1254# are defined before the preprocessor is started (similar to the -D option of
1255# gcc). The argument of the tag is a list of macros of the form: name
1256# or name=definition (no spaces). If the definition and the = are
1257# omitted =1 is assumed. To prevent a macro definition from being
1258# undefined via #undef or recursively expanded use the := operator
1259# instead of the = operator.
1260
1261PREDEFINED = __UNUSED__=
1262
1263# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1264# this tag can be used to specify a list of macro names that should be expanded.
1265# The macro definition that is found in the sources will be used.
1266# Use the PREDEFINED tag if you want to use a different macro definition.
1267
1268EXPAND_AS_DEFINED =
1269
1270# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1271# doxygen's preprocessor will remove all function-like macros that are alone
1272# on a line, have an all uppercase name, and do not end with a semicolon. Such
1273# function macros are typically used for boiler-plate code, and will confuse
1274# the parser if not removed.
1275
1276SKIP_FUNCTION_MACROS = YES
1277
1278#---------------------------------------------------------------------------
1279# Configuration::additions related to external references
1280#---------------------------------------------------------------------------
1281
1282# The TAGFILES option can be used to specify one or more tagfiles.
1283# Optionally an initial location of the external documentation
1284# can be added for each tagfile. The format of a tag file without
1285# this location is as follows:
1286#
1287# TAGFILES = file1 file2 ...
1288# Adding location for the tag files is done as follows:
1289#
1290# TAGFILES = file1=loc1 "file2 = loc2" ...
1291# where "loc1" and "loc2" can be relative or absolute paths or
1292# URLs. If a location is present for each tag, the installdox tool
1293# does not have to be run to correct the links.
1294# Note that each tag file must have a unique name
1295# (where the name does NOT include the path)
1296# If a tag file is not located in the directory in which doxygen
1297# is run, you must also specify the path to the tagfile here.
1298
1299TAGFILES =
1300
1301# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1302# a tag file that is based on the input files it reads.
1303
1304GENERATE_TAGFILE =
1305
1306# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1307# in the class index. If set to NO only the inherited external classes
1308# will be listed.
1309
1310ALLEXTERNALS = NO
1311
1312# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1313# in the modules index. If set to NO, only the current project's groups will
1314# be listed.
1315
1316EXTERNAL_GROUPS = YES
1317
1318# The PERL_PATH should be the absolute path and name of the perl script
1319# interpreter (i.e. the result of `which perl').
1320
1321PERL_PATH = /usr/bin/perl
1322
1323#---------------------------------------------------------------------------
1324# Configuration options related to the dot tool
1325#---------------------------------------------------------------------------
1326
1327# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1328# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1329# or super classes. Setting the tag to NO turns the diagrams off. Note that
1330# this option is superseded by the HAVE_DOT option below. This is only a
1331# fallback. It is recommended to install and use dot, since it yields more
1332# powerful graphs.
1333
1334CLASS_DIAGRAMS = YES
1335
1336# You can define message sequence charts within doxygen comments using the \msc
1337# command. Doxygen will then run the mscgen tool (see
1338# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1339# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1340# the mscgen tool resides. If left empty the tool is assumed to be found in the
1341# default search path.
1342
1343MSCGEN_PATH =
1344
1345# If set to YES, the inheritance and collaboration graphs will hide
1346# inheritance and usage relations if the target is undocumented
1347# or is not a class.
1348
1349HIDE_UNDOC_RELATIONS = YES
1350
1351# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1352# available from the path. This tool is part of Graphviz, a graph visualization
1353# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1354# have no effect if this option is set to NO (the default)
1355
1356HAVE_DOT = NO
1357
1358# By default doxygen will write a font called FreeSans.ttf to the output
1359# directory and reference it in all dot files that doxygen generates. This
1360# font does not include all possible unicode characters however, so when you need
1361# these (or just want a differently looking font) you can specify the font name
1362# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1363# which can be done by putting it in a standard location or by setting the
1364# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1365# containing the font.
1366
1367DOT_FONTNAME = FreeSans
1368
1369# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1370# The default size is 10pt.
1371
1372DOT_FONTSIZE = 10
1373
1374# By default doxygen will tell dot to use the output directory to look for the
1375# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1376# different font using DOT_FONTNAME you can set the path where dot
1377# can find it using this tag.
1378
1379DOT_FONTPATH =
1380
1381# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1382# will generate a graph for each documented class showing the direct and
1383# indirect inheritance relations. Setting this tag to YES will force the
1384# the CLASS_DIAGRAMS tag to NO.
1385
1386CLASS_GRAPH = YES
1387
1388# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1389# will generate a graph for each documented class showing the direct and
1390# indirect implementation dependencies (inheritance, containment, and
1391# class references variables) of the class with other documented classes.
1392
1393COLLABORATION_GRAPH = YES
1394
1395# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1396# will generate a graph for groups, showing the direct groups dependencies
1397
1398GROUP_GRAPHS = YES
1399
1400# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1401# collaboration diagrams in a style similar to the OMG's Unified Modeling
1402# Language.
1403
1404UML_LOOK = NO
1405
1406# If set to YES, the inheritance and collaboration graphs will show the
1407# relations between templates and their instances.
1408
1409TEMPLATE_RELATIONS = NO
1410
1411# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1412# tags are set to YES then doxygen will generate a graph for each documented
1413# file showing the direct and indirect include dependencies of the file with
1414# other documented files.
1415
1416INCLUDE_GRAPH = YES
1417
1418# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1419# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1420# documented header file showing the documented files that directly or
1421# indirectly include this file.
1422
1423INCLUDED_BY_GRAPH = YES
1424
1425# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1426# doxygen will generate a call dependency graph for every global function
1427# or class method. Note that enabling this option will significantly increase
1428# the time of a run. So in most cases it will be better to enable call graphs
1429# for selected functions only using the \callgraph command.
1430
1431CALL_GRAPH = NO
1432
1433# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1434# doxygen will generate a caller dependency graph for every global function
1435# or class method. Note that enabling this option will significantly increase
1436# the time of a run. So in most cases it will be better to enable caller
1437# graphs for selected functions only using the \callergraph command.
1438
1439CALLER_GRAPH = NO
1440
1441# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1442# will graphical hierarchy of all classes instead of a textual one.
1443
1444GRAPHICAL_HIERARCHY = YES
1445
1446# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1447# then doxygen will show the dependencies a directory has on other directories
1448# in a graphical way. The dependency relations are determined by the #include
1449# relations between the files in the directories.
1450
1451DIRECTORY_GRAPH = YES
1452
1453# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1454# generated by dot. Possible values are png, jpg, or gif
1455# If left blank png will be used.
1456
1457DOT_IMAGE_FORMAT = png
1458
1459# The tag DOT_PATH can be used to specify the path where the dot tool can be
1460# found. If left blank, it is assumed the dot tool can be found in the path.
1461
1462DOT_PATH =
1463
1464# The DOTFILE_DIRS tag can be used to specify one or more directories that
1465# contain dot files that are included in the documentation (see the
1466# \dotfile command).
1467
1468DOTFILE_DIRS =
1469
1470# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1471# nodes that will be shown in the graph. If the number of nodes in a graph
1472# becomes larger than this value, doxygen will truncate the graph, which is
1473# visualized by representing a node as a red box. Note that doxygen if the
1474# number of direct children of the root node in a graph is already larger than
1475# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1476# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1477
1478DOT_GRAPH_MAX_NODES = 50
1479
1480# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1481# graphs generated by dot. A depth value of 3 means that only nodes reachable
1482# from the root by following a path via at most 3 edges will be shown. Nodes
1483# that lay further from the root node will be omitted. Note that setting this
1484# option to 1 or 2 may greatly reduce the computation time needed for large
1485# code bases. Also note that the size of a graph can be further restricted by
1486# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1487
1488MAX_DOT_GRAPH_DEPTH = 0
1489
1490# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1491# background. This is disabled by default, because dot on Windows does not
1492# seem to support this out of the box. Warning: Depending on the platform used,
1493# enabling this option may lead to badly anti-aliased labels on the edges of
1494# a graph (i.e. they become hard to read).
1495
1496DOT_TRANSPARENT = NO
1497
1498# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1499# files in one run (i.e. multiple -o and -T options on the command line). This
1500# makes dot run faster, but since only newer versions of dot (>1.8.10)
1501# support this, this feature is disabled by default.
1502
1503DOT_MULTI_TARGETS = NO
1504
1505# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1506# generate a legend page explaining the meaning of the various boxes and
1507# arrows in the dot generated graphs.
1508
1509GENERATE_LEGEND = YES
1510
1511# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1512# remove the intermediate dot files that are used to generate
1513# the various graphs.
1514
1515DOT_CLEANUP = YES
diff --git a/legacy/ephysics/doc/Makefile.am b/legacy/ephysics/doc/Makefile.am
new file mode 100644
index 0000000000..b00aa037c0
--- /dev/null
+++ b/legacy/ephysics/doc/Makefile.am
@@ -0,0 +1,35 @@
1
2MAINTAINERCLEANFILES = Makefile.in
3
4.PHONY: doc
5
6PACKAGE_DOCNAME = $(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc
7
8if EFL_BUILD_DOC
9
10doc-clean:
11 rm -rf html/ latex/ man/ xml/ $(top_builddir)/$(PACKAGE_DOCNAME).tar*
12
13doc: all doc-clean
14 $(efl_doxygen)
15 cp $(srcdir)/img/* html/
16 cp $(srcdir)/img/* latex/
17 rm -rf $(PACKAGE_DOCNAME).tar*
18 mkdir -p $(PACKAGE_DOCNAME)/doc
19 cp -R html/ latex/ man/ $(PACKAGE_DOCNAME)/doc
20 tar cf $(PACKAGE_DOCNAME).tar $(PACKAGE_DOCNAME)/
21 bzip2 -9 $(PACKAGE_DOCNAME).tar
22 rm -rf $(PACKAGE_DOCNAME)/
23 mv $(PACKAGE_DOCNAME).tar.bz2 $(top_builddir)
24
25clean-local: doc-clean
26
27else
28
29doc:
30 @echo "Documentation not built. Run ./configure --help"
31
32endif
33
34EXTRA_DIST = Doxyfile e.css foot.html head.html $(wildcard img/*.*) \
35 $(wildcard examples/*.*) examples.dox
diff --git a/legacy/ephysics/doc/e.css b/legacy/ephysics/doc/e.css
new file mode 100644
index 0000000000..44a9f254db
--- /dev/null
+++ b/legacy/ephysics/doc/e.css
@@ -0,0 +1,295 @@
1/*
2 Author:
3 Andres Blanc <andresblanc@gmail.com>
4 DaveMDS Andreoli <dave@gurumeditation.it>
5
6 Supported Browsers:
7 ie7, opera9, konqueror4 and firefox3
8
9 Please use a different file for ie6, ie5, etc. hacks.
10*/
11
12
13/* Necessary to place the footer at the bottom of the page */
14html, body {
15 height: 100%;
16 margin: 0px;
17 padding: 0px;
18}
19
20#container {
21 min-height: 100%;
22 height: auto !important;
23 height: 100%;
24 margin: 0 auto -53px;
25}
26
27#footer, #push {
28 height: 53px;
29}
30
31
32* html #container {
33 height: 100%;
34}
35
36/* Prevent floating elements overflowing containers */
37.clear {
38 clear: both;
39 width: 0px;
40 height: 0px;
41}
42
43/* Flexible & centered layout from 750 to 960 pixels */
44.layout {
45 max-width: 960px;
46 min-width: 760px;
47 margin-left: auto;
48 margin-right: auto;
49}
50
51body {
52 /*font-family: Lucida Grande, Helvetica, sans-serif;*/
53 font-family: "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif
54}
55
56/* Prevent design overflowing the viewport in small resolutions */
57#container {
58 padding-right: 17px;
59 padding-left: 17px;
60 background-image: url(head_bg.png);
61 background-repeat: repeat-x;
62}
63
64/****************************/
65/* Top main menu */
66/****************************/
67#header_logo {
68 background-image : url(logo.png);
69 width : 61px;
70}
71
72#header_logo a {
73 position : absolute;
74 border : 0px;
75 background-color : transparent;
76 top : 0px;
77 width : 60px;
78 height : 60px;
79}
80
81#header_menu {
82 background-image : url(header_menu_background.png);
83 font : normal 10pt verdana,'Bitstream Vera Sans',helvetica,arial,sans-serif;
84 text-align : right;
85}
86
87#header_last {
88 background-image : url(header_menu_background_last.png);
89 width : 15px;
90}
91
92td.nav_passive {
93 background : url(header_menu_unselected_background.png) 0 0 no-repeat;
94 height : 63px;
95 font-family : "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif;
96 font-size : 11px;
97 padding : 20px 10px 20px 10px;
98 vertical-align : middle;
99}
100
101td.nav_active {
102 background : url(header_menu_current_background.png) 0 0 no-repeat;
103 height : 63px;
104 color : #646464;
105 font-family : "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif;
106 font-size : 11px;
107 font-weight : bold;
108 padding : 20px 10px 20px 10px;
109 vertical-align : middle;
110}
111
112#header_menu a {
113 display : block;
114 text-decoration : none;
115 cursor : pointer;
116 color : #cdcdcd;
117}
118
119
120
121#header {
122 width: 100%;
123 height: 102px;
124}
125
126#header h1 {
127 width: 63px;
128 height: 63px;
129 position: absolute;
130 margin: 0px;
131}
132
133#header h1 span {
134 display: none;
135}
136
137#header h2 {
138 display: none;
139}
140
141/* .menu-container is used to set properties common to .menu and .submenu */
142#header .menu-container {
143}
144
145#header .menu-container ul {
146 list-style-type: none;
147 list-style-position: inside;
148 margin: 0;
149}
150
151#header .menu-container li {
152 display: block;
153 float: right;
154}
155
156#header .menu {
157 height: 63px;
158 display: block;
159 background-image: url(menu_bg.png);
160 background-repeat: repeat-x;
161}
162
163#header .menu ul {
164 height: 100%;
165 display: block;
166 background-image: url(menu_bg_last.png);
167 background-repeat: no-repeat;
168 background-position: top right;
169 padding-right: 17px;
170}
171
172#header .menu li {
173 height: 100%;
174 text-align: center;
175 background-image: url(menu_bg_unsel.png);
176 background-repeat: no-repeat;
177}
178
179#header .menu a {
180 height: 100%;
181 display: block;
182 color: #cdcdcd;
183 text-decoration: none;
184 font-size: 10pt;
185 line-height: 59px;
186 text-align: center;
187 padding: 0px 15px 0px 15px;
188}
189
190#header .menu li:hover {
191 background-image: url(menu_bg_hover.png);
192 background-repeat: no-repeat;
193}
194
195#header .menu li:hover a {
196 color: #FFFFFF;
197}
198
199#header .menu li.current {
200 background-image: url(menu_bg_current.png);
201 background-repeat: no-repeat;
202}
203
204#header .menu li.current a {
205 color: #646464;
206}
207
208
209/* Hide all the submenus but the current */
210#header .submenu ul {
211 display: none;
212}
213
214#header .submenu .current {
215 display: block;
216}
217
218#header .submenu {
219 font: bold 10px verdana,'Bitstream Vera Sans',helvetica,arial,sans-serif;
220 margin-top: 10px;
221}
222
223#header .submenu a {
224 color: #888888;
225 text-decoration: none;
226 font-size: 0.9em;
227 line-height: 15px;
228 padding:0px 5px 0px 5px;
229}
230
231#header .submenu a:hover {
232 color: #444444;
233}
234
235#header .submenu li {
236 border-left: 1px solid #DDDDDD;
237}
238
239#header .submenu li:last-child {
240 border-left: 0;
241}
242
243#header .doxytitle {
244 position: absolute;
245 font-size: 1.8em;
246 font-weight: bold;
247 color: #444444;
248 line-height: 35px;
249}
250
251#header small {
252 font-size: 0.4em;
253}
254
255#footer {
256 background-image: url(foot_bg.png);
257 width: 100%;
258}
259
260#footer table {
261 width: 100%;
262 text-align: center;
263 white-space: nowrap;
264 padding: 5px 30px 5px 30px;
265 font-size: 0.8em;
266 font-family: "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif;
267 color: #888888;
268}
269
270#footer td.copyright {
271 width: 100%;
272}
273
274table.edcref tr td.block {
275 vertical-align: top;
276 padding-top: 10px;
277}
278
279table.edcref tr.section td.section, div.luaclass {
280 color: #888;
281 font-size: 16pt;
282 padding: 15px;
283 border-top: 1px solid #ccc;
284 text-align: center;
285}
286
287table.edcref tr.section td.section a {
288 color: #888;
289 text-decoration: none;
290}
291
292div.luaattrib {
293 color: #888;
294 border: 1px solid #ccc;
295}
diff --git a/legacy/ephysics/doc/examples.dox b/legacy/ephysics/doc/examples.dox
new file mode 100644
index 0000000000..56ceb48221
--- /dev/null
+++ b/legacy/ephysics/doc/examples.dox
@@ -0,0 +1,208 @@
1/**
2 * @page Examples Examples
3 *
4 * Here is a page with examples.
5 *
6 * @li @ref tutorial_ephysics_bouncing_ball
7 * @li @ref ephysics_logo_c
8 */
9
10/**
11 * @page tutorial_ephysics_bouncing_ball EPhysics - Bouncing Ball
12 *
13 * The purpose of this example is to show how to write an simple application -
14 * as the name suggests - with a small ball bouncing on the ground and
15 * responding to users events by making it jump - applying a central impulse on
16 * it.
17 *
18 * We'll guide you on defining a EPhysics world, defining its render geometry
19 * and the physics limiting boundaries, you'll learn how to add EPhysics bodies
20 * and how to associate it to evas objects. We also explain how to change
21 * restitution and friction properties. We see how to apply central impulse on
22 * a EPhysics_Body by implementing an elementary input event callback and
23 * calling the proper function.
24 *
25 * @section test-structure A test struct
26 * @dontinclude ephysics_test.h
27 *
28 * While in this example we'll be working with a struct to hold some objects in
29 * our code. For clarity sake we present you the struct declaration in the
30 * following block.
31 *
32 *
33 * @skip struct _Test_Data
34 * @until };
35 *
36 * @section world-new World Initialization
37 * @dontinclude test_bouncing_ball.c
38 *
39 * Calling ephysics_world_new()
40 * will create a new physics world with its collision configuration, constraint
41 * solver, broadphase interface and dispatcher.
42 *
43 * The default gravity is set to -9.81. It's possible to stop a running world
44 * but its default status is running. Take a look at
45 * ephysics_world_running_set() for further informations about world running
46 * status.
47 *
48 * @skipline ephysics_world_new
49 *
50 * @section render-geometry Render geometry
51 *
52 * By setting the render geometry you tell ephysics the dimensions of rendered
53 * area to be take on account by default updates.
54 *
55 * By default it starts with null x, y, width and height. Initially there's no
56 * physics limits but - as we'll see later in this example - boundaries can be
57 * added by issuing either ephysics_body_top_boundary_add(),
58 * ephysics_body_bottom_boundary_add(), ephysics_body_left_boundary_add() and
59 * ephysics_body_right_boundary_add().
60 *
61 * While setting the worlds render geometry the first parameter is our just
62 * created world, the following parameters indicate the x, y, width and height
63 * of our area of interest.
64 *
65 * @skipline ephysics_world_render_geometry_set
66 *
67 * @section boundaries Adding boundaries
68 *
69 * Boundaries are physics limits added by EPhysics which you can use to limit
70 * the area where your objects can move around. Bear in mind that those
71 * boundaries are created by EPhysics taking in account the render geometry you
72 * have previously defined by calling ephysics_world_render_geometry_set().
73 *
74 * In our example we start by adding a bottom boundary. This EPhysics_Body
75 * represents a physics limit under the world render geometry.
76 *
77 * The second line states the restitution factor for that bottom boundary, and
78 * the third line its friction. These changes will make our ball to bounce
79 * whenever it hits the ground.
80 *
81 * @skip ephysics_body_bottom_boundary_add
82 * @until ephysics_body_friction_set
83 *
84 * Then we add a right boundary limiting the physics world on the left side, we
85 * also change its restitution and friction factors but with a smaller value,
86 * we don't want to make it bounce as much as it is when hits the ground.
87 *
88 * @skip ephysics_body_right_boundary_add
89 * @until ephysics_body_friction_set
90 *
91 * We also add a left boundary taking the same considerations for right
92 * boundary.
93 *
94 * @skip ephysics_body_left_boundary_add
95 * @until ephysics_body_friction_set
96 *
97 * One of this examples requirements is to make the ball jump after a specific
98 * user event, so the ball can suffer an impulse for any direction.
99 *
100 * With an upper impulse we don't want our ball to fly all over there, we want
101 * to limit its upper movements, it's intended to limit the ball movement
102 * within a box, it should not leave the render geometry area, for that purpose
103 * we must define a top boundary.
104 *
105 * @skipline ephysics_body_top_boundary_add
106 * @dontinclude test_bouncing_ball.c
107 *
108 * @section world-populate Adding a ball
109 *
110 * Since we have defined the physics limits with our boundaries it's time to
111 * add some fun. Here we add a ball as an elementary image widget and tell
112 * ephysics about it.
113 *
114 * After setting the file that will be used as the image's source of our elm
115 * image we move it to the center of render geometry and resize it to 70x70
116 * pixels and show it.
117 *
118 * @skip elm_image_add
119 * @until evas_object_show
120 *
121 * The evas object is just set and we must tell EPhysics about it, creating the
122 * EPhysics_Body representing our ball and associating it to the just created
123 * evas object.
124 *
125 * Once the ball has been moved to the center of render geometry it should
126 * start falling after associating it to the EPhysics_Body. By default its mass
127 * is initially set to 1 kilo, but it can be changed by calling
128 * ephysics_body_mass_set(). Bear in mind that if you change its mass to 0
129 * kilos it becomes a static body and will not move at all, the body will
130 * remain fixed in the initial position.
131 *
132 * In the following code the first line adds a circle body, then we associate
133 * the evas object to EPhysics_Body, EPhysics will map every changes on physics
134 * object simulation to its evas object. Some restitution and friction factors
135 * are added as well.
136 *
137 * @skip ephysics_body_circle_add
138 * @until ephysics_body_friction_set
139 *
140 * @section jumping-ball Making it jump
141 *
142 * The next step is to give us the ability to make our ball to jump - actually
143 * apply some impulse whenever a key has been pressed. Then we add a elementary
144 * input callback to the window widget.
145 *
146 * @skipline elm_object_event_callback_add
147 *
148 * @dontinclude test_bouncing_ball.c
149 *
150 * The jumping callback implementation consists on handling only key up events
151 * and discarding any other input event we get. We're interested on keyboard
152 * events only. All the operations done in the following lines are done on
153 * sphere EPhysics_Body previously created.
154 *
155 * We mainly use the ephysics_body_central_impulse_apply() function. This
156 * function applies an inpulse on the center of a body.
157 *
158 * Once pressed \<Up> key it applies a central impulse of 0 kilos on X axis and
159 * 10 kilos on Y - so the ball is forced up.
160 *
161 * If \<Down> key has been pressed we apply an impulse of 0 kilos on X axis and
162 * -10 on Y - here the ball is forced down.
163 *
164 * In the case of \<Right> key pressing it's applied an impulse of 10 kilos on X
165 * axis and 0 kilos on Y - which applies a force to the right side. But if the
166 * key being pressed is \<Left> the opposite is done, and an impulse of -10
167 * kilos is applied on X and 0 kilos on Y - and the ball is forced to the left.
168 *
169 * @skip _on_keydown
170 * @until }
171 *
172 * Here we finish the very simple bouncing ball example. The full source code
173 * can be found at @ref test_bouncing_ball_c.
174 *
175 */
176
177/**
178 * @page test_bouncing_ball_c test_bouncing_ball.c
179 *
180 * @section ephysics-test-h ephysics_test.h
181 * @include ephysics_test.h
182 *
183 * @section test-bouncing-ball-c test_bouncing_ball.c
184 * @dontinclude test.c
185 * @skip test_clean
186 * @until }
187 *
188 * @skip test_data_new
189 * @until }
190 *
191 * @skip test_win_add
192 * @until }
193 *
194 * @include test_bouncing_ball.c
195 *
196 *
197 * @example test_bouncing_ball.c
198 */
199
200/**
201 * @page ephysics_logo_c ephysics_logo.c
202 *
203 * @section ephysics-logo-c ephysics_logo.c
204 * @include ephysics_logo.c
205 *
206 * @example ephysics_logo.c
207 */
208
diff --git a/legacy/ephysics/doc/foot.html b/legacy/ephysics/doc/foot.html
new file mode 100644
index 0000000000..d43cf8fcc0
--- /dev/null
+++ b/legacy/ephysics/doc/foot.html
@@ -0,0 +1,18 @@
1
2 <div id="push"></div>
3 </div> <!-- #content -->
4 </div> <!-- .layout -->
5
6 </div> <!-- #container -->
7
8
9 <div id="footer">
10 <table><tr>
11 <td class="copyright">Copyright &copy;$year Enlightenment</td>
12 <td class="generated">Docs generated $datetime</td>
13 </tr></table>
14 </div>
15
16
17</body>
18</html>
diff --git a/legacy/ephysics/doc/head.html b/legacy/ephysics/doc/head.html
new file mode 100644
index 0000000000..35236ace8d
--- /dev/null
+++ b/legacy/ephysics/doc/head.html
@@ -0,0 +1,67 @@
1<html>
2<head>
3 <title>$title</title>
4 <meta http-equiv="content-type" content="text/html;charset=UTF-8">
5 <meta name="author" content="Andres Blanc" >
6
7 <link rel="icon" href="img/favicon.png" type="image/x-icon">
8 <link rel="shortcut icon" href="img/favicon.png" type="image/x-icon">
9 <link rel="icon" href="img/favicon.png" type="image/ico">
10 <link rel="shortcut icon" href="img/favicon.png" type="image/ico">
11
12 <link rel="stylesheet" type="text/css" href="e.css">
13 <link rel="stylesheet" type="text/css" href="edoxy.css">
14</head>
15
16<body>
17
18<div id="container">
19
20<div id="header">
21<div class="layout">
22
23 <h1><span>Enlightenment</span></h1>
24 <h2><span>Beauty at your fingertips</span></h2>
25
26 <table cellspacing="0" cellpadding="0" width="100%"><tr>
27 <td id="header_logo">
28 <a href="http://www.enlightenment.org"></a>
29 </td>
30 <td id="header_menu">
31 <table cellspacing="0" cellpadding="0" align="right"><tr>
32 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=home">Home</a></td>
33 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=news">News</a></td>
34 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=about">About</a></td>
35 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=download">Download</a></td>
36 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=support">Support</a></td>
37 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=contribute">Contribute</a></td>
38 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=contact">Contact</a></td>
39 <td class="nav_passive"><a class="nav_passive" href="http://trac.enlightenment.org/e">Tracker</a></td>
40 <td class="nav_passive"><a class="nav_passive" href="http://www.enlightenment.org/p.php?p=docs">Docs</a></td>
41 </tr></table>
42 </td>
43 <td id="header_last"></td>
44 </tr></table>
45
46 <div class="doxytitle">
47 $projectname Documentation <small>at $date</small>
48 </div>
49
50 <div class="menu-container">
51 <div class="submenu">
52 <ul class="current">
53 <li><a href="files.html">Files</a></li>
54 <li><a href="Examples.html">Examples</a></li>
55 <li><a href="EPhysics_8h.html">EPhysics API</a></li>
56 <li class="current"><a href="index.html">Main Page</a></li>
57 </ul>
58 </div>
59 </div>
60
61
62 <div class="clear"></div>
63</div>
64</div>
65
66<div id="content">
67<div class="layout">
diff --git a/legacy/ephysics/doc/img/diagram_ephysics.png b/legacy/ephysics/doc/img/diagram_ephysics.png
new file mode 100644
index 0000000000..706c796a7e
--- /dev/null
+++ b/legacy/ephysics/doc/img/diagram_ephysics.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/e.png b/legacy/ephysics/doc/img/e.png
new file mode 100644
index 0000000000..d42aeb4200
--- /dev/null
+++ b/legacy/ephysics/doc/img/e.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/edoxy.css b/legacy/ephysics/doc/img/edoxy.css
new file mode 100644
index 0000000000..311ca23d46
--- /dev/null
+++ b/legacy/ephysics/doc/img/edoxy.css
@@ -0,0 +1,486 @@
1/*
2 * This file contain a custom doxygen style to match e.org graphics
3 */
4
5
6
7/* BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV {
8 font-family: Geneva, Arial, Helvetica, sans-serif;
9}*/
10BODY, TD {
11 font-size: 12px;
12}
13H1 {
14 text-align: center;
15 font-size: 160%;
16}
17H2 {
18 font-size: 120%;
19}
20H3 {
21 font-size: 100%;
22}
23CAPTION {
24 font-weight: bold
25}
26DIV.qindex {
27 width: 100%;
28 background-color: #e8eef2;
29 border: 1px solid #84b0c7;
30 text-align: center;
31 margin: 2px;
32 padding: 2px;
33 line-height: 140%;
34}
35DIV.navpath {
36 width: 100%;
37 background-color: #e8eef2;
38 border: 1px solid #84b0c7;
39 text-align: center;
40 margin: 2px;
41 padding: 2px;
42 line-height: 140%;
43}
44DIV.navtab {
45 background-color: #e8eef2;
46 border: 1px solid #84b0c7;
47 text-align: center;
48 margin: 2px;
49 margin-right: 15px;
50 padding: 2px;
51}
52TD.navtab {
53 font-size: 70%;
54}
55A.qindex {
56 text-decoration: none;
57 font-weight: bold;
58 color: #1A419D;
59}
60A.qindex:visited {
61 text-decoration: none;
62 font-weight: bold;
63 color: #1A419D
64}
65A.qindex:hover {
66 text-decoration: none;
67 background-color: #ddddff;
68}
69A.qindexHL {
70 text-decoration: none;
71 font-weight: bold;
72 background-color: #6666cc;
73 color: #ffffff;
74 border: 1px double #9295C2;
75}
76A.qindexHL:hover {
77 text-decoration: none;
78 background-color: #6666cc;
79 color: #ffffff;
80}
81A.qindexHL:visited {
82 text-decoration: none;
83 background-color: #6666cc;
84 color: #ffffff
85}
86A.el {
87 text-decoration: none;
88 font-weight: bold
89}
90A.elRef {
91 font-weight: bold
92}
93A.code:link {
94 text-decoration: none;
95 font-weight: normal;
96 color: #0000FF
97}
98A.code:visited {
99 text-decoration: none;
100 font-weight: normal;
101 color: #0000FF
102}
103A.codeRef:link {
104 font-weight: normal;
105 color: #0000FF
106}
107A.codeRef:visited {
108 font-weight: normal;
109 color: #0000FF
110}
111A:hover, A:visited:hover {
112 text-decoration: none;
113 /* background-color: #f2f2ff; */
114 color: #000055;
115}
116A.anchor {
117 color: #000;
118}
119DL.el {
120 margin-left: -1cm
121}
122.fragment {
123 font-family: monospace, fixed;
124 font-size: 95%;
125}
126PRE.fragment {
127 border: 1px solid #CCCCCC;
128 background-color: #f5f5f5;
129 margin-top: 4px;
130 margin-bottom: 4px;
131 margin-left: 2px;
132 margin-right: 8px;
133 padding-left: 6px;
134 padding-right: 6px;
135 padding-top: 4px;
136 padding-bottom: 4px;
137}
138DIV.ah {
139 background-color: black;
140 font-weight: bold;
141 color: #ffffff;
142 margin-bottom: 3px;
143 margin-top: 3px
144}
145
146DIV.groupHeader {
147 margin-left: 16px;
148 margin-top: 12px;
149 margin-bottom: 6px;
150 font-weight: bold;
151}
152DIV.groupText {
153 margin-left: 16px;
154 font-style: italic;
155 font-size: 90%
156}
157/*BODY {
158 background: white;
159 color: black;
160 margin-right: 20px;
161 margin-left: 20px;
162}*/
163TD.indexkey {
164 background-color: #e8eef2;
165 font-weight: bold;
166 padding-right : 10px;
167 padding-top : 2px;
168 padding-left : 10px;
169 padding-bottom : 2px;
170 margin-left : 0px;
171 margin-right : 0px;
172 margin-top : 2px;
173 margin-bottom : 2px;
174 border: 1px solid #CCCCCC;
175}
176TD.indexvalue {
177 background-color: #e8eef2;
178 font-style: italic;
179 padding-right : 10px;
180 padding-top : 2px;
181 padding-left : 10px;
182 padding-bottom : 2px;
183 margin-left : 0px;
184 margin-right : 0px;
185 margin-top : 2px;
186 margin-bottom : 2px;
187 border: 1px solid #CCCCCC;
188}
189TR.memlist {
190 background-color: #f0f0f0;
191}
192P.formulaDsp {
193 text-align: center;
194}
195IMG.formulaDsp {
196}
197IMG.formulaInl {
198 vertical-align: middle;
199}
200SPAN.keyword { color: #008000 }
201SPAN.keywordtype { color: #604020 }
202SPAN.keywordflow { color: #e08000 }
203SPAN.comment { color: #800000 }
204SPAN.preprocessor { color: #806020 }
205SPAN.stringliteral { color: #002080 }
206SPAN.charliteral { color: #008080 }
207SPAN.vhdldigit { color: #ff00ff }
208SPAN.vhdlchar { color: #000000 }
209SPAN.vhdlkeyword { color: #700070 }
210SPAN.vhdllogic { color: #ff0000 }
211
212.mdescLeft {
213 padding: 0px 8px 4px 8px;
214 font-size: 80%;
215 font-style: italic;
216 background-color: #FAFAFA;
217 border-top: 1px none #E0E0E0;
218 border-right: 1px none #E0E0E0;
219 border-bottom: 1px none #E0E0E0;
220 border-left: 1px none #E0E0E0;
221 margin: 0px;
222}
223.mdescRight {
224 padding: 0px 8px 4px 8px;
225 font-size: 80%;
226 font-style: italic;
227 background-color: #FAFAFA;
228 border-top: 1px none #E0E0E0;
229 border-right: 1px none #E0E0E0;
230 border-bottom: 1px none #E0E0E0;
231 border-left: 1px none #E0E0E0;
232 margin: 0px;
233}
234.memItemLeft {
235 padding: 1px 0px 0px 8px;
236 margin: 4px;
237 border-top-width: 1px;
238 border-right-width: 1px;
239 border-bottom-width: 1px;
240 border-left-width: 1px;
241 border-top-color: #E0E0E0;
242 border-right-color: #E0E0E0;
243 border-bottom-color: #E0E0E0;
244 border-left-color: #E0E0E0;
245 border-top-style: solid;
246 border-right-style: none;
247 border-bottom-style: none;
248 border-left-style: none;
249 background-color: #FAFAFA;
250 font-size: 80%;
251}
252.memItemRight {
253 padding: 1px 8px 0px 8px;
254 margin: 4px;
255 border-top-width: 1px;
256 border-right-width: 1px;
257 border-bottom-width: 1px;
258 border-left-width: 1px;
259 border-top-color: #E0E0E0;
260 border-right-color: #E0E0E0;
261 border-bottom-color: #E0E0E0;
262 border-left-color: #E0E0E0;
263 border-top-style: solid;
264 border-right-style: none;
265 border-bottom-style: none;
266 border-left-style: none;
267 background-color: #FAFAFA;
268 font-size: 80%;
269}
270.memTemplItemLeft {
271 padding: 1px 0px 0px 8px;
272 margin: 4px;
273 border-top-width: 1px;
274 border-right-width: 1px;
275 border-bottom-width: 1px;
276 border-left-width: 1px;
277 border-top-color: #E0E0E0;
278 border-right-color: #E0E0E0;
279 border-bottom-color: #E0E0E0;
280 border-left-color: #E0E0E0;
281 border-top-style: none;
282 border-right-style: none;
283 border-bottom-style: none;
284 border-left-style: none;
285 background-color: #FAFAFA;
286 font-size: 80%;
287}
288.memTemplItemRight {
289 padding: 1px 8px 0px 8px;
290 margin: 4px;
291 border-top-width: 1px;
292 border-right-width: 1px;
293 border-bottom-width: 1px;
294 border-left-width: 1px;
295 border-top-color: #E0E0E0;
296 border-right-color: #E0E0E0;
297 border-bottom-color: #E0E0E0;
298 border-left-color: #E0E0E0;
299 border-top-style: none;
300 border-right-style: none;
301 border-bottom-style: none;
302 border-left-style: none;
303 background-color: #FAFAFA;
304 font-size: 80%;
305}
306.memTemplParams {
307 padding: 1px 0px 0px 8px;
308 margin: 4px;
309 border-top-width: 1px;
310 border-right-width: 1px;
311 border-bottom-width: 1px;
312 border-left-width: 1px;
313 border-top-color: #E0E0E0;
314 border-right-color: #E0E0E0;
315 border-bottom-color: #E0E0E0;
316 border-left-color: #E0E0E0;
317 border-top-style: solid;
318 border-right-style: none;
319 border-bottom-style: none;
320 border-left-style: none;
321 color: #606060;
322 background-color: #FAFAFA;
323 font-size: 80%;
324}
325.search {
326 color: #003399;
327 font-weight: bold;
328}
329FORM.search {
330 margin-bottom: 0px;
331 margin-top: 0px;
332}
333INPUT.search {
334 font-size: 75%;
335 color: #000080;
336 font-weight: normal;
337 background-color: #e8eef2;
338}
339TD.tiny {
340 font-size: 75%;
341}
342a {
343 color: #1A41A8;
344}
345a:visited {
346 color: #2A3798;
347}
348.dirtab {
349 padding: 4px;
350 border-collapse: collapse;
351 border: 1px solid #84b0c7;
352}
353TH.dirtab {
354 background: #e8eef2;
355 font-weight: bold;
356}
357HR {
358 height: 1px;
359 border: none;
360 border-top: 1px solid black;
361}
362
363/* Style for detailed member documentation */
364.memtemplate {
365 font-size: 80%;
366 color: #606060;
367 font-weight: normal;
368 margin-left: 3px;
369}
370.memnav {
371 background-color: #eeeeee;
372 border: 1px solid #dddddd;
373 text-align: center;
374 margin: 2px;
375 margin-right: 15px;
376 padding: 2px;
377}
378.memitem {
379 padding: 4px;
380 background-color: #eeeeee;
381 border-width: 1px;
382 border-style: solid;
383 border-color: #dddddd;
384 -moz-border-radius: 4px 4px 4px 4px;
385}
386.memname {
387 white-space: nowrap;
388 font-weight: bold;
389 color: #ffffff;
390}
391.memdoc{
392 padding-left: 10px;
393}
394.memproto {
395 background-color: #111111;
396 width: 100%;
397 border-width: 1px;
398 border-style: solid;
399 border-color: #000000;
400 font-weight: bold;
401 -moz-border-radius: 4px 4px 4px 4px;
402}
403.paramkey {
404 text-align: right;
405 color: #ffffff;
406}
407.paramtype {
408 white-space: nowrap;
409 color: #aaaaaa;
410}
411.paramname {
412 color: #ff0000;
413 font-style: italic;
414 white-space: nowrap;
415}
416/* End Styling for detailed member documentation */
417
418/* for the tree view */
419.ftvtree {
420 font-family: sans-serif;
421 margin:0.5em;
422}
423/* these are for tree view when used as main index */
424.directory {
425 font-size: 9pt;
426 font-weight: bold;
427}
428.directory h3 {
429 margin: 0px;
430 margin-top: 1em;
431 font-size: 11pt;
432}
433
434/* The following two styles can be used to replace the root node title */
435/* with an image of your choice. Simply uncomment the next two styles, */
436/* specify the name of your image and be sure to set 'height' to the */
437/* proper pixel height of your image. */
438
439/* .directory h3.swap { */
440/* height: 61px; */
441/* background-repeat: no-repeat; */
442/* background-image: url("yourimage.gif"); */
443/* } */
444/* .directory h3.swap span { */
445/* display: none; */
446/* } */
447
448.directory > h3 {
449 margin-top: 0;
450}
451.directory p {
452 margin: 0px;
453 white-space: nowrap;
454}
455.directory div {
456 display: none;
457 margin: 0px;
458}
459.directory img {
460 vertical-align: -30%;
461}
462/* these are for tree view when not used as main index */
463.directory-alt {
464 font-size: 100%;
465 font-weight: bold;
466}
467.directory-alt h3 {
468 margin: 0px;
469 margin-top: 1em;
470 font-size: 11pt;
471}
472.directory-alt > h3 {
473 margin-top: 0;
474}
475.directory-alt p {
476 margin: 0px;
477 white-space: nowrap;
478}
479.directory-alt div {
480 display: none;
481 margin: 0px;
482}
483.directory-alt img {
484 vertical-align: -30%;
485}
486
diff --git a/legacy/ephysics/doc/img/foot_bg.png b/legacy/ephysics/doc/img/foot_bg.png
new file mode 100644
index 0000000000..b24f3a48b4
--- /dev/null
+++ b/legacy/ephysics/doc/img/foot_bg.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/head_bg.png b/legacy/ephysics/doc/img/head_bg.png
new file mode 100644
index 0000000000..081dc131e4
--- /dev/null
+++ b/legacy/ephysics/doc/img/head_bg.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/header_menu_background.png b/legacy/ephysics/doc/img/header_menu_background.png
new file mode 100644
index 0000000000..e978743651
--- /dev/null
+++ b/legacy/ephysics/doc/img/header_menu_background.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/header_menu_background_last.png b/legacy/ephysics/doc/img/header_menu_background_last.png
new file mode 100644
index 0000000000..88c116c8c8
--- /dev/null
+++ b/legacy/ephysics/doc/img/header_menu_background_last.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/header_menu_current_background.png b/legacy/ephysics/doc/img/header_menu_current_background.png
new file mode 100644
index 0000000000..de97c9268e
--- /dev/null
+++ b/legacy/ephysics/doc/img/header_menu_current_background.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/header_menu_unselected_background.png b/legacy/ephysics/doc/img/header_menu_unselected_background.png
new file mode 100644
index 0000000000..50e5fd8d3d
--- /dev/null
+++ b/legacy/ephysics/doc/img/header_menu_unselected_background.png
Binary files differ
diff --git a/legacy/ephysics/doc/img/logo.png b/legacy/ephysics/doc/img/logo.png
new file mode 100644
index 0000000000..b3884a5cbc
--- /dev/null
+++ b/legacy/ephysics/doc/img/logo.png
Binary files differ