summaryrefslogtreecommitdiff
path: root/legacy/ephysics
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
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')
-rw-r--r--legacy/ephysics/.gitignore41
-rw-r--r--legacy/ephysics/AUTHORS2
-rw-r--r--legacy/ephysics/COPYING26
-rw-r--r--legacy/ephysics/COPYING_ARTS94
-rw-r--r--legacy/ephysics/ChangeLog3
-rw-r--r--legacy/ephysics/INSTALL365
-rw-r--r--legacy/ephysics/Makefile.am48
-rw-r--r--legacy/ephysics/NEWS3
-rw-r--r--legacy/ephysics/README50
-rw-r--r--legacy/ephysics/TODO17
-rwxr-xr-xlegacy/ephysics/autogen.sh39
-rw-r--r--legacy/ephysics/configure.ac244
-rw-r--r--legacy/ephysics/data/Makefile.am3
-rw-r--r--legacy/ephysics/data/logo_images/Makefile.am30
-rw-r--r--legacy/ephysics/data/logo_images/logo_background.pngbin0 -> 64375 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-C.pngbin0 -> 1720 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-E.pngbin0 -> 2503 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-H.pngbin0 -> 1094 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-I.pngbin0 -> 1022 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-P.pngbin0 -> 1716 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-S1.pngbin0 -> 2070 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-S2.pngbin0 -> 2099 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_letter-Y.pngbin0 -> 1499 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-C.pngbin0 -> 2457 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-E.pngbin0 -> 4420 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-H.pngbin0 -> 1785 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-I.pngbin0 -> 1343 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-P.pngbin0 -> 1761 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-S1.pngbin0 -> 2613 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-S2.pngbin0 -> 2582 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_light-Y.pngbin0 -> 2023 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-C.pngbin0 -> 1450 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-E.pngbin0 -> 1974 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-H.pngbin0 -> 1433 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-I.pngbin0 -> 1264 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-P.pngbin0 -> 1319 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-S1.pngbin0 -> 1405 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-S2.pngbin0 -> 1425 bytes
-rw-r--r--legacy/ephysics/data/logo_images/logo_shadow-Y.pngbin0 -> 1353 bytes
-rw-r--r--legacy/ephysics/data/themes/Makefile.am51
-rw-r--r--legacy/ephysics/data/themes/balls.edc124
-rw-r--r--legacy/ephysics/data/themes/buttons.edc133
-rw-r--r--legacy/ephysics/data/themes/cubes.edc42
-rw-r--r--legacy/ephysics/data/themes/effects.edc49
-rw-r--r--legacy/ephysics/data/themes/ephysics_test.edc13
-rw-r--r--legacy/ephysics/data/themes/frame.edc116
-rw-r--r--legacy/ephysics/data/themes/images/arrows.pngbin0 -> 2846 bytes
-rw-r--r--legacy/ephysics/data/themes/images/background.jpgbin0 -> 17522 bytes
-rw-r--r--legacy/ephysics/data/themes/images/ball-blue.pngbin0 -> 3223 bytes
-rw-r--r--legacy/ephysics/data/themes/images/ball-blue70.pngbin0 -> 3899 bytes
-rw-r--r--legacy/ephysics/data/themes/images/ball-green.pngbin0 -> 3228 bytes
-rw-r--r--legacy/ephysics/data/themes/images/ball-green70.pngbin0 -> 3727 bytes
-rw-r--r--legacy/ephysics/data/themes/images/ball-red.pngbin0 -> 3217 bytes
-rw-r--r--legacy/ephysics/data/themes/images/ball-red70.pngbin0 -> 3867 bytes
-rw-r--r--legacy/ephysics/data/themes/images/bt_jump.pngbin0 -> 1736 bytes
-rw-r--r--legacy/ephysics/data/themes/images/bt_jump_pressed.pngbin0 -> 1808 bytes
-rw-r--r--legacy/ephysics/data/themes/images/bt_restart.pngbin0 -> 1959 bytes
-rw-r--r--legacy/ephysics/data/themes/images/bt_restart_pressed.pngbin0 -> 2094 bytes
-rw-r--r--legacy/ephysics/data/themes/images/collisionL.pngbin0 -> 1212 bytes
-rw-r--r--legacy/ephysics/data/themes/images/cube-blue.pngbin0 -> 3734 bytes
-rw-r--r--legacy/ephysics/data/themes/images/cube-purple.pngbin0 -> 5835 bytes
-rw-r--r--legacy/ephysics/data/themes/images/impact.pngbin0 -> 514 bytes
-rw-r--r--legacy/ephysics/data/themes/images/list-item-corner-pressed.pngbin0 -> 1872 bytes
-rw-r--r--legacy/ephysics/data/themes/images/list-item-corner.pngbin0 -> 1828 bytes
-rw-r--r--legacy/ephysics/data/themes/images/list-item-pressed.pngbin0 -> 1026 bytes
-rw-r--r--legacy/ephysics/data/themes/images/list-item.pngbin0 -> 1026 bytes
-rw-r--r--legacy/ephysics/data/themes/images/list.pngbin0 -> 24619 bytes
-rw-r--r--legacy/ephysics/data/themes/images/shadow-ball.pngbin0 -> 989 bytes
-rw-r--r--legacy/ephysics/data/themes/images/shadow-cube.pngbin0 -> 969 bytes
-rw-r--r--legacy/ephysics/data/themes/list.edc134
-rw-r--r--legacy/ephysics/data/themes/shadows.edc49
-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
-rw-r--r--legacy/ephysics/ephysics.pc.in12
-rw-r--r--legacy/ephysics/m4/ac_attribute.m447
-rw-r--r--legacy/ephysics/m4/efl_binary.m471
-rw-r--r--legacy/ephysics/m4/efl_compiler_flag.m457
-rw-r--r--legacy/ephysics/m4/efl_doxygen.m497
-rw-r--r--legacy/ephysics/m4/efl_path_max.m436
-rw-r--r--legacy/ephysics/src/Makefile.am3
-rw-r--r--legacy/ephysics/src/bin/Makefile.am44
-rw-r--r--legacy/ephysics/src/bin/ephysics_logo.c279
-rw-r--r--legacy/ephysics/src/bin/ephysics_test.h79
-rw-r--r--legacy/ephysics/src/bin/test.c198
-rw-r--r--legacy/ephysics/src/bin/test_bouncing_ball.c111
-rw-r--r--legacy/ephysics/src/bin/test_bouncing_text.c68
-rw-r--r--legacy/ephysics/src/bin/test_colliding_balls.c91
-rw-r--r--legacy/ephysics/src/bin/test_collision_detection.c185
-rw-r--r--legacy/ephysics/src/bin/test_constraint.c105
-rw-r--r--legacy/ephysics/src/bin/test_falling_letters.c76
-rw-r--r--legacy/ephysics/src/bin/test_jumping_balls.c141
-rw-r--r--legacy/ephysics/src/bin/test_rotate.c100
-rw-r--r--legacy/ephysics/src/lib/EPhysics.h1230
-rw-r--r--legacy/ephysics/src/lib/Makefile.am28
-rw-r--r--legacy/ephysics/src/lib/ephysics_body.cpp760
-rw-r--r--legacy/ephysics/src/lib/ephysics_camera.cpp109
-rw-r--r--legacy/ephysics/src/lib/ephysics_constraints.cpp89
-rw-r--r--legacy/ephysics/src/lib/ephysics_main.cpp58
-rw-r--r--legacy/ephysics/src/lib/ephysics_private.h79
-rw-r--r--legacy/ephysics/src/lib/ephysics_world.cpp650
114 files changed, 9103 insertions, 0 deletions
diff --git a/legacy/ephysics/.gitignore b/legacy/ephysics/.gitignore
new file mode 100644
index 0000000..37f7814
--- /dev/null
+++ b/legacy/ephysics/.gitignore
@@ -0,0 +1,41 @@
1*~
2*.o
3*.lo
4*.la
5.libs
6.deps
7*.pc
8Makefile
9Makefile.in
10*.so
11/aclocal.m4
12/autom4te.cache/
13/compile
14/config.cache
15/config.guess
16/config.h
17/config.h.in
18/config.log
19/config.status
20/config.sub
21/configure
22/depcomp
23/install-sh
24/libtool
25/ltmain.sh
26/missing
27/stamp-h1
28/ABOUT-NLS
29/config.cache-env
30doc/Doxyfile
31m4/libtool.m4
32m4/ltoptions.m4
33m4/ltsugar.m4
34m4/ltversion.m4
35m4/lt~obsolete.m4
36data/themes/ephysics_test.edj
37src/bin/ephysics_test
38src/bin/ephysics_logo
39doc/html/
40doc/latex/
41doc/man/
diff --git a/legacy/ephysics/AUTHORS b/legacy/ephysics/AUTHORS
new file mode 100644
index 0000000..b9ef7b6
--- /dev/null
+++ b/legacy/ephysics/AUTHORS
@@ -0,0 +1,2 @@
1Bruno Dilly <bdilly@profusion.mobi>
2Leandro Dorileo <dorileo@profusion.mobi>
diff --git a/legacy/ephysics/COPYING b/legacy/ephysics/COPYING
new file mode 100644
index 0000000..1dd67cb
--- /dev/null
+++ b/legacy/ephysics/COPYING
@@ -0,0 +1,26 @@
1Copyright notice for EPhysics:
2
3Copyright (C) 2012 ProFUSION Embedded Systems and various contributors
4 (see AUTHORS).
5
6All rights reserved.
7
8Redistribution and use in source and binary forms, with or without
9modification, are permitted provided that the following conditions are met:
10
11 1. Redistributions of source code must retain the above copyright
12 notice, this list of conditions and the following disclaimer.
13 2. Redistributions in binary form must reproduce the above copyright
14 notice, this list of conditions and the following disclaimer in the
15 documentation and/or other materials provided with the distribution.
16
17THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
18INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
19FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
20COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
21INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
22LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
23OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
24LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
25NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
26EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff --git a/legacy/ephysics/COPYING_ARTS b/legacy/ephysics/COPYING_ARTS
new file mode 100644
index 0000000..a727139
--- /dev/null
+++ b/legacy/ephysics/COPYING_ARTS
@@ -0,0 +1,94 @@
1The follwing images were drawn by Marina Proni <marina.proni@profusion.mobi>
2and are licensed under Creative Commons Attribution-ShareAlike 3.0
3Unported License:
4
5 arrows.png
6 background.jpg
7 ball-blue70.png
8 ball-blue.png
9 ball-green70.png
10 ball-green.png
11 ball-red70.png
12 ball-red.png
13 bt_jump.png
14 bt_jump_pressed.png
15 bt_restart.png
16 bt_restart_pressed.png
17 collisionL.png
18 cube-blue.png
19 cube-purple.png
20 impact.png
21 list-item-corner.png
22 list-item-corner-pressed.png
23 list-item.png
24 list-item-pressed.png
25 list.png
26 shadow-ball.png
27 shadow-cube.png
28
29===
30
31Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)
32
33
34THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.
35
36BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
37
381. Definitions
39
40 a. "Adaptation" means a work based upon the Work, or upon the Work and other pre-existing works, such as a translation, adaptation, derivative work, arrangement of music or other alterations of a literary or artistic work, or phonogram or performance and includes cinematographic adaptations or any other form in which the Work may be recast, transformed, or adapted including in any form recognizably derived from the original, except that a work that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.
41 b. "Collection" means a collection of literary or artistic works, such as encyclopedias and anthologies, or performances, phonograms or broadcasts, or other works or subject matter other than works listed in Section 1(f) below, which, by reason of the selection and arrangement of their contents, constitute intellectual creations, in which the Work is included in its entirety in unmodified form along with one or more other contributions, each constituting separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined below) for the purposes of this License.
42 c. "Creative Commons Compatible License" means a license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Elements of this License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this License or a Creative Commons jurisdiction license with the same License Elements as this License.
43 d. "Distribute" means to make available to the public the original and copies of the Work or Adaptation, as appropriate, through sale or other transfer of ownership.
44 e. "License Elements" means the following high-level license attributes as selected by Licensor and indicated in the title of this License: Attribution, ShareAlike.
45 f. "Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.
46 g. "Original Author" means, in the case of a literary or artistic work, the individual, individuals, entity or entities who created the Work or if no individual or entity can be identified, the publisher; and in addition (i) in the case of a performance the actors, singers, musicians, dancers, and other persons who act, sing, deliver, declaim, play in, interpret or otherwise perform literary or artistic works or expressions of folklore; (ii) in the case of a phonogram the producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.
47 h. "Work" means the literary and/or artistic work offered under the terms of this License including without limitation any production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography, topography, architecture or science; a performance; a broadcast; a phonogram; a compilation of data to the extent it is protected as a copyrightable work; or a work performed by a variety or circus performer to the extent it is not otherwise considered a literary or artistic work.
48 i. "You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a previous violation.
49 j. "Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the communication to the public of the performances of the Work, including by public digital performance; to broadcast and rebroadcast the Work by any means including signs, sounds or images.
50 k. "Reproduce" means to make copies of the Work by any means including without limitation by sound or visual recordings and the right of fixation and reproducing fixations of the Work, including storage of a protected performance or phonogram in digital form or other electronic medium.
51
522. Fair Dealing Rights. Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other applicable laws.
53
543. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:
55
56 a. to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections;
57 b. to create and Reproduce Adaptations provided that any such Adaptation, including any translation in any medium, takes reasonable steps to clearly label, demarcate or otherwise identify that changes were made to the original Work. For example, a translation could be marked "The original work was translated from English to Spanish," or a modification could indicate "The original work has been modified.";
58 c. to Distribute and Publicly Perform the Work including as incorporated in Collections; and,
59 d. to Distribute and Publicly Perform Adaptations.
60
61 e. For the avoidance of doubt:
62 i. Non-waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme cannot be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License;
63 ii. Waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme can be waived, the Licensor waives the exclusive right to collect such royalties for any exercise by You of the rights granted under this License; and,
64 iii. Voluntary License Schemes. The Licensor waives the right to collect royalties, whether individually or, in the event that the Licensor is a member of a collecting society that administers voluntary licensing schemes, via that society, from any exercise by You of the rights granted under this License.
65
66The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights include the right to make such modifications as are technically necessary to exercise the rights in other media and formats. Subject to Section 8(f), all rights not expressly granted by Licensor are hereby reserved.
67
684. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
69
70 a. You may Distribute or Publicly Perform the Work only under the terms of this License. You must include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License. This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested. If You create an Adaptation, upon notice from any Licensor You must, to the extent practicable, remove from the Adaptation any credit as required by Section 4(c), as requested.
71 b. You may Distribute or Publicly Perform an Adaptation only under the terms of: (i) this License; (ii) a later version of this License with the same License Elements as this License; (iii) a Creative Commons jurisdiction license (either this or a later license version) that contains the same License Elements as this License (e.g., Attribution-ShareAlike 3.0 US)); (iv) a Creative Commons Compatible License. If you license the Adaptation under one of the licenses mentioned in (iv), you must comply with the terms of that license. If you license the Adaptation under the terms of any of the licenses mentioned in (i), (ii) or (iii) (the "Applicable License"), you must comply with the terms of the Applicable License generally and the following provisions: (I) You must include a copy of, or the URI for, the Applicable License with every copy of each Adaptation You Distribute or Publicly Perform; (II) You may not offer or impose any terms on the Adaptation that restrict the terms of the Applicable License or the ability of the recipient of the Adaptation to exercise the rights granted to that recipient under the terms of the Applicable License; (III) You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties with every copy of the Work as included in the Adaptation You Distribute or Publicly Perform; (IV) when You Distribute or Publicly Perform the Adaptation, You may not impose any effective technological measures on the Adaptation that restrict the ability of a recipient of the Adaptation from You to exercise the rights granted to that recipient under the terms of the Applicable License. This Section 4(b) applies to the Adaptation as incorporated in a Collection, but this does not require the Collection apart from the Adaptation itself to be made subject to the terms of the Applicable License.
72 c. If You Distribute, or Publicly Perform the Work or any Adaptations or Collections, You must, unless a request has been made pursuant to Section 4(a), keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied, and/or if the Original Author and/or Licensor designate another party or parties (e.g., a sponsor institute, publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work; and (iv) , consistent with Ssection 3(b), in the case of an Adaptation, a credit identifying the use of the Work in the Adaptation (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). The credit required by this Section 4(c) may be implemented in any reasonable manner; provided, however, that in the case of a Adaptation or Collection, at a minimum such credit will appear, if a credit for all contributing authors of the Adaptation or Collection appears, then as part of these credits and in a manner at least as prominent as the credits for the other contributing authors. For the avoidance of doubt, You may only use the credit required by this Section for the purpose of attribution in the manner set out above and, by exercising Your rights under this License, You may not implicitly or explicitly assert or imply any connection with, sponsorship or endorsement by the Original Author, Licensor and/or Attribution Parties, as appropriate, of You or Your use of the Work, without the separate, express prior written permission of the Original Author, Licensor and/or Attribution Parties.
73 d. Except as otherwise agreed in writing by the Licensor or as may be otherwise permitted by applicable law, if You Reproduce, Distribute or Publicly Perform the Work either by itself or as part of any Adaptations or Collections, You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation. Licensor agrees that in those jurisdictions (e.g. Japan), in which any exercise of the right granted in Section 3(b) of this License (the right to make Adaptations) would be deemed to be a distortion, mutilation, modification or other derogatory action prejudicial to the Original Author's honor and reputation, the Licensor will waive or not assert, as appropriate, this Section, to the fullest extent permitted by the applicable national law, to enable You to reasonably exercise Your right under Section 3(b) of this License (right to make Adaptations) but not otherwise.
74
755. Representations, Warranties and Disclaimer
76
77UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.
78
796. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
80
817. Termination
82
83 a. This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Adaptations or Collections from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.
84 b. Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.
85
868. Miscellaneous
87
88 a. Each time You Distribute or Publicly Perform the Work or a Collection, the Licensor offers to the recipient a license to the Work on the same terms and conditions as the license granted to You under this License.
89 b. Each time You Distribute or Publicly Perform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.
90 c. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
91 d. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
92 e. This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.
93 f. The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979), the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the license of any rights under applicable law.
94
diff --git a/legacy/ephysics/ChangeLog b/legacy/ephysics/ChangeLog
new file mode 100644
index 0000000..490c3dc
--- /dev/null
+++ b/legacy/ephysics/ChangeLog
@@ -0,0 +1,3 @@
12012-05-15 Bruno Dilly
2
3 Initial version
diff --git a/legacy/ephysics/INSTALL b/legacy/ephysics/INSTALL
new file mode 100644
index 0000000..7d1c323
--- /dev/null
+++ b/legacy/ephysics/INSTALL
@@ -0,0 +1,365 @@
1Installation Instructions
2*************************
3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
52006, 2007, 2008, 2009 Free Software Foundation, Inc.
6
7 Copying and distribution of this file, with or without modification,
8are permitted in any medium without royalty provided the copyright
9notice and this notice are preserved. This file is offered as-is,
10without warranty of any kind.
11
12Basic Installation
13==================
14
15 Briefly, the shell commands `./configure; make; make install' should
16configure, build, and install this package. The following
17more-detailed instructions are generic; see the `README' file for
18instructions specific to this package. Some packages provide this
19`INSTALL' file but do not implement all of the features documented
20below. The lack of an optional feature in a given package is not
21necessarily a bug. More recommendations for GNU packages can be found
22in *note Makefile Conventions: (standards)Makefile Conventions.
23
24 The `configure' shell script attempts to guess correct values for
25various system-dependent variables used during compilation. It uses
26those values to create a `Makefile' in each directory of the package.
27It may also create one or more `.h' files containing system-dependent
28definitions. Finally, it creates a shell script `config.status' that
29you can run in the future to recreate the current configuration, and a
30file `config.log' containing compiler output (useful mainly for
31debugging `configure').
32
33 It can also use an optional file (typically called `config.cache'
34and enabled with `--cache-file=config.cache' or simply `-C') that saves
35the results of its tests to speed up reconfiguring. Caching is
36disabled by default to prevent problems with accidental use of stale
37cache files.
38
39 If you need to do unusual things to compile the package, please try
40to figure out how `configure' could check whether to do them, and mail
41diffs or instructions to the address given in the `README' so they can
42be considered for the next release. If you are using the cache, and at
43some point `config.cache' contains results you don't want to keep, you
44may remove or edit it.
45
46 The file `configure.ac' (or `configure.in') is used to create
47`configure' by a program called `autoconf'. You need `configure.ac' if
48you want to change it or regenerate `configure' using a newer version
49of `autoconf'.
50
51 The simplest way to compile this package is:
52
53 1. `cd' to the directory containing the package's source code and type
54 `./configure' to configure the package for your system.
55
56 Running `configure' might take a while. While running, it prints
57 some messages telling which features it is checking for.
58
59 2. Type `make' to compile the package.
60
61 3. Optionally, type `make check' to run any self-tests that come with
62 the package, generally using the just-built uninstalled binaries.
63
64 4. Type `make install' to install the programs and any data files and
65 documentation. When installing into a prefix owned by root, it is
66 recommended that the package be configured and built as a regular
67 user, and only the `make install' phase executed with root
68 privileges.
69
70 5. Optionally, type `make installcheck' to repeat any self-tests, but
71 this time using the binaries in their final installed location.
72 This target does not install anything. Running this target as a
73 regular user, particularly if the prior `make install' required
74 root privileges, verifies that the installation completed
75 correctly.
76
77 6. You can remove the program binaries and object files from the
78 source code directory by typing `make clean'. To also remove the
79 files that `configure' created (so you can compile the package for
80 a different kind of computer), type `make distclean'. There is
81 also a `make maintainer-clean' target, but that is intended mainly
82 for the package's developers. If you use it, you may have to get
83 all sorts of other programs in order to regenerate files that came
84 with the distribution.
85
86 7. Often, you can also type `make uninstall' to remove the installed
87 files again. In practice, not all packages have tested that
88 uninstallation works correctly, even though it is required by the
89 GNU Coding Standards.
90
91 8. Some packages, particularly those that use Automake, provide `make
92 distcheck', which can by used by developers to test that all other
93 targets like `make install' and `make uninstall' work correctly.
94 This target is generally not run by end users.
95
96Compilers and Options
97=====================
98
99 Some systems require unusual options for compilation or linking that
100the `configure' script does not know about. Run `./configure --help'
101for details on some of the pertinent environment variables.
102
103 You can give `configure' initial values for configuration parameters
104by setting variables in the command line or in the environment. Here
105is an example:
106
107 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
108
109 *Note Defining Variables::, for more details.
110
111Compiling For Multiple Architectures
112====================================
113
114 You can compile the package for more than one kind of computer at the
115same time, by placing the object files for each architecture in their
116own directory. To do this, you can use GNU `make'. `cd' to the
117directory where you want the object files and executables to go and run
118the `configure' script. `configure' automatically checks for the
119source code in the directory that `configure' is in and in `..'. This
120is known as a "VPATH" build.
121
122 With a non-GNU `make', it is safer to compile the package for one
123architecture at a time in the source code directory. After you have
124installed the package for one architecture, use `make distclean' before
125reconfiguring for another architecture.
126
127 On MacOS X 10.5 and later systems, you can create libraries and
128executables that work on multiple system types--known as "fat" or
129"universal" binaries--by specifying multiple `-arch' options to the
130compiler but only a single `-arch' option to the preprocessor. Like
131this:
132
133 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
134 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
135 CPP="gcc -E" CXXCPP="g++ -E"
136
137 This is not guaranteed to produce working output in all cases, you
138may have to build one architecture at a time and combine the results
139using the `lipo' tool if you have problems.
140
141Installation Names
142==================
143
144 By default, `make install' installs the package's commands under
145`/usr/local/bin', include files under `/usr/local/include', etc. You
146can specify an installation prefix other than `/usr/local' by giving
147`configure' the option `--prefix=PREFIX', where PREFIX must be an
148absolute file name.
149
150 You can specify separate installation prefixes for
151architecture-specific files and architecture-independent files. If you
152pass the option `--exec-prefix=PREFIX' to `configure', the package uses
153PREFIX as the prefix for installing programs and libraries.
154Documentation and other data files still use the regular prefix.
155
156 In addition, if you use an unusual directory layout you can give
157options like `--bindir=DIR' to specify different values for particular
158kinds of files. Run `configure --help' for a list of the directories
159you can set and what kinds of files go in them. In general, the
160default for these options is expressed in terms of `${prefix}', so that
161specifying just `--prefix' will affect all of the other directory
162specifications that were not explicitly provided.
163
164 The most portable way to affect installation locations is to pass the
165correct locations to `configure'; however, many packages provide one or
166both of the following shortcuts of passing variable assignments to the
167`make install' command line to change installation locations without
168having to reconfigure or recompile.
169
170 The first method involves providing an override variable for each
171affected directory. For example, `make install
172prefix=/alternate/directory' will choose an alternate location for all
173directory configuration variables that were expressed in terms of
174`${prefix}'. Any directories that were specified during `configure',
175but not in terms of `${prefix}', must each be overridden at install
176time for the entire installation to be relocated. The approach of
177makefile variable overrides for each directory variable is required by
178the GNU Coding Standards, and ideally causes no recompilation.
179However, some platforms have known limitations with the semantics of
180shared libraries that end up requiring recompilation when using this
181method, particularly noticeable in packages that use GNU Libtool.
182
183 The second method involves providing the `DESTDIR' variable. For
184example, `make install DESTDIR=/alternate/directory' will prepend
185`/alternate/directory' before all installation names. The approach of
186`DESTDIR' overrides is not required by the GNU Coding Standards, and
187does not work on platforms that have drive letters. On the other hand,
188it does better at avoiding recompilation issues, and works well even
189when some directory options were not specified in terms of `${prefix}'
190at `configure' time.
191
192Optional Features
193=================
194
195 If the package supports it, you can cause programs to be installed
196with an extra prefix or suffix on their names by giving `configure' the
197option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
198
199 Some packages pay attention to `--enable-FEATURE' options to
200`configure', where FEATURE indicates an optional part of the package.
201They may also pay attention to `--with-PACKAGE' options, where PACKAGE
202is something like `gnu-as' or `x' (for the X Window System). The
203`README' should mention any `--enable-' and `--with-' options that the
204package recognizes.
205
206 For packages that use the X Window System, `configure' can usually
207find the X include and library files automatically, but if it doesn't,
208you can use the `configure' options `--x-includes=DIR' and
209`--x-libraries=DIR' to specify their locations.
210
211 Some packages offer the ability to configure how verbose the
212execution of `make' will be. For these packages, running `./configure
213--enable-silent-rules' sets the default to minimal output, which can be
214overridden with `make V=1'; while running `./configure
215--disable-silent-rules' sets the default to verbose, which can be
216overridden with `make V=0'.
217
218Particular systems
219==================
220
221 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
222CC is not installed, it is recommended to use the following options in
223order to use an ANSI C compiler:
224
225 ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
226
227and if that doesn't work, install pre-built binaries of GCC for HP-UX.
228
229 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
230parse its `<wchar.h>' header file. The option `-nodtk' can be used as
231a workaround. If GNU CC is not installed, it is therefore recommended
232to try
233
234 ./configure CC="cc"
235
236and if that doesn't work, try
237
238 ./configure CC="cc -nodtk"
239
240 On Solaris, don't put `/usr/ucb' early in your `PATH'. This
241directory contains several dysfunctional programs; working variants of
242these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
243in your `PATH', put it _after_ `/usr/bin'.
244
245 On Haiku, software installed for all users goes in `/boot/common',
246not `/usr/local'. It is recommended to use the following options:
247
248 ./configure --prefix=/boot/common
249
250Specifying the System Type
251==========================
252
253 There may be some features `configure' cannot figure out
254automatically, but needs to determine by the type of machine the package
255will run on. Usually, assuming the package is built to be run on the
256_same_ architectures, `configure' can figure that out, but if it prints
257a message saying it cannot guess the machine type, give it the
258`--build=TYPE' option. TYPE can either be a short name for the system
259type, such as `sun4', or a canonical name which has the form:
260
261 CPU-COMPANY-SYSTEM
262
263where SYSTEM can have one of these forms:
264
265 OS
266 KERNEL-OS
267
268 See the file `config.sub' for the possible values of each field. If
269`config.sub' isn't included in this package, then this package doesn't
270need to know the machine type.
271
272 If you are _building_ compiler tools for cross-compiling, you should
273use the option `--target=TYPE' to select the type of system they will
274produce code for.
275
276 If you want to _use_ a cross compiler, that generates code for a
277platform different from the build platform, you should specify the
278"host" platform (i.e., that on which the generated programs will
279eventually be run) with `--host=TYPE'.
280
281Sharing Defaults
282================
283
284 If you want to set default values for `configure' scripts to share,
285you can create a site shell script called `config.site' that gives
286default values for variables like `CC', `cache_file', and `prefix'.
287`configure' looks for `PREFIX/share/config.site' if it exists, then
288`PREFIX/etc/config.site' if it exists. Or, you can set the
289`CONFIG_SITE' environment variable to the location of the site script.
290A warning: not all `configure' scripts look for a site script.
291
292Defining Variables
293==================
294
295 Variables not defined in a site shell script can be set in the
296environment passed to `configure'. However, some packages may run
297configure again during the build, and the customized values of these
298variables may be lost. In order to avoid this problem, you should set
299them in the `configure' command line, using `VAR=value'. For example:
300
301 ./configure CC=/usr/local2/bin/gcc
302
303causes the specified `gcc' to be used as the C compiler (unless it is
304overridden in the site shell script).
305
306Unfortunately, this technique does not work for `CONFIG_SHELL' due to
307an Autoconf bug. Until the bug is fixed you can use this workaround:
308
309 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
310
311`configure' Invocation
312======================
313
314 `configure' recognizes the following options to control how it
315operates.
316
317`--help'
318`-h'
319 Print a summary of all of the options to `configure', and exit.
320
321`--help=short'
322`--help=recursive'
323 Print a summary of the options unique to this package's
324 `configure', and exit. The `short' variant lists options used
325 only in the top level, while the `recursive' variant lists options
326 also present in any nested packages.
327
328`--version'
329`-V'
330 Print the version of Autoconf used to generate the `configure'
331 script, and exit.
332
333`--cache-file=FILE'
334 Enable the cache: use and save the results of the tests in FILE,
335 traditionally `config.cache'. FILE defaults to `/dev/null' to
336 disable caching.
337
338`--config-cache'
339`-C'
340 Alias for `--cache-file=config.cache'.
341
342`--quiet'
343`--silent'
344`-q'
345 Do not print messages saying which checks are being made. To
346 suppress all normal output, redirect it to `/dev/null' (any error
347 messages will still be shown).
348
349`--srcdir=DIR'
350 Look for the package's source code in directory DIR. Usually
351 `configure' can determine that directory automatically.
352
353`--prefix=DIR'
354 Use DIR as the installation prefix. *note Installation Names::
355 for more details, including other options available for fine-tuning
356 the installation locations.
357
358`--no-create'
359`-n'
360 Run the configure checks, but stop before creating any output
361 files.
362
363`configure' also accepts some other, not widely useful, options. Run
364`configure --help' for more details.
365
diff --git a/legacy/ephysics/Makefile.am b/legacy/ephysics/Makefile.am
new file mode 100644
index 0000000..5340ca3
--- /dev/null
+++ b/legacy/ephysics/Makefile.am
@@ -0,0 +1,48 @@
1ACLOCAL_AMFLAGS = -I m4
2
3SUBDIRS = src doc data
4
5MAINTAINERCLEANFILES = \
6Makefile.in \
7aclocal.m4 \
8compile \
9config.guess \
10config.h.in \
11config.h.in~ \
12config.sub \
13configure \
14depcomp \
15install-sh \
16ltmain.sh \
17missing \
18$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.gz \
19$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.bz2 \
20$(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc.tar.bz2 \
21m4/libtool.m4 \
22m4/lt~obsolete.m4 \
23m4/ltoptions.m4 \
24m4/ltsugar.m4 \
25m4/ltversion.m4
26
27bin_SCRIPTS =
28
29EXTRA_DIST = \
30AUTHORS \
31COPYING \
32COPYING_ARTS \
33autogen.sh \
34ephysics.pc.in \
35ephysics.spec \
36ephysics.spec.in \
37README
38
39pkgconfigdir = $(libdir)/pkgconfig
40pkgconfig_DATA = ephysics.pc
41
42.PHONY: doc
43
44# Documentation
45
46doc:
47 @echo "entering doc/"
48 make -C doc doc
diff --git a/legacy/ephysics/NEWS b/legacy/ephysics/NEWS
new file mode 100644
index 0000000..6ea6655
--- /dev/null
+++ b/legacy/ephysics/NEWS
@@ -0,0 +1,3 @@
1Ephysics 0.1.0
2
3 * Very initial implementation
diff --git a/legacy/ephysics/README b/legacy/ephysics/README
new file mode 100644
index 0000000..9407244
--- /dev/null
+++ b/legacy/ephysics/README
@@ -0,0 +1,50 @@
1EPhysics 0.1.0
2
3******************************************************************************
4
5 FOR ANY ISSUES PLEASE EMAIL:
6 enlightenment-devel@lists.sourceforge.net
7
8******************************************************************************
9
10Requirements:
11-------------
12
13Must:
14 libc
15 ecore (at least 1.1.0)
16 ecore-evas (at least 1.1.0)
17 evas (at least 1.1.0)
18 bullet (at least 2.80)
19Optional:
20 elementary (at least 1.0.0, required to build ephysics_test)
21
22EPhysics is a library that manages Ecore, Evas and Bullet Physics into
23an easy to use way. It's a kind of wrapper, a glue, between these libraries.
24It's not intended to be a physics library (we already have many out there).
25
26------------------------------------------------------------------------------
27
28COMPILING AND INSTALLING:
29
30 $ ./configure
31 $ make
32(as root unless you are installing in your users directories):
33 $ make install
34
35If elementary is installed, it will build and install a test application as
36well, that showcases EPhysics capabilites. Run
37
38 $ ephysics_test
39
40to see these examples.
41----
42
43DOCS
44
45To generate documentation, doxygen is required.
46
47 $ make doc
48
49will create a ephysics/doc/html directory. You could start looking at
50index.html.
diff --git a/legacy/ephysics/TODO b/legacy/ephysics/TODO
new file mode 100644
index 0000000..8c930df
--- /dev/null
+++ b/legacy/ephysics/TODO
@@ -0,0 +1,17 @@
1* collision filters
2* receive collision point on collision cb
3* valgrind supp
4* EPhysics_Constants
5* Sandbox tools to try different materials / properties
6* camera
7* create shape from image
8* simple game using ephysics
9* set best shape based on evas object
10* optimize collision shapes usage
11* deform objects
12* improve docs
13* run simulation on other thread
14
15FAR FAR FUTURE:
16* support Box2d backend
17* support Chipmunk backend
diff --git a/legacy/ephysics/autogen.sh b/legacy/ephysics/autogen.sh
new file mode 100755
index 0000000..00116ea
--- /dev/null
+++ b/legacy/ephysics/autogen.sh
@@ -0,0 +1,39 @@
1#!/bin/sh
2
3rm -rf autom4te.cache
4rm -f aclocal.m4 ltmain.sh
5
6touch README
7touch ABOUT-NLS
8
9echo "Running aclocal..." ; aclocal $ACLOCAL_FLAGS -I m4 || exit 1
10echo "Running autoheader..." ; autoheader || exit 1
11echo "Running autoconf..." ; autoconf || exit 1
12echo "Running libtoolize..." ; (libtoolize --copy --automake || glibtoolize --automake) || exit 1
13echo "Running automake..." ; automake --add-missing --copy --gnu || exit 1
14
15W=0
16
17rm -f config.cache-env.tmp
18echo "OLD_PARM=\"$@\"" >> config.cache-env.tmp
19echo "OLD_CFLAGS=\"$CFLAGS\"" >> config.cache-env.tmp
20echo "OLD_PATH=\"$PATH\"" >> config.cache-env.tmp
21echo "OLD_PKG_CONFIG_PATH=\"$PKG_CONFIG_PATH\"" >> config.cache-env.tmp
22echo "OLD_LDFLAGS=\"$LDFLAGS\"" >> config.cache-env.tmp
23
24cmp config.cache-env.tmp config.cache-env >> /dev/null
25if [ $? -ne 0 ]; then
26 W=1;
27fi
28
29if [ $W -ne 0 ]; then
30 echo "Cleaning configure cache...";
31 rm -f config.cache config.cache-env
32 mv config.cache-env.tmp config.cache-env
33else
34 rm -f config.cache-env.tmp
35fi
36
37if [ -z "$NOCONFIGURE" ]; then
38 ./configure -C "$@"
39fi
diff --git a/legacy/ephysics/configure.ac b/legacy/ephysics/configure.ac
new file mode 100644
index 0000000..30659db
--- /dev/null
+++ b/legacy/ephysics/configure.ac
@@ -0,0 +1,244 @@
1##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
2##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
3m4_define([v_maj], [0])
4m4_define([v_min], [1])
5m4_define([v_mic], [0])
6m4_define([v_rev], m4_esyscmd([(svnversion "${SVN_REPO_PATH:-.}" | grep -v '\(export\|Unversioned directory\)' || echo 0) | awk -F : '{printf("%s\n", $1);}' | tr -d ' :MSP\n']))
7m4_if(v_rev, [0], [m4_define([v_rev], m4_esyscmd([git log 2> /dev/null | (grep -m1 git-svn-id || echo 0) | sed -e 's/.*@\([0-9]*\).*/\1/' | tr -d '\n']))])
8##-- When released, remove the dnl on the below line
9dnl m4_undefine([v_rev])
10##-- When doing snapshots - change soname. remove dnl on below line
11dnl m4_define([relname], [ver-pre-svn-07])
12dnl m4_define([v_rel], [-release relname])
13##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
14m4_ifdef([v_rev], [m4_define([v_ver], [v_maj.v_min.v_mic.v_rev])], [m4_define([v_ver], [v_maj.v_min.v_mic])])
15m4_define([lt_cur], m4_eval(v_maj + v_min))
16m4_define([lt_rev], v_mic)
17m4_define([lt_age], v_min)
18##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
19##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
20
21AC_INIT([ephysics], [v_ver], [enlightenment-devel@lists.sourceforge.net])
22AC_PREREQ([2.52])
23AC_CONFIG_SRCDIR([configure.ac])
24AC_CONFIG_MACRO_DIR([m4])
25
26AC_CONFIG_HEADERS([config.h])
27AH_TOP([
28#ifndef EFL_CONFIG_H__
29#define EFL_CONFIG_H__
30])
31AH_BOTTOM([
32#endif /* EFL_CONFIG_H__ */
33])
34
35AM_INIT_AUTOMAKE([1.6 dist-bzip2])
36m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
37
38AC_LIBTOOL_WIN32_DLL
39define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
40AC_PROG_LIBTOOL
41
42##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
43##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
44m4_ifdef([v_rev], , [m4_define([v_rev], [0])])
45m4_ifdef([v_rel], , [m4_define([v_rel], [])])
46AC_DEFINE_UNQUOTED(VMAJ, [v_maj], [Major version])
47AC_DEFINE_UNQUOTED(VMIN, [v_min], [Minor version])
48AC_DEFINE_UNQUOTED(VMIC, [v_mic], [Micro version])
49AC_DEFINE_UNQUOTED(VREV, [v_rev], [Revison])
50version_info="lt_cur:lt_rev:lt_age"
51release_info="v_rel"
52AC_SUBST(version_info)
53AC_SUBST(release_info)
54##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
55##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
56VMAJ=v_maj
57AC_SUBST(VMAJ)
58
59AC_DEFINE_UNQUOTED([SHARED_LIB_SUFFIX], ["$shrext_cmds"], [Suffix for shared objects])
60
61### Default options with respect to host
62AC_CANONICAL_BUILD
63AC_CANONICAL_HOST
64
65
66case "$host_os" in
67 mingw32ce*)
68 MODULE_ARCH="$host_os-$host_cpu"
69 install_vim="no"
70 have_ephysics_cc="no"
71 ;;
72 *)
73 MODULE_ARCH="$host_os-$host_cpu-v_maj.0.0"
74 install_vim="yes"
75 have_ephysics_cc="yes"
76 ;;
77esac
78
79requirement_ephysics=""
80
81AC_SUBST(MODULE_ARCH)
82AC_DEFINE_UNQUOTED(MODULE_ARCH, "${MODULE_ARCH}", "Module architecture")
83
84m4_ifdef([v_mic],
85 [
86 EFL_COMPILER_FLAG([-Wshadow])
87 EFL_COMPILER_FLAG([-Wall])
88 EFL_COMPILER_FLAG([-Wextra])
89 EFL_COMPILER_FLAG([-W])
90 ])
91
92### Checks for programs
93AC_PROG_CC
94AC_PROG_CXX
95
96# doxygen program for documentation building
97
98EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])
99
100# python
101
102AM_PATH_PYTHON([2.5], , [:])
103AM_CONDITIONAL([HAVE_PYTHON], [test "$PYTHON" != : ])
104
105# pkg-config
106
107PKG_PROG_PKG_CONFIG
108
109# Check whether pkg-config supports Requires.private
110
111if $PKG_CONFIG --atleast-pkgconfig-version 0.22; then
112 pkgconfig_requires_private="Requires.private"
113else
114 pkgconfig_requires_private="Requires"
115fi
116AC_SUBST(pkgconfig_requires_private)
117
118
119### Checks for libraries
120
121# Evil library for compilation on Windows
122
123EFL_EPHYSICS_BUILD=""
124case "$host_os" in
125 mingw*)
126 PKG_CHECK_MODULES([EVIL], [evil >= 1.0.0])
127 AC_DEFINE([HAVE_EVIL], [1], [Set to 1 if Evil library is installed])
128 requirement_ephysics="evil ${requirement_ephysics}"
129 EFL_EPHYSICS_BUILD="-DEFL_EPHYSICS_BUILD"
130 ;;
131esac
132AC_SUBST(EFL_EPHYSICS_BUILD)
133
134# Dependencies for the library
135
136PKG_CHECK_MODULES([EPHYSICS],
137 [
138 eina >= 1.2.0
139 evas >= 1.2.0
140 ecore >= 1.2.0
141 ecore-evas >= 1.2.0
142 bullet >= 2.80
143 ])
144
145requirement_ephysics="bullet >= 2.80 ecore-evas >= 1.2.0 ecore >= 1.2.0 evas >= 1.2.0 eina >= 1.2.0 ${requirement_ephysics}"
146
147### Checks for header files
148AC_CHECK_HEADERS([locale.h sys/resource.h])
149
150EFL_WITH_BIN([edje], [edje-cc], [edje_cc])
151
152EFL_CHECK_PATH_MAX
153
154### Checks for compiler characteristics
155AM_PROG_CC_C_O
156AC_C_CONST
157AC_PROG_CC_STDC
158AC_HEADER_STDC
159AC_C___ATTRIBUTE__
160
161case "$host_os" in
162 mingw32ce*)
163 EPHYSICS_CFLAGS="${EPHYSICS_CFLAGS} -D_WIN32_WCE=0x0420"
164 ;;
165esac
166
167
168### Checks for linker characteristics
169
170lt_enable_auto_import=""
171case "$host_os" in
172 mingw*)
173 lt_enable_auto_import="-Wl,--enable-auto-import"
174 ;;
175esac
176AC_SUBST(lt_enable_auto_import)
177
178## Tests
179PKG_CHECK_MODULES([ELEMENTARY], [elementary >= 1.0.0], [build_tests="yes"], [build_tests="no"])
180AC_ARG_ENABLE([build-tests],
181 AC_HELP_STRING([--disable-build-tests],
182 [Disable building tests. It is enabled by default unless
183 required dependencies are not present. @<:@default==enabled@:>@]),
184 [
185 if test "x${enableval}" = "xno" ; then
186 build_tests="no"
187 else
188 requirement_ephysics="elementary >= 1.0.0 ${requirement_ephysics}"
189 fi
190 ],
191 [])
192AM_CONDITIONAL([BUILD_TESTS], [test "x${build_tests}" = "xyes"])
193
194if test "${build_tests}" = "yes" ; then
195PKG_CHECK_MODULES([EPHYSICS_TEST],
196 [
197 eina >= 1.2.0
198 evas >= 1.2.0
199 ecore >= 1.2.0
200 ecore-evas >= 1.2.0
201 elementary >= 1.0.0
202 bullet >= 2.80
203 ])
204fi
205
206AC_SUBST(requirement_ephysics)
207
208AC_OUTPUT([
209ephysics.pc
210Makefile
211data/Makefile
212data/logo_images/Makefile
213data/themes/Makefile
214doc/Makefile
215doc/Doxyfile
216src/Makefile
217src/lib/Makefile
218src/bin/Makefile
219])
220
221
222#####################################################################
223## Info
224
225echo
226echo
227echo
228echo "------------------------------------------------------------------------"
229echo "$PACKAGE $VERSION"
230echo "------------------------------------------------------------------------"
231echo
232echo "Configuration Options Summary:"
233echo
234echo " Documentation........: ${build_doc}"
235echo " Tests................: ${build_tests}"
236echo
237echo "Compilation............: make (or gmake)"
238echo " CPPFLAGS.............: $CPPFLAGS"
239echo " CFLAGS...............: $CFLAGS"
240echo " LDFLAGS..............: $LDFLAGS"
241echo
242echo "Installation...........: make install (as root if needed, with 'su' or 'sudo')"
243echo " prefix...............: $prefix"
244echo
diff --git a/legacy/ephysics/data/Makefile.am b/legacy/ephysics/data/Makefile.am
new file mode 100644
index 0000000..a52a0c0
--- /dev/null
+++ b/legacy/ephysics/data/Makefile.am
@@ -0,0 +1,3 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3SUBDIRS = logo_images themes
diff --git a/legacy/ephysics/data/logo_images/Makefile.am b/legacy/ephysics/data/logo_images/Makefile.am
new file mode 100644
index 0000000..c8bb4ff
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/Makefile.am
@@ -0,0 +1,30 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3filesdir = $(datadir)/ephysics/
4
5files_DATA = \
6 logo_background.png \
7 logo_letter-C.png \
8 logo_letter-E.png \
9 logo_letter-H.png \
10 logo_letter-I.png \
11 logo_letter-P.png \
12 logo_letter-S1.png \
13 logo_letter-S2.png \
14 logo_letter-Y.png \
15 logo_light-C.png \
16 logo_light-E.png \
17 logo_light-H.png \
18 logo_light-I.png \
19 logo_light-P.png \
20 logo_light-S1.png \
21 logo_light-S2.png \
22 logo_light-Y.png \
23 logo_shadow-C.png \
24 logo_shadow-E.png \
25 logo_shadow-H.png \
26 logo_shadow-I.png \
27 logo_shadow-P.png \
28 logo_shadow-S1.png \
29 logo_shadow-S2.png \
30 logo_shadow-Y.png
diff --git a/legacy/ephysics/data/logo_images/logo_background.png b/legacy/ephysics/data/logo_images/logo_background.png
new file mode 100644
index 0000000..c9c7bfd
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_background.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-C.png b/legacy/ephysics/data/logo_images/logo_letter-C.png
new file mode 100644
index 0000000..ad11d7d
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-C.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-E.png b/legacy/ephysics/data/logo_images/logo_letter-E.png
new file mode 100644
index 0000000..94e0db0
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-E.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-H.png b/legacy/ephysics/data/logo_images/logo_letter-H.png
new file mode 100644
index 0000000..b795538
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-H.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-I.png b/legacy/ephysics/data/logo_images/logo_letter-I.png
new file mode 100644
index 0000000..6123480
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-I.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-P.png b/legacy/ephysics/data/logo_images/logo_letter-P.png
new file mode 100644
index 0000000..da984c5
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-P.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-S1.png b/legacy/ephysics/data/logo_images/logo_letter-S1.png
new file mode 100644
index 0000000..e386cc0
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-S1.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-S2.png b/legacy/ephysics/data/logo_images/logo_letter-S2.png
new file mode 100644
index 0000000..59cc4a6
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-S2.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_letter-Y.png b/legacy/ephysics/data/logo_images/logo_letter-Y.png
new file mode 100644
index 0000000..ce36ffa
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_letter-Y.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-C.png b/legacy/ephysics/data/logo_images/logo_light-C.png
new file mode 100644
index 0000000..9a40c18
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-C.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-E.png b/legacy/ephysics/data/logo_images/logo_light-E.png
new file mode 100644
index 0000000..7b8a09e
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-E.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-H.png b/legacy/ephysics/data/logo_images/logo_light-H.png
new file mode 100644
index 0000000..2877840
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-H.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-I.png b/legacy/ephysics/data/logo_images/logo_light-I.png
new file mode 100644
index 0000000..64a3195
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-I.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-P.png b/legacy/ephysics/data/logo_images/logo_light-P.png
new file mode 100644
index 0000000..0b8962f
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-P.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-S1.png b/legacy/ephysics/data/logo_images/logo_light-S1.png
new file mode 100644
index 0000000..7011172
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-S1.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-S2.png b/legacy/ephysics/data/logo_images/logo_light-S2.png
new file mode 100644
index 0000000..97b3362
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-S2.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_light-Y.png b/legacy/ephysics/data/logo_images/logo_light-Y.png
new file mode 100644
index 0000000..e70a956
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_light-Y.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-C.png b/legacy/ephysics/data/logo_images/logo_shadow-C.png
new file mode 100644
index 0000000..07b9a24
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-C.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-E.png b/legacy/ephysics/data/logo_images/logo_shadow-E.png
new file mode 100644
index 0000000..261b30b
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-E.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-H.png b/legacy/ephysics/data/logo_images/logo_shadow-H.png
new file mode 100644
index 0000000..4389823
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-H.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-I.png b/legacy/ephysics/data/logo_images/logo_shadow-I.png
new file mode 100644
index 0000000..eee7437
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-I.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-P.png b/legacy/ephysics/data/logo_images/logo_shadow-P.png
new file mode 100644
index 0000000..c177cf6
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-P.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-S1.png b/legacy/ephysics/data/logo_images/logo_shadow-S1.png
new file mode 100644
index 0000000..23daa8d
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-S1.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-S2.png b/legacy/ephysics/data/logo_images/logo_shadow-S2.png
new file mode 100644
index 0000000..24f832c
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-S2.png
Binary files differ
diff --git a/legacy/ephysics/data/logo_images/logo_shadow-Y.png b/legacy/ephysics/data/logo_images/logo_shadow-Y.png
new file mode 100644
index 0000000..6369dcc
--- /dev/null
+++ b/legacy/ephysics/data/logo_images/logo_shadow-Y.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/Makefile.am b/legacy/ephysics/data/themes/Makefile.am
new file mode 100644
index 0000000..8aac2f3
--- /dev/null
+++ b/legacy/ephysics/data/themes/Makefile.am
@@ -0,0 +1,51 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3EDJE_CC = @edje_cc@
4EDJE_FLAGS_VERBOSE_ =
5EDJE_FLAGS_VERBOSE_0 =
6EDJE_FLAGS_VERBOSE_1 = -v
7EDJE_FLAGS = $(EDJE_FLAGS_$(V)) -id $(top_srcdir)/data/themes/images -fd $(top_srcdir)/data/themes/fonts
8
9filesdir = $(datadir)/ephysics/
10
11files_DATA = ephysics_test.edj
12
13EXTRA_DIST = \
14 ephysics_test.edc \
15 balls.edc \
16 buttons.edc \
17 cubes.edc \
18 effects.edc \
19 ephysics_test.edc \
20 frame.edc \
21 list.edc \
22 shadows.edc \
23 images/arrows.png \
24 images/background.jpg \
25 images/ball-blue.png \
26 images/ball-blue70.png \
27 images/ball-green.png \
28 images/ball-green70.png \
29 images/ball-red.png \
30 images/ball-red70.png \
31 images/bt_jump.png \
32 images/bt_jump_pressed.png \
33 images/bt_restart.png \
34 images/bt_restart_pressed.png \
35 images/collisionL.png \
36 images/cube-blue.png \
37 images/cube-purple.png \
38 images/list-item.png \
39 images/list-item-corner.png \
40 images/list-item-corner-pressed.png \
41 images/list-item-pressed.png \
42 images/shadow-ball.png \
43 images/shadow-cube.png
44
45ephysics_test.edj: Makefile $(EXTRA_DIST)
46 $(EDJE_CC) $(EDJE_FLAGS) \
47 $(top_srcdir)/data/themes/ephysics_test.edc \
48 $(top_builddir)/data/themes/ephysics_test.edj
49
50clean-local:
51 rm -f *.edj
diff --git a/legacy/ephysics/data/themes/balls.edc b/legacy/ephysics/data/themes/balls.edc
new file mode 100644
index 0000000..957c1c4
--- /dev/null
+++ b/legacy/ephysics/data/themes/balls.edc
@@ -0,0 +1,124 @@
1 images {
2 image: "ball-blue.png" COMP;
3 image: "ball-blue70.png" COMP;
4 image: "ball-green.png" COMP;
5 image: "ball-green70.png" COMP;
6 image: "ball-red.png" COMP;
7 image: "ball-red70.png" COMP;
8 }
9
10 group {
11 name: "blue-ball";
12
13 parts {
14
15 part {
16 name: "ball";
17 mouse_events: 0;
18 type: IMAGE;
19 description {
20 state: "default" 0.0;
21 image.normal: "ball-blue.png";
22 }
23 }
24
25 }
26
27 }
28
29 group {
30 name: "big-blue-ball";
31
32 parts {
33
34 part {
35 name: "ball";
36 mouse_events: 0;
37 type: IMAGE;
38 description {
39 state: "default" 0.0;
40 image.normal: "ball-blue70.png";
41 }
42 }
43
44 }
45
46 }
47
48 group {
49 name: "red-ball";
50
51 parts {
52
53 part {
54 name: "ball";
55 mouse_events: 0;
56 type: IMAGE;
57 description {
58 state: "default" 0.0;
59 image.normal: "ball-red.png";
60 }
61 }
62
63 }
64
65 }
66
67 group {
68 name: "big-red-ball";
69
70 parts {
71
72 part {
73 name: "ball";
74 mouse_events: 0;
75 type: IMAGE;
76 description {
77 state: "default" 0.0;
78 image.normal: "ball-red70.png";
79 }
80 }
81
82 }
83
84 }
85
86 group {
87 name: "green-ball";
88
89 parts {
90
91 part {
92 name: "ball";
93 mouse_events: 0;
94 type: IMAGE;
95 description {
96 state: "default" 0.0;
97 image.normal: "ball-green.png";
98 }
99 }
100
101 }
102
103 }
104
105 group {
106 name: "big-green-ball";
107
108 parts {
109
110 part {
111 name: "ball";
112 mouse_events: 0;
113 type: IMAGE;
114 description {
115 state: "default" 0.0;
116 image.normal: "ball-green70.png";
117 }
118 }
119
120 }
121
122 }
123
124
diff --git a/legacy/ephysics/data/themes/buttons.edc b/legacy/ephysics/data/themes/buttons.edc
new file mode 100644
index 0000000..0fe801c
--- /dev/null
+++ b/legacy/ephysics/data/themes/buttons.edc
@@ -0,0 +1,133 @@
1 images {
2 image: "bt_jump.png" COMP;
3 image: "bt_jump_pressed.png" COMP;
4 image: "bt_restart.png" COMP;
5 image: "bt_restart_pressed.png" COMP;
6 }
7
8#define BUTTON_GROUP(_name) \
9 group { \
10 name: "elm/button/base/ephysics-test-"#_name; \
11 \
12 parts { \
13 \
14 part { \
15 name: "blocker"; \
16 type: RECT; \
17 mouse_events: 1; \
18 description { \
19 state: "default" 0.0; \
20 color: 255 255 255 0; \
21 } \
22 } \
23 \
24 part { \
25 name: "base"; \
26 type: IMAGE; \
27 mouse_events: 0; \
28 description { \
29 state: "default" 0.0; \
30 min: 80 28; \
31 max: 80 28; \
32 aspect: 1 1; \
33 image.normal: "bt_"##_name##".png"; \
34 } \
35 description { \
36 state: "pressed" 0.0; \
37 inherit: "default" 0.0; \
38 image.normal: "bt_"##_name##"_pressed.png"; \
39 } \
40 description { \
41 state: "disabled" 0.0; \
42 inherit: "default" 0.0; \
43 color: 255 255 255 80; \
44 } \
45 } \
46 \
47 part { \
48 name: "over"; \
49 type: RECT; \
50 mouse_events: 1; \
51 ignore_flags: ON_HOLD; \
52 description { \
53 state: "default" 0.0; \
54 color: 255 255 255 0; \
55 } \
56 description { \
57 state: "disabled" 0.0; \
58 inherit: "default" 0.0; \
59 visible: 0; \
60 } \
61 } \
62 \
63 } \
64 \
65 programs { \
66 \
67 program { \
68 name: "bt_click"; \
69 source: "ephysics_test"; \
70 signal: "click"; \
71 in: 0.2 0; \
72 action: STATE_SET "pressed" 0.0; \
73 target: "base"; \
74 after: "bt_click2"; \
75 } \
76 \
77 program { \
78 name: "bt_click2"; \
79 in: 0.4 0; \
80 action: STATE_SET "default" 0.0; \
81 target: "base"; \
82 after: "bt_clicked"; \
83 } \
84 \
85 program { \
86 name: "bt_clicked"; \
87 source: "over"; \
88 signal: "mouse,clicked,1"; \
89 action: SIGNAL_EMIT "elm,action,click" ""; \
90 } \
91 \
92 program { \
93 name: "bt_pressed"; \
94 source: "over"; \
95 signal: "mouse,down,1"; \
96 action: STATE_SET "pressed" 0.0; \
97 target: "base"; \
98 } \
99 \
100 program { \
101 name: "bt_unpressed"; \
102 source: "over"; \
103 signal: "mouse,up,1"; \
104 action: STATE_SET "default" 0.0; \
105 target: "base"; \
106 } \
107 \
108 program { \
109 name: "disable"; \
110 source: "elm"; \
111 signal: "elm,state,disabled"; \
112 action: STATE_SET "disabled" 0.0; \
113 target: "base"; \
114 target: "over"; \
115 } \
116 \
117 program { \
118 name: "enable"; \
119 source: "elm"; \
120 signal: "elm,state,enabled"; \
121 action: STATE_SET "default" 0.0; \
122 target: "base"; \
123 target: "over"; \
124 } \
125 \
126 } \
127 \
128 }
129
130BUTTON_GROUP(restart)
131BUTTON_GROUP(jump)
132
133#undef BUTTON_GROUP
diff --git a/legacy/ephysics/data/themes/cubes.edc b/legacy/ephysics/data/themes/cubes.edc
new file mode 100644
index 0000000..6c55343
--- /dev/null
+++ b/legacy/ephysics/data/themes/cubes.edc
@@ -0,0 +1,42 @@
1 images {
2 image: "cube-blue.png" COMP;
3 image: "cube-purple.png" COMP;
4 }
5
6 group {
7 name: "blue-cube";
8
9 parts {
10
11 part {
12 name: "cube";
13 mouse_events: 0;
14 type: IMAGE;
15 description {
16 state: "default" 0.0;
17 image.normal: "cube-blue.png";
18 }
19 }
20
21 }
22
23 }
24
25 group {
26 name: "purple-cube";
27
28 parts {
29
30 part {
31 name: "cube";
32 mouse_events: 0;
33 type: IMAGE;
34 description {
35 state: "default" 0.0;
36 image.normal: "cube-purple.png";
37 }
38 }
39
40 }
41
42 }
diff --git a/legacy/ephysics/data/themes/effects.edc b/legacy/ephysics/data/themes/effects.edc
new file mode 100644
index 0000000..1a6b429
--- /dev/null
+++ b/legacy/ephysics/data/themes/effects.edc
@@ -0,0 +1,49 @@
1 images {
2 image: "collisionL.png" COMP;
3 }
4
5 group {
6 name: "impact";
7
8 parts {
9
10 part {
11 name: "impact";
12 mouse_events: 0;
13 type: IMAGE;
14 description {
15 state: "default" 0.0;
16 image.normal: "collisionL.png";
17 color: 255 255 255 0;
18 }
19 description {
20 state: "visible" 0.0;
21 inherit: "default" 0.0;
22 color: 255 255 255 255;
23 }
24 }
25
26 }
27
28 programs {
29
30 program {
31 name: "impact,show";
32 source: "ephysics_test";
33 signal: "impact,show";
34 action: STATE_SET "visible" 0.0;
35 transition: LINEAR 0.2;
36 target: "impact";
37 after: "impact,show2";
38 }
39
40 program {
41 name: "impact,show2";
42 action: STATE_SET "default" 0.0;
43 transition: LINEAR 0.2;
44 target: "impact";
45 }
46
47 }
48
49 }
diff --git a/legacy/ephysics/data/themes/ephysics_test.edc b/legacy/ephysics/data/themes/ephysics_test.edc
new file mode 100644
index 0000000..c8d4312
--- /dev/null
+++ b/legacy/ephysics/data/themes/ephysics_test.edc
@@ -0,0 +1,13 @@
1externals {
2 external: "elm";
3}
4
5collections {
6#include "balls.edc"
7#include "buttons.edc"
8#include "cubes.edc"
9#include "effects.edc"
10#include "frame.edc"
11#include "list.edc"
12#include "shadows.edc"
13}
diff --git a/legacy/ephysics/data/themes/frame.edc b/legacy/ephysics/data/themes/frame.edc
new file mode 100644
index 0000000..f4b072c
--- /dev/null
+++ b/legacy/ephysics/data/themes/frame.edc
@@ -0,0 +1,116 @@
1 images {
2 image: "arrows.png" COMP;
3 image: "background.jpg" COMP;
4 }
5
6 group {
7 name: "frame";
8
9 parts {
10
11 part {
12 name: "bg";
13 type: IMAGE;
14 mouse_events: 0;
15 description {
16 state: "default" 0.0;
17 min: 512 384;
18 max: 512 384;
19 image.normal: "background.jpg";
20 }
21 }
22
23 part {
24 name: "arrows";
25 type: IMAGE;
26 mouse_events: 0;
27 description {
28 state: "default" 0.0;
29 min: 326 241;
30 max: 326 241;
31 rel1.offset: -18 10;
32 color: 255 255 255 0;
33 image.normal: "arrows.png";
34 }
35 description {
36 state: "visible" 0.0;
37 inherit: "default" 0.0;
38 color: 255 255 255 255;
39 }
40 }
41
42 part {
43 name: "arrows_msg";
44 type: TEXT;
45 mouse_events: 0;
46 description {
47 state: "default" 0.0;
48 color: 232 224 215 0;
49 rel1.relative: 0.08 0.96;
50 rel2.relative: 0.92 1.0;
51 text {
52 font: "Sans";
53 size: 12;
54 text: "Press the arrows on the keyboard to give impulse to the object.";
55 }
56 }
57 description {
58 state: "visible" 0.0;
59 inherit: "default" 0.0;
60 color: 95 56 19 255;
61 }
62 }
63
64 part {
65 name: "restart_button";
66 type: EXTERNAL;
67 source: "elm/button";
68 mouse_events: 1;
69 description {
70 state: "default" 0.0;
71 rel1.relative: 1 0.08;
72 rel2.relative: 1 0.08;
73 fixed: 1 1;
74 align: 1 0.5;
75 params {
76 string: "style" "ephysics-test-restart";
77 }
78 }
79 }
80
81 part {
82 name: "extra_button";
83 type: SWALLOW;
84 mouse_events: 1;
85 description {
86 state: "default" 0.0;
87 rel1.relative: 0 0.08;
88 rel2.relative: 0 0.08;
89 fixed: 1 1;
90 align: 0 0.5;
91 }
92 }
93
94 }
95
96 programs {
97
98 program {
99 name: "restart_clicked";
100 source: "restart_button";
101 signal: "clicked";
102 action: SIGNAL_EMIT "restart" "test-theme";
103 }
104
105 program {
106 name: "arrows,show";
107 source: "ephysics_test";
108 signal: "arrows,show";
109 action: STATE_SET "visible" 0.0;
110 target: "arrows";
111 target: "arrows_msg";
112 }
113
114 }
115
116 }
diff --git a/legacy/ephysics/data/themes/images/arrows.png b/legacy/ephysics/data/themes/images/arrows.png
new file mode 100644
index 0000000..25f5e58
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/arrows.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/background.jpg b/legacy/ephysics/data/themes/images/background.jpg
new file mode 100644
index 0000000..7af3d58
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/background.jpg
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/ball-blue.png b/legacy/ephysics/data/themes/images/ball-blue.png
new file mode 100644
index 0000000..c74c249
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/ball-blue.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/ball-blue70.png b/legacy/ephysics/data/themes/images/ball-blue70.png
new file mode 100644
index 0000000..38546e5
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/ball-blue70.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/ball-green.png b/legacy/ephysics/data/themes/images/ball-green.png
new file mode 100644
index 0000000..a19945d
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/ball-green.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/ball-green70.png b/legacy/ephysics/data/themes/images/ball-green70.png
new file mode 100644
index 0000000..83ba8b9
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/ball-green70.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/ball-red.png b/legacy/ephysics/data/themes/images/ball-red.png
new file mode 100644
index 0000000..8fe0e4d
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/ball-red.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/ball-red70.png b/legacy/ephysics/data/themes/images/ball-red70.png
new file mode 100644
index 0000000..3a4af0a
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/ball-red70.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/bt_jump.png b/legacy/ephysics/data/themes/images/bt_jump.png
new file mode 100644
index 0000000..3116830
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/bt_jump.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/bt_jump_pressed.png b/legacy/ephysics/data/themes/images/bt_jump_pressed.png
new file mode 100644
index 0000000..b2fe316
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/bt_jump_pressed.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/bt_restart.png b/legacy/ephysics/data/themes/images/bt_restart.png
new file mode 100644
index 0000000..558c596
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/bt_restart.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/bt_restart_pressed.png b/legacy/ephysics/data/themes/images/bt_restart_pressed.png
new file mode 100644
index 0000000..62c8210
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/bt_restart_pressed.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/collisionL.png b/legacy/ephysics/data/themes/images/collisionL.png
new file mode 100644
index 0000000..160af4f
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/collisionL.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/cube-blue.png b/legacy/ephysics/data/themes/images/cube-blue.png
new file mode 100644
index 0000000..e848d2b
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/cube-blue.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/cube-purple.png b/legacy/ephysics/data/themes/images/cube-purple.png
new file mode 100644
index 0000000..096cdbb
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/cube-purple.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/impact.png b/legacy/ephysics/data/themes/images/impact.png
new file mode 100644
index 0000000..1dd89db
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/impact.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/list-item-corner-pressed.png b/legacy/ephysics/data/themes/images/list-item-corner-pressed.png
new file mode 100644
index 0000000..37a03d6
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/list-item-corner-pressed.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/list-item-corner.png b/legacy/ephysics/data/themes/images/list-item-corner.png
new file mode 100644
index 0000000..6f55f3c
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/list-item-corner.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/list-item-pressed.png b/legacy/ephysics/data/themes/images/list-item-pressed.png
new file mode 100644
index 0000000..21f218d
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/list-item-pressed.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/list-item.png b/legacy/ephysics/data/themes/images/list-item.png
new file mode 100644
index 0000000..6194a25
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/list-item.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/list.png b/legacy/ephysics/data/themes/images/list.png
new file mode 100644
index 0000000..8966ec3
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/list.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/shadow-ball.png b/legacy/ephysics/data/themes/images/shadow-ball.png
new file mode 100644
index 0000000..0221b58
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/shadow-ball.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/images/shadow-cube.png b/legacy/ephysics/data/themes/images/shadow-cube.png
new file mode 100644
index 0000000..12ac300
--- /dev/null
+++ b/legacy/ephysics/data/themes/images/shadow-cube.png
Binary files differ
diff --git a/legacy/ephysics/data/themes/list.edc b/legacy/ephysics/data/themes/list.edc
new file mode 100644
index 0000000..f0906fd
--- /dev/null
+++ b/legacy/ephysics/data/themes/list.edc
@@ -0,0 +1,134 @@
1 images {
2 image: "list-item-corner-pressed.png" COMP;
3 image: "list-item-corner.png" COMP;
4 image: "list-item-pressed.png" COMP;
5 image: "list-item.png" COMP;
6 }
7
8 group {
9 name: "elm/list/base/ephysics-test";
10
11 parts {
12
13 part {
14 name: "bg";
15 type: RECT;
16 mouse_events: 1;
17 description {
18 state: "default" 0.0;
19 color: 179 149 117 255;
20 }
21 }
22
23 part {
24 name: "elm.swallow.content";
25 type: SWALLOW;
26 description {
27 state: "default" 0.0;
28 rel1.offset: 0 40;
29 rel2.offset: -1 -41;
30 }
31 }
32
33 }
34
35 }
36
37 group {
38 name: "elm/list/item/ephysics-test";
39 name: "elm/list/item_odd/ephysics-test";
40
41 parts {
42
43 part {
44 name: "event";
45 type: RECT;
46 repeat_events: 1;
47 description {
48 state: "default" 0.0;
49 color: 0 0 0 0;
50 }
51 }
52
53 part {
54 name: "base";
55 mouse_events: 0;
56 description {
57 state: "default" 0.0;
58 min: 8 60;
59 rel2.relative: 0.8 1;
60 image.normal: "list-item.png";
61 }
62 description {
63 state: "selected" 0.0;
64 inherit: "default" 0.0;
65 image.normal: "list-item-pressed.png";
66 }
67 }
68
69 part {
70 name: "base-corner";
71 mouse_events: 0;
72 description {
73 state: "default" 0.0;
74 min: 42 60;
75 max: 42 60;
76 rel1 {
77 to: "base";
78 relative: 1 0;
79 }
80 align: 0 0.5;
81 image.normal: "list-item-corner.png";
82 }
83 description {
84 state: "selected" 0.0;
85 inherit: "default" 0.0;
86 image.normal: "list-item-corner-pressed.png";
87 }
88 }
89
90 part {
91 name: "elm.text";
92 type: TEXT;
93 mouse_events: 0;
94 scale: 1;
95 description {
96 state: "default" 0.0;
97 color: 232 224 215 255;
98 text {
99 font: "Sans";
100 style: "Bold";
101 size: 18;
102 min: 1 1;
103 align: 0 0.5;
104 }
105 align: 0 0.5;
106 rel1.offset: 36 0;
107 }
108 }
109
110 }
111
112 programs {
113
114 program {
115 name: "go_active";
116 source: "elm";
117 signal: "elm,state,selected";
118 action: STATE_SET "selected" 0.0;
119 target: "base";
120 target: "base-corner";
121 }
122
123 program {
124 name: "go_passive";
125 source: "elm";
126 signal: "elm,state,unselected";
127 action: STATE_SET "default" 0.0;
128 target: "base";
129 target: "base-corner";
130 }
131
132 }
133
134 }
diff --git a/legacy/ephysics/data/themes/shadows.edc b/legacy/ephysics/data/themes/shadows.edc
new file mode 100644
index 0000000..e4e1f44
--- /dev/null
+++ b/legacy/ephysics/data/themes/shadows.edc
@@ -0,0 +1,49 @@
1#define SHADOW_ALPHA_ID 1
2
3 images {
4 image: "shadow-ball.png" COMP;
5 image: "shadow-cube.png" COMP;
6 }
7
8#define SHADOW_GROUP(_name) \
9 group { \
10 name: #_name; \
11 \
12 script { \
13 public message(Msg_Type:type, id, ...) \
14 { \
15 if ((type == MSG_FLOAT) && (id == SHADOW_ALPHA_ID)) \
16 { \
17 new Float:shadow_alpha = getfarg(2); \
18 set_tween_state(PART:"shadow", shadow_alpha, "default", 0.0, \
19 "visible", 0.0); \
20 } \
21 } \
22 } \
23 \
24 parts { \
25 \
26 part { \
27 name: "shadow"; \
28 mouse_events: 0; \
29 type: IMAGE; \
30 description { \
31 state: "default" 0.0; \
32 image.normal: _name##".png"; \
33 color: 255 255 255 0; \
34 } \
35 description { \
36 state: "visible" 0.0; \
37 inherit: "default" 0.0; \
38 color: 255 255 255 255; \
39 } \
40 } \
41 } \
42 \
43 }
44
45SHADOW_GROUP(shadow-ball)
46SHADOW_GROUP(shadow-cube)
47
48#undef SHADOW_GROUP
49#undef SHADOW_ALPHA_ID
diff --git a/legacy/ephysics/doc/Doxyfile.in b/legacy/ephysics/doc/Doxyfile.in
new file mode 100644
index 0000000..f698331
--- /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 0000000..b00aa03
--- /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 0000000..44a9f25
--- /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 {