• R/O
  • SSH

mhack: Commit

マルチプレイヤーっぽいローグライク開発用のリポジトリ。


Commit MetaInfo

Revisiond270659754af46b3afc4b34c1bcc50dab75df436 (tree)
Time2011-07-15 07:48:55
Authorsatofumi
Commitersatofumi

Log Message

remove

Change Summary

Incremental Difference

diff -r 8d6d058ff897 -r d270659754af .hgignore
--- a/.hgignore Mon Dec 20 07:25:07 2010 +0900
+++ b/.hgignore Fri Jul 15 07:48:55 2011 +0900
@@ -3,6 +3,9 @@
33 *.o
44 *.a
55 *.exe
6+
67 generated_html/
78 light_sample/light_sample
89 walking_sample/walking_sample
10+
11+source/mhack
diff -r 8d6d058ff897 -r d270659754af Doxyfile
--- a/Doxyfile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1631 +0,0 @@
1-# Doxyfile 1.7.1-20100822
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-
23-DOXYFILE_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-
28-PROJECT_NAME =
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-
34-PROJECT_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-
41-OUTPUT_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-
50-CREATE_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-
63-OUTPUT_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-
70-BRIEF_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-
77-REPEAT_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-
89-ABBREVIATE_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-
95-ALWAYS_DETAILED_SEC = NO
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-
102-INLINE_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-
108-FULL_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-
117-STRIP_FROM_PATH =
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-
126-STRIP_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 if your file system
130-# doesn't support long names like on DOS, Mac, or CD-ROM.
131-
132-SHORT_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-
140-JAVADOC_AUTOBRIEF = NO
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-
148-QT_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-
156-MULTILINE_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-
162-INHERIT_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-
168-SEPARATE_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-
173-TAB_SIZE = 8
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 =
183-
184-# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
185-# sources only. Doxygen will then generate output that is more tailored for C.
186-# For instance, some of the names that are used will be different. The list
187-# of all members will be omitted, etc.
188-
189-OPTIMIZE_OUTPUT_FOR_C = NO
190-
191-# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
192-# sources only. Doxygen will then generate output that is more tailored for
193-# Java. For instance, namespaces will be presented as packages, qualified
194-# scopes will look different, etc.
195-
196-OPTIMIZE_OUTPUT_JAVA = NO
197-
198-# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
199-# sources only. Doxygen will then generate output that is more tailored for
200-# Fortran.
201-
202-OPTIMIZE_FOR_FORTRAN = NO
203-
204-# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
205-# sources. Doxygen will then generate output that is tailored for
206-# VHDL.
207-
208-OPTIMIZE_OUTPUT_VHDL = NO
209-
210-# Doxygen selects the parser to use depending on the extension of the files it
211-# parses. With this tag you can assign which parser to use for a given extension.
212-# Doxygen has a built-in mapping, but you can override or extend it using this
213-# tag. The format is ext=language, where ext is a file extension, and language
214-# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
215-# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
216-# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
217-# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
218-# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
219-
220-EXTENSION_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 makes the inheritance and collaboration
227-# diagrams that involve STL classes more complete and accurate.
228-
229-BUILTIN_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-
234-CPP_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-
240-SIP_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 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-
249-IDL_PROPERTY_SUPPORT = YES
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-
256-DISTRIBUTE_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-
264-SUBGROUPING = 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-
274-TYPEDEF_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 rougly 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-
290-SYMBOL_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-
301-EXTRACT_ALL = NO
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-
306-EXTRACT_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-
311-EXTRACT_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-
317-EXTRACT_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-
324-EXTRACT_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 namespaces are hidden.
331-
332-EXTRACT_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-
340-HIDE_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-
347-HIDE_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-
354-HIDE_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-
361-HIDE_IN_BODY_DOCS = NO
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-
368-INTERNAL_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-
376-CASE_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-
382-HIDE_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-
388-SHOW_INCLUDE_FILES = YES
389-
390-# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
391-# will list include files with double quotes in the documentation
392-# rather than with sharp brackets.
393-
394-FORCE_LOCAL_INCLUDES = NO
395-
396-# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
397-# is inserted in the documentation for inline members.
398-
399-INLINE_INFO = YES
400-
401-# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
402-# will sort the (detailed) documentation of file and class members
403-# alphabetically by member name. If set to NO the members will appear in
404-# declaration order.
405-
406-SORT_MEMBER_DOCS = YES
407-
408-# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
409-# brief documentation of file, namespace and class members alphabetically
410-# by member name. If set to NO (the default) the members will appear in
411-# declaration order.
412-
413-SORT_BRIEF_DOCS = NO
414-
415-# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
416-# will sort the (brief and detailed) documentation of class members so that
417-# constructors and destructors are listed first. If set to NO (the default)
418-# the constructors will appear in the respective orders defined by
419-# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
420-# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
421-# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
422-
423-SORT_MEMBERS_CTORS_1ST = NO
424-
425-# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
426-# hierarchy of group names into alphabetical order. If set to NO (the default)
427-# the group names will appear in their defined order.
428-
429-SORT_GROUP_NAMES = NO
430-
431-# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
432-# sorted by fully-qualified names, including namespaces. If set to
433-# NO (the default), the class list will be sorted only by class name,
434-# not including the namespace part.
435-# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
436-# Note: This option applies only to the class list, not to the
437-# alphabetical list.
438-
439-SORT_BY_SCOPE_NAME = NO
440-
441-# The GENERATE_TODOLIST tag can be used to enable (YES) or
442-# disable (NO) the todo list. This list is created by putting \todo
443-# commands in the documentation.
444-
445-GENERATE_TODOLIST = YES
446-
447-# The GENERATE_TESTLIST tag can be used to enable (YES) or
448-# disable (NO) the test list. This list is created by putting \test
449-# commands in the documentation.
450-
451-GENERATE_TESTLIST = YES
452-
453-# The GENERATE_BUGLIST tag can be used to enable (YES) or
454-# disable (NO) the bug list. This list is created by putting \bug
455-# commands in the documentation.
456-
457-GENERATE_BUGLIST = YES
458-
459-# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
460-# disable (NO) the deprecated list. This list is created by putting
461-# \deprecated commands in the documentation.
462-
463-GENERATE_DEPRECATEDLIST= YES
464-
465-# The ENABLED_SECTIONS tag can be used to enable conditional
466-# documentation sections, marked by \if sectionname ... \endif.
467-
468-ENABLED_SECTIONS =
469-
470-# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
471-# the initial value of a variable or macro consists of for it to appear in
472-# the documentation. If the initializer consists of more lines than specified
473-# here it will be hidden. Use a value of 0 to hide initializers completely.
474-# The appearance of the initializer of individual variables and macros in the
475-# documentation can be controlled using \showinitializer or \hideinitializer
476-# command in the documentation regardless of this setting.
477-
478-MAX_INITIALIZER_LINES = 30
479-
480-# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
481-# at the bottom of the documentation of classes and structs. If set to YES the
482-# list will mention the files that were used to generate the documentation.
483-
484-SHOW_USED_FILES = YES
485-
486-# If the sources in your project are distributed over multiple directories
487-# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
488-# in the documentation. The default is NO.
489-
490-SHOW_DIRECTORIES = NO
491-
492-# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
493-# This will remove the Files entry from the Quick Index and from the
494-# Folder Tree View (if specified). The default is YES.
495-
496-SHOW_FILES = YES
497-
498-# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
499-# Namespaces page.
500-# This will remove the Namespaces entry from the Quick Index
501-# and from the Folder Tree View (if specified). The default is YES.
502-
503-SHOW_NAMESPACES = YES
504-
505-# The FILE_VERSION_FILTER tag can be used to specify a program or script that
506-# doxygen should invoke to get the current version for each file (typically from
507-# the version control system). Doxygen will invoke the program by executing (via
508-# popen()) the command <command> <input-file>, where <command> is the value of
509-# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
510-# provided by doxygen. Whatever the program writes to standard output
511-# is used as the file version. See the manual for examples.
512-
513-FILE_VERSION_FILTER =
514-
515-# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
516-# by doxygen. The layout file controls the global structure of the generated
517-# output files in an output format independent way. The create the layout file
518-# that represents doxygen's defaults, run doxygen with the -l option.
519-# You can optionally specify a file name after the option, if omitted
520-# DoxygenLayout.xml will be used as the name of the layout file.
521-
522-LAYOUT_FILE =
523-
524-#---------------------------------------------------------------------------
525-# configuration options related to warning and progress messages
526-#---------------------------------------------------------------------------
527-
528-# The QUIET tag can be used to turn on/off the messages that are generated
529-# by doxygen. Possible values are YES and NO. If left blank NO is used.
530-
531-QUIET = NO
532-
533-# The WARNINGS tag can be used to turn on/off the warning messages that are
534-# generated by doxygen. Possible values are YES and NO. If left blank
535-# NO is used.
536-
537-WARNINGS = YES
538-
539-# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
540-# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
541-# automatically be disabled.
542-
543-WARN_IF_UNDOCUMENTED = YES
544-
545-# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
546-# potential errors in the documentation, such as not documenting some
547-# parameters in a documented function, or documenting parameters that
548-# don't exist or using markup commands wrongly.
549-
550-WARN_IF_DOC_ERROR = YES
551-
552-# The WARN_NO_PARAMDOC option can be abled to get warnings for
553-# functions that are documented, but have no documentation for their parameters
554-# or return value. If set to NO (the default) doxygen will only warn about
555-# wrong or incomplete parameter documentation, but not about the absence of
556-# documentation.
557-
558-WARN_NO_PARAMDOC = NO
559-
560-# The WARN_FORMAT tag determines the format of the warning messages that
561-# doxygen can produce. The string should contain the $file, $line, and $text
562-# tags, which will be replaced by the file and line number from which the
563-# warning originated and the warning text. Optionally the format may contain
564-# $version, which will be replaced by the version of the file (if it could
565-# be obtained via FILE_VERSION_FILTER)
566-
567-WARN_FORMAT = "$file:$line: $text"
568-
569-# The WARN_LOGFILE tag can be used to specify a file to which warning
570-# and error messages should be written. If left blank the output is written
571-# to stderr.
572-
573-WARN_LOGFILE =
574-
575-#---------------------------------------------------------------------------
576-# configuration options related to the input files
577-#---------------------------------------------------------------------------
578-
579-# The INPUT tag can be used to specify the files and/or directories that contain
580-# documented source files. You may enter file names like "myfile.cpp" or
581-# directories like "/usr/src/myproject". Separate the files or directories
582-# with spaces.
583-
584-INPUT = dox/ sample/walking_sample sample/light_sample
585-
586-# This tag can be used to specify the character encoding of the source files
587-# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
588-# also the default input encoding. Doxygen uses libiconv (or the iconv built
589-# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
590-# the list of possible encodings.
591-
592-INPUT_ENCODING = UTF-8
593-
594-# If the value of the INPUT tag contains directories, you can use the
595-# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
596-# and *.h) to filter out the source-files in the directories. If left
597-# blank the following patterns are tested:
598-# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
599-# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
600-
601-FILE_PATTERNS =
602-
603-# The RECURSIVE tag can be used to turn specify whether or not subdirectories
604-# should be searched for input files as well. Possible values are YES and NO.
605-# If left blank NO is used.
606-
607-RECURSIVE = NO
608-
609-# The EXCLUDE tag can be used to specify files and/or directories that should
610-# excluded from the INPUT source files. This way you can easily exclude a
611-# subdirectory from a directory tree whose root is specified with the INPUT tag.
612-
613-EXCLUDE =
614-
615-# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
616-# directories that are symbolic links (a Unix filesystem feature) are excluded
617-# from the input.
618-
619-EXCLUDE_SYMLINKS = NO
620-
621-# If the value of the INPUT tag contains directories, you can use the
622-# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
623-# certain files from those directories. Note that the wildcards are matched
624-# against the file with absolute path, so to exclude all test directories
625-# for example use the pattern */test/*
626-
627-EXCLUDE_PATTERNS =
628-
629-# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
630-# (namespaces, classes, functions, etc.) that should be excluded from the
631-# output. The symbol name can be a fully qualified name, a word, or if the
632-# wildcard * is used, a substring. Examples: ANamespace, AClass,
633-# AClass::ANamespace, ANamespace::*Test
634-
635-EXCLUDE_SYMBOLS =
636-
637-# The EXAMPLE_PATH tag can be used to specify one or more files or
638-# directories that contain example code fragments that are included (see
639-# the \include command).
640-
641-EXAMPLE_PATH = sample/walking_sample sample/light_sample
642-
643-# If the value of the EXAMPLE_PATH tag contains directories, you can use the
644-# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
645-# and *.h) to filter out the source-files in the directories. If left
646-# blank all files are included.
647-
648-EXAMPLE_PATTERNS =
649-
650-# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
651-# searched for input files to be used with the \include or \dontinclude
652-# commands irrespective of the value of the RECURSIVE tag.
653-# Possible values are YES and NO. If left blank NO is used.
654-
655-EXAMPLE_RECURSIVE = NO
656-
657-# The IMAGE_PATH tag can be used to specify one or more files or
658-# directories that contain image that are included in the documentation (see
659-# the \image command).
660-
661-IMAGE_PATH = dox/img/
662-
663-# The INPUT_FILTER tag can be used to specify a program that doxygen should
664-# invoke to filter for each input file. Doxygen will invoke the filter program
665-# by executing (via popen()) the command <filter> <input-file>, where <filter>
666-# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
667-# input file. Doxygen will then use the output that the filter program writes
668-# to standard output.
669-# If FILTER_PATTERNS is specified, this tag will be
670-# ignored.
671-
672-INPUT_FILTER =
673-
674-# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
675-# basis.
676-# Doxygen will compare the file name with each pattern and apply the
677-# filter if there is a match.
678-# The filters are a list of the form:
679-# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
680-# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
681-# is applied to all files.
682-
683-FILTER_PATTERNS =
684-
685-# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
686-# INPUT_FILTER) will be used to filter the input files when producing source
687-# files to browse (i.e. when SOURCE_BROWSER is set to YES).
688-
689-FILTER_SOURCE_FILES = NO
690-
691-#---------------------------------------------------------------------------
692-# configuration options related to source browsing
693-#---------------------------------------------------------------------------
694-
695-# If the SOURCE_BROWSER tag is set to YES then a list of source files will
696-# be generated. Documented entities will be cross-referenced with these sources.
697-# Note: To get rid of all source code in the generated output, make sure also
698-# VERBATIM_HEADERS is set to NO.
699-
700-SOURCE_BROWSER = NO
701-
702-# Setting the INLINE_SOURCES tag to YES will include the body
703-# of functions and classes directly in the documentation.
704-
705-INLINE_SOURCES = NO
706-
707-# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
708-# doxygen to hide any special comment blocks from generated source code
709-# fragments. Normal C and C++ comments will always remain visible.
710-
711-STRIP_CODE_COMMENTS = YES
712-
713-# If the REFERENCED_BY_RELATION tag is set to YES
714-# then for each documented function all documented
715-# functions referencing it will be listed.
716-
717-REFERENCED_BY_RELATION = NO
718-
719-# If the REFERENCES_RELATION tag is set to YES
720-# then for each documented function all documented entities
721-# called/used by that function will be listed.
722-
723-REFERENCES_RELATION = NO
724-
725-# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
726-# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
727-# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
728-# link to the source code.
729-# Otherwise they will link to the documentation.
730-
731-REFERENCES_LINK_SOURCE = YES
732-
733-# If the USE_HTAGS tag is set to YES then the references to source code
734-# will point to the HTML generated by the htags(1) tool instead of doxygen
735-# built-in source browser. The htags tool is part of GNU's global source
736-# tagging system (see http://www.gnu.org/software/global/global.html). You
737-# will need version 4.8.6 or higher.
738-
739-USE_HTAGS = NO
740-
741-# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
742-# will generate a verbatim copy of the header file for each class for
743-# which an include is specified. Set to NO to disable this.
744-
745-VERBATIM_HEADERS = YES
746-
747-#---------------------------------------------------------------------------
748-# configuration options related to the alphabetical class index
749-#---------------------------------------------------------------------------
750-
751-# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
752-# of all compounds will be generated. Enable this if the project
753-# contains a lot of classes, structs, unions or interfaces.
754-
755-ALPHABETICAL_INDEX = YES
756-
757-# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
758-# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
759-# in which this list will be split (can be a number in the range [1..20])
760-
761-COLS_IN_ALPHA_INDEX = 5
762-
763-# In case all classes in a project start with a common prefix, all
764-# classes will be put under the same header in the alphabetical index.
765-# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
766-# should be ignored while generating the index headers.
767-
768-IGNORE_PREFIX =
769-
770-#---------------------------------------------------------------------------
771-# configuration options related to the HTML output
772-#---------------------------------------------------------------------------
773-
774-# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
775-# generate HTML output.
776-
777-GENERATE_HTML = YES
778-
779-# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
780-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
781-# put in front of it. If left blank `html' will be used as the default path.
782-
783-HTML_OUTPUT = generated_html
784-
785-# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
786-# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
787-# doxygen will generate files with .html extension.
788-
789-HTML_FILE_EXTENSION = .html
790-
791-# The HTML_HEADER tag can be used to specify a personal HTML header for
792-# each generated HTML page. If it is left blank doxygen will generate a
793-# standard header.
794-
795-HTML_HEADER =
796-
797-# The HTML_FOOTER tag can be used to specify a personal HTML footer for
798-# each generated HTML page. If it is left blank doxygen will generate a
799-# standard footer.
800-
801-HTML_FOOTER =
802-
803-# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
804-# style sheet that is used by each HTML page. It can be used to
805-# fine-tune the look of the HTML output. If the tag is left blank doxygen
806-# will generate a default style sheet. Note that doxygen will try to copy
807-# the style sheet file to the HTML output directory, so don't put your own
808-# stylesheet in the HTML output directory as well, or it will be erased!
809-
810-HTML_STYLESHEET = dox/doxygen_stylesheet.css
811-
812-# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
813-# Doxygen will adjust the colors in the stylesheet and background images
814-# according to this color. Hue is specified as an angle on a colorwheel,
815-# see http://en.wikipedia.org/wiki/Hue for more information.
816-# For instance the value 0 represents red, 60 is yellow, 120 is green,
817-# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
818-# The allowed range is 0 to 359.
819-
820-HTML_COLORSTYLE_HUE = 220
821-
822-# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
823-# the colors in the HTML output. For a value of 0 the output will use
824-# grayscales only. A value of 255 will produce the most vivid colors.
825-
826-HTML_COLORSTYLE_SAT = 100
827-
828-# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
829-# the luminance component of the colors in the HTML output. Values below
830-# 100 gradually make the output lighter, whereas values above 100 make
831-# the output darker. The value divided by 100 is the actual gamma applied,
832-# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
833-# and 100 does not change the gamma.
834-
835-HTML_COLORSTYLE_GAMMA = 80
836-
837-# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
838-# page will contain the date and time when the page was generated. Setting
839-# this to NO can help when comparing the output of multiple runs.
840-
841-HTML_TIMESTAMP = YES
842-
843-# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
844-# files or namespaces will be aligned in HTML using tables. If set to
845-# NO a bullet list will be used.
846-
847-HTML_ALIGN_MEMBERS = YES
848-
849-# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
850-# documentation will contain sections that can be hidden and shown after the
851-# page has loaded. For this to work a browser that supports
852-# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
853-# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
854-
855-HTML_DYNAMIC_SECTIONS = NO
856-
857-# If the GENERATE_DOCSET tag is set to YES, additional index files
858-# will be generated that can be used as input for Apple's Xcode 3
859-# integrated development environment, introduced with OSX 10.5 (Leopard).
860-# To create a documentation set, doxygen will generate a Makefile in the
861-# HTML output directory. Running make will produce the docset in that
862-# directory and running "make install" will install the docset in
863-# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
864-# it at startup.
865-# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
866-# for more information.
867-
868-GENERATE_DOCSET = NO
869-
870-# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
871-# feed. A documentation feed provides an umbrella under which multiple
872-# documentation sets from a single provider (such as a company or product suite)
873-# can be grouped.
874-
875-DOCSET_FEEDNAME = "Doxygen generated docs"
876-
877-# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
878-# should uniquely identify the documentation set bundle. This should be a
879-# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
880-# will append .docset to the name.
881-
882-DOCSET_BUNDLE_ID = org.doxygen.Project
883-
884-# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
885-# the documentation publisher. This should be a reverse domain-name style
886-# string, e.g. com.mycompany.MyDocSet.documentation.
887-
888-DOCSET_PUBLISHER_ID = org.doxygen.Publisher
889-
890-# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
891-
892-DOCSET_PUBLISHER_NAME = Publisher
893-
894-# If the GENERATE_HTMLHELP tag is set to YES, additional index files
895-# will be generated that can be used as input for tools like the
896-# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
897-# of the generated HTML documentation.
898-
899-GENERATE_HTMLHELP = NO
900-
901-# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
902-# be used to specify the file name of the resulting .chm file. You
903-# can add a path in front of the file if the result should not be
904-# written to the html output directory.
905-
906-CHM_FILE =
907-
908-# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
909-# be used to specify the location (absolute path including file name) of
910-# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
911-# the HTML help compiler on the generated index.hhp.
912-
913-HHC_LOCATION =
914-
915-# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
916-# controls if a separate .chi index file is generated (YES) or that
917-# it should be included in the master .chm file (NO).
918-
919-GENERATE_CHI = NO
920-
921-# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
922-# is used to encode HtmlHelp index (hhk), content (hhc) and project file
923-# content.
924-
925-CHM_INDEX_ENCODING =
926-
927-# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
928-# controls whether a binary table of contents is generated (YES) or a
929-# normal table of contents (NO) in the .chm file.
930-
931-BINARY_TOC = NO
932-
933-# The TOC_EXPAND flag can be set to YES to add extra items for group members
934-# to the contents of the HTML help documentation and to the tree view.
935-
936-TOC_EXPAND = NO
937-
938-# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
939-# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
940-# that can be used as input for Qt's qhelpgenerator to generate a
941-# Qt Compressed Help (.qch) of the generated HTML documentation.
942-
943-GENERATE_QHP = NO
944-
945-# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
946-# be used to specify the file name of the resulting .qch file.
947-# The path specified is relative to the HTML output folder.
948-
949-QCH_FILE =
950-
951-# The QHP_NAMESPACE tag specifies the namespace to use when generating
952-# Qt Help Project output. For more information please see
953-# http://doc.trolltech.com/qthelpproject.html#namespace
954-
955-QHP_NAMESPACE = org.doxygen.Project
956-
957-# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
958-# Qt Help Project output. For more information please see
959-# http://doc.trolltech.com/qthelpproject.html#virtual-folders
960-
961-QHP_VIRTUAL_FOLDER = doc
962-
963-# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
964-# add. For more information please see
965-# http://doc.trolltech.com/qthelpproject.html#custom-filters
966-
967-QHP_CUST_FILTER_NAME =
968-
969-# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
970-# custom filter to add. For more information please see
971-# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
972-# Qt Help Project / Custom Filters</a>.
973-
974-QHP_CUST_FILTER_ATTRS =
975-
976-# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
977-# project's
978-# filter section matches.
979-# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
980-# Qt Help Project / Filter Attributes</a>.
981-
982-QHP_SECT_FILTER_ATTRS =
983-
984-# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
985-# be used to specify the location of Qt's qhelpgenerator.
986-# If non-empty doxygen will try to run qhelpgenerator on the generated
987-# .qhp file.
988-
989-QHG_LOCATION =
990-
991-# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
992-# will be generated, which together with the HTML files, form an Eclipse help
993-# plugin. To install this plugin and make it available under the help contents
994-# menu in Eclipse, the contents of the directory containing the HTML and XML
995-# files needs to be copied into the plugins directory of eclipse. The name of
996-# the directory within the plugins directory should be the same as
997-# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
998-# the help appears.
999-
1000-GENERATE_ECLIPSEHELP = NO
1001-
1002-# A unique identifier for the eclipse help plugin. When installing the plugin
1003-# the directory name containing the HTML and XML files should also have
1004-# this name.
1005-
1006-ECLIPSE_DOC_ID = org.doxygen.Project
1007-
1008-# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1009-# top of each HTML page. The value NO (the default) enables the index and
1010-# the value YES disables it.
1011-
1012-DISABLE_INDEX = NO
1013-
1014-# This tag can be used to set the number of enum values (range [0,1..20])
1015-# that doxygen will group on one line in the generated HTML documentation.
1016-# Note that a value of 0 will completely suppress the enum values from appearing in the overview section.
1017-
1018-ENUM_VALUES_PER_LINE = 4
1019-
1020-# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1021-# structure should be generated to display hierarchical information.
1022-# If the tag value is set to YES, a side panel will be generated
1023-# containing a tree-like index structure (just like the one that
1024-# is generated for HTML Help). For this to work a browser that supports
1025-# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1026-# Windows users are probably better off using the HTML help feature.
1027-
1028-GENERATE_TREEVIEW = NO
1029-
1030-# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1031-# and Class Hierarchy pages using a tree view instead of an ordered list.
1032-
1033-USE_INLINE_TREES = NO
1034-
1035-# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1036-# used to set the initial width (in pixels) of the frame in which the tree
1037-# is shown.
1038-
1039-TREEVIEW_WIDTH = 250
1040-
1041-# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1042-# links to external symbols imported via tag files in a separate window.
1043-
1044-EXT_LINKS_IN_WINDOW = NO
1045-
1046-# Use this tag to change the font size of Latex formulas included
1047-# as images in the HTML documentation. The default is 10. Note that
1048-# when you change the font size after a successful doxygen run you need
1049-# to manually remove any form_*.png images from the HTML output directory
1050-# to force them to be regenerated.
1051-
1052-FORMULA_FONTSIZE = 10
1053-
1054-# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1055-# generated for formulas are transparent PNGs. Transparent PNGs are
1056-# not supported properly for IE 6.0, but are supported on all modern browsers.
1057-# Note that when changing this option you need to delete any form_*.png files
1058-# in the HTML output before the changes have effect.
1059-
1060-FORMULA_TRANSPARENT = YES
1061-
1062-# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1063-# for the HTML output. The underlying search engine uses javascript
1064-# and DHTML and should work on any modern browser. Note that when using
1065-# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1066-# (GENERATE_DOCSET) there is already a search function so this one should
1067-# typically be disabled. For large projects the javascript based search engine
1068-# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1069-
1070-SEARCHENGINE = YES
1071-
1072-# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1073-# implemented using a PHP enabled web server instead of at the web client
1074-# using Javascript. Doxygen will generate the search PHP script and index
1075-# file to put on the web server. The advantage of the server
1076-# based approach is that it scales better to large projects and allows
1077-# full text search. The disadvances is that it is more difficult to setup
1078-# and does not have live searching capabilities.
1079-
1080-SERVER_BASED_SEARCH = NO
1081-
1082-#---------------------------------------------------------------------------
1083-# configuration options related to the LaTeX output
1084-#---------------------------------------------------------------------------
1085-
1086-# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1087-# generate Latex output.
1088-
1089-GENERATE_LATEX = NO
1090-
1091-# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1092-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1093-# put in front of it. If left blank `latex' will be used as the default path.
1094-
1095-LATEX_OUTPUT = latex
1096-
1097-# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1098-# invoked. If left blank `latex' will be used as the default command name.
1099-# Note that when enabling USE_PDFLATEX this option is only used for
1100-# generating bitmaps for formulas in the HTML output, but not in the
1101-# Makefile that is written to the output directory.
1102-
1103-LATEX_CMD_NAME = latex
1104-
1105-# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1106-# generate index for LaTeX. If left blank `makeindex' will be used as the
1107-# default command name.
1108-
1109-MAKEINDEX_CMD_NAME = makeindex
1110-
1111-# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1112-# LaTeX documents. This may be useful for small projects and may help to
1113-# save some trees in general.
1114-
1115-COMPACT_LATEX = NO
1116-
1117-# The PAPER_TYPE tag can be used to set the paper type that is used
1118-# by the printer. Possible values are: a4, a4wide, letter, legal and
1119-# executive. If left blank a4wide will be used.
1120-
1121-PAPER_TYPE = a4wide
1122-
1123-# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1124-# packages that should be included in the LaTeX output.
1125-
1126-EXTRA_PACKAGES =
1127-
1128-# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1129-# the generated latex document. The header should contain everything until
1130-# the first chapter. If it is left blank doxygen will generate a
1131-# standard header. Notice: only use this tag if you know what you are doing!
1132-
1133-LATEX_HEADER =
1134-
1135-# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1136-# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1137-# contain links (just like the HTML output) instead of page references
1138-# This makes the output suitable for online browsing using a pdf viewer.
1139-
1140-PDF_HYPERLINKS = YES
1141-
1142-# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1143-# plain latex in the generated Makefile. Set this option to YES to get a
1144-# higher quality PDF documentation.
1145-
1146-USE_PDFLATEX = YES
1147-
1148-# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1149-# command to the generated LaTeX files. This will instruct LaTeX to keep
1150-# running if errors occur, instead of asking the user for help.
1151-# This option is also used when generating formulas in HTML.
1152-
1153-LATEX_BATCHMODE = NO
1154-
1155-# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1156-# include the index chapters (such as File Index, Compound Index, etc.)
1157-# in the output.
1158-
1159-LATEX_HIDE_INDICES = NO
1160-
1161-# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1162-# source code with syntax highlighting in the LaTeX output.
1163-# Note that which sources are shown also depends on other settings
1164-# such as SOURCE_BROWSER.
1165-
1166-LATEX_SOURCE_CODE = NO
1167-
1168-#---------------------------------------------------------------------------
1169-# configuration options related to the RTF output
1170-#---------------------------------------------------------------------------
1171-
1172-# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1173-# The RTF output is optimized for Word 97 and may not look very pretty with
1174-# other RTF readers or editors.
1175-
1176-GENERATE_RTF = NO
1177-
1178-# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1179-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1180-# put in front of it. If left blank `rtf' will be used as the default path.
1181-
1182-RTF_OUTPUT = rtf
1183-
1184-# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1185-# RTF documents. This may be useful for small projects and may help to
1186-# save some trees in general.
1187-
1188-COMPACT_RTF = NO
1189-
1190-# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1191-# will contain hyperlink fields. The RTF file will
1192-# contain links (just like the HTML output) instead of page references.
1193-# This makes the output suitable for online browsing using WORD or other
1194-# programs which support those fields.
1195-# Note: wordpad (write) and others do not support links.
1196-
1197-RTF_HYPERLINKS = NO
1198-
1199-# Load stylesheet definitions from file. Syntax is similar to doxygen's
1200-# config file, i.e. a series of assignments. You only have to provide
1201-# replacements, missing definitions are set to their default value.
1202-
1203-RTF_STYLESHEET_FILE =
1204-
1205-# Set optional variables used in the generation of an rtf document.
1206-# Syntax is similar to doxygen's config file.
1207-
1208-RTF_EXTENSIONS_FILE =
1209-
1210-#---------------------------------------------------------------------------
1211-# configuration options related to the man page output
1212-#---------------------------------------------------------------------------
1213-
1214-# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1215-# generate man pages
1216-
1217-GENERATE_MAN = NO
1218-
1219-# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1220-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1221-# put in front of it. If left blank `man' will be used as the default path.
1222-
1223-MAN_OUTPUT = man
1224-
1225-# The MAN_EXTENSION tag determines the extension that is added to
1226-# the generated man pages (default is the subroutine's section .3)
1227-
1228-MAN_EXTENSION = .3
1229-
1230-# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1231-# then it will generate one additional man file for each entity
1232-# documented in the real man page(s). These additional files
1233-# only source the real man page, but without them the man command
1234-# would be unable to find the correct page. The default is NO.
1235-
1236-MAN_LINKS = NO
1237-
1238-#---------------------------------------------------------------------------
1239-# configuration options related to the XML output
1240-#---------------------------------------------------------------------------
1241-
1242-# If the GENERATE_XML tag is set to YES Doxygen will
1243-# generate an XML file that captures the structure of
1244-# the code including all documentation.
1245-
1246-GENERATE_XML = NO
1247-
1248-# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1249-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1250-# put in front of it. If left blank `xml' will be used as the default path.
1251-
1252-XML_OUTPUT = xml
1253-
1254-# The XML_SCHEMA tag can be used to specify an XML schema,
1255-# which can be used by a validating XML parser to check the
1256-# syntax of the XML files.
1257-
1258-XML_SCHEMA =
1259-
1260-# The XML_DTD tag can be used to specify an XML DTD,
1261-# which can be used by a validating XML parser to check the
1262-# syntax of the XML files.
1263-
1264-XML_DTD =
1265-
1266-# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1267-# dump the program listings (including syntax highlighting
1268-# and cross-referencing information) to the XML output. Note that
1269-# enabling this will significantly increase the size of the XML output.
1270-
1271-XML_PROGRAMLISTING = YES
1272-
1273-#---------------------------------------------------------------------------
1274-# configuration options for the AutoGen Definitions output
1275-#---------------------------------------------------------------------------
1276-
1277-# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1278-# generate an AutoGen Definitions (see autogen.sf.net) file
1279-# that captures the structure of the code including all
1280-# documentation. Note that this feature is still experimental
1281-# and incomplete at the moment.
1282-
1283-GENERATE_AUTOGEN_DEF = NO
1284-
1285-#---------------------------------------------------------------------------
1286-# configuration options related to the Perl module output
1287-#---------------------------------------------------------------------------
1288-
1289-# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1290-# generate a Perl module file that captures the structure of
1291-# the code including all documentation. Note that this
1292-# feature is still experimental and incomplete at the
1293-# moment.
1294-
1295-GENERATE_PERLMOD = NO
1296-
1297-# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1298-# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1299-# to generate PDF and DVI output from the Perl module output.
1300-
1301-PERLMOD_LATEX = NO
1302-
1303-# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1304-# nicely formatted so it can be parsed by a human reader.
1305-# This is useful
1306-# if you want to understand what is going on.
1307-# On the other hand, if this
1308-# tag is set to NO the size of the Perl module output will be much smaller
1309-# and Perl will parse it just the same.
1310-
1311-PERLMOD_PRETTY = YES
1312-
1313-# The names of the make variables in the generated doxyrules.make file
1314-# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1315-# This is useful so different doxyrules.make files included by the same
1316-# Makefile don't overwrite each other's variables.
1317-
1318-PERLMOD_MAKEVAR_PREFIX =
1319-
1320-#---------------------------------------------------------------------------
1321-# Configuration options related to the preprocessor
1322-#---------------------------------------------------------------------------
1323-
1324-# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1325-# evaluate all C-preprocessor directives found in the sources and include
1326-# files.
1327-
1328-ENABLE_PREPROCESSING = YES
1329-
1330-# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1331-# names in the source code. If set to NO (the default) only conditional
1332-# compilation will be performed. Macro expansion can be done in a controlled
1333-# way by setting EXPAND_ONLY_PREDEF to YES.
1334-
1335-MACRO_EXPANSION = NO
1336-
1337-# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1338-# then the macro expansion is limited to the macros specified with the
1339-# PREDEFINED and EXPAND_AS_DEFINED tags.
1340-
1341-EXPAND_ONLY_PREDEF = NO
1342-
1343-# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1344-# in the INCLUDE_PATH (see below) will be search if a #include is found.
1345-
1346-SEARCH_INCLUDES = YES
1347-
1348-# The INCLUDE_PATH tag can be used to specify one or more directories that
1349-# contain include files that are not input files but should be processed by
1350-# the preprocessor.
1351-
1352-INCLUDE_PATH =
1353-
1354-# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1355-# patterns (like *.h and *.hpp) to filter out the header-files in the
1356-# directories. If left blank, the patterns specified with FILE_PATTERNS will
1357-# be used.
1358-
1359-INCLUDE_FILE_PATTERNS =
1360-
1361-# The PREDEFINED tag can be used to specify one or more macro names that
1362-# are defined before the preprocessor is started (similar to the -D option of
1363-# gcc). The argument of the tag is a list of macros of the form: name
1364-# or name=definition (no spaces). If the definition and the = are
1365-# omitted =1 is assumed. To prevent a macro definition from being
1366-# undefined via #undef or recursively expanded use the := operator
1367-# instead of the = operator.
1368-
1369-PREDEFINED =
1370-
1371-# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1372-# this tag can be used to specify a list of macro names that should be expanded.
1373-# The macro definition that is found in the sources will be used.
1374-# Use the PREDEFINED tag if you want to use a different macro definition.
1375-
1376-EXPAND_AS_DEFINED =
1377-
1378-# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1379-# doxygen's preprocessor will remove all function-like macros that are alone
1380-# on a line, have an all uppercase name, and do not end with a semicolon. Such
1381-# function macros are typically used for boiler-plate code, and will confuse
1382-# the parser if not removed.
1383-
1384-SKIP_FUNCTION_MACROS = YES
1385-
1386-#---------------------------------------------------------------------------
1387-# Configuration::additions related to external references
1388-#---------------------------------------------------------------------------
1389-
1390-# The TAGFILES option can be used to specify one or more tagfiles.
1391-# Optionally an initial location of the external documentation
1392-# can be added for each tagfile. The format of a tag file without
1393-# this location is as follows:
1394-#
1395-# TAGFILES = file1 file2 ...
1396-# Adding location for the tag files is done as follows:
1397-#
1398-# TAGFILES = file1=loc1 "file2 = loc2" ...
1399-# where "loc1" and "loc2" can be relative or absolute paths or
1400-# URLs. If a location is present for each tag, the installdox tool
1401-# does not have to be run to correct the links.
1402-# Note that each tag file must have a unique name
1403-# (where the name does NOT include the path)
1404-# If a tag file is not located in the directory in which doxygen
1405-# is run, you must also specify the path to the tagfile here.
1406-
1407-TAGFILES =
1408-
1409-# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1410-# a tag file that is based on the input files it reads.
1411-
1412-GENERATE_TAGFILE =
1413-
1414-# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1415-# in the class index. If set to NO only the inherited external classes
1416-# will be listed.
1417-
1418-ALLEXTERNALS = NO
1419-
1420-# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1421-# in the modules index. If set to NO, only the current project's groups will
1422-# be listed.
1423-
1424-EXTERNAL_GROUPS = YES
1425-
1426-# The PERL_PATH should be the absolute path and name of the perl script
1427-# interpreter (i.e. the result of `which perl').
1428-
1429-PERL_PATH = /usr/bin/perl
1430-
1431-#---------------------------------------------------------------------------
1432-# Configuration options related to the dot tool
1433-#---------------------------------------------------------------------------
1434-
1435-# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1436-# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1437-# or super classes. Setting the tag to NO turns the diagrams off. Note that
1438-# this option is superseded by the HAVE_DOT option below. This is only a
1439-# fallback. It is recommended to install and use dot, since it yields more
1440-# powerful graphs.
1441-
1442-CLASS_DIAGRAMS = YES
1443-
1444-# You can define message sequence charts within doxygen comments using the \msc
1445-# command. Doxygen will then run the mscgen tool (see
1446-# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1447-# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1448-# the mscgen tool resides. If left empty the tool is assumed to be found in the
1449-# default search path.
1450-
1451-MSCGEN_PATH =
1452-
1453-# If set to YES, the inheritance and collaboration graphs will hide
1454-# inheritance and usage relations if the target is undocumented
1455-# or is not a class.
1456-
1457-HIDE_UNDOC_RELATIONS = YES
1458-
1459-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1460-# available from the path. This tool is part of Graphviz, a graph visualization
1461-# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1462-# have no effect if this option is set to NO (the default)
1463-
1464-HAVE_DOT = NO
1465-
1466-# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1467-# allowed to run in parallel. When set to 0 (the default) doxygen will
1468-# base this on the number of processors available in the system. You can set it
1469-# explicitly to a value larger than 0 to get control over the balance
1470-# between CPU load and processing speed.
1471-
1472-DOT_NUM_THREADS = 0
1473-
1474-# By default doxygen will write a font called FreeSans.ttf to the output
1475-# directory and reference it in all dot files that doxygen generates. This
1476-# font does not include all possible unicode characters however, so when you need
1477-# these (or just want a differently looking font) you can specify the font name
1478-# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1479-# which can be done by putting it in a standard location or by setting the
1480-# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1481-# containing the font.
1482-
1483-DOT_FONTNAME = FreeSans.ttf
1484-
1485-# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1486-# The default size is 10pt.
1487-
1488-DOT_FONTSIZE = 10
1489-
1490-# By default doxygen will tell dot to use the output directory to look for the
1491-# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1492-# different font using DOT_FONTNAME you can set the path where dot
1493-# can find it using this tag.
1494-
1495-DOT_FONTPATH =
1496-
1497-# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1498-# will generate a graph for each documented class showing the direct and
1499-# indirect inheritance relations. Setting this tag to YES will force the
1500-# the CLASS_DIAGRAMS tag to NO.
1501-
1502-CLASS_GRAPH = YES
1503-
1504-# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1505-# will generate a graph for each documented class showing the direct and
1506-# indirect implementation dependencies (inheritance, containment, and
1507-# class references variables) of the class with other documented classes.
1508-
1509-COLLABORATION_GRAPH = YES
1510-
1511-# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1512-# will generate a graph for groups, showing the direct groups dependencies
1513-
1514-GROUP_GRAPHS = YES
1515-
1516-# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1517-# collaboration diagrams in a style similar to the OMG's Unified Modeling
1518-# Language.
1519-
1520-UML_LOOK = NO
1521-
1522-# If set to YES, the inheritance and collaboration graphs will show the
1523-# relations between templates and their instances.
1524-
1525-TEMPLATE_RELATIONS = NO
1526-
1527-# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1528-# tags are set to YES then doxygen will generate a graph for each documented
1529-# file showing the direct and indirect include dependencies of the file with
1530-# other documented files.
1531-
1532-INCLUDE_GRAPH = YES
1533-
1534-# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1535-# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1536-# documented header file showing the documented files that directly or
1537-# indirectly include this file.
1538-
1539-INCLUDED_BY_GRAPH = YES
1540-
1541-# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1542-# doxygen will generate a call dependency graph for every global function
1543-# or class method. Note that enabling this option will significantly increase
1544-# the time of a run. So in most cases it will be better to enable call graphs
1545-# for selected functions only using the \callgraph command.
1546-
1547-CALL_GRAPH = NO
1548-
1549-# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1550-# doxygen will generate a caller dependency graph for every global function
1551-# or class method. Note that enabling this option will significantly increase
1552-# the time of a run. So in most cases it will be better to enable caller
1553-# graphs for selected functions only using the \callergraph command.
1554-
1555-CALLER_GRAPH = NO
1556-
1557-# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1558-# will generate a graphical hierarchy of all classes instead of a textual one.
1559-
1560-GRAPHICAL_HIERARCHY = YES
1561-
1562-# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1563-# then doxygen will show the dependencies a directory has on other directories
1564-# in a graphical way. The dependency relations are determined by the #include
1565-# relations between the files in the directories.
1566-
1567-DIRECTORY_GRAPH = YES
1568-
1569-# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1570-# generated by dot. Possible values are png, jpg, or gif.
1571-# If left blank png will be used.
1572-
1573-DOT_IMAGE_FORMAT = png
1574-
1575-# The tag DOT_PATH can be used to specify the path where the dot tool can be
1576-# found. If left blank, it is assumed the dot tool can be found in the path.
1577-
1578-DOT_PATH =
1579-
1580-# The DOTFILE_DIRS tag can be used to specify one or more directories that
1581-# contain dot files that are included in the documentation (see the
1582-# \dotfile command).
1583-
1584-DOTFILE_DIRS =
1585-
1586-# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1587-# nodes that will be shown in the graph. If the number of nodes in a graph
1588-# becomes larger than this value, doxygen will truncate the graph, which is
1589-# visualized by representing a node as a red box. Note that doxygen if the
1590-# number of direct children of the root node in a graph is already larger than
1591-# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1592-# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1593-
1594-DOT_GRAPH_MAX_NODES = 50
1595-
1596-# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1597-# graphs generated by dot. A depth value of 3 means that only nodes reachable
1598-# from the root by following a path via at most 3 edges will be shown. Nodes
1599-# that lay further from the root node will be omitted. Note that setting this
1600-# option to 1 or 2 may greatly reduce the computation time needed for large
1601-# code bases. Also note that the size of a graph can be further restricted by
1602-# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1603-
1604-MAX_DOT_GRAPH_DEPTH = 0
1605-
1606-# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1607-# background. This is disabled by default, because dot on Windows does not
1608-# seem to support this out of the box. Warning: Depending on the platform used,
1609-# enabling this option may lead to badly anti-aliased labels on the edges of
1610-# a graph (i.e. they become hard to read).
1611-
1612-DOT_TRANSPARENT = NO
1613-
1614-# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1615-# files in one run (i.e. multiple -o and -T options on the command line). This
1616-# makes dot run faster, but since only newer versions of dot (>1.8.10)
1617-# support this, this feature is disabled by default.
1618-
1619-DOT_MULTI_TARGETS = NO
1620-
1621-# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1622-# generate a legend page explaining the meaning of the various boxes and
1623-# arrows in the dot generated graphs.
1624-
1625-GENERATE_LEGEND = YES
1626-
1627-# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1628-# remove the intermediate dot files that are used to generate
1629-# the various graphs.
1630-
1631-DOT_CLEANUP = YES
diff -r 8d6d058ff897 -r d270659754af Makefile
--- a/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,23 +0,0 @@
1-# mhack
2-
3-HTML_DIR = generated_html
4-TARGET =
5-
6-all : $(TARGET)
7- $(MAKE) html
8- cd source/ && $(MAKE)
9- cd sample/ && $(MAKE)
10-
11-clean :
12- $(RM) $(TARGET) *.o
13- $(RM) -rf $(HTML_DIR)
14- cd source/ && $(MAKE) clean
15- cd sample/ && $(MAKE) clean
16-
17-html : $(HTML_DIR)/index.html
18-
19-.PHONY : all clean depend html
20-######################################################################
21-
22-$(HTML_DIR)/index.html : Doxyfile $(wildcard dox/* dox/img/* sample/walking_sample sample/light_sample)
23- doxygen
diff -r 8d6d058ff897 -r d270659754af dox/Makefile
--- a/dox/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,9 +0,0 @@
1-# dox/
2-
3-all :
4- cd ../ && $(MAKE)
5-
6-clean :
7- cd ../ && $(MAKE) clean
8-
9-.PHONY : all clean
diff -r 8d6d058ff897 -r d270659754af dox/application_scene.dox
--- a/dox/application_scene.dox Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,131 +0,0 @@
1-/*!
2- \page application_scene_page アプリケーションのシーン定義
3-
4- ゲーム中にメニュー画面を開くような処理を実現するために、アプリケーションはゲーム用、メニュー用など目的に応じたシーン処理モジュールを持ち、それらを切替えられるようにする。
5-
6-
7- \section application_scene_list シーンの一覧
8-
9- - \ref application_scene_first_menu
10- - \ref application_scene_menu
11- - \ref application_scene_game
12- - \ref application_scene_shop
13- - \ref application_scene_scenario
14- - \ref application_scene_quit
15-
16-
17- \subsection application_scene_first_menu 起動後のメニュー表示
18-
19- ゲーム起動後のメニュー画面。\n
20- 新規ゲームの開始、ロードするゲームの選択、オプション設定、などのシーンの選択を待つ。
21-
22- このメニュー画面の初期化において、サーバに問い合わせを行い、バージョンアップの処理を行っても良い。
23-
24-
25- \subsection application_scene_option オプション設定
26-
27- オプション設定を行う。\n
28- 任意のシーンからこのシーンに遷移するため、背景は透過させない方がよい。
29-
30- \subsection application_scene_menu ゲーム中のメニュー表示
31-
32- \ref application_scene_first_menu 以外の全てのシーンからこのシーンに遷移しうる。\n
33- 背景を半透明にして、ゲーム画面を表示してもよい。
34-
35-
36- \subsection application_scene_game ダンジョン表示
37-
38- ゲーム画面。
39-
40-
41- \subsection application_scene_shop ショップ表示
42-
43- ショップ毎に表示を変更してもよい。
44-
45-
46- \subsection application_scene_scenario シナリオ再生
47-
48- 立ち絵やメッセージの表示、動画の再生を行う。
49-
50-
51- \subsection application_menu ゲーム中のメニュー
52-
53- ゲーム中のメニュー項目を表示する。\n
54- このシーンの処理が終了すると、遷移元のシーンに遷移する。
55-
56-
57- \subsection application_scene_quit 終了しますかダイアログの表示
58-
59- Ctrl-q や ALT-F4 による遷移を行う。
60- 終了しなかった場合、遷移元のシーンに戻る。
61-
62-
63- \section application_scene_flow シーンの遷移
64-
65- \subsection application_scene_flow_main 主要なシーン遷移
66-
67- - quit は全てのシーンから遷移するため、シーン遷移図には記述しない。
68- - menu は first_menu 以外の全てのシーンから遷移するため、シーン遷移図には記述しない。
69- - quit, menu を中断すると、遷移元のシーンに戻る。
70- - 点線は、遷移元のシーンに戻ることを示す。
71-
72- \dot
73- digraph scene_flow {
74- node [fontname = "arialuni.ttf", fontsize = 10];
75- edge [fontname = "arialuni.ttf", fontsize = 10];
76-
77- start -> first_menu
78-
79- first_menu -> end
80- first_menu -> option
81- first_menu -> game
82-
83- option -> first_menu [style = "dotted"];
84-
85- game -> shop
86- game -> scenario
87- game -> first_menu [style = "dotted"];
88-
89- scenario -> game [style = "dotted"];
90-
91- shop -> game [style = "dotted"];
92-
93- first_menu [label = " 起動後のメニュー表示 "];
94- option [label = " オプション設定 "];
95- game [label = " ダンジョン表示 "];
96- shop [label = " ショップ表示 "];
97- scenario [label = " シナリオ再生 "];
98- }
99- \enddot
100-
101-
102- \subsection application_scene_flow_menu ゲーム中メニューのシーン遷移
103-
104- \dot
105- digraph menu_flow {
106- node [fontname = "arialuni.ttf", fontsize = 10];
107- edge [fontname = "arialuni.ttf", fontsize = 10];
108-
109- menu -> option
110- menu -> first_menu
111-
112- first_menu [label = " 起動後のメニュー表示 "];
113- option [label = " オプション設定 "];
114- menu [label = " ゲーム中のメニュー "];
115- }
116- \enddot
117-
118-
119- \subsection application_scene_flow_quit 終了しいますかダイアログのシーン遷移
120-
121- \dot
122- digraph quit_flow {
123- node [fontname = "arialuni.ttf", fontsize = 10];
124- edge [fontname = "arialuni.ttf", fontsize = 10];
125-
126- quit -> end
127-
128- quit [label = " 終了しますかダイアログの表示 "];
129- }
130- \enddot
131-*/
diff -r 8d6d058ff897 -r d270659754af dox/development.dox
--- a/dox/development.dox Mon Dec 20 07:25:07 2010 +0900
+++ b/dox/development.dox Fri Jul 15 07:48:55 2011 +0900
@@ -16,9 +16,6 @@
1616 - \ref layer_draw
1717 - \ref layer_input
1818
19-
20- \section development_detail 実装の詳細
21-
2219 - \subpage flow_page
2320 - \ref flow_abstract
2421
@@ -30,17 +27,21 @@
3027 - \subpage turn_handler_list
3128 - \subpage turn_handler_next
3229
33- - ダンジョンの実現
34- - ダンジョンのデータ表現
35- - キャラクターの移動
36- - アイテムの生成
30+ - \subpage game_data.dox ゲーム用データについて
31+ - !!!
32+
33+ - \subpage dungeon_page
34+ - \ref dungeon_struct
35+ - \ref dungeon_moving
36+ - \ref dungeon_item
3737
3838 - ダンジョンの生成
3939 - 固定マップ
4040 - 固定サイズの部屋 + 通路
4141 - 洞窟風
4242 \n \n
43- - アイテムの実装
43+ - \subpage item_page
44+ - !!!
4445 \n \n
4546 - キャラクターの実装
4647 - スキルの実装
@@ -48,5 +49,19 @@
4849 - 町の実装
4950 \n \n
5051 - ショップの実装
51- - !!!
52+
53+ - \subpage draw_page
54+ - \ref draw_map
55+ - \ref draw_character
56+ - \ref draw_action
57+
58+ - マルチプレイ対応
59+ - !!!
60+
61+
62+ \section development_detail 詳細
63+
64+ - \subpage modules_page
65+
66+ !!!
5267 */
diff -r 8d6d058ff897 -r d270659754af dox/doxygen_stylesheet.css
--- a/dox/doxygen_stylesheet.css Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,688 +0,0 @@
1-/* The standard CSS for doxygen */
2-
3-body, table, div, p, dl {
4- font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;
5- font-size: 12px;
6-}
7-
8-/* @group Heading Levels */
9-
10-h1 {
11- font-size: 140%;
12-}
13-
14-h2 {
15- font-size: 130%;
16- margin-top: 30px;
17-}
18-
19-h3 {
20- font-size: 120%;
21- margin-top: 28px;
22-}
23-
24-dt {
25- font-weight: bold;
26-}
27-
28-div.multicol {
29- -moz-column-gap: 1em;
30- -webkit-column-gap: 1em;
31- -moz-column-count: 3;
32- -webkit-column-count: 3;
33-}
34-
35-p.startli, p.startdd, p.starttd {
36- margin-top: 2px;
37-}
38-
39-p.endli {
40- margin-bottom: 0px;
41-}
42-
43-p.enddd {
44- margin-bottom: 4px;
45-}
46-
47-p.endtd {
48- margin-bottom: 2px;
49-}
50-
51-/* @end */
52-
53-caption {
54- font-weight: bold;
55-}
56-
57-span.legend {
58- font-size: 70%;
59- text-align: center;
60-}
61-
62-h3.version {
63- font-size: 90%;
64- text-align: center;
65-}
66-
67-div.qindex, div.navtab{
68- background-color: #EBEFF6;
69- border: 1px solid #A3B4D7;
70- text-align: center;
71- margin: 2px;
72- padding: 2px;
73-}
74-
75-div.qindex, div.navpath {
76- width: 100%;
77- line-height: 140%;
78-}
79-
80-div.navtab {
81- margin-right: 15px;
82-}
83-
84-/* @group Link Styling */
85-
86-a {
87- color: #3D578C;
88- font-weight: normal;
89- text-decoration: none;
90-}
91-
92-.contents a:visited {
93- color: #4665A2;
94-}
95-
96-a:hover {
97- text-decoration: underline;
98-}
99-
100-a.qindex {
101- font-weight: bold;
102-}
103-
104-a.qindexHL {
105- font-weight: bold;
106- background-color: #9CAFD4;
107- color: #ffffff;
108- border: 1px double #869DCA;
109-}
110-
111-.contents a.qindexHL:visited {
112- color: #ffffff;
113-}
114-
115-a.el {
116- font-weight: bold;
117-}
118-
119-a.elRef {
120-}
121-
122-a.code {
123- color: #4665A2;
124-}
125-
126-a.codeRef {
127- color: #4665A2;
128-}
129-
130-/* @end */
131-
132-dl.el {
133- margin-left: -1cm;
134-}
135-
136-.fragment {
137- font-family: monospace, fixed;
138- font-size: 105%;
139-}
140-
141-pre.fragment {
142- border: 1px solid #C4CFE5;
143- background-color: #FBFCFD;
144- padding: 4px 6px;
145- margin: 4px 8px 4px 2px;
146- overflow: auto;
147- word-wrap: break-word;
148- font-size: 9pt;
149- line-height: 125%;
150-}
151-
152-div.ah {
153- background-color: black;
154- font-weight: bold;
155- color: #ffffff;
156- margin-bottom: 3px;
157- margin-top: 3px;
158- padding: 0.2em;
159- border: solid thin #333;
160- border-radius: 0.5em;
161- -webkit-border-radius: .5em;
162- -moz-border-radius: .5em;
163- box-shadow: 2px 2px 3px #999;
164- -webkit-box-shadow: 2px 2px 3px #999;
165- -moz-box-shadow: rgba(0, 0, 0, 0.15) 2px 2px 2px;
166- background-image: -webkit-gradient(linear, left top, left bottom, from(#eee), to(#000),color-stop(0.3, #444));
167- background-image: -moz-linear-gradient(center top, #eee 0%, #444 40%, #000);
168-}
169-
170-div.groupHeader {
171- margin-left: 16px;
172- margin-top: 12px;
173- font-weight: bold;
174-}
175-
176-div.groupText {
177- margin-left: 16px;
178- font-style: italic;
179-}
180-
181-body {
182- background: white;
183- color: black;
184- margin: 0;
185-}
186-
187-div.contents {
188- margin-top: 10px;
189- margin-left: 10px;
190- margin-right: 10px;
191-}
192-
193-td.indexkey {
194- background-color: #EBEFF6;
195- font-weight: bold;
196- border: 1px solid #C4CFE5;
197- margin: 2px 0px 2px 0;
198- padding: 2px 10px;
199-}
200-
201-td.indexvalue {
202- background-color: #EBEFF6;
203- border: 1px solid #C4CFE5;
204- padding: 2px 10px;
205- margin: 2px 0px;
206-}
207-
208-tr.memlist {
209- background-color: #EEF1F7;
210-}
211-
212-p.formulaDsp {
213- text-align: center;
214-}
215-
216-img.formulaDsp {
217-
218-}
219-
220-img.formulaInl {
221- vertical-align: middle;
222-}
223-
224-div.center {
225- text-align: center;
226- margin-top: 0px;
227- margin-bottom: 0px;
228- padding: 0px;
229-}
230-
231-div.center img {
232- border: 0px;
233-}
234-
235-address.footer {
236- text-align: right;
237- padding-right: 12px;
238-}
239-
240-img.footer {
241- border: 0px;
242- vertical-align: middle;
243-}
244-
245-/* @group Code Colorization */
246-
247-span.keyword {
248- color: #008000
249-}
250-
251-span.keywordtype {
252- color: #604020
253-}
254-
255-span.keywordflow {
256- color: #e08000
257-}
258-
259-span.comment {
260- color: #800000
261-}
262-
263-span.preprocessor {
264- color: #806020
265-}
266-
267-span.stringliteral {
268- color: #002080
269-}
270-
271-span.charliteral {
272- color: #008080
273-}
274-
275-span.vhdldigit {
276- color: #ff00ff
277-}
278-
279-span.vhdlchar {
280- color: #000000
281-}
282-
283-span.vhdlkeyword {
284- color: #700070
285-}
286-
287-span.vhdllogic {
288- color: #ff0000
289-}
290-
291-/* @end */
292-
293-/*
294-.search {
295- color: #003399;
296- font-weight: bold;
297-}
298-
299-form.search {
300- margin-bottom: 0px;
301- margin-top: 0px;
302-}
303-
304-input.search {
305- font-size: 75%;
306- color: #000080;
307- font-weight: normal;
308- background-color: #e8eef2;
309-}
310-*/
311-
312-td.tiny {
313- font-size: 75%;
314-}
315-
316-.dirtab {
317- padding: 4px;
318- border-collapse: collapse;
319- border: 1px solid #A3B4D7;
320-}
321-
322-th.dirtab {
323- background: #EBEFF6;
324- font-weight: bold;
325-}
326-
327-hr {
328- height: 0px;
329- border: none;
330- border-top: 1px solid #4A6AAA;
331-}
332-
333-hr.footer {
334- height: 1px;
335-}
336-
337-/* @group Member Descriptions */
338-
339-table.memberdecls {
340- border-spacing: 0px;
341- padding: 0px;
342-}
343-
344-.mdescLeft, .mdescRight,
345-.memItemLeft, .memItemRight,
346-.memTemplItemLeft, .memTemplItemRight, .memTemplParams {
347- background-color: #F9FAFC;
348- border: none;
349- margin: 4px;
350- padding: 1px 0 0 8px;
351-}
352-
353-.mdescLeft, .mdescRight {
354- padding: 0px 8px 4px 8px;
355- color: #555;
356-}
357-
358-.memItemLeft, .memItemRight, .memTemplParams {
359- border-top: 1px solid #C4CFE5;
360-}
361-
362-.memItemLeft, .memTemplItemLeft {
363- white-space: nowrap;
364-}
365-
366-.memTemplParams {
367- color: #4665A2;
368- white-space: nowrap;
369-}
370-
371-/* @end */
372-
373-/* @group Member Details */
374-
375-/* Styles for detailed member documentation */
376-
377-.memtemplate {
378- font-size: 80%;
379- color: #4665A2;
380- font-weight: normal;
381- margin-left: 9px;
382-}
383-
384-.memnav {
385- background-color: #EBEFF6;
386- border: 1px solid #A3B4D7;
387- text-align: center;
388- margin: 2px;
389- margin-right: 15px;
390- padding: 2px;
391-}
392-
393-.memitem {
394- padding: 0;
395- margin-bottom: 10px;
396-}
397-
398-.memname {
399- white-space: nowrap;
400- font-weight: bold;
401- margin-left: 6px;
402-}
403-
404-.memproto {
405- border-top: 1px solid #A8B8D9;
406- border-left: 1px solid #A8B8D9;
407- border-right: 1px solid #A8B8D9;
408- padding: 6px 0px 6px 0px;
409- color: #253555;
410- font-weight: bold;
411- text-shadow: 0px 1px 1px rgba(255, 255, 255, 0.9);
412- /* opera specific markup */
413- box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
414- border-top-right-radius: 8px;
415- border-top-left-radius: 8px;
416- /* firefox specific markup */
417- -moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
418- -moz-border-radius-topright: 8px;
419- -moz-border-radius-topleft: 8px;
420- /* webkit specific markup */
421- -webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
422- -webkit-border-top-right-radius: 8px;
423- -webkit-border-top-left-radius: 8px;
424- background-image:url('nav_f.png');
425- background-repeat:repeat-x;
426- background-color: #E2E8F2;
427-
428-}
429-
430-.memdoc {
431- border-bottom: 1px solid #A8B8D9;
432- border-left: 1px solid #A8B8D9;
433- border-right: 1px solid #A8B8D9;
434- padding: 2px 5px;
435- background-color: #FBFCFD;
436- border-top-width: 0;
437- /* opera specific markup */
438- border-bottom-left-radius: 8px;
439- border-bottom-right-radius: 8px;
440- box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
441- /* firefox specific markup */
442- -moz-border-radius-bottomleft: 8px;
443- -moz-border-radius-bottomright: 8px;
444- -moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
445- background-image: -moz-linear-gradient(center top, #FFFFFF 0%, #FFFFFF 60%, #F7F8FB 95%, #EEF1F7);
446- /* webkit specific markup */
447- -webkit-border-bottom-left-radius: 8px;
448- -webkit-border-bottom-right-radius: 8px;
449- -webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
450- background-image: -webkit-gradient(linear,center top,center bottom,from(#FFFFFF), color-stop(0.6,#FFFFFF), color-stop(0.60,#FFFFFF), color-stop(0.95,#F7F8FB), to(#EEF1F7));
451-}
452-
453-.paramkey {
454- text-align: right;
455-}
456-
457-.paramtype {
458- white-space: nowrap;
459-}
460-
461-.paramname {
462- color: #602020;
463- white-space: nowrap;
464-}
465-.paramname em {
466- font-style: normal;
467-}
468-
469-.params, .retval, .exception, .tparams {
470- border-spacing: 6px 2px;
471-}
472-
473-.params .paramname, .retval .paramname {
474- font-weight: bold;
475- vertical-align: top;
476-}
477-
478-.params .paramtype {
479- font-style: italic;
480- vertical-align: top;
481-}
482-
483-.params .paramdir {
484- font-family: "courier new",courier,monospace;
485- vertical-align: top;
486-}
487-
488-
489-
490-
491-/* @end */
492-
493-/* @group Directory (tree) */
494-
495-/* for the tree view */
496-
497-.ftvtree {
498- font-family: sans-serif;
499- margin: 0px;
500-}
501-
502-/* these are for tree view when used as main index */
503-
504-.directory {
505- font-size: 9pt;
506- font-weight: bold;
507- margin: 5px;
508-}
509-
510-.directory h3 {
511- margin: 0px;
512- margin-top: 1em;
513- font-size: 11pt;
514-}
515-
516-/*
517-The following two styles can be used to replace the root node title
518-with an image of your choice. Simply uncomment the next two styles,
519-specify the name of your image and be sure to set 'height' to the
520-proper pixel height of your image.
521-*/
522-
523-/*
524-.directory h3.swap {
525- height: 61px;
526- background-repeat: no-repeat;
527- background-image: url("yourimage.gif");
528-}
529-.directory h3.swap span {
530- display: none;
531-}
532-*/
533-
534-.directory > h3 {
535- margin-top: 0;
536-}
537-
538-.directory p {
539- margin: 0px;
540- white-space: nowrap;
541-}
542-
543-.directory div {
544- display: none;
545- margin: 0px;
546-}
547-
548-.directory img {
549- vertical-align: -30%;
550-}
551-
552-/* these are for tree view when not used as main index */
553-
554-.directory-alt {
555- font-size: 100%;
556- font-weight: bold;
557-}
558-
559-.directory-alt h3 {
560- margin: 0px;
561- margin-top: 1em;
562- font-size: 11pt;
563-}
564-
565-.directory-alt > h3 {
566- margin-top: 0;
567-}
568-
569-.directory-alt p {
570- margin: 0px;
571- white-space: nowrap;
572-}
573-
574-.directory-alt div {
575- display: none;
576- margin: 0px;
577-}
578-
579-.directory-alt img {
580- vertical-align: -30%;
581-}
582-
583-/* @end */
584-
585-div.dynheader {
586- margin-top: 8px;
587-}
588-
589-address {
590- font-style: normal;
591- color: #2A3D61;
592-}
593-
594-table.doxtable {
595- border-collapse:collapse;
596-}
597-
598-table.doxtable td, table.doxtable th {
599- border: 1px solid #2D4068;
600- padding: 3px 7px 2px;
601-}
602-
603-table.doxtable th {
604- background-color: #374F7F;
605- color: #FFFFFF;
606- font-size: 110%;
607- padding-bottom: 4px;
608- padding-top: 5px;
609- text-align:left;
610-}
611-
612-.tabsearch {
613- top: 0px;
614- left: 10px;
615- height: 36px;
616- background-image: url('tab_b.png');
617- z-index: 101;
618- overflow: hidden;
619- font-size: 13px;
620-}
621-
622-.navpath ul
623-{
624- font-size: 11px;
625- background-image:url('tab_b.png');
626- background-repeat:repeat-x;
627- height:30px;
628- line-height:30px;
629- color:#8AA0CC;
630- border:solid 1px #C2CDE4;
631- overflow:hidden;
632- margin:0px;
633- padding:0px;
634-}
635-
636-.navpath li
637-{
638- list-style-type:none;
639- float:left;
640- padding-left:10px;
641- padding-right: 15px;
642- background-image:url('bc_s.png');
643- background-repeat:no-repeat;
644- background-position:right;
645- color:#364D7C;
646-}
647-
648-.navpath a
649-{
650- height:32px;
651- display:block;
652- text-decoration: none;
653- outline: none;
654-}
655-
656-.navpath a:hover
657-{
658- color:#6884BD;
659-}
660-
661-div.summary
662-{
663- float: right;
664- font-size: 8pt;
665- padding-right: 5px;
666- width: 50%;
667- text-align: right;
668-}
669-
670-div.summary a
671-{
672- white-space: nowrap;
673-}
674-
675-div.header
676-{
677- background-image:url('nav_h.png');
678- background-repeat:repeat-x;
679- background-color: #F9FAFC;
680- margin: 0px;
681- border-bottom: 1px solid #C4CFE5;
682-}
683-
684-div.headertitle
685-{
686- padding: 5px 5px 5px 10px;
687-}
688-
diff -r 8d6d058ff897 -r d270659754af dox/draw.dox
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/dox/draw.dox Fri Jul 15 07:48:55 2011 +0900
@@ -0,0 +1,23 @@
1+/*!
2+ \page draw_page 画面への表示
3+
4+ 描画は、3次元座標系に対して行う。
5+
6+
7+ \section draw_map マップの表示
8+
9+ 地面、および地形に対してそれとわかるように描画を行う。
10+ 移動できる領域と移動できない領域、および特殊効果のある場所は区別しやすくすること。\n
11+ テクスチャーを貼りつけてもよい。
12+
13+
14+ \section draw_character キャラクターの表示
15+
16+ 向きがわかるように表示する。\n
17+ 地形と区別するために、常にアニメーションさせてもよい。
18+
19+
20+ \section draw_action 攻撃アクションの表示
21+
22+ 実時間で適切にアニメーションされるように描画する。
23+*/
diff -r 8d6d058ff897 -r d270659754af dox/dungeon.dox
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/dox/dungeon.dox Fri Jul 15 07:48:55 2011 +0900
@@ -0,0 +1,46 @@
1+/*!
2+ \page dungeon_page ダンジョンの実現
3+
4+ \section dungeon_struct ダンジョンのデータ表現
5+
6+ ダンジョンは、正方グリッドで表現する。\n
7+ 高さの概念は導入しない。
8+
9+
10+ \subsection dungeon_struct_wall 壁
11+
12+ - 壁は正方グリッドに沿って配置する。
13+ - 通常は移動できないようにする。
14+ - 掘削できるようにするために、壁に体力の概念を持たせる。
15+ - 攻撃の種類によって掘削しやすさを変えるために、攻撃の種類に応じた耐久力を持つ。
16+ - 掘削専用の属性を持たせても良い。
17+ - 属性への耐久力を定義し、掘削が自然な行為になるように調整する。
18+ - 全ての属性への耐久力を "immune" にすると、掘削できないようにする。
19+ - 掘削して壁を破壊したときに、中にアイテムがあれば取得できるようにする。
20+ - 壁の掘削が完了したときに "石" などのアイテムを出現させてもよい。
21+ - 壁の地面に対して "宝石" を保持させてもよい。
22+
23+ - 壁の表示方法は、表示させるプラットフォームに依存させる。
24+
25+
26+ \subsection dungeon_struct_items アイテム
27+
28+ - アイテムは散らばり具合を表現するために、正方グリッドより細かい単位で配置位置を定義してもよい。
29+ - 複数のアイテムが同じ位置に配置されてもよい。
30+ - アイテムのある正方グリッド上に壁がある場合、その壁が破壊されなければ、アイテムを拾うことができないようにする。
31+ - 正方グリッドに関係なく、近くにあるアイテムは拾えるようにする。
32+ - 拾う候補に表示されるようにする。
33+
34+
35+ \section dungeon_moving キャラクターの移動
36+
37+ - キャラクターの位置は、正方グリッドに沿って配置される。
38+ - アニメーション時には、グリッド間を滑らかに移動してもよい。
39+
40+
41+ \section dungeon_item アイテムの生成
42+
43+ - キャラクター生成時に、アイテムも生成される。
44+ - キャラクターが死亡したときに、保持しているアイテムのいくつかが地面に落ちる。
45+ - ダンジョン生成時に、いくつかのアイテムも生成される。
46+*/
diff -r 8d6d058ff897 -r d270659754af dox/flow.dox
--- a/dox/flow.dox Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,19 +0,0 @@
1-/*!
2- \page flow_page ソフトウェアのフロー
3-
4- \section flow_abstract 基本フロー
5-
6- \dot
7- digraph flow_basic {
8- node [fontname = "arialuni.ttf", fontsize = 10];
9- edge [fontname = "arialuni.ttf", fontsize = 10];
10-
11- input -> end
12- start -> input -> action -> draw -> input
13-
14- input [label = " 入力 "];
15- action [label = " 行動 "];
16- draw [label = "表示" ];
17- }
18- \enddot
19-*/
diff -r 8d6d058ff897 -r d270659754af dox/game_data.dox
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/dox/game_data.dox Fri Jul 15 07:48:55 2011 +0900
@@ -0,0 +1,22 @@
1+/*!
2+ \page game_data.dox ゲーム用データについて (!!! 記述中)
3+
4+ マルチプレイヤー風味は、全プレイヤーが共通に使うデータを用意することで実現する。
5+
6+ - 全キャラクターで共通に管理するデータの例
7+ - 酒場に配置したキャラクターを、他のキャラクターのパーティに加えられるようにする、など。
8+ - 掲示板へのコメントなど。
9+
10+
11+ !!! データは DB に保存する。
12+
13+ !!! DB がローカル PC か、遠隔サーバかどうかで
14+
15+ !!! データの管理方法について
16+
17+ !!! サーバにデータを貯めるのか、など
18+
19+ !!!
20+
21+ !!!
22+*/
diff -r 8d6d058ff897 -r d270659754af dox/idea.dox
--- a/dox/idea.dox Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,63 +0,0 @@
1-/*!
2- \page idea_page 実現したいこと
3-
4- - \ref idea_items_singleplay
5- - \ref idea_items_scripts
6- - \ref idea_items_log
7- - \ref idea_items_party
8- - \ref idea_items_ai
9- - \ref idea_items_graphic
10- - \ref idea_items_input
11-
12-
13- \section idea_items_singleplay シングルプレイ・ローグライク
14-
15- このローグライクでは、次の行動を何にするかの決定を楽しむゲームを目指す。次の行動を決定する時間に制限を設けたくないため、リアルタイム性は導入しない。
16-
17- また、プレイヤー各自のペースで操作できることを保証するために、マルチプレイヤー対応にはしない。ただし、チャットやオークションなど、ゲームプレイに直接関係しないシーンにおいて、複数プレイヤーによるデータ共有を可能にしてもよい。
18-
19-
20- \section idea_items_scripts 拡張しやすい設定ファイル構成
21-
22- 拡張性を保証するために、アイテム、キャラクター特性、シナリオの記述はテキストファイルで行う。ただし、特性が記述されたテキストファイルは、配布時に難読化できるようにする。また、テキストで記述した内容における整合性やスペルミスなどのチェックは、専用ツールで検証できるようにする。
23-
24- 記述については、専用のフォーマットや Light Language 言語の採用を検討している。
25-
26-
27- \section idea_items_log プレイの記録と中継
28-
29- ユーザのプレイ状況は、再生できるフォーマットで記録する。\n
30- このプレイ状況は、プレイヤー自身や、他のプレイヤーも設定によって閲覧できるようにする。
31-
32- プレイ状況の見どころを再生前に確認するために、体力の値や所持金の値などをグラフで表示する機能を実装してもよい。
33-
34-
35- \section idea_items_party パーティプレイ
36-
37- Nethack のペットや Diabllo II の傭兵, Elona の仲間に相当するキャラクターを導入する。これにより、ゲームプレイのバリエーションが増えることを目指す。\n
38- 疑似的なマルチプレイ実現の一環として、他プレイヤーのキャラクターをレンタルできるようにしてもよい。
39-
40-
41- \section idea_items_ai キャラクターの AI 操作
42-
43- 自分の操作するキャラクター以外の行動は、専用のスクリプトにしたがって行動させる。このスクリプトでは可能なかぎり多くの情報を取得できるようにする。\n
44- また、自分の操作するキャラクターを、作成したスクリプトにしたがって行動するようにできるようにしてもよい。
45-
46- 最速クリアや低レベルクリアなど、項目毎のスクリプトについてランキング処理ができるような仕組みを実現してもよい。
47-
48-
49- \section idea_items_graphic グラフィカルを考慮したローグライク
50-
51- 既存のローグライクユーザの獲得、および新規ユーザの取り込みを目指し、CUI 形式ではなく、グラフィックでの表示を基本とする。
52-
53- 最終的には Diabllo II の画面内のキャラクターやアイテムが 3D ASCII 文字で表現されているようなものを目指す。3D ASCII 文字による表現は、データを変更することで異なるグラフィックに変更できるようにする。
54-
55-
56- \section idea_items_input 入力の扱いについて
57-
58- キー入力、およびタッチパネルでの操作が可能になるようにする。\n
59-
60- キー入力においては、遠隔攻撃のターゲットをキーを押下することでトグル選択できるようにしたり、処理できるキーの候補を表示したりしてもよい。
61-
62- タッチパネルでの操作については、最もよく使う行動のアイコンを押し易い位置に配置するなどの工夫を行う。現時点では、どのような入力方法がタッチパネルに適しているかはあまり理解できていない。
63-*/
diff -r 8d6d058ff897 -r d270659754af dox/img/Makefile
--- a/dox/img/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,5 +0,0 @@
1-# dox/img
2-
3-all :
4-
5-clean :
diff -r 8d6d058ff897 -r d270659754af dox/item.dox
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/dox/item.dox Fri Jul 15 07:48:55 2011 +0900
@@ -0,0 +1,12 @@
1+/*!
2+ \page item_page アイテムの実装 (!!! 記述中)
3+
4+ !!!
5+
6+ - "使う" コマンドで効果が発生するようにする。
7+ - アイテムによっては、誰に(or 何に)アイテムを使うのか選択できるようにする。
8+ - アイテムによっては "投げる" で効果が発動するようにする。
9+ - !!!
10+
11+ !!!
12+*/
diff -r 8d6d058ff897 -r d270659754af dox/layer.dox
--- a/dox/layer.dox Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,24 +0,0 @@
1-/*!
2- \page layer_page ソフトウェアのレイヤー
3-
4- マルチプラットフォームや入出力デバイスに対する処理を抽象化することを目指し、ソフトウェアを複数のレイヤーに分け、操作 API を定義する。
5-
6- - \ref layer_draw
7- - \ref layer_input
8-
9-
10- \section layer_draw 表示レイヤー
11-
12- PC や Mobile phone, 様々の OS で動作させることができるように、画面に表示するデータを登録するためのレイヤーを用意して表示まわりを抽象化する。\n
13- このレイヤーでは、キャラクターやアイテムの位置を渡すと、動作しているプラットフォームに適した表示が行われるようにする。
14-
15- - 表示レイヤーの実装例
16- - Curses 用の実装
17- - SDL + OpenGL 用の実装
18-
19-
20- \section layer_input 行動の入力レイヤー
21-
22- キー入力やタッチパッドによる入力を抽象化する。\n
23- ここのレイヤーでは、移動や攻撃などの行動を決定するまでの入力を抽象化し、行動の処理モジュールに決定された操作を渡す。
24-*/
diff -r 8d6d058ff897 -r d270659754af dox/mainpage.dox
--- a/dox/mainpage.dox Mon Dec 20 07:25:07 2010 +0900
+++ b/dox/mainpage.dox Fri Jul 15 07:48:55 2011 +0900
@@ -1,5 +1,5 @@
11 /*!
2- \mainpage マルチプレイ風ローグライク
2+ \mainpage マルチプレイヤー風ローグライク
33
44 複数プレイヤーとのデータ共有が可能なシングルプレイ・ローグライクです。 \n
55 妄想をたくさんつめこんでいく予定です。
diff -r 8d6d058ff897 -r d270659754af dox/modules.dox
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/dox/modules.dox Fri Jul 15 07:48:55 2011 +0900
@@ -0,0 +1,10 @@
1+/*!
2+ \page modules_page ソフトウェアのモジュール構成 (!!! 記述中)
3+
4+ プログラムの実装言語は C++, Lua とする。\n
5+ 描画まわりは OpenGL + SDL にて実現する。
6+
7+ !!! モジュール構成の書き出し
8+
9+ !!!
10+*/
diff -r 8d6d058ff897 -r d270659754af dox/turn_handler.dox
--- a/dox/turn_handler.dox Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,31 +0,0 @@
1-/*!
2- \page turn_handler_page 行動のターン・ハンドラ
3-
4- \section turn_handler_list 行動のリスト管理
5-
6- 全てのキャラクターの行動、アイテムの発動、イベント用の処理ハンドラは、リストに登録された順番に処理される。
7-
8- \dot
9- digraph event_basic {
10- node [fontname = "arialuni.ttf", fontsize = 10];
11- edge [fontname = "arialuni.ttf", fontsize = 10];
12-
13- list_first -> character_move -> enemy_attack
14-
15- list_first [label = " リストの先頭 "];
16- enemy_attack [label = " 敵キャラの攻撃 "];
17- character_move [label = " 自キャラの移動 "];
18-
19- { rank = same; list_first character_move enemy_attack }
20- }
21- \enddot
22-
23-
24- \section turn_handler_next 次のイベントの配置
25-
26- 画面への表示の関係上、行動が複数に渡ることがある。\n
27- 行動が3つにわかれる場合、行動1の処理時に行動2の配置を行う、という風に順番に行動を配置する。\n
28- この方法により、発動までの時間が長い詠唱などを表現できる。
29-
30- 攻撃を受けたときに、次の行動がキャンセされて被ダメージ処理が挿入されるかは、処理中の行動の設定に依存する。
31-*/
diff -r 8d6d058ff897 -r d270659754af resource/IPA_Font_License_Agreement_v1.0.txt
--- a/resource/IPA_Font_License_Agreement_v1.0.txt Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,117 +0,0 @@
1---------------------------------------------------
2-IPA Font License Agreement v1.0 <Japanese/English>
3---------------------------------------------------
4-
5-IPAフォントライセンスv1.0
6-
7-許諾者は、この使用許諾(以下「本契約」といいます。)に定める条件の下で、許諾プログラム(1条に定義するところによります。)を提供します。受領者(1条に定義するところによります。)が、許諾プログラムを使用し、複製し、または頒布する行為、その他、本契約に定める権利の利用を行った場合、受領者は本契約に同意したものと見なします。
8-
9-
10-第1条 用語の定義
11-
12-本契約において、次の各号に掲げる用語は、当該各号に定めるところによります。
13-
14-1.「デジタル・フォント・プログラム」とは、フォントを含み、レンダリングしまたは表示するために用いられるコンピュータ・プログラムをいいます。
15-2.「許諾プログラム」とは、許諾者が本契約の下で許諾するデジタル・フォント・プログラムをいいます。
16-3.「派生プログラム」とは、許諾プログラムの一部または全部を、改変し、加除修正等し、入れ替え、その他翻案したデジタル・フォント・プログラムをいい、許諾プログラムの一部もしくは全部から文字情報を取り出し、またはデジタル・ドキュメント・ファイルからエンベッドされたフォントを取り出し、取り出された文字情報をそのまま、または改変をなして新たなデジタル・フォント・プログラムとして製作されたものを含みます。
17-4.「デジタル・コンテンツ」とは、デジタル・データ形式によってエンド・ユーザに提供される制作物のことをいい、動画・静止画等の映像コンテンツおよびテレビ番組等の放送コンテンツ、ならびに文字テキスト、画像、図形等を含んで構成された制作物を含みます。
18-5.「デジタル・ドキュメント・ファイル」とは、PDFファイルその他、各種ソフトウェア・プログラムによって製作されたデジタル・コンテンツであって、その中にフォントを表示するために許諾プログラムの全部または一部が埋め込まれた(エンベッドされた)ものをいいます。フォントが「エンベッドされた」とは、当該フォントが埋め込まれた特定の「デジタル・ドキュメント・ファイル」においてのみ表示されるために使用されている状態を指し、その特定の「デジタル・ドキュメント・ファイル」以外でフォントを表示するために使用できるデジタル・フォント・プログラムに含まれている場合と区別されます。
19-6.「コンピュータ」とは、本契約においては、サーバを含みます。
20-7.「複製その他の利用」とは、複製、譲渡、頒布、貸与、公衆送信、上映、展示、翻案その他の利用をいいます。
21-8.「受領者」とは、許諾プログラムを本契約の下で受領した人をいい、受領者から許諾プログラムを受領した人を含みます。
22-
23-第2条 使用許諾の付与
24-
25-許諾者は受領者に対し、本契約の条項に従い、すべての国で、許諾プログラムを使用することを許諾します。ただし、許諾プログラムに存在する一切の権利はすべて許諾者が保有しています。本契約は、本契約で明示的に定められている場合を除き、いかなる意味においても、許諾者が保有する許諾プログラムに関する一切の権利および、いかなる商標、商号、もしくはサービス・マークに関する権利をも受領者に移転するものではありません。
26-
27-1.受領者は本契約に定める条件に従い、許諾プログラムを任意の数のコンピュータにインストールし、当該コンピュータで使用することができます。
28-2.受領者はコンピュータにインストールされた許諾プログラムをそのまま、または改変を行ったうえで、印刷物およびデジタル・コンテンツにおいて、文字テキスト表現等として使用することができます。
29-3.受領者は前項の定めに従い作成した印刷物およびデジタル・コンテンツにつき、その商用・非商用の別、および放送、通信、各種記録メディアなどの媒体の形式を問わず、複製その他の利用をすることができます。
30-4.受領者がデジタル・ドキュメント・ファイルからエンベッドされたフォントを取り出して派生プログラムを作成した場合には、かかる派生プログラムは本契約に定める条件に従う必要があります。
31-5.許諾プログラムのエンベッドされたフォントがデジタル・ドキュメント・ファイル内のデジタル・コンテンツをレンダリングするためにのみ使用される場合において、受領者が当該デジタル・ドキュメント・ファイルを複製その他の利用をする場合には、受領者はかかる行為に関しては本契約の下ではいかなる義務をも負いません。
32-6.受領者は、3条2項の定めに従い、商用・非商用を問わず、許諾プログラムをそのままの状態で改変することなく複製して第三者への譲渡し、公衆送信し、その他の方法で再配布することができます(以下、「再配布」といいます。)。
33-7.受領者は、上記の許諾プログラムについて定められた条件と同様の条件に従って、派生プログラムを作成し、使用し、複製し、再配布することができます。ただし、受領者が派生プログラムを再配布する場合には、3条1項の定めに従うものとします。
34-
35-第3条 制限
36-
37-前条により付与された使用許諾は、以下の制限に服します。
38-
39-1.派生プログラムが前条4項及び7項に基づき再配布される場合には、以下の全ての条件を満たさなければなりません。
40- (1)派生プログラムを再配布する際には、下記もまた、当該派生プログラムと一緒に再配布され、オンラインで提供され、または、郵送費・媒体及び取扱手数料の合計を超えない実費と引き換えに媒体を郵送する方法により提供されなければなりません。
41-  (a)派生プログラムの写し; および
42-  (b)派生プログラムを作成する過程でフォント開発プログラムによって作成された追加のファイルであって派生プログラムをさらに加工するにあたって利用できるファイルが存在すれば、当該ファイル
43- (2)派生プログラムの受領者が、派生プログラムを、このライセンスの下で最初にリリースされた許諾プログラム(以下、「オリジナル・プログラム」といいます。)に置き換えることができる方法を再配布するものとします。かかる方法は、オリジナル・ファイルからの差分ファイルの提供、または、派生プログラムをオリジナル・プログラムに置き換える方法を示す指示の提供などが考えられます。
44- (3)派生プログラムを、本契約書に定められた条件の下でライセンスしなければなりません。
45- (4)派生プログラムのプログラム名、フォント名またはファイル名として、許諾プログラムが用いているのと同一の名称、またはこれを含む名称を使用してはなりません。
46- (5)本項の要件を満たすためにオンラインで提供し、または媒体を郵送する方法で提供されるものは、その提供を希望するいかなる者によっても提供が可能です。
47-2.受領者が前条6項に基づき許諾プログラムを再配布する場合には、以下の全ての条件を満たさなければなりません。
48- (1)許諾プログラムの名称を変更してはなりません。
49- (2)許諾プログラムに加工その他の改変を加えてはなりません。
50- (3)本契約の写しを許諾プログラムに添付しなければなりません。
51-3.許諾プログラムは、現状有姿で提供されており、許諾プログラムまたは派生プログラムについて、許諾者は一切の明示または黙示の保証(権利の所在、非侵害、商品性、特定目的への適合性を含むがこれに限られません)を行いません。いかなる場合にも、その原因を問わず、契約上の責任か厳格責任か過失その他の不法行為責任かにかかわらず、また事前に通知されたか否かにかかわらず、許諾者は、許諾プログラムまたは派生プログラムのインストール、使用、複製その他の利用または本契約上の権利の行使によって生じた一切の損害(直接・間接・付随的・特別・拡大・懲罰的または結果的損害)(商品またはサービスの代替品の調達、システム障害から生じた損害、現存するデータまたはプログラムの紛失または破損、逸失利益を含むがこれに限られません)について責任を負いません。
52-4.許諾プログラムまたは派生プログラムのインストール、使用、複製その他の利用に関して、許諾者は技術的な質問や問い合わせ等に対する対応その他、いかなるユーザ・サポートをも行う義務を負いません。
53-
54-第4条 契約の終了
55-
56-1.本契約の有効期間は、受領者が許諾プログラムを受領した時に開始し、受領者が許諾プログラムを何らかの方法で保持する限り続くものとします。
57-2.前項の定めにかかわらず、受領者が本契約に定める各条項に違反したときは、本契約は、何らの催告を要することなく、自動的に終了し、当該受領者はそれ以後、許諾プログラムおよび派生プログラムを一切使用しまたは複製その他の利用をすることができないものとします。ただし、かかる契約の終了は、当該違反した受領者から許諾プログラムまたは派生プログラムの配布を受けた受領者の権利に影響を及ぼすものではありません。
58-
59-第5条 準拠法
60-
61-1.IPAは、本契約の変更バージョンまたは新しいバージョンを公表することができます。その場合には、受領者は、許諾プログラムまたは派生プログラムの使用、複製その他の利用または再配布にあたり、本契約または変更後の契約のいずれかを選択することができます。その他、上記に記載されていない条項に関しては日本の著作権法および関連法規に従うものとします。
62-2.本契約は、日本法に基づき解釈されます。
63-
64-
65-----------
66-
67-IPA Font License Agreement v1.0
68-
69-The Licensor provides the Licensed Program (as defined in Article 1 below) under the terms of this license agreement (“Agreement”). Any use, reproduction or distribution of the Licensed Program, or any exercise of rights under this Agreement by a Recipient (as defined in Article 1 below) constitutes the Recipient's acceptance of this Agreement.
70-
71-Article 1 (Definitions)
72-1.“Digital Font Program” shall mean a computer program containing, or used to render or display fonts.
73-2.“Licensed Program” shall mean a Digital Font Program licensed by the Licensor under this Agreement.
74-3.“Derived Program” shall mean a Digital Font Program created as a result of a modification, addition, deletion, replacement or any other adaptation to or of a part or all of the Licensed Program, and includes a case where a Digital Font Program newly created by retrieving font information from a part or all of the Licensed Program or Embedded Fonts from a Digital Document File with or without modification of the retrieved font information.
75-4.“Digital Content” shall mean products provided to end users in the form of digital data, including video content, motion and/or still pictures, TV programs or other broadcasting content and products consisting of character text, pictures, photographic images, graphic symbols and/or the like.
76-5.“Digital Document File” shall mean a PDF file or other Digital Content created by various software programs in which a part or all of the Licensed Program becomes embedded or contained in the file for the display of the font (“Embedded Fonts”). Embedded Fonts are used only in the display of characters in the particular Digital Document File within which they are embedded, and shall be distinguished from those in any Digital Font Program, which may be used for display of characters outside that particular Digital Document File.
77-6.“Computer” shall include a server in this Agreement.
78-7.“Reproduction and Other Exploitation” shall mean reproduction, transfer, distribution, lease, public transmission, presentation, exhibition, adaptation and any other exploitation.
79-8.“Recipient” shall mean anyone who receives the Licensed Program under this Agreement, including one that receives the Licensed Program from a Recipient.
80-
81-Article 2 (Grant of License)
82-The Licensor grants to the Recipient a license to use the Licensed Program in any and all countries in accordance with each of the provisions set forth in this Agreement. However, any and all rights underlying in the Licensed Program shall be held by the Licensor. In no sense is this Agreement intended to transfer any right relating to the Licensed Program held by the Licensor except as specifically set forth herein or any right relating to any trademark, trade name, or service mark to the Recipient.
83-
84-1.The Recipient may install the Licensed Program on any number of Computers and use the same in accordance with the provisions set forth in this Agreement.
85-2.The Recipient may use the Licensed Program, with or without modification in printed materials or in Digital Content as an expression of character texts or the like.
86-3.The Recipient may conduct Reproduction and Other Exploitation of the printed materials and Digital Content created in accordance with the preceding Paragraph, for commercial or non-commercial purposes and in any form of media including but not limited to broadcasting, communication and various recording media.
87-4.If any Recipient extracts Embedded Fonts from a Digital Document File to create a Derived Program, such Derived Program shall be subject to the terms of this agreement.
88-5.If any Recipient performs Reproduction or Other Exploitation of a Digital Document File in which Embedded Fonts of the Licensed Program are used only for rendering the Digital Content within such Digital Document File then such Recipient shall have no further obligations under this Agreement in relation to such actions.
89-6.The Recipient may reproduce the Licensed Program as is without modification and transfer such copies, publicly transmit or otherwise redistribute the Licensed Program to a third party for commercial or non-commercial purposes (“Redistribute”), in accordance with the provisions set forth in Article 3 Paragraph 2.
90-7.The Recipient may create, use, reproduce and/or Redistribute a Derived Program under the terms stated above for the Licensed Program: provided, that the Recipient shall follow the provisions set forth in Article 3 Paragraph 1 when Redistributing the Derived Program.
91-
92-Article 3 (Restriction)
93-The license granted in the preceding Article shall be subject to the following restrictions:
94-
95-1.If a Derived Program is Redistributed pursuant to Paragraph 4 and 7 of the preceding Article, the following conditions must be met :
96- (1)The following must be also Redistributed together with the Derived Program, or be made available online or by means of mailing mechanisms in exchange for a cost which does not exceed the total costs of postage, storage medium and handling fees:
97-  (a)a copy of the Derived Program; and
98-  (b)any additional file created by the font developing program in the course of creating the Derived Program that can be used for further modification of the Derived Program, if any.
99- (2)It is required to also Redistribute means to enable recipients of the Derived Program to replace the Derived Program with the Licensed Program first released under this License (the “Original Program”). Such means may be to provide a difference file from the Original Program, or instructions setting out a method to replace the Derived Program with the Original Program.
100- (3)The Recipient must license the Derived Program under the terms and conditions of this Agreement.
101- (4)No one may use or include the name of the Licensed Program as a program name, font name or file name of the Derived Program.
102- (5)Any material to be made available online or by means of mailing a medium to satisfy the requirements of this paragraph may be provided, verbatim, by any party wishing to do so.
103-2.If the Recipient Redistributes the Licensed Program pursuant to Paragraph 6 of the preceding Article, the Recipient shall meet all of the following conditions:
104- (1)The Recipient may not change the name of the Licensed Program.
105- (2)The Recipient may not alter or otherwise modify the Licensed Program.
106- (3)The Recipient must attach a copy of this Agreement to the Licensed Program.
107-3.THIS LICENSED PROGRAM IS PROVIDED BY THE LICENSOR “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTY AS TO THE LICENSED PROGRAM OR ANY DERIVED PROGRAM, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXTENDED, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO; PROCUREMENT OF SUBSTITUTED GOODS OR SERVICE; DAMAGES ARISING FROM SYSTEM FAILURE; LOSS OR CORRUPTION OF EXISTING DATA OR PROGRAM; LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE INSTALLATION, USE, THE REPRODUCTION OR OTHER EXPLOITATION OF THE LICENSED PROGRAM OR ANY DERIVED PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
108-4.The Licensor is under no obligation to respond to any technical questions or inquiries, or provide any other user support in connection with the installation, use or the Reproduction and Other Exploitation of the Licensed Program or Derived Programs thereof.
109-
110-Article 4 (Termination of Agreement)
111-1.The term of this Agreement shall begin from the time of receipt of the Licensed Program by the Recipient and shall continue as long as the Recipient retains any such Licensed Program in any way.
112-2.Notwithstanding the provision set forth in the preceding Paragraph, in the event of the breach of any of the provisions set forth in this Agreement by the Recipient, this Agreement shall automatically terminate without any notice. In the case of such termination, the Recipient may not use or conduct Reproduction and Other Exploitation of the Licensed Program or a Derived Program: provided that such termination shall not affect any rights of any other Recipient receiving the Licensed Program or the Derived Program from such Recipient who breached this Agreement.
113-
114-Article 5 (Governing Law)
115-1.IPA may publish revised and/or new versions of this License. In such an event, the Recipient may select either this Agreement or any subsequent version of the Agreement in using, conducting the Reproduction and Other Exploitation of, or Redistributing the Licensed Program or a Derived Program. Other matters not specified above shall be subject to the Copyright Law of Japan and other related laws and regulations of Japan.
116-2.This Agreement shall be construed under the laws of Japan.
117-
diff -r 8d6d058ff897 -r d270659754af resource/ipagp.ttf
Binary file resource/ipagp.ttf has changed
diff -r 8d6d058ff897 -r d270659754af sample/Makefile
--- a/sample/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,9 +0,0 @@
1-# mhack/sample
2-
3-all :
4- cd light_sample/ && $(MAKE)
5- cd walking_sample/ && $(MAKE)
6-
7-clean :
8- cd light_sample/ && $(MAKE) clean
9- cd walking_sample/ && $(MAKE) clean
diff -r 8d6d058ff897 -r d270659754af sample/light_sample/Makefile
--- a/sample/light_sample/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,48 +0,0 @@
1-# sample/light_sample
2-
3-QRK_LIBS = ../../../../../libs
4-
5-CC = g++
6-CXXFLAGS = -g -O0 -Wall -Werror $(INCLUDES) `sdl-config --cflags`
7-INCLUDES = -I$(QRK_LIBS)/gui -I$(QRK_LIBS)/geometry -I$(QRK_LIBS)/common -I$(QRK_LIBS)/system
8-LDFLAGS = -L/usr/X11/lib
9-LDLIBS = `sdl-config --libs` -lGL -lSDL_ttf -lboost_signals-mt
10-
11-TARGET = light_sample
12-
13-
14-all : $(TARGET)
15-
16-clean :
17- $(RM) *.o $(TARGET) error_log.txt
18-
19-depend :
20- makedepend -Y -- $(INCLUDES) -- $(wildcard *.h *.cpp)
21-
22-.PHONY : all clean depend
23-######################################################################
24-REQUIRE_LIBS = $(QRK_LIBS)/gui/gui.a $(QRK_LIBS)/geometry/geometry.a $(QRK_LIBS)/system/system.a $(QRK_LIBS)/system/sdl/system_sdl.a
25-
26-$(REQUIRE_LIBS) :
27- cd $(@D)/ && $(MAKE) $(@F)
28-
29-light_sample : $(REQUIRE_LIBS)
30-
31-# DO NOT DELETE
32-
33-light_sample.o: ../../../../../libs/gui/Screen.h
34-light_sample.o: ../../../../../libs/geometry/Rect.h
35-light_sample.o: ../../../../../libs/gui/LayerManager.h
36-light_sample.o: ../../../../../libs/gui/LayerInterface.h
37-light_sample.o: ../../../../../libs/geometry/Point.h
38-light_sample.o: ../../../../../libs/gui/Layer.h
39-light_sample.o: ../../../../../libs/gui/Font.h
40-light_sample.o: ../../../../../libs/common/Color.h
41-light_sample.o: ../../../../../libs/gui/CanvasSurface.h
42-light_sample.o: ../../../../../libs/gui/Surface.h
43-light_sample.o: ../../../../../libs/gui/Label.h
44-light_sample.o: ../../../../../libs/gui/Component.h
45-light_sample.o: ../../../../../libs/gui/CallbackEvent.h
46-light_sample.o: ../../../../../libs/gui/Event.h
47-light_sample.o: ../../../../../libs/gui/EventUtils.h
48-light_sample.o: ../../../../../libs/system/delay.h
diff -r 8d6d058ff897 -r d270659754af sample/light_sample/light_sample.cpp
--- a/sample/light_sample/light_sample.cpp Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,124 +0,0 @@
1-/*!
2- \example light_sample.cpp 光源の動作サンプル
3-
4- \author Satofumi KAMIMURA
5-
6- $Id$
7-*/
8-
9-#include "Screen.h"
10-#include "LayerManager.h"
11-#include "Layer.h"
12-#include "Font.h"
13-#include "CanvasSurface.h"
14-#include "Label.h"
15-#include "CallbackEvent.h"
16-#include "EventUtils.h"
17-#include "delay.h"
18-#include <iostream>
19-
20-using namespace qrk;
21-using namespace std;
22-
23-
24-namespace {
25- const char Default_font[] = "../../resource/ipagp.ttf";
26- const int Font_size = 16;
27-}
28-
29-
30-int main(int argc, char *argv[])
31-{
32- Screen screen;
33- if (! screen.show(SDL_OPENGL)) {
34- cout << "Screen::show(): " << screen.what() << endl;
35- return 1;
36- }
37-
38- // 描画レイヤーの初期化
39- LayerManager layer_manager;
40- Layer layer;
41- layer_manager.push_front(&layer);
42-
43- // 環境シンボルの作成
44- const char* font_file = (argc <= 1) ? Default_font : argv[1];
45- Font font(font_file, Font_size);
46- if (!font.resource()) {
47- cout << "Font: " << font.what() << endl;
48- return 1;
49- }
50-
51- // マップのデータ定義
52- const string wall_map[] = {
53- " ",
54- " ###### ",
55- " #<...# ",
56- " #.@..# ",
57- " #...... ",
58- " #....# ",
59- " ###### ",
60- " ",
61- };
62-
63- // 光源のデータ定義
64- const float light_max_intensity = 6.0;
65- const float light_intensity_base = 0.55;
66- const string light_map[] = {
67- " ",
68- " 2 ",
69- " 343 ",
70- " 24642 ",
71- " 343 ",
72- " 2 ",
73- " ",
74- " ",
75- };
76-
77- size_t line_n = sizeof(wall_map) / sizeof(wall_map[0]);
78- Rect<long> draw_rect(0, 0,
79- wall_map[0].size() * Font_size, line_n * Font_size);
80- CanvasSurface canvas(draw_rect);
81- canvas.setFont(font);
82-
83- // 光源を考慮して描画
84- for (size_t y = 0; y < line_n; ++y) {
85- const string& line = wall_map[y];
86- for (size_t x = 0; x < line.size(); ++x) {
87- char ch[] = "x";
88- ch[0] = line[x];
89-
90- // 色の変更
91- char light_intensity_char[] = "x";
92- light_intensity_char[0] = light_map[y][x];
93- float light_intensity =
94- min(((atoi(light_intensity_char) / light_max_intensity)
95- * light_intensity_base) + light_intensity_base,
96- 1.0f);
97- Color color(light_intensity, light_intensity, light_intensity);
98- font.setForegroundColor(color);
99-
100- Point<long> position(x * Font_size, y * Font_size);
101- canvas.drawText(ch, position);
102- }
103- }
104- Label label(canvas);
105- layer.push_front(&label);
106-
107- CallbackEvent quit_event;
108- setQuitEvent(&quit_event);
109- layer_manager.insertEvent(&quit_event);
110-
111- bool quit = false;
112- while (!quit) {
113- layer_manager.updateEvent();
114- quit |= quit_event.isActive();
115-
116- screen.clear();
117- layer_manager.draw();
118- layer_manager.swap();
119-
120- delay(50);
121- }
122-
123- return 0;
124-}
diff -r 8d6d058ff897 -r d270659754af sample/walking_sample/Makefile
--- a/sample/walking_sample/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,49 +0,0 @@
1-# Makefile for walkingAtmark
2-
3-QRK_LIBS = ../../../../../libs
4-
5-CC = g++
6-CXXFLAGS = -g -O0 -Wall -Werror $(INCLUDES) `sdl-config --cflags`
7-INCLUDES = -I$(QRK_LIBS)/gui -I$(QRK_LIBS)/geometry -I$(QRK_LIBS)/common -I$(QRK_LIBS)/system
8-LDFLAGS = -L/usr/X11/lib
9-LDLIBS = `sdl-config --libs` -lGL -lSDL_ttf -lboost_signals-mt
10-
11-TARGET = walking_sample
12-
13-
14-all : $(TARGET)
15-
16-clean :
17- $(RM) *.o $(TARGET) error_log.txt
18-
19-depend :
20- makedepend -Y -- $(INCLUDES) -- $(wildcard *.h *.cpp)
21-
22-.PHONY : all clean depend
23-######################################################################
24-REQUIRE_LIBS = $(QRK_LIBS)/gui/gui.a $(QRK_LIBS)/geometry/geometry.a $(QRK_LIBS)/system/system.a $(QRK_LIBS)/system/sdl/system_sdl.a
25-
26-$(REQUIRE_LIBS) :
27- cd $(@D)/ && $(MAKE) $(@F)
28-
29-walking_sample : $(REQUIRE_LIBS)
30-
31-# DO NOT DELETE
32-
33-walking_sample.o: ../../../../../libs/gui/Screen.h
34-walking_sample.o: ../../../../../libs/geometry/Rect.h
35-walking_sample.o: ../../../../../libs/gui/LayerManager.h
36-walking_sample.o: ../../../../../libs/gui/LayerInterface.h
37-walking_sample.o: ../../../../../libs/geometry/Point.h
38-walking_sample.o: ../../../../../libs/gui/Layer.h
39-walking_sample.o: ../../../../../libs/gui/Font.h
40-walking_sample.o: ../../../../../libs/common/Color.h
41-walking_sample.o: ../../../../../libs/gui/TextSurface.h
42-walking_sample.o: ../../../../../libs/gui/Surface.h
43-walking_sample.o: ../../../../../libs/gui/Label.h
44-walking_sample.o: ../../../../../libs/gui/Component.h
45-walking_sample.o: ../../../../../libs/gui/CallbackEvent.h
46-walking_sample.o: ../../../../../libs/gui/Event.h
47-walking_sample.o: ../../../../../libs/gui/EventUtils.h
48-walking_sample.o: ../../../../../libs/system/delay.h
49-walking_sample.o: ../../../../../libs/geometry/Angle.h
diff -r 8d6d058ff897 -r d270659754af sample/walking_sample/walking_sample.cpp
--- a/sample/walking_sample/walking_sample.cpp Mon Dec 20 07:25:07 2010 +0900
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,94 +0,0 @@
1-/*!
2- \example walking_sample.cpp \@ が移動するサンプル
3-
4- \author Satofumi KAMIMURA
5-
6- $Id$
7-*/
8-
9-#include "Screen.h"
10-#include "LayerManager.h"
11-#include "Layer.h"
12-#include "Font.h"
13-#include "TextSurface.h"
14-#include "Label.h"
15-#include "CallbackEvent.h"
16-#include "EventUtils.h"
17-#include "delay.h"
18-#include "Angle.h"
19-#include <iostream>
20-
21-using namespace qrk;
22-using namespace std;
23-
24-
25-namespace {
26- const char Default_font[] = "../../resource/ipagp.ttf";
27- const int Font_size = 32;
28-}
29-
30-
31-int main(int argc, char *argv[])
32-{
33- Screen screen;
34- if (!screen.show(SDL_OPENGL)) {
35- cout << "Screen::show(): " << screen.what() << endl;
36- return 1;
37- }
38-
39- // 描画レイヤーの初期化
40- LayerManager layer_manager;
41- Layer layer;
42- layer_manager.push_front(&layer);
43-
44- // '@' キャラクタの生成
45- const char* font_file = (argc <= 1) ? Default_font : argv[1];
46- Font font(font_file, Font_size);
47- if (!font.resource()) {
48- cout << "Font: " << font.what() << endl;
49- return 1;
50- }
51- TextSurface surface(font, "@");
52- Label label(surface);
53- layer.push_front(&label);
54-
55- CallbackEvent quit_event;
56- setQuitEvent(&quit_event);
57- layer_manager.insertEvent(&quit_event);
58-
59- Point<long> position(0, 0);
60- int degrees[] = { 0, +12, 0, -12, };
61- int pattern_size = sizeof(degrees) / sizeof(degrees[0]);
62- int pattern_index = 0;
63-
64- enum {
65- Move_velocity = 4,
66- Move_max = 100,
67- };
68- bool quit = false;
69- int xx = +Move_velocity;
70- while (!quit) {
71-
72- position.x += xx;
73- if ((position.x >= Move_max) || (position.x <= 0)) {
74- xx = -xx;
75- }
76- label.setPosition(position);
77- ++pattern_index;
78- if (pattern_index >= pattern_size) {
79- pattern_index = 0;
80- }
81- label.setRotateAngle(deg(degrees[pattern_index]));
82-
83- layer_manager.updateEvent();
84- quit |= quit_event.isActive();
85-
86- screen.clear();
87- layer_manager.draw();
88- layer_manager.swap();
89-
90- delay(50);
91- }
92-
93- return 0;
94-}
diff -r 8d6d058ff897 -r d270659754af source/Makefile
--- a/source/Makefile Mon Dec 20 07:25:07 2010 +0900
+++ b/source/Makefile Fri Jul 15 07:48:55 2011 +0900
@@ -1,5 +1,20 @@
11 # mhack/source
22
3-all :
3+CXXFLAGS = -g -O0 -Wall -W -Werror
4+LDFLAGS =
5+LDLIBS =
46
5-clean :
\ No newline at end of file
7+
8+TARGET = mhack
9+
10+all : $(TARGET)
11+
12+clean :
13+ $(RM) $(TARGET) *.o
14+
15+depend :
16+ makedepend -Y -- $(INCLUDES) -- $(wildcard *.h *.cpp)
17+
18+######################################################################
19+
20+# DO NOT DELETE
diff -r 8d6d058ff897 -r d270659754af source/mhack.cpp
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/source/mhack.cpp Fri Jul 15 07:48:55 2011 +0900
@@ -0,0 +1,29 @@
1+/*!
2+ \file
3+ \brief マルチプレイ風ローグライク
4+
5+ \author Satofumi KAMIMURA
6+
7+ $Id$
8+*/
9+
10+
11+int main(int argc, char *argv[])
12+{
13+ (void)argc;
14+ (void)argv;
15+
16+ // ゲーム用データの読み出し
17+ // !!!
18+
19+ // 画面の初期化
20+ // !!!
21+
22+ // サウンドの初期化
23+ // !!!
24+
25+ // ゲーム・スクリプトの起動
26+ // !!!
27+
28+ return 0;
29+}
Show on old repository browser