--- /dev/null
+<doxygenlayout version="1.0">
+ <!-- Navigation index tabs for HTML output -->
+ <navindex>
+ <tab type="mainpage" visible="yes" title=""/>
+ <tab type="pages" visible="yes" title=""/>
+ <tab type="modules" visible="yes" title="Libraries"/>
+ <tab type="namespaces" visible="yes" title="">
+ <tab type="namespaces" visible="yes" title=""/>
+ <tab type="namespacemembers" visible="yes" title=""/>
+ </tab>
+ <tab type="classes" visible="yes" title="">
+ <tab type="classes" visible="yes" title=""/>
+ <tab type="classindex" visible="$ALPHABETICAL_INDEX" title=""/>
+ <tab type="hierarchy" visible="yes" title=""/>
+ <tab type="classmembers" visible="yes" title=""/>
+ </tab>
+ <tab type="files" visible="yes" title="">
+ <tab type="files" visible="yes" title=""/>
+ <tab type="globals" visible="yes" title=""/>
+ </tab>
+ <tab type="dirs" visible="yes" title=""/>
+ <tab type="examples" visible="yes" title=""/>
+ </navindex>
+
+ <!-- Layout definition for a class page -->
+ <class>
+ <briefdescription visible="no"/>
+ <includes visible="$SHOW_INCLUDE_FILES"/>
+ <inheritancegraph visible="$CLASS_GRAPH"/>
+ <collaborationgraph visible="$COLLABORATION_GRAPH"/>
+ <detaileddescription title=" "/>
+ <allmemberslink visible="yes"/>
+ <memberdecl>
+ <membergroups visible="yes"/>
+ <nestedclasses visible="yes" title=""/>
+ <publictypes title=""/>
+ <publicslots title=""/>
+ <signals title=""/>
+ <publicmethods title=""/>
+ <publicstaticmethods title=""/>
+ <publicattributes title=""/>
+ <publicstaticattributes title=""/>
+ <protectedtypes title=""/>
+ <protectedslots title=""/>
+ <protectedmethods title=""/>
+ <protectedstaticmethods title=""/>
+ <protectedattributes title=""/>
+ <protectedstaticattributes title=""/>
+ <packagetypes title=""/>
+ <packagemethods title=""/>
+ <packagestaticmethods title=""/>
+ <packageattributes title=""/>
+ <packagestaticattributes title=""/>
+ <properties title=""/>
+ <events title=""/>
+ <privatetypes title=""/>
+ <privateslots title=""/>
+ <privatemethods title=""/>
+ <privatestaticmethods title=""/>
+ <privateattributes title=""/>
+ <privatestaticattributes title=""/>
+ <friends title=""/>
+ <related title="" subtitle=""/>
+ </memberdecl>
+ <memberdef>
+ <typedefs title=""/>
+ <enums title=""/>
+ <constructors title=""/>
+ <functions title=""/>
+ <related title=""/>
+ <variables title=""/>
+ <properties title=""/>
+ <events title=""/>
+ </memberdef>
+ <usedfiles visible="$SHOW_USED_FILES"/>
+ <authorsection visible="yes"/>
+ </class>
+
+ <!-- Layout definition for a namespace page -->
+ <namespace>
+ <briefdescription visible="no"/>
+ <detaileddescription title=" "/>
+ <memberdecl>
+ <nestednamespaces visible="yes" title=""/>
+ <classes visible="yes" title=""/>
+ <membergroups visible="yes"/>
+ <typedefs title=""/>
+ <enums title=""/>
+ <functions title=""/>
+ <variables title=""/>
+ </memberdecl>
+ <memberdef>
+ <typedefs title=""/>
+ <enums title=""/>
+ <functions title=""/>
+ <variables title=""/>
+ </memberdef>
+ <authorsection visible="yes"/>
+ </namespace>
+
+ <!-- Layout definition for a file page -->
+ <file>
+ <briefdescription visible="no"/>
+ <includes visible="$SHOW_INCLUDE_FILES"/>
+ <includegraph visible="$INCLUDE_GRAPH"/>
+ <includedbygraph visible="$INCLUDED_BY_GRAPH"/>
+ <sourcelink visible="yes"/>
+ <detaileddescription title=""/>
+ <memberdecl>
+ <classes visible="yes" title=""/>
+ <namespaces visible="yes" title=""/>
+ <defines title=""/>
+ <typedefs title=""/>
+ <enums title=""/>
+ <functions title=""/>
+ <variables title=""/>
+ </memberdecl>
+ <memberdef>
+ <defines title=""/>
+ <typedefs title=""/>
+ <enums title=""/>
+ <functions title=""/>
+ <variables title=""/>
+ </memberdef>
+ <authorsection/>
+ </file>
+
+ <!-- Layout definition for a group page -->
+ <group>
+ <briefdescription visible="yes"/>
+ <groupgraph visible="$GROUP_GRAPHS"/>
+ <detaileddescription title=" "/>
+ <memberdecl>
+ <classes visible="yes" title=""/>
+ <namespaces visible="yes" title=""/>
+ <dirs visible="yes" title=""/>
+ <nestedgroups visible="yes" title=""/>
+ <files visible="yes" title=""/>
+ <defines title=""/>
+ <typedefs title=""/>
+ <enums title=""/>
+ <enumvalues title=""/>
+ <functions title=""/>
+ <variables title=""/>
+ <signals title=""/>
+ <publicslots title=""/>
+ <protectedslots title=""/>
+ <privateslots title=""/>
+ <events title=""/>
+ <properties title=""/>
+ <friends title=""/>
+ </memberdecl>
+ <memberdef>
+ <pagedocs/>
+ <defines title=""/>
+ <typedefs title=""/>
+ <enums title=""/>
+ <enumvalues title=""/>
+ <functions title=""/>
+ <variables title=""/>
+ <signals title=""/>
+ <publicslots title=""/>
+ <protectedslots title=""/>
+ <privateslots title=""/>
+ <events title=""/>
+ <properties title=""/>
+ <friends title=""/>
+ </memberdef>
+ <authorsection visible="yes"/>
+ </group>
+
+ <!-- Layout definition for a directory page -->
+ <directory>
+ <briefdescription visible="no"/>
+ <directorygraph visible="yes"/>
+ <detaileddescription title=""/>
+ <memberdecl>
+ <dirs visible="yes"/>
+ <files visible="yes"/>
+ </memberdecl>
+ </directory>
+</doxygenlayout>
--- /dev/null
+/* The standard CSS for doxygen */\r
+\r
+body, table, div, p, dl {\r
+ font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;\r
+ font-size: 12px;\r
+}\r
+\r
+/* @group Heading Levels */\r
+\r
+h1 {\r
+ font-size: 150%;\r
+}\r
+\r
+.title {\r
+ font-size: 150%;\r
+ font-weight: bold;\r
+ margin: 10px 2px;\r
+}\r
+\r
+h2 {\r
+ font-size: 120%;\r
+}\r
+\r
+h3 {\r
+ font-size: 100%;\r
+}\r
+\r
+dt {\r
+ font-weight: bold;\r
+}\r
+\r
+div.multicol {\r
+ -moz-column-gap: 1em;\r
+ -webkit-column-gap: 1em;\r
+ -moz-column-count: 3;\r
+ -webkit-column-count: 3;\r
+}\r
+\r
+p.startli, p.startdd, p.starttd {\r
+ margin-top: 2px;\r
+}\r
+\r
+p.endli {\r
+ margin-bottom: 0px;\r
+}\r
+\r
+p.enddd {\r
+ margin-bottom: 4px;\r
+}\r
+\r
+p.endtd {\r
+ margin-bottom: 2px;\r
+}\r
+\r
+/* @end */\r
+\r
+caption {\r
+ font-weight: bold;\r
+}\r
+\r
+span.legend {\r
+ font-size: 70%;\r
+ text-align: center;\r
+}\r
+\r
+h3.version {\r
+ font-size: 90%;\r
+ text-align: center;\r
+}\r
+\r
+div.qindex, div.navtab{\r
+ background-color: #EBEFF6;\r
+ border: 1px solid #A3B4D7;\r
+ text-align: center;\r
+ margin: 2px;\r
+ padding: 2px;\r
+}\r
+\r
+div.qindex, div.navpath {\r
+ width: 100%;\r
+ line-height: 140%;\r
+}\r
+\r
+div.navtab {\r
+ margin-right: 15px;\r
+}\r
+\r
+/* @group Link Styling */\r
+\r
+a {\r
+ color: #3D578C;\r
+ font-weight: normal;\r
+ text-decoration: none;\r
+}\r
+\r
+.contents a:visited {\r
+ color: #4665A2;\r
+}\r
+\r
+a:hover {\r
+ text-decoration: underline;\r
+}\r
+\r
+a.qindex {\r
+ font-weight: bold;\r
+}\r
+\r
+a.qindexHL {\r
+ font-weight: bold;\r
+ background-color: #9CAFD4;\r
+ color: #ffffff;\r
+ border: 1px double #869DCA;\r
+}\r
+\r
+.contents a.qindexHL:visited {\r
+ color: #ffffff;\r
+}\r
+\r
+a.el {\r
+ font-weight: bold;\r
+}\r
+\r
+a.elRef {\r
+}\r
+\r
+a.code {\r
+ color: #642880;\r
+}\r
+\r
+a.codeRef {\r
+ color: #4665A2;\r
+}\r
+\r
+/* @end */\r
+\r
+dl.el {\r
+ margin-left: -1cm;\r
+}\r
+\r
+.fragment {\r
+ font-family: monospace, fixed;\r
+ font-size: 105%;\r
+}\r
+\r
+pre.fragment {\r
+ border: 1px solid #C4CFE5;\r
+ background-color: #FBFCFD;\r
+ padding: 4px 6px;\r
+ margin: 4px 8px 4px 2px;\r
+ overflow: auto;\r
+ word-wrap: break-word;\r
+ font-size: 9pt;\r
+ line-height: 125%;\r
+}\r
+\r
+div.ah {\r
+ background-color: black;\r
+ font-weight: bold;\r
+ color: #ffffff;\r
+ margin-bottom: 3px;\r
+ margin-top: 3px;\r
+ padding: 0.2em;\r
+ border: solid thin #333;\r
+ border-radius: 0.5em;\r
+ -webkit-border-radius: .5em;\r
+ -moz-border-radius: .5em;\r
+ box-shadow: 2px 2px 3px #999;\r
+ -webkit-box-shadow: 2px 2px 3px #999;\r
+ -moz-box-shadow: rgba(0, 0, 0, 0.15) 2px 2px 2px;\r
+ background-image: -webkit-gradient(linear, left top, left bottom, from(#eee), to(#000),color-stop(0.3, #444));\r
+ background-image: -moz-linear-gradient(center top, #eee 0%, #444 40%, #000);\r
+}\r
+\r
+div.groupHeader {\r
+ margin-left: 16px;\r
+ margin-top: 12px;\r
+ font-weight: bold;\r
+}\r
+\r
+div.groupText {\r
+ margin-left: 16px;\r
+ font-style: italic;\r
+}\r
+\r
+body {\r
+ background: white;\r
+ color: black;\r
+ margin: 0;\r
+}\r
+\r
+div.contents {\r
+ margin-top: 10px;\r
+ margin-left: 10px;\r
+ margin-right: 5px;\r
+}\r
+\r
+td.indexkey {\r
+ background-color: #EBEFF6;\r
+ font-weight: bold;\r
+ border: 1px solid #C4CFE5;\r
+ margin: 2px 0px 2px 0;\r
+ padding: 2px 10px;\r
+}\r
+\r
+td.indexvalue {\r
+ background-color: #EBEFF6;\r
+ border: 1px solid #C4CFE5;\r
+ padding: 2px 10px;\r
+ margin: 2px 0px;\r
+}\r
+\r
+tr.memlist {\r
+ background-color: #EEF1F7;\r
+}\r
+\r
+p.formulaDsp {\r
+ text-align: center;\r
+}\r
+\r
+img.formulaDsp {\r
+ \r
+}\r
+\r
+img.formulaInl {\r
+ vertical-align: middle;\r
+}\r
+\r
+div.center {\r
+ text-align: center;\r
+ margin-top: 0px;\r
+ margin-bottom: 0px;\r
+ padding: 0px;\r
+}\r
+\r
+div.center img {\r
+ border: 0px;\r
+}\r
+\r
+address.footer {\r
+ text-align: right;\r
+ padding-right: 12px;\r
+}\r
+\r
+img.footer {\r
+ border: 0px;\r
+ vertical-align: middle;\r
+}\r
+\r
+/* @group Code Colorization */\r
+\r
+span.keyword {\r
+ color: #7F0055\r
+}\r
+\r
+span.keywordtype {\r
+ color: #7F0055\r
+}\r
+\r
+span.keywordflow {\r
+ color: #7F0055\r
+}\r
+\r
+span.comment {\r
+ color: #3F7F5F\r
+}\r
+\r
+span.preprocessor {\r
+ color: #7F0055\r
+}\r
+\r
+span.stringliteral {\r
+ color: #0000C0\r
+}\r
+\r
+span.charliteral {\r
+ color: #008080\r
+}\r
+\r
+span.vhdldigit { \r
+ color: #ff00ff \r
+}\r
+\r
+span.vhdlchar { \r
+ color: #000000 \r
+}\r
+\r
+span.vhdlkeyword { \r
+ color: #700070 \r
+}\r
+\r
+span.vhdllogic { \r
+ color: #ff0000 \r
+}\r
+\r
+/* @end */\r
+\r
+/*\r
+.search {\r
+ color: #003399;\r
+ font-weight: bold;\r
+}\r
+\r
+form.search {\r
+ margin-bottom: 0px;\r
+ margin-top: 0px;\r
+}\r
+\r
+input.search {\r
+ font-size: 75%;\r
+ color: #000080;\r
+ font-weight: normal;\r
+ background-color: #e8eef2;\r
+}\r
+*/\r
+\r
+td.tiny {\r
+ font-size: 75%;\r
+}\r
+\r
+.dirtab {\r
+ padding: 4px;\r
+ border-collapse: collapse;\r
+ border: 1px solid #A3B4D7;\r
+}\r
+\r
+th.dirtab {\r
+ background: #EBEFF6;\r
+ font-weight: bold;\r
+}\r
+\r
+hr {\r
+ height: 0px;\r
+ border: none;\r
+ border-top: 1px solid #4A6AAA;\r
+}\r
+\r
+hr.footer {\r
+ height: 1px;\r
+}\r
+\r
+/* @group Member Descriptions */\r
+\r
+table.memberdecls {\r
+ border-spacing: 0px;\r
+ padding: 0px;\r
+}\r
+\r
+.mdescLeft, .mdescRight,\r
+.memItemLeft, .memItemRight,\r
+.memTemplItemLeft, .memTemplItemRight, .memTemplParams {\r
+ background-color: #F9FAFC;\r
+ border: none;\r
+ margin: 4px;\r
+ padding: 1px 0 0 8px;\r
+}\r
+\r
+.mdescLeft, .mdescRight {\r
+ padding: 0px 8px 4px 8px;\r
+ color: #555;\r
+}\r
+\r
+.memItemLeft, .memItemRight, .memTemplParams {\r
+ border-top: 1px solid #C4CFE5;\r
+}\r
+\r
+.memItemLeft, .memTemplItemLeft {\r
+ white-space: nowrap;\r
+}\r
+\r
+.memItemRight {\r
+ width: 100%;\r
+}\r
+\r
+.memTemplParams {\r
+ color: #4665A2;\r
+ white-space: nowrap;\r
+}\r
+\r
+/* @end */\r
+\r
+/* @group Member Details */\r
+\r
+/* Styles for detailed member documentation */\r
+\r
+.memtemplate {\r
+ font-size: 80%;\r
+ color: #4665A2;\r
+ font-weight: normal;\r
+ margin-left: 9px;\r
+}\r
+\r
+.memnav {\r
+ background-color: #EBEFF6;\r
+ border: 1px solid #A3B4D7;\r
+ text-align: center;\r
+ margin: 2px;\r
+ margin-right: 15px;\r
+ padding: 2px;\r
+}\r
+\r
+.mempage {\r
+ width: 100%;\r
+}\r
+\r
+.memitem {\r
+ padding: 0;\r
+ margin-bottom: 10px;\r
+ margin-right: 5px;\r
+}\r
+\r
+.memname {\r
+ white-space: nowrap;\r
+ font-weight: bold;\r
+ margin-left: 6px;\r
+}\r
+\r
+.memproto {\r
+ border-top: 1px solid #A8B8D9;\r
+ border-left: 1px solid #A8B8D9;\r
+ border-right: 1px solid #A8B8D9;\r
+ padding: 6px 0px 6px 0px;\r
+ color: #253555;\r
+ font-weight: bold;\r
+ text-shadow: 0px 1px 1px rgba(255, 255, 255, 0.9);\r
+ /* opera specific markup */\r
+ box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);\r
+ border-top-right-radius: 8px;\r
+ border-top-left-radius: 8px;\r
+ /* firefox specific markup */\r
+ -moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;\r
+ -moz-border-radius-topright: 8px;\r
+ -moz-border-radius-topleft: 8px;\r
+ /* webkit specific markup */\r
+ -webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);\r
+ -webkit-border-top-right-radius: 8px;\r
+ -webkit-border-top-left-radius: 8px;\r
+ background-image:url('nav_f.png');\r
+ background-repeat:repeat-x;\r
+ background-color: #E2E8F2;\r
+\r
+}\r
+\r
+.memdoc {\r
+ border-bottom: 1px solid #A8B8D9; \r
+ border-left: 1px solid #A8B8D9; \r
+ border-right: 1px solid #A8B8D9; \r
+ padding: 2px 5px;\r
+ background-color: #FBFCFD;\r
+ border-top-width: 0;\r
+ /* opera specific markup */\r
+ border-bottom-left-radius: 8px;\r
+ border-bottom-right-radius: 8px;\r
+ box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);\r
+ /* firefox specific markup */\r
+ -moz-border-radius-bottomleft: 8px;\r
+ -moz-border-radius-bottomright: 8px;\r
+ -moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;\r
+ background-image: -moz-linear-gradient(center top, #FFFFFF 0%, #FFFFFF 60%, #F7F8FB 95%, #EEF1F7);\r
+ /* webkit specific markup */\r
+ -webkit-border-bottom-left-radius: 8px;\r
+ -webkit-border-bottom-right-radius: 8px;\r
+ -webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);\r
+ 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));\r
+}\r
+\r
+.paramkey {\r
+ text-align: right;\r
+}\r
+\r
+.paramtype {\r
+ white-space: nowrap;\r
+}\r
+\r
+.paramname {\r
+ color: #602020;\r
+ white-space: nowrap;\r
+}\r
+.paramname em {\r
+ font-style: normal;\r
+}\r
+\r
+.params, .retval, .exception, .tparams {\r
+ border-spacing: 6px 2px;\r
+} \r
+\r
+.params .paramname, .retval .paramname {\r
+ font-weight: bold;\r
+ vertical-align: top;\r
+}\r
+ \r
+.params .paramtype {\r
+ font-style: italic;\r
+ vertical-align: top;\r
+} \r
+ \r
+.params .paramdir {\r
+ font-family: "courier new",courier,monospace;\r
+ vertical-align: top;\r
+}\r
+\r
+\r
+\r
+\r
+/* @end */\r
+\r
+/* @group Directory (tree) */\r
+\r
+/* for the tree view */\r
+\r
+.ftvtree {\r
+ font-family: sans-serif;\r
+ margin: 0px;\r
+}\r
+\r
+/* these are for tree view when used as main index */\r
+\r
+.directory {\r
+ font-size: 9pt;\r
+ font-weight: bold;\r
+ margin: 5px;\r
+}\r
+\r
+.directory h3 {\r
+ margin: 0px;\r
+ margin-top: 1em;\r
+ font-size: 11pt;\r
+}\r
+\r
+/*\r
+The following two styles can be used to replace the root node title\r
+with an image of your choice. Simply uncomment the next two styles,\r
+specify the name of your image and be sure to set 'height' to the\r
+proper pixel height of your image.\r
+*/\r
+\r
+/*\r
+.directory h3.swap {\r
+ height: 61px;\r
+ background-repeat: no-repeat;\r
+ background-image: url("yourimage.gif");\r
+}\r
+.directory h3.swap span {\r
+ display: none;\r
+}\r
+*/\r
+\r
+.directory > h3 {\r
+ margin-top: 0;\r
+}\r
+\r
+.directory p {\r
+ margin: 0px;\r
+ white-space: nowrap;\r
+}\r
+\r
+.directory div {\r
+ display: none;\r
+ margin: 0px;\r
+}\r
+\r
+.directory img {\r
+ vertical-align: -30%;\r
+}\r
+\r
+/* these are for tree view when not used as main index */\r
+\r
+.directory-alt {\r
+ font-size: 100%;\r
+ font-weight: bold;\r
+}\r
+\r
+.directory-alt h3 {\r
+ margin: 0px;\r
+ margin-top: 1em;\r
+ font-size: 11pt;\r
+}\r
+\r
+.directory-alt > h3 {\r
+ margin-top: 0;\r
+}\r
+\r
+.directory-alt p {\r
+ margin: 0px;\r
+ white-space: nowrap;\r
+}\r
+\r
+.directory-alt div {\r
+ display: none;\r
+ margin: 0px;\r
+}\r
+\r
+.directory-alt img {\r
+ vertical-align: -30%;\r
+}\r
+\r
+/* @end */\r
+\r
+div.dynheader {\r
+ margin-top: 8px;\r
+}\r
+\r
+address {\r
+ font-style: normal;\r
+ color: #2A3D61;\r
+}\r
+\r
+table.doxtable {\r
+ border-collapse:collapse;\r
+}\r
+\r
+table.doxtable td, table.doxtable th {\r
+ border: 1px solid #2D4068;\r
+ padding: 3px 7px 2px;\r
+}\r
+\r
+table.doxtable th {\r
+ background-color: #374F7F;\r
+ color: #FFFFFF;\r
+ font-size: 110%;\r
+ padding-bottom: 4px;\r
+ padding-top: 5px;\r
+ text-align:left;\r
+}\r
+\r
+.tabsearch {\r
+ top: 0px;\r
+ left: 10px;\r
+ height: 36px;\r
+ background-image: url('tab_b.png');\r
+ z-index: 101;\r
+ overflow: hidden;\r
+ font-size: 13px;\r
+}\r
+\r
+.navpath ul\r
+{\r
+ font-size: 11px;\r
+ background-image:url('tab_b.png');\r
+ background-repeat:repeat-x;\r
+ height:30px;\r
+ line-height:30px;\r
+ color:#8AA0CC;\r
+ border:solid 1px #C2CDE4;\r
+ overflow:hidden;\r
+ margin:0px;\r
+ padding:0px;\r
+}\r
+\r
+.navpath li\r
+{\r
+ list-style-type:none;\r
+ float:left;\r
+ padding-left:10px;\r
+ padding-right:15px;\r
+ background-image:url('bc_s.png');\r
+ background-repeat:no-repeat;\r
+ background-position:right;\r
+ color:#364D7C;\r
+}\r
+\r
+.navpath li.navelem a\r
+{\r
+ height:32px;\r
+/* display:block; */\r
+ text-decoration: none;\r
+ outline: none;\r
+}\r
+\r
+.navpath li.navelem a:hover\r
+{\r
+ color:#6884BD;\r
+}\r
+\r
+.navpath li.footer\r
+{\r
+ list-style-type:none;\r
+ float:right;\r
+ padding-left:10px;\r
+ padding-right:15px;\r
+ background-image:none;\r
+ background-repeat:no-repeat;\r
+ background-position:right;\r
+ color:#364D7C;\r
+ font-size: 8pt;\r
+}\r
+\r
+\r
+div.summary\r
+{\r
+ float: right;\r
+ font-size: 8pt;\r
+ padding-right: 5px;\r
+ width: 50%;\r
+ text-align: right;\r
+} \r
+\r
+div.summary a\r
+{\r
+ white-space: nowrap;\r
+}\r
+\r
+div.ingroups\r
+{\r
+ font-size: 8pt;\r
+ padding-left: 5px;\r
+ width: 50%;\r
+ text-align: left;\r
+}\r
+\r
+div.ingroups a\r
+{\r
+ white-space: nowrap;\r
+}\r
+\r
+div.header\r
+{\r
+ background-image:url('nav_h.png');\r
+ background-repeat:repeat-x;\r
+ background-color: #F9FAFC;\r
+ margin: 0px;\r
+ border-bottom: 1px solid #C4CFE5;\r
+}\r
+\r
+div.headertitle\r
+{\r
+ padding: 5px 5px 5px 10px;\r
+}\r
+\r
+dl\r
+{\r
+ padding: 0 0 0 10px;\r
+}\r
+\r
+dl.note, dl.warning, dl.attention, dl.pre, dl.post, dl.invariant, dl.deprecated, dl.user, dl.todo, dl.test, dl.bug\r
+{\r
+ border-left:4px solid;\r
+ padding: 0 0 0 6px;\r
+}\r
+\r
+dl.note\r
+{\r
+ border-color: #D0C000;\r
+}\r
+\r
+dl.warning, dl.attention\r
+{\r
+ border-color: #FF0000;\r
+}\r
+\r
+dl.pre, dl.post, dl.invariant\r
+{\r
+ border-color: #00D000;\r
+}\r
+\r
+dl.deprecated\r
+{\r
+ border-color: #505050;\r
+}\r
+\r
+dl.user\r
+{\r
+ border-color: #505050;\r
+}\r
+\r
+dl.todo\r
+{\r
+ border-color: #00C0E0;\r
+}\r
+\r
+dl.test\r
+{\r
+ border-color: #3030E0;\r
+}\r
+\r
+dl.bug\r
+{\r
+ border-color: #C08050;\r
+}\r
+\r
+#projectlogo\r
+{\r
+ text-align: center;\r
+ vertical-align: bottom;\r
+ border-collapse: separate;\r
+}\r
+ \r
+#projectlogo img\r
+{ \r
+ border: 0px none;\r
+}\r
+ \r
+#projectname\r
+{\r
+ font: 300% Tahoma, Arial,sans-serif;\r
+ margin: 0px;\r
+ padding: 2px 0px;\r
+}\r
+ \r
+#projectbrief\r
+{\r
+ font: 120% Tahoma, Arial,sans-serif;\r
+ margin: 0px;\r
+ padding: 0px;\r
+}\r
+\r
+#projectnumber\r
+{\r
+ font: 50% Tahoma, Arial,sans-serif;\r
+ margin: 0px;\r
+ padding: 0px;\r
+}\r
+\r
+#titlearea\r
+{\r
+ padding: 0px;\r
+ margin: 0px;\r
+ width: 100%;\r
+ border-bottom: 1px solid #5373B4;\r
+}\r
+\r
+.image\r
+{\r
+ text-align: center;\r
+}\r
+\r
+.dotgraph\r
+{\r
+ text-align: center;\r
+}\r
+\r
+.mscgraph\r
+{\r
+ text-align: center;\r
+}\r
+\r
+.caption\r
+{\r
+ font-weight: bold;\r
+}\r
+\r
--- /dev/null
+#!/bin/sh
+
+check_errs()
+{
+ # Function. Parameter 1 is the return code
+ # Para. 2 is text to display on failure.
+ if [ "${1}" -ne "0" ]; then
+ echo "ERROR # ${1} : ${2}"
+ # as a bonus, make our script exit with the right error code.
+ exit ${1}
+ fi
+}
+
+print_help()
+{
+ echo "Usage : $0 [options]"
+ echo " "
+ echo " -public, --public AR \t Generate API Reference for public sdk"
+ echo " -xml, \t\t Generate doxygen xml files"
+ echo " -h, \t --help\t Show this message"
+ exit 1
+}
+
+update_rel_pages()
+{
+ cd tools
+# perl Visibility.pl ../apidocs/visibility.html
+ perl Namespace.pl ../apidocs/compatibility.html
+ perl Namespace.pl ../apidocs/deprecated.html
+ perl Privilege.pl ../apidocs/privilege.html
+ perl Privilege.pl ../apidocs/privlevel.html
+ perl Feature.pl -i ../apidocs/ -o ../apidocs/
+ perl TreeGenerate.pl ../apidocs/toc.xml -r replace.properties
+ check_errs $? "fail to call TreeGenerate.pl"
+
+ cd ../ # move to api-reference
+ cp -rf style/* apidocs
+}
+
+doxygen_patch()
+{
+ python doxygen_patch.py apidocs
+ check_errs $? "fail to patch"
+}
+
+if [ $# -eq 0 ]; then
+ print_help
+ exit 0
+fi
+
+rm -rf apidocs apidocs-platform
+
+os_name=`cat /etc/issue.net | cut -d" " -f3`
+if [ "$os_name" = "openSUSE" ]; then
+ doxygen_tool=doxygen_suse
+else
+ doxygen_tool=doxygen
+fi
+
+if [ "$1" = "-xml" ]; then
+ rm -rf _xml
+ echo 'generating xml'
+ sed -e "s/GENERATE_XML.*= NO/GENERATE_XML=YES/" framework.dox > _f2.dox
+ ./${doxygen_tool} _f2.dox
+ exit 0
+fi
+
+
+if [ "$1" = "-public" ]
+then
+ echo '..calling public doxygen'
+ if [ "$2" = "-pkg" ]; then
+ ./${doxygen_tool} framework_pkg.dox
+ else
+ ./${doxygen_tool} framework.dox
+ fi
+ check_errs $? "fail to call doxygen"
+
+elif [ "$1" = "-h" ]
+then
+ print_help
+fi
+
+ update_rel_pages
+ cp -rf style/META-INF apidocs
+ doxygen_patch
+ cd apidocs
+ zip -r -q org.tizen.native.apireference_2.2.1.jar *
+
+ check_errs $? "fail to zip"
+ mv *.jar ../../../plugins/
+
+ cd ../
+ echo '..calling public platform doxygen'
+ if [ "$2" = "-pkg" ]; then
+ ./${doxygen_tool} public-platform-developer/framework_pkg.dox
+ else
+ ./${doxygen_tool} public-platform-developer/framework.dox
+ fi
+ check_errs $? "fail to call doxygen"
+ cp -rf public-platform-developer/style/* apidocs-platform
+
+ doxygen_patch
+ cd apidocs-platform
+ zip -r -q org.tizen.platform.native.apireference_2.2.1.jar *
+ check_errs $? "fail to zip"
+
+mv *.jar ../../../plugins/
+cd ../../../
+
--- /dev/null
+import sys
+import os
+
+if (len(sys.argv) < 2):
+ print 'missing arg'
+ sys.exit(1)
+
+def convert(file):
+ f = open(file)
+ raw = f.read()
+ converted =raw.replace('<a href="pages.html"><span>Related Pages</span>','<a href="pages.html"><span>Privilege</span>')
+ f.close()
+ f = open(file, 'w')
+ f.write(converted)
+ f.close()
+
+for root,dirs,files in os.walk(sys.argv[1]):
+ for fname in files:
+ #if fname.endswith('.html'):
+ # fullpath = os.path.join(root, fname)
+ # convert(fullpath)
+ # pure vitual patch
+ if fname.endswith('classOsp_1_1Locations_1_1Controls_1_1IMapEventListener.html'):
+ fullpath = os.path.join(root, fname)
+ f = open(fullpath)
+ raw = f.read()
+ raw = raw.replace('errorMsg)</td></tr>','errorMsg)=0</td></tr>')
+ raw = raw.replace('<td></td><td><code> [inline, virtual]</code></td>','<td></td><td><code> [pure, virtual]</code></td>')
+ f.close()
+ f = open(fullpath, 'w')
+ f.write(raw)
+ f.close()
+ if fname.endswith('classOsp_1_1Media_1_1IPlayerEventListener.html'):
+ fullpath = os.path.join(root, fname)
+ f = open(fullpath)
+ raw = f.read()
+ raw = raw.replace('result</a> r)</td>','result</a> r)=0</td>')
+ raw = raw.replace('[inline, virtual]','[pure, virtual]')
+ f.close()
+ f = open(fullpath, 'w')
+ f.write(raw)
+ f.close()
+
--- /dev/null
+<hr size="1"> </hr>
+<center>
+<small>Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a>
+and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>. </small>
+</center>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-15055292-3']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+</html>
--- /dev/null
+# Doxyfile 1.7.4\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project.\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored.\r
+# The format is:\r
+# TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+# TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ").\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# This tag specifies the encoding used for all characters in the config file\r
+# that follow. The default is UTF-8 which is also the encoding used for all\r
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the\r
+# iconv built into libc) for the transcoding. See\r
+# http://www.gnu.org/software/libiconv for the list of possible encodings.\r
+\r
+DOXYFILE_ENCODING = UTF-8\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded\r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME = \r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.\r
+# This could be handy for archiving the generated documentation or\r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER =\r
+\r
+# Using the PROJECT_BRIEF tag one can provide an optional one line description\r
+# for a project that appears at the top of each page and should give viewer\r
+# a quick idea about the purpose of the project. Keep the description short.\r
+\r
+PROJECT_BRIEF =\r
+\r
+# With the PROJECT_LOGO tag one can specify an logo or icon that is\r
+# included in the documentation. The maximum height of the logo should not\r
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.\r
+# Doxygen will copy the logo to the output directory.\r
+\r
+PROJECT_LOGO =\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)\r
+# base path where the generated documentation will be put.\r
+# If a relative path is entered, it will be relative to the location\r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY = \r
+\r
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create\r
+# 4096 sub-directories (in 2 levels) under the output directory of each output\r
+# format and will distribute the generated files over these directories.\r
+# Enabling this option can be useful when feeding doxygen a huge amount of\r
+# source files, where putting all generated files in the same directory would\r
+# otherwise cause performance problems for the file system.\r
+\r
+CREATE_SUBDIRS = NO\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all\r
+# documentation generated by doxygen is written. Doxygen will use this\r
+# information to generate all constant output in the proper language.\r
+# The default language is English, other supported languages are:\r
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,\r
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,\r
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English\r
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,\r
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,\r
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.\r
+\r
+OUTPUT_LANGUAGE = English\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will\r
+# include brief member descriptions after the members that are listed in\r
+# the file and class documentation (similar to JavaDoc).\r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend\r
+# the brief description of a member or function before the detailed description.\r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF = NO\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator\r
+# that is used to form the text in various listings. Each string\r
+# in this list, if found as the leading text of the brief description, will be\r
+# stripped from the text and the result after processing the whole list, is\r
+# used as the annotated text. Otherwise, the brief description is used as-is.\r
+# If left blank, the following values are used ("$name" is automatically\r
+# replaced with the name of the entity): "The $name class" "The $name widget"\r
+# "The $name file" "is" "provides" "specifies" "contains"\r
+# "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF =\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\r
+# Doxygen will generate a detailed section even if there is only a brief\r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC = YES\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\r
+# inherited members of a class in the documentation of that class as if those\r
+# members were ordinary class members. Constructors, destructors and assignment\r
+# operators of the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full\r
+# path before files name in the file list and in the header files. If set\r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag\r
+# can be used to strip a user-defined part of the path. Stripping is\r
+# only done if one of the specified strings matches the left-hand part of\r
+# the path. The tag can be used to show relative paths in the file list.\r
+# If left blank the directory from which doxygen is run is used as the\r
+# path to strip.\r
+\r
+STRIP_FROM_PATH =\r
+\r
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of\r
+# the path mentioned in the documentation of a class, which tells\r
+# the reader which header file to include in order to use a class.\r
+# If left blank only the name of the header file containing the class\r
+# definition is used. Otherwise one should specify the include paths that\r
+# are normally passed to the compiler using the -I flag.\r
+\r
+STRIP_FROM_INC_PATH =\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter\r
+# (but less readable) file names. This can be useful if your file system\r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen\r
+# will interpret the first line (until the first dot) of a JavaDoc-style\r
+# comment as the brief description. If set to NO, the JavaDoc\r
+# comments will behave just like regular Qt-style comments\r
+# (thus requiring an explicit @brief command for a brief description.)\r
+\r
+JAVADOC_AUTOBRIEF = NO\r
+\r
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will\r
+# interpret the first line (until the first dot) of a Qt-style\r
+# comment as the brief description. If set to NO, the comments\r
+# will behave just like regular Qt-style comments (thus requiring\r
+# an explicit \brief command for a brief description.)\r
+\r
+QT_AUTOBRIEF = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen\r
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///\r
+# comments) as a brief description. This used to be the default behaviour.\r
+# The new default is to treat a multi-line C++ comment block as a detailed\r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented\r
+# member inherits the documentation from any documented member that it\r
+# re-implements.\r
+\r
+INHERIT_DOCS = NO\r
+\r
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce\r
+# a new page for each member. If set to NO, the documentation of a member will\r
+# be part of the file/class/namespace that contains it.\r
+\r
+SEPARATE_MEMBER_PAGES = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.\r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts\r
+# as commands in the documentation. An alias has the form "name=value".\r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to\r
+# put the command \sideeffect (or @sideeffect) in the documentation, which\r
+# will result in a user-defined paragraph with heading "Side Effects:".\r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES = "prototype = @b Warning: This is a prototype" \\r
+ "privlevel = @xrefitem privlevel \"Privilege level\" \"Privilege Level\"" \\r
+ "privilege = @xrefitem privilege \"Privilege\" \"Privilege\"" \\r
+ "compatibility = @xrefitem compatibility \"Compatibility\" \"Compatibility \"" \\r
+ "feature = @xrefitem feature \"Required feature\" \"Required Feature \"" \\r
+ "final=\par Final:\n @xmlonly <pcheck-final>final</pcheck-final> @endxmlonly "\r
+ \r
+\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C\r
+# sources only. Doxygen will then generate output that is more tailored for C.\r
+# For instance, some of the names that are used will be different. The list\r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Java. For instance, namespaces will be presented as packages, qualified\r
+# scopes will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA = NO\r
+\r
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Fortran.\r
+\r
+OPTIMIZE_FOR_FORTRAN = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\r
+# sources. Doxygen will then generate output that is tailored for\r
+# VHDL.\r
+\r
+OPTIMIZE_OUTPUT_VHDL = NO\r
+\r
+# Doxygen selects the parser to use depending on the extension of the files it\r
+# parses. With this tag you can assign which parser to use for a given extension.\r
+# Doxygen has a built-in mapping, but you can override or extend it using this\r
+# tag. The format is ext=language, where ext is a file extension, and language\r
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,\r
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make\r
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C\r
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions\r
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.\r
+\r
+EXTENSION_MAPPING =\r
+\r
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\r
+# to include (a tag file for) the STL sources as input, then you should\r
+# set this tag to YES in order to let doxygen match functions declarations and\r
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.\r
+# func(std::string) {}). This also makes the inheritance and collaboration\r
+# diagrams that involve STL classes more complete and accurate.\r
+\r
+BUILTIN_STL_SUPPORT = NO\r
+\r
+# If you use Microsoft's C++/CLI language, you should set this option to YES to\r
+# enable parsing support.\r
+\r
+CPP_CLI_SUPPORT = NO\r
+\r
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.\r
+# Doxygen will parse them like normal C++ but will assume all classes use public\r
+# instead of private inheritance when no explicit protection keyword is present.\r
+\r
+SIP_SUPPORT = NO\r
+\r
+# For Microsoft's IDL there are propget and propput attributes to indicate getter\r
+# and setter methods for a property. Setting this option to YES (the default)\r
+# will make doxygen replace the get and set methods by a property in the\r
+# documentation. This will only work if the methods are indeed getting or\r
+# setting a simple type. If this is not the case, or you want to show the\r
+# methods anyway, you should set this option to NO.\r
+\r
+IDL_PROPERTY_SUPPORT = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\r
+# tag is set to YES, then doxygen will reuse the documentation of the first\r
+# member in the group (if any) for the other members of the group. By default\r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of\r
+# the same type (for instance a group of public functions) to be put as a\r
+# subgroup of that type (e.g. under the Public Functions section). Set it to\r
+# NO to prevent subgrouping. Alternatively, this can be done per class using\r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING = YES\r
+\r
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and\r
+# unions are shown inside the group in which they are included (e.g. using\r
+# @ingroup) instead of on a separate page (for HTML and Man pages) or\r
+# section (for LaTeX and RTF).\r
+\r
+INLINE_GROUPED_CLASSES = NO\r
+\r
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum\r
+# is documented as struct, union, or enum with the name of the typedef. So\r
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\r
+# with name TypeT. When disabled the typedef will appear as a member of a file,\r
+# namespace, or class. And the struct will be named TypeS. This can typically\r
+# be useful for C code in case the coding convention dictates that all compound\r
+# types are typedef'ed and only the typedef is referenced, never the tag name.\r
+\r
+TYPEDEF_HIDES_STRUCT = NO\r
+\r
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to\r
+# determine which symbols to keep in memory and which to flush to disk.\r
+# When the cache is full, less often used symbols will be written to disk.\r
+# For small to medium size projects (<1000 input files) the default value is\r
+# probably good enough. For larger projects a too small cache size can cause\r
+# doxygen to be busy swapping symbols to and from disk most of the time\r
+# causing a significant performance penalty.\r
+# If the system has enough physical memory increasing the cache will improve the\r
+# performance by keeping more symbols in memory. Note that the value works on\r
+# a logarithmic scale so increasing the size by one will roughly double the\r
+# memory usage. The cache size is given by this formula:\r
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,\r
+# corresponding to a cache size of 2^16 = 65536 symbols\r
+\r
+SYMBOL_CACHE_SIZE = 0\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in\r
+# documentation are documented, even if no documentation was available.\r
+# Private class members and static file members will be hidden unless\r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class\r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file\r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC = YES\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)\r
+# defined locally in source files will be included in the documentation.\r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES = NO\r
+\r
+# This flag is only useful for Objective-C code. When set to YES local\r
+# methods, which are defined in the implementation section but not in\r
+# the interface are included in the documentation.\r
+# If set to NO (the default) only methods in the interface are included.\r
+\r
+EXTRACT_LOCAL_METHODS = NO\r
+\r
+# If this flag is set to YES, the members of anonymous namespaces will be\r
+# extracted and appear in the documentation as a namespace called\r
+# 'anonymous_namespace{file}', where file will be replaced with the base\r
+# name of the file that contains the anonymous namespace. By default\r
+# anonymous namespaces are hidden.\r
+\r
+EXTRACT_ANON_NSPACES = NO\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\r
+# undocumented members of documented classes, files or namespaces.\r
+# If set to NO (the default) these members will be included in the\r
+# various overviews, but no documentation section is generated.\r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS = YES\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\r
+# undocumented classes that are normally visible in the class hierarchy.\r
+# If set to NO (the default) these classes will be included in the various\r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES = YES\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all\r
+# friend (class|struct|union) declarations.\r
+# If set to NO (the default) these declarations will be included in the\r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS = YES\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\r
+# documentation blocks found inside the body of a function.\r
+# If set to NO (the default) these blocks will be appended to the\r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS = YES\r
+\r
+# The INTERNAL_DOCS tag determines if documentation\r
+# that is typed after a \internal command is included. If the tag is set\r
+# to NO (the default) then the documentation will be excluded.\r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate\r
+# file names in lower-case letters. If set to YES upper-case letters are also\r
+# allowed. This is useful if you have classes or files whose names only differ\r
+# in case and if your file system supports case sensitive file names. Windows\r
+# and Mac users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen\r
+# will show members with their full class and namespace scopes in the\r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen\r
+# will put a list of the files that are included by a file in the documentation\r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES = NO\r
+\r
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen\r
+# will list include files with double quotes in the documentation\r
+# rather than with sharp brackets.\r
+\r
+FORCE_LOCAL_INCLUDES = NO\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]\r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen\r
+# will sort the (detailed) documentation of file and class members\r
+# alphabetically by member name. If set to NO the members will appear in\r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS = YES\r
+\r
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the\r
+# brief documentation of file, namespace and class members alphabetically\r
+# by member name. If set to NO (the default) the members will appear in\r
+# declaration order.\r
+\r
+SORT_BRIEF_DOCS = YES\r
+\r
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen\r
+# will sort the (brief and detailed) documentation of class members so that\r
+# constructors and destructors are listed first. If set to NO (the default)\r
+# the constructors will appear in the respective orders defined by\r
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.\r
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO\r
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.\r
+\r
+SORT_MEMBERS_CTORS_1ST = NO\r
+\r
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the\r
+# hierarchy of group names into alphabetical order. If set to NO (the default)\r
+# the group names will appear in their defined order.\r
+\r
+SORT_GROUP_NAMES = NO\r
+\r
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be\r
+# sorted by fully-qualified names, including namespaces. If set to\r
+# NO (the default), the class list will be sorted only by class name,\r
+# not including the namespace part.\r
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\r
+# Note: This option applies only to the class list, not to the\r
+# alphabetical list.\r
+\r
+SORT_BY_SCOPE_NAME = YES\r
+\r
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to\r
+# do proper type resolution of all parameters of a function it will reject a\r
+# match between the prototype and the implementation of a member function even\r
+# if there is only one candidate or it is obvious which candidate to choose\r
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen\r
+# will still accept a match between prototype and implementation in such cases.\r
+\r
+STRICT_PROTO_MATCHING = NO\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or\r
+# disable (NO) the todo list. This list is created by putting \todo\r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or\r
+# disable (NO) the test list. This list is created by putting \test\r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or\r
+# disable (NO) the bug list. This list is created by putting \bug\r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST = NO\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or\r
+# disable (NO) the deprecated list. This list is created by putting\r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional\r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines\r
+# the initial value of a variable or macro consists of for it to appear in\r
+# the documentation. If the initializer consists of more lines than specified\r
+# here it will be hidden. Use a value of 0 to hide initializers completely.\r
+# The appearance of the initializer of individual variables and macros in the\r
+# documentation can be controlled using \showinitializer or \hideinitializer\r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated\r
+# at the bottom of the documentation of classes and structs. If set to YES the\r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES = NO\r
+\r
+# If the sources in your project are distributed over multiple directories\r
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy\r
+# in the documentation. The default is NO.\r
+\r
+SHOW_DIRECTORIES = NO\r
+\r
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.\r
+# This will remove the Files entry from the Quick Index and from the\r
+# Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_FILES = YES\r
+\r
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the\r
+# Namespaces page.\r
+# This will remove the Namespaces entry from the Quick Index\r
+# and from the Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_NAMESPACES = YES\r
+\r
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that\r
+# doxygen should invoke to get the current version for each file (typically from\r
+# the version control system). Doxygen will invoke the program by executing (via\r
+# popen()) the command <command> <input-file>, where <command> is the value of\r
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file\r
+# provided by doxygen. Whatever the program writes to standard output\r
+# is used as the file version. See the manual for examples.\r
+\r
+FILE_VERSION_FILTER =\r
+\r
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\r
+# by doxygen. The layout file controls the global structure of the generated\r
+# output files in an output format independent way. The create the layout file\r
+# that represents doxygen's defaults, run doxygen with the -l option.\r
+# You can optionally specify a file name after the option, if omitted\r
+# DoxygenLayout.xml will be used as the name of the layout file.\r
+\r
+LAYOUT_FILE = DoxygenLayout.xml\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated\r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are\r
+# generated by doxygen. Possible values are YES and NO. If left blank\r
+# NO is used.\r
+\r
+WARNINGS = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings\r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will\r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED = YES\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for\r
+# potential errors in the documentation, such as not documenting some\r
+# parameters in a documented function, or documenting parameters that\r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR = YES\r
+\r
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for\r
+# functions that are documented, but have no documentation for their parameters\r
+# or return value. If set to NO (the default) doxygen will only warn about\r
+# wrong or incomplete parameter documentation, but not about the absence of\r
+# documentation.\r
+\r
+WARN_NO_PARAMDOC = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that\r
+# doxygen can produce. The string should contain the $file, $line, and $text\r
+# tags, which will be replaced by the file and line number from which the\r
+# warning originated and the warning text. Optionally the format may contain\r
+# $version, which will be replaced by the version of the file (if it could\r
+# be obtained via FILE_VERSION_FILTER)\r
+\r
+WARN_FORMAT = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning\r
+# and error messages should be written. If left blank the output is written\r
+# to stderr.\r
+\r
+WARN_LOGFILE = warning.txt\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain\r
+# documented source files. You may enter file names like "myfile.cpp" or\r
+# directories like "/usr/src/myproject". Separate the files or directories\r
+# with spaces.\r
+\r
+INPUT = ../../../../framework/osp/osp-appfw/inc \\r
+ ../../../../framework/osp/osp-bluetooth/inc \\r
+ ../../../../framework/osp/osp-content/inc \\r
+ ../../../../framework/osp/osp-face/inc \\r
+ ../../../../framework/osp/osp-image/inc \\r
+ ../../../../framework/osp/osp-image-core/inc \\r
+ ../../../../framework/osp/osp-ime/inc \\r
+ ../../../../framework/osp/osp-json/inc \\r
+ ../../../../framework/osp/osp-locations/inc \\r
+ ../../../../framework/osp/osp-media/inc \\r
+ ../../../../framework/osp/osp-messaging/inc \\r
+ ../../../../framework/osp/osp-net/inc \\r
+ ../../../../framework/osp/osp-nfc/inc \\r
+ ../../../../framework/osp/osp-secure-element/inc \ \r
+ ../../../../framework/osp/osp-shell/inc \\r
+ ../../../../framework/osp/osp-social/inc \\r
+ ../../../../framework/osp/osp-speech/inc \\r
+ ../../../../framework/osp/osp-telephony/inc \\r
+ ../../../../framework/osp/osp-uifw/inc \\r
+ ../../../../framework/osp/osp-uix/inc \\r
+ ../../../../framework/osp/osp-vision/inc \\r
+ ../../../../framework/osp/osp-web/inc \\r
+ ./libraries\r
+\r
+# This tag can be used to specify the character encoding of the source files\r
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is\r
+# also the default input encoding. Doxygen uses libiconv (or the iconv built\r
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for\r
+# the list of possible encodings.\r
+\r
+INPUT_ENCODING = UTF-8\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank the following patterns are tested:\r
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh\r
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py\r
+# *.f90 *.f *.for *.vhd *.vhdl\r
+\r
+FILE_PATTERNS = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories\r
+# should be searched for input files as well. Possible values are YES and NO.\r
+# If left blank NO is used.\r
+\r
+RECURSIVE = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should\r
+# excluded from the INPUT source files. This way you can easily exclude a\r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE = ../../../../framework/osp/osp-appfw/inc/FBaseSysLog.h \\r
+ ../../../../framework/osp/osp-appfw/inc/FXml.h \\r
+ ./libraries/newlib\r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or\r
+# directories that are symbolic links (a Unix file system feature) are excluded\r
+# from the input.\r
+\r
+EXCLUDE_SYMLINKS = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\r
+# certain files from those directories. Note that the wildcards are matched\r
+# against the file with absolute path, so to exclude all test directories\r
+# for example use the pattern */test/*\r
+\r
+EXCLUDE_PATTERNS = \r
+\r
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\r
+# (namespaces, classes, functions, etc.) that should be excluded from the\r
+# output. The symbol name can be a fully qualified name, a word, or if the\r
+# wildcard * is used, a substring. Examples: ANamespace, AClass,\r
+# AClass::ANamespace, ANamespace::*Test\r
+\r
+EXCLUDE_SYMBOLS =\r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or\r
+# directories that contain example code fragments that are included (see\r
+# the \include command).\r
+\r
+EXAMPLE_PATH = \r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the\r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS = \r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\r
+# searched for input files to be used with the \include or \dontinclude\r
+# commands irrespective of the value of the RECURSIVE tag.\r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or\r
+# directories that contain image that are included in the documentation (see\r
+# the \image command).\r
+\r
+IMAGE_PATH = images\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should\r
+# invoke to filter for each input file. Doxygen will invoke the filter program\r
+# by executing (via popen()) the command <filter> <input-file>, where <filter>\r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an\r
+# input file. Doxygen will then use the output that the filter program writes\r
+# to standard output.\r
+# If FILTER_PATTERNS is specified, this tag will be\r
+# ignored.\r
+\r
+INPUT_FILTER =\r
+\r
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\r
+# basis.\r
+# Doxygen will compare the file name with each pattern and apply the\r
+# filter if there is a match.\r
+# The filters are a list of the form:\r
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further\r
+# info on how filters are used. If FILTER_PATTERNS is empty or if\r
+# non of the patterns match the file name, INPUT_FILTER is applied.\r
+\r
+FILTER_PATTERNS =\r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\r
+# INPUT_FILTER) will be used to filter the input files when producing source\r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES = NO\r
+\r
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\r
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)\r
+# and it is also possible to disable source filtering for a specific pattern\r
+# using *.ext= (so without naming a filter). This option only has effect when\r
+# FILTER_SOURCE_FILES is enabled.\r
+\r
+FILTER_SOURCE_PATTERNS =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will\r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+# Note: To get rid of all source code in the generated output, make sure also\r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body\r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct\r
+# doxygen to hide any special comment blocks from generated source code\r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES\r
+# then for each documented function all documented\r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = NO\r
+\r
+# If the REFERENCES_RELATION tag is set to YES\r
+# then for each documented function all documented entities\r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION = NO\r
+\r
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\r
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\r
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\r
+# link to the source code.\r
+# Otherwise they will link to the documentation.\r
+\r
+REFERENCES_LINK_SOURCE = NO\r
+\r
+# If the USE_HTAGS tag is set to YES then the references to source code\r
+# will point to the HTML generated by the htags(1) tool instead of doxygen\r
+# built-in source browser. The htags tool is part of GNU's global source\r
+# tagging system (see http://www.gnu.org/software/global/global.html). You\r
+# will need version 4.8.6 or higher.\r
+\r
+USE_HTAGS = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen\r
+# will generate a verbatim copy of the header file for each class for\r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index\r
+# of all compounds will be generated. Enable this if the project\r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then\r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns\r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX = 5\r
+\r
+# In case all classes in a project start with a common prefix, all\r
+# classes will be put under the same header in the alphabetical index.\r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that\r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will\r
+# generate HTML output.\r
+\r
+GENERATE_HTML = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT = apidocs\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for\r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank\r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard header. Note that when using a custom header you are responsible\r
+# for the proper inclusion of any scripts and style sheets that doxygen\r
+# needs, which is dependent on the configuration options used.\r
+# It is adviced to generate a default header using "doxygen -w html\r
+# header.html footer.html stylesheet.css YourConfigFile" and then modify\r
+# that header. Note that the header is subject to change so you typically\r
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!\r
+\r
+HTML_HEADER =\r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard footer.\r
+\r
+HTML_FOOTER = footer.html\r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading\r
+# style sheet that is used by each HTML page. It can be used to\r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen\r
+# will generate a default style sheet. Note that doxygen will try to copy\r
+# the style sheet file to the HTML output directory, so don't put your own\r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET = Tizen.css\r
+\r
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\r
+# other source files which should be copied to the HTML output directory. Note\r
+# that these files will be copied to the base HTML output directory. Use the\r
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\r
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that\r
+# the files will be copied as-is; there are no commands or markers available.\r
+\r
+HTML_EXTRA_FILES =\r
+\r
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.\r
+# Doxygen will adjust the colors in the stylesheet and background images\r
+# according to this color. Hue is specified as an angle on a colorwheel,\r
+# see http://en.wikipedia.org/wiki/Hue for more information.\r
+# For instance the value 0 represents red, 60 is yellow, 120 is green,\r
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.\r
+# The allowed range is 0 to 359.\r
+\r
+HTML_COLORSTYLE_HUE = 220\r
+\r
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of\r
+# the colors in the HTML output. For a value of 0 the output will use\r
+# grayscales only. A value of 255 will produce the most vivid colors.\r
+\r
+HTML_COLORSTYLE_SAT = 100\r
+\r
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to\r
+# the luminance component of the colors in the HTML output. Values below\r
+# 100 gradually make the output lighter, whereas values above 100 make\r
+# the output darker. The value divided by 100 is the actual gamma applied,\r
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,\r
+# and 100 does not change the gamma.\r
+\r
+HTML_COLORSTYLE_GAMMA = 80\r
+\r
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\r
+# page will contain the date and time when the page was generated. Setting\r
+# this to NO can help when comparing the output of multiple runs.\r
+\r
+HTML_TIMESTAMP = YES\r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,\r
+# files or namespaces will be aligned in HTML using tables. If set to\r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS = YES\r
+\r
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\r
+# documentation will contain sections that can be hidden and shown after the\r
+# page has loaded. For this to work a browser that supports\r
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox\r
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).\r
+\r
+HTML_DYNAMIC_SECTIONS = NO\r
+\r
+# If the GENERATE_DOCSET tag is set to YES, additional index files\r
+# will be generated that can be used as input for Apple's Xcode 3\r
+# integrated development environment, introduced with OSX 10.5 (Leopard).\r
+# To create a documentation set, doxygen will generate a Makefile in the\r
+# HTML output directory. Running make will produce the docset in that\r
+# directory and running "make install" will install the docset in\r
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find\r
+# it at startup.\r
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html\r
+# for more information.\r
+\r
+GENERATE_DOCSET = NO\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the\r
+# feed. A documentation feed provides an umbrella under which multiple\r
+# documentation sets from a single provider (such as a company or product suite)\r
+# can be grouped.\r
+\r
+DOCSET_FEEDNAME = "Doxygen generated docs"\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that\r
+# should uniquely identify the documentation set bundle. This should be a\r
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen\r
+# will append .docset to the name.\r
+\r
+DOCSET_BUNDLE_ID = org.doxygen.Project\r
+\r
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify\r
+# the documentation publisher. This should be a reverse domain-name style\r
+# string, e.g. com.mycompany.MyDocSet.documentation.\r
+\r
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher\r
+\r
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.\r
+\r
+DOCSET_PUBLISHER_NAME = Publisher\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files\r
+# will be generated that can be used as input for tools like the\r
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)\r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can\r
+# be used to specify the file name of the resulting .chm file. You\r
+# can add a path in front of the file if the result should not be\r
+# written to the html output directory.\r
+\r
+CHM_FILE =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can\r
+# be used to specify the location (absolute path including file name) of\r
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run\r
+# the HTML help compiler on the generated index.hhp.\r
+\r
+HHC_LOCATION =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag\r
+# controls if a separate .chi index file is generated (YES) or that\r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\r
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file\r
+# content.\r
+\r
+CHM_INDEX_ENCODING =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag\r
+# controls whether a binary table of contents is generated (YES) or a\r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC = YES\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members\r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND = YES\r
+\r
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\r
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated\r
+# that can be used as input for Qt's qhelpgenerator to generate a\r
+# Qt Compressed Help (.qch) of the generated HTML documentation.\r
+\r
+GENERATE_QHP = NO\r
+\r
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can\r
+# be used to specify the file name of the resulting .qch file.\r
+# The path specified is relative to the HTML output folder.\r
+\r
+QCH_FILE =\r
+\r
+# The QHP_NAMESPACE tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#namespace\r
+\r
+QHP_NAMESPACE = org.doxygen.Project\r
+\r
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders\r
+\r
+QHP_VIRTUAL_FOLDER = doc\r
+\r
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to\r
+# add. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#custom-filters\r
+\r
+QHP_CUST_FILTER_NAME =\r
+\r
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the\r
+# custom filter to add. For more information please see\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">\r
+# Qt Help Project / Custom Filters</a>.\r
+\r
+QHP_CUST_FILTER_ATTRS =\r
+\r
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\r
+# project's\r
+# filter section matches.\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">\r
+# Qt Help Project / Filter Attributes</a>.\r
+\r
+QHP_SECT_FILTER_ATTRS =\r
+\r
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can\r
+# be used to specify the location of Qt's qhelpgenerator.\r
+# If non-empty doxygen will try to run qhelpgenerator on the generated\r
+# .qhp file.\r
+\r
+QHG_LOCATION =\r
+\r
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files\r
+# will be generated, which together with the HTML files, form an Eclipse help\r
+# plugin. To install this plugin and make it available under the help contents\r
+# menu in Eclipse, the contents of the directory containing the HTML and XML\r
+# files needs to be copied into the plugins directory of eclipse. The name of\r
+# the directory within the plugins directory should be the same as\r
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before\r
+# the help appears.\r
+\r
+GENERATE_ECLIPSEHELP = YES\r
+\r
+# A unique identifier for the eclipse help plugin. When installing the plugin\r
+# the directory name containing the HTML and XML files should also have\r
+# this name.\r
+\r
+ECLIPSE_DOC_ID = org.doxygen.Project\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at\r
+# top of each HTML page. The value NO (the default) enables the index and\r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX = NO\r
+\r
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values\r
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML\r
+# documentation. Note that a value of 0 will completely suppress the enum\r
+# values from appearing in the overview section.\r
+\r
+ENUM_VALUES_PER_LINE = 4\r
+\r
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\r
+# structure should be generated to display hierarchical information.\r
+# If the tag value is set to YES, a side panel will be generated\r
+# containing a tree-like index structure (just like the one that\r
+# is generated for HTML Help). For this to work a browser that supports\r
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).\r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW = NO\r
+\r
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,\r
+# and Class Hierarchy pages using a tree view instead of an ordered list.\r
+\r
+USE_INLINE_TREES = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be\r
+# used to set the initial width (in pixels) of the frame in which the tree\r
+# is shown.\r
+\r
+TREEVIEW_WIDTH = 250\r
+\r
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open\r
+# links to external symbols imported via tag files in a separate window.\r
+\r
+EXT_LINKS_IN_WINDOW = NO\r
+\r
+# Use this tag to change the font size of Latex formulas included\r
+# as images in the HTML documentation. The default is 10. Note that\r
+# when you change the font size after a successful doxygen run you need\r
+# to manually remove any form_*.png images from the HTML output directory\r
+# to force them to be regenerated.\r
+\r
+FORMULA_FONTSIZE = 10\r
+\r
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images\r
+# generated for formulas are transparent PNGs. Transparent PNGs are\r
+# not supported properly for IE 6.0, but are supported on all modern browsers.\r
+# Note that when changing this option you need to delete any form_*.png files\r
+# in the HTML output before the changes have effect.\r
+\r
+FORMULA_TRANSPARENT = YES\r
+\r
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax\r
+# (see http://www.mathjax.org) which uses client side Javascript for the\r
+# rendering instead of using prerendered bitmaps. Use this if you do not\r
+# have LaTeX installed or if you want to formulas look prettier in the HTML\r
+# output. When enabled you also need to install MathJax separately and\r
+# configure the path to it using the MATHJAX_RELPATH option.\r
+\r
+USE_MATHJAX = NO\r
+\r
+# When MathJax is enabled you need to specify the location relative to the\r
+# HTML output directory using the MATHJAX_RELPATH option. The destination\r
+# directory should contain the MathJax.js script. For instance, if the mathjax\r
+# directory is located at the same level as the HTML output directory, then\r
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the\r
+# mathjax.org site, so you can quickly see the result without installing\r
+# MathJax, but it is strongly recommended to install a local copy of MathJax\r
+# before deployment.\r
+\r
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax\r
+\r
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box\r
+# for the HTML output. The underlying search engine uses javascript\r
+# and DHTML and should work on any modern browser. Note that when using\r
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets\r
+# (GENERATE_DOCSET) there is already a search function so this one should\r
+# typically be disabled. For large projects the javascript based search engine\r
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.\r
+\r
+SEARCHENGINE = NO\r
+\r
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be\r
+# implemented using a PHP enabled web server instead of at the web client\r
+# using Javascript. Doxygen will generate the search PHP script and index\r
+# file to put on the web server. The advantage of the server\r
+# based approach is that it scales better to large projects and allows\r
+# full text search. The disadvantages are that it is more difficult to setup\r
+# and does not have live searching capabilities.\r
+\r
+SERVER_BASED_SEARCH = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will\r
+# generate Latex output.\r
+\r
+GENERATE_LATEX = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be\r
+# invoked. If left blank `latex' will be used as the default command name.\r
+# Note that when enabling USE_PDFLATEX this option is only used for\r
+# generating bitmaps for formulas in the HTML output, but not in the\r
+# Makefile that is written to the output directory.\r
+\r
+LATEX_CMD_NAME = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to\r
+# generate index for LaTeX. If left blank `makeindex' will be used as the\r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact\r
+# LaTeX documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_LATEX = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used\r
+# by the printer. Possible values are: a4, letter, legal and\r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX\r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES =\r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for\r
+# the generated latex document. The header should contain everything until\r
+# the first chapter. If it is left blank doxygen will generate a\r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER =\r
+\r
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for\r
+# the generated latex document. The footer should contain everything after\r
+# the last chapter. If it is left blank doxygen will generate a\r
+# standard footer. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_FOOTER =\r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated\r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will\r
+# contain links (just like the HTML output) instead of page references\r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of\r
+# plain latex in the generated Makefile. Set this option to YES to get a\r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.\r
+# command to the generated LaTeX files. This will instruct LaTeX to keep\r
+# running if errors occur, instead of asking the user for help.\r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not\r
+# include the index chapters (such as File Index, Compound Index, etc.)\r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES = NO\r
+\r
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include\r
+# source code with syntax highlighting in the LaTeX output.\r
+# Note that which sources are shown also depends on other settings\r
+# such as SOURCE_BROWSER.\r
+\r
+LATEX_SOURCE_CODE = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output\r
+# The RTF output is optimized for Word 97 and may not look very pretty with\r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact\r
+# RTF documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_RTF = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated\r
+# will contain hyperlink fields. The RTF file will\r
+# contain links (just like the HTML output) instead of page references.\r
+# This makes the output suitable for online browsing using WORD or other\r
+# programs which support those fields.\r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's\r
+# config file, i.e. a series of assignments. You only have to provide\r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE =\r
+\r
+# Set optional variables used in the generation of an rtf document.\r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will\r
+# generate man pages\r
+\r
+GENERATE_MAN = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to\r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,\r
+# then it will generate one additional man file for each entity\r
+# documented in the real man page(s). These additional files\r
+# only source the real man page, but without them the man command\r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will\r
+# generate an XML file that captures the structure of\r
+# the code including all documentation.\r
+\r
+GENERATE_XML = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT = _xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA =\r
+\r
+# The XML_DTD tag can be used to specify an XML DTD,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_DTD =\r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will\r
+# dump the program listings (including syntax highlighting\r
+# and cross-referencing information) to the XML output. Note that\r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will\r
+# generate an AutoGen Definitions (see autogen.sf.net) file\r
+# that captures the structure of the code including all\r
+# documentation. Note that this feature is still experimental\r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will\r
+# generate a Perl module file that captures the structure of\r
+# the code including all documentation. Note that this\r
+# feature is still experimental and incomplete at the\r
+# moment.\r
+\r
+GENERATE_PERLMOD = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate\r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able\r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be\r
+# nicely formatted so it can be parsed by a human reader.\r
+# This is useful\r
+# if you want to understand what is going on.\r
+# On the other hand, if this\r
+# tag is set to NO the size of the Perl module output will be much smaller\r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file\r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.\r
+# This is useful so different doxyrules.make files included by the same\r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will\r
+# evaluate all C-preprocessor directives found in the sources and include\r
+# files.\r
+\r
+ENABLE_PREPROCESSING = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro\r
+# names in the source code. If set to NO (the default) only conditional\r
+# compilation will be performed. Macro expansion can be done in a controlled\r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES\r
+# then the macro expansion is limited to the macros specified with the\r
+# PREDEFINED and EXPAND_AS_DEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF = YES\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files\r
+# pointed to by INCLUDE_PATH will be searched when a #include is found.\r
+\r
+SEARCH_INCLUDES = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that\r
+# contain include files that are not input files but should be processed by\r
+# the preprocessor.\r
+\r
+INCLUDE_PATH =\r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard\r
+# patterns (like *.h and *.hpp) to filter out the header-files in the\r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will\r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS =\r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that\r
+# are defined before the preprocessor is started (similar to the -D option of\r
+# gcc). The argument of the tag is a list of macros of the form: name\r
+# or name=definition (no spaces). If the definition and the = are\r
+# omitted =1 is assumed. To prevent a macro definition from being\r
+# undefined via #undef or recursively expanded use the := operator\r
+# instead of the = operator.\r
+\r
+PREDEFINED = LIBXML_OUTPUT_ENABLED LIBXML_PUSH_ENABLED LIBXML_TREE_ENABLED LIBXML_HTML_ENABLED GL_API GL_APICALL _OSP_EXPORT_ _OSP_LOCAL_\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then\r
+# this tag can be used to specify a list of macro names that should be expanded.\r
+# The macro definition that is found in the sources will be used.\r
+# Use the PREDEFINED tag if you want to use a different macro definition that\r
+# overrules the definition found in the source code.\r
+\r
+EXPAND_AS_DEFINED =\r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then\r
+# doxygen's preprocessor will remove all references to function-like macros\r
+# that are alone on a line, have an all uppercase name, and do not end with a\r
+# semicolon, because these will confuse the parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::additions related to external references\r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles.\r
+# Optionally an initial location of the external documentation\r
+# can be added for each tagfile. The format of a tag file without\r
+# this location is as follows:\r
+#\r
+# TAGFILES = file1 file2 ...\r
+# Adding location for the tag files is done as follows:\r
+#\r
+# TAGFILES = file1=loc1 "file2 = loc2" ...\r
+# where "loc1" and "loc2" can be relative or absolute paths or\r
+# URLs. If a location is present for each tag, the installdox tool\r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen\r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES =\r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create\r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE =\r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed\r
+# in the class index. If set to NO only the inherited external classes\r
+# will be listed.\r
+\r
+ALLEXTERNALS = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed\r
+# in the modules index. If set to NO, only the current project's groups will\r
+# be listed.\r
+\r
+EXTERNAL_GROUPS = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script\r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool\r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will\r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base\r
+# or super classes. Setting the tag to NO turns the diagrams off. Note that\r
+# this option also works with HAVE_DOT disabled, but it is recommended to\r
+# install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS = YES\r
+\r
+# You can define message sequence charts within doxygen comments using the \msc\r
+# command. Doxygen will then run the mscgen tool (see\r
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the\r
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where\r
+# the mscgen tool resides. If left empty the tool is assumed to be found in the\r
+# default search path.\r
+\r
+MSCGEN_PATH =\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide\r
+# inheritance and usage relations if the target is undocumented\r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\r
+# available from the path. This tool is part of Graphviz, a graph visualization\r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section\r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT = NO\r
+\r
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is\r
+# allowed to run in parallel. When set to 0 (the default) doxygen will\r
+# base this on the number of processors available in the system. You can set it\r
+# explicitly to a value larger than 0 to get control over the balance\r
+# between CPU load and processing speed.\r
+\r
+DOT_NUM_THREADS = 0\r
+\r
+# By default doxygen will write a font called Helvetica to the output\r
+# directory and reference it in all dot files that doxygen generates.\r
+# When you want a differently looking font you can specify the font name\r
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,\r
+# which can be done by putting it in a standard location or by setting the\r
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory\r
+# containing the font.\r
+\r
+DOT_FONTNAME = FreeSans\r
+\r
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.\r
+# The default size is 10pt.\r
+\r
+DOT_FONTSIZE = 10\r
+\r
+# By default doxygen will tell dot to use the output directory to look for the\r
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a\r
+# different font using DOT_FONTNAME you can set the path where dot\r
+# can find it using this tag.\r
+\r
+DOT_FONTPATH =\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect inheritance relations. Setting this tag to YES will force the\r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect implementation dependencies (inheritance, containment, and\r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH = YES\r
+\r
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for groups, showing the direct groups dependencies\r
+\r
+GROUP_GRAPHS = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and\r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling\r
+# Language.\r
+\r
+UML_LOOK = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the\r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT\r
+# tags are set to YES then doxygen will generate a graph for each documented\r
+# file showing the direct and indirect include dependencies of the file with\r
+# other documented files.\r
+\r
+INCLUDE_GRAPH = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and\r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each\r
+# documented header file showing the documented files that directly or\r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then\r
+# doxygen will generate a call dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable call graphs\r
+# for selected functions only using the \callgraph command.\r
+\r
+CALL_GRAPH = NO\r
+\r
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then\r
+# doxygen will generate a caller dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable caller\r
+# graphs for selected functions only using the \callergraph command.\r
+\r
+CALLER_GRAPH = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY = YES\r
+\r
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES\r
+# then doxygen will show the dependencies a directory has on other directories\r
+# in a graphical way. The dependency relations are determined by the #include\r
+# relations between the files in the directories.\r
+\r
+DIRECTORY_GRAPH = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\r
+# generated by dot. Possible values are svg, png, jpg, or gif.\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be\r
+# found. If left blank, it is assumed the dot tool can be found in the path.\r
+\r
+DOT_PATH =\r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that\r
+# contain dot files that are included in the documentation (see the\r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS =\r
+\r
+# The MSCFILE_DIRS tag can be used to specify one or more directories that\r
+# contain msc files that are included in the documentation (see the\r
+# \mscfile command).\r
+\r
+MSCFILE_DIRS =\r
+\r
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of\r
+# nodes that will be shown in the graph. If the number of nodes in a graph\r
+# becomes larger than this value, doxygen will truncate the graph, which is\r
+# visualized by representing a node as a red box. Note that doxygen if the\r
+# number of direct children of the root node in a graph is already larger than\r
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note\r
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\r
+\r
+DOT_GRAPH_MAX_NODES = 50\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the\r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable\r
+# from the root by following a path via at most 3 edges will be shown. Nodes\r
+# that lay further from the root node will be omitted. Note that setting this\r
+# option to 1 or 2 may greatly reduce the computation time needed for large\r
+# code bases. Also note that the size of a graph can be further restricted by\r
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\r
+\r
+MAX_DOT_GRAPH_DEPTH = 0\r
+\r
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent\r
+# background. This is disabled by default, because dot on Windows does not\r
+# seem to support this out of the box. Warning: Depending on the platform used,\r
+# enabling this option may lead to badly anti-aliased labels on the edges of\r
+# a graph (i.e. they become hard to read).\r
+\r
+DOT_TRANSPARENT = NO\r
+\r
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output\r
+# files in one run (i.e. multiple -o and -T options on the command line). This\r
+# makes dot run faster, but since only newer versions of dot (>1.8.10)\r
+# support this, this feature is disabled by default.\r
+\r
+DOT_MULTI_TARGETS = NO\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will\r
+# generate a legend page explaining the meaning of the various boxes and\r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will\r
+# remove the intermediate dot files that are used to generate\r
+# the various graphs.\r
+\r
+DOT_CLEANUP = YES\r
--- /dev/null
+# Doxyfile 1.7.4\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project.\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored.\r
+# The format is:\r
+# TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+# TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ").\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# This tag specifies the encoding used for all characters in the config file\r
+# that follow. The default is UTF-8 which is also the encoding used for all\r
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the\r
+# iconv built into libc) for the transcoding. See\r
+# http://www.gnu.org/software/libiconv for the list of possible encodings.\r
+\r
+DOXYFILE_ENCODING = UTF-8\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded\r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME = \r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.\r
+# This could be handy for archiving the generated documentation or\r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER =\r
+\r
+# Using the PROJECT_BRIEF tag one can provide an optional one line description\r
+# for a project that appears at the top of each page and should give viewer\r
+# a quick idea about the purpose of the project. Keep the description short.\r
+\r
+PROJECT_BRIEF =\r
+\r
+# With the PROJECT_LOGO tag one can specify an logo or icon that is\r
+# included in the documentation. The maximum height of the logo should not\r
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.\r
+# Doxygen will copy the logo to the output directory.\r
+\r
+PROJECT_LOGO =\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)\r
+# base path where the generated documentation will be put.\r
+# If a relative path is entered, it will be relative to the location\r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY = \r
+\r
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create\r
+# 4096 sub-directories (in 2 levels) under the output directory of each output\r
+# format and will distribute the generated files over these directories.\r
+# Enabling this option can be useful when feeding doxygen a huge amount of\r
+# source files, where putting all generated files in the same directory would\r
+# otherwise cause performance problems for the file system.\r
+\r
+CREATE_SUBDIRS = NO\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all\r
+# documentation generated by doxygen is written. Doxygen will use this\r
+# information to generate all constant output in the proper language.\r
+# The default language is English, other supported languages are:\r
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,\r
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,\r
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English\r
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,\r
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,\r
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.\r
+\r
+OUTPUT_LANGUAGE = English\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will\r
+# include brief member descriptions after the members that are listed in\r
+# the file and class documentation (similar to JavaDoc).\r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend\r
+# the brief description of a member or function before the detailed description.\r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF = NO\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator\r
+# that is used to form the text in various listings. Each string\r
+# in this list, if found as the leading text of the brief description, will be\r
+# stripped from the text and the result after processing the whole list, is\r
+# used as the annotated text. Otherwise, the brief description is used as-is.\r
+# If left blank, the following values are used ("$name" is automatically\r
+# replaced with the name of the entity): "The $name class" "The $name widget"\r
+# "The $name file" "is" "provides" "specifies" "contains"\r
+# "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF =\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\r
+# Doxygen will generate a detailed section even if there is only a brief\r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC = YES\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\r
+# inherited members of a class in the documentation of that class as if those\r
+# members were ordinary class members. Constructors, destructors and assignment\r
+# operators of the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full\r
+# path before files name in the file list and in the header files. If set\r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag\r
+# can be used to strip a user-defined part of the path. Stripping is\r
+# only done if one of the specified strings matches the left-hand part of\r
+# the path. The tag can be used to show relative paths in the file list.\r
+# If left blank the directory from which doxygen is run is used as the\r
+# path to strip.\r
+\r
+STRIP_FROM_PATH =\r
+\r
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of\r
+# the path mentioned in the documentation of a class, which tells\r
+# the reader which header file to include in order to use a class.\r
+# If left blank only the name of the header file containing the class\r
+# definition is used. Otherwise one should specify the include paths that\r
+# are normally passed to the compiler using the -I flag.\r
+\r
+STRIP_FROM_INC_PATH =\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter\r
+# (but less readable) file names. This can be useful if your file system\r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen\r
+# will interpret the first line (until the first dot) of a JavaDoc-style\r
+# comment as the brief description. If set to NO, the JavaDoc\r
+# comments will behave just like regular Qt-style comments\r
+# (thus requiring an explicit @brief command for a brief description.)\r
+\r
+JAVADOC_AUTOBRIEF = NO\r
+\r
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will\r
+# interpret the first line (until the first dot) of a Qt-style\r
+# comment as the brief description. If set to NO, the comments\r
+# will behave just like regular Qt-style comments (thus requiring\r
+# an explicit \brief command for a brief description.)\r
+\r
+QT_AUTOBRIEF = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen\r
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///\r
+# comments) as a brief description. This used to be the default behaviour.\r
+# The new default is to treat a multi-line C++ comment block as a detailed\r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented\r
+# member inherits the documentation from any documented member that it\r
+# re-implements.\r
+\r
+INHERIT_DOCS = NO\r
+\r
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce\r
+# a new page for each member. If set to NO, the documentation of a member will\r
+# be part of the file/class/namespace that contains it.\r
+\r
+SEPARATE_MEMBER_PAGES = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.\r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts\r
+# as commands in the documentation. An alias has the form "name=value".\r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to\r
+# put the command \sideeffect (or @sideeffect) in the documentation, which\r
+# will result in a user-defined paragraph with heading "Side Effects:".\r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES = "prototype = @b Warning: This is a prototype" \\r
+ "privlevel = @xrefitem privlevel \"Privilege level\" \"Privilege Level\"" \\r
+ "privilege = @xrefitem privilege \"Privilege\" \"Privilege\"" \\r
+ "compatibility = @xrefitem compatibility \"Compatibility\" \"Compatibility \"" \\r
+ "feature = @xrefitem feature \"Required feature\" \"Required Feature \"" \\r
+ "final=\par Final:\n @xmlonly <pcheck-final>final</pcheck-final> @endxmlonly "\r
+\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C\r
+# sources only. Doxygen will then generate output that is more tailored for C.\r
+# For instance, some of the names that are used will be different. The list\r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Java. For instance, namespaces will be presented as packages, qualified\r
+# scopes will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA = NO\r
+\r
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Fortran.\r
+\r
+OPTIMIZE_FOR_FORTRAN = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\r
+# sources. Doxygen will then generate output that is tailored for\r
+# VHDL.\r
+\r
+OPTIMIZE_OUTPUT_VHDL = NO\r
+\r
+# Doxygen selects the parser to use depending on the extension of the files it\r
+# parses. With this tag you can assign which parser to use for a given extension.\r
+# Doxygen has a built-in mapping, but you can override or extend it using this\r
+# tag. The format is ext=language, where ext is a file extension, and language\r
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,\r
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make\r
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C\r
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions\r
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.\r
+\r
+EXTENSION_MAPPING =\r
+\r
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\r
+# to include (a tag file for) the STL sources as input, then you should\r
+# set this tag to YES in order to let doxygen match functions declarations and\r
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.\r
+# func(std::string) {}). This also makes the inheritance and collaboration\r
+# diagrams that involve STL classes more complete and accurate.\r
+\r
+BUILTIN_STL_SUPPORT = NO\r
+\r
+# If you use Microsoft's C++/CLI language, you should set this option to YES to\r
+# enable parsing support.\r
+\r
+CPP_CLI_SUPPORT = NO\r
+\r
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.\r
+# Doxygen will parse them like normal C++ but will assume all classes use public\r
+# instead of private inheritance when no explicit protection keyword is present.\r
+\r
+SIP_SUPPORT = NO\r
+\r
+# For Microsoft's IDL there are propget and propput attributes to indicate getter\r
+# and setter methods for a property. Setting this option to YES (the default)\r
+# will make doxygen replace the get and set methods by a property in the\r
+# documentation. This will only work if the methods are indeed getting or\r
+# setting a simple type. If this is not the case, or you want to show the\r
+# methods anyway, you should set this option to NO.\r
+\r
+IDL_PROPERTY_SUPPORT = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\r
+# tag is set to YES, then doxygen will reuse the documentation of the first\r
+# member in the group (if any) for the other members of the group. By default\r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of\r
+# the same type (for instance a group of public functions) to be put as a\r
+# subgroup of that type (e.g. under the Public Functions section). Set it to\r
+# NO to prevent subgrouping. Alternatively, this can be done per class using\r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING = YES\r
+\r
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and\r
+# unions are shown inside the group in which they are included (e.g. using\r
+# @ingroup) instead of on a separate page (for HTML and Man pages) or\r
+# section (for LaTeX and RTF).\r
+\r
+INLINE_GROUPED_CLASSES = NO\r
+\r
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum\r
+# is documented as struct, union, or enum with the name of the typedef. So\r
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\r
+# with name TypeT. When disabled the typedef will appear as a member of a file,\r
+# namespace, or class. And the struct will be named TypeS. This can typically\r
+# be useful for C code in case the coding convention dictates that all compound\r
+# types are typedef'ed and only the typedef is referenced, never the tag name.\r
+\r
+TYPEDEF_HIDES_STRUCT = NO\r
+\r
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to\r
+# determine which symbols to keep in memory and which to flush to disk.\r
+# When the cache is full, less often used symbols will be written to disk.\r
+# For small to medium size projects (<1000 input files) the default value is\r
+# probably good enough. For larger projects a too small cache size can cause\r
+# doxygen to be busy swapping symbols to and from disk most of the time\r
+# causing a significant performance penalty.\r
+# If the system has enough physical memory increasing the cache will improve the\r
+# performance by keeping more symbols in memory. Note that the value works on\r
+# a logarithmic scale so increasing the size by one will roughly double the\r
+# memory usage. The cache size is given by this formula:\r
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,\r
+# corresponding to a cache size of 2^16 = 65536 symbols\r
+\r
+SYMBOL_CACHE_SIZE = 0\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in\r
+# documentation are documented, even if no documentation was available.\r
+# Private class members and static file members will be hidden unless\r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class\r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file\r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC = YES\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)\r
+# defined locally in source files will be included in the documentation.\r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES = NO\r
+\r
+# This flag is only useful for Objective-C code. When set to YES local\r
+# methods, which are defined in the implementation section but not in\r
+# the interface are included in the documentation.\r
+# If set to NO (the default) only methods in the interface are included.\r
+\r
+EXTRACT_LOCAL_METHODS = NO\r
+\r
+# If this flag is set to YES, the members of anonymous namespaces will be\r
+# extracted and appear in the documentation as a namespace called\r
+# 'anonymous_namespace{file}', where file will be replaced with the base\r
+# name of the file that contains the anonymous namespace. By default\r
+# anonymous namespaces are hidden.\r
+\r
+EXTRACT_ANON_NSPACES = NO\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\r
+# undocumented members of documented classes, files or namespaces.\r
+# If set to NO (the default) these members will be included in the\r
+# various overviews, but no documentation section is generated.\r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS = YES\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\r
+# undocumented classes that are normally visible in the class hierarchy.\r
+# If set to NO (the default) these classes will be included in the various\r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES = YES\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all\r
+# friend (class|struct|union) declarations.\r
+# If set to NO (the default) these declarations will be included in the\r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS = YES\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\r
+# documentation blocks found inside the body of a function.\r
+# If set to NO (the default) these blocks will be appended to the\r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS = YES\r
+\r
+# The INTERNAL_DOCS tag determines if documentation\r
+# that is typed after a \internal command is included. If the tag is set\r
+# to NO (the default) then the documentation will be excluded.\r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate\r
+# file names in lower-case letters. If set to YES upper-case letters are also\r
+# allowed. This is useful if you have classes or files whose names only differ\r
+# in case and if your file system supports case sensitive file names. Windows\r
+# and Mac users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen\r
+# will show members with their full class and namespace scopes in the\r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen\r
+# will put a list of the files that are included by a file in the documentation\r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES = NO\r
+\r
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen\r
+# will list include files with double quotes in the documentation\r
+# rather than with sharp brackets.\r
+\r
+FORCE_LOCAL_INCLUDES = NO\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]\r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen\r
+# will sort the (detailed) documentation of file and class members\r
+# alphabetically by member name. If set to NO the members will appear in\r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS = YES\r
+\r
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the\r
+# brief documentation of file, namespace and class members alphabetically\r
+# by member name. If set to NO (the default) the members will appear in\r
+# declaration order.\r
+\r
+SORT_BRIEF_DOCS = YES\r
+\r
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen\r
+# will sort the (brief and detailed) documentation of class members so that\r
+# constructors and destructors are listed first. If set to NO (the default)\r
+# the constructors will appear in the respective orders defined by\r
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.\r
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO\r
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.\r
+\r
+SORT_MEMBERS_CTORS_1ST = NO\r
+\r
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the\r
+# hierarchy of group names into alphabetical order. If set to NO (the default)\r
+# the group names will appear in their defined order.\r
+\r
+SORT_GROUP_NAMES = NO\r
+\r
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be\r
+# sorted by fully-qualified names, including namespaces. If set to\r
+# NO (the default), the class list will be sorted only by class name,\r
+# not including the namespace part.\r
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\r
+# Note: This option applies only to the class list, not to the\r
+# alphabetical list.\r
+\r
+SORT_BY_SCOPE_NAME = YES\r
+\r
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to\r
+# do proper type resolution of all parameters of a function it will reject a\r
+# match between the prototype and the implementation of a member function even\r
+# if there is only one candidate or it is obvious which candidate to choose\r
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen\r
+# will still accept a match between prototype and implementation in such cases.\r
+\r
+STRICT_PROTO_MATCHING = NO\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or\r
+# disable (NO) the todo list. This list is created by putting \todo\r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or\r
+# disable (NO) the test list. This list is created by putting \test\r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or\r
+# disable (NO) the bug list. This list is created by putting \bug\r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST = NO\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or\r
+# disable (NO) the deprecated list. This list is created by putting\r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional\r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines\r
+# the initial value of a variable or macro consists of for it to appear in\r
+# the documentation. If the initializer consists of more lines than specified\r
+# here it will be hidden. Use a value of 0 to hide initializers completely.\r
+# The appearance of the initializer of individual variables and macros in the\r
+# documentation can be controlled using \showinitializer or \hideinitializer\r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated\r
+# at the bottom of the documentation of classes and structs. If set to YES the\r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES = NO\r
+\r
+# If the sources in your project are distributed over multiple directories\r
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy\r
+# in the documentation. The default is NO.\r
+\r
+SHOW_DIRECTORIES = NO\r
+\r
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.\r
+# This will remove the Files entry from the Quick Index and from the\r
+# Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_FILES = YES\r
+\r
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the\r
+# Namespaces page.\r
+# This will remove the Namespaces entry from the Quick Index\r
+# and from the Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_NAMESPACES = YES\r
+\r
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that\r
+# doxygen should invoke to get the current version for each file (typically from\r
+# the version control system). Doxygen will invoke the program by executing (via\r
+# popen()) the command <command> <input-file>, where <command> is the value of\r
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file\r
+# provided by doxygen. Whatever the program writes to standard output\r
+# is used as the file version. See the manual for examples.\r
+\r
+FILE_VERSION_FILTER =\r
+\r
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\r
+# by doxygen. The layout file controls the global structure of the generated\r
+# output files in an output format independent way. The create the layout file\r
+# that represents doxygen's defaults, run doxygen with the -l option.\r
+# You can optionally specify a file name after the option, if omitted\r
+# DoxygenLayout.xml will be used as the name of the layout file.\r
+\r
+LAYOUT_FILE = DoxygenLayout.xml\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated\r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are\r
+# generated by doxygen. Possible values are YES and NO. If left blank\r
+# NO is used.\r
+\r
+WARNINGS = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings\r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will\r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED = YES\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for\r
+# potential errors in the documentation, such as not documenting some\r
+# parameters in a documented function, or documenting parameters that\r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR = YES\r
+\r
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for\r
+# functions that are documented, but have no documentation for their parameters\r
+# or return value. If set to NO (the default) doxygen will only warn about\r
+# wrong or incomplete parameter documentation, but not about the absence of\r
+# documentation.\r
+\r
+WARN_NO_PARAMDOC = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that\r
+# doxygen can produce. The string should contain the $file, $line, and $text\r
+# tags, which will be replaced by the file and line number from which the\r
+# warning originated and the warning text. Optionally the format may contain\r
+# $version, which will be replaced by the version of the file (if it could\r
+# be obtained via FILE_VERSION_FILTER)\r
+\r
+WARN_FORMAT = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning\r
+# and error messages should be written. If left blank the output is written\r
+# to stderr.\r
+\r
+WARN_LOGFILE = warning.txt\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain\r
+# documented source files. You may enter file names like "myfile.cpp" or\r
+# directories like "/usr/src/myproject". Separate the files or directories\r
+# with spaces.\r
+\r
+INPUT = ../../../../../osp \\r
+ ./libraries \r
+ \r
+\r
+# This tag can be used to specify the character encoding of the source files\r
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is\r
+# also the default input encoding. Doxygen uses libiconv (or the iconv built\r
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for\r
+# the list of possible encodings.\r
+\r
+INPUT_ENCODING = UTF-8\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank the following patterns are tested:\r
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh\r
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py\r
+# *.f90 *.f *.for *.vhd *.vhdl\r
+\r
+FILE_PATTERNS = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories\r
+# should be searched for input files as well. Possible values are YES and NO.\r
+# If left blank NO is used.\r
+\r
+RECURSIVE = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should\r
+# excluded from the INPUT source files. This way you can easily exclude a\r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE = ../../../../../osp/FBaseSysLog.h \\r
+ ../../../../../osp/FXml.h \\r
+ ./libraries/newlib \r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or\r
+# directories that are symbolic links (a Unix file system feature) are excluded\r
+# from the input.\r
+\r
+EXCLUDE_SYMLINKS = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\r
+# certain files from those directories. Note that the wildcards are matched\r
+# against the file with absolute path, so to exclude all test directories\r
+# for example use the pattern */test/*\r
+\r
+EXCLUDE_PATTERNS = \r
+\r
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\r
+# (namespaces, classes, functions, etc.) that should be excluded from the\r
+# output. The symbol name can be a fully qualified name, a word, or if the\r
+# wildcard * is used, a substring. Examples: ANamespace, AClass,\r
+# AClass::ANamespace, ANamespace::*Test\r
+\r
+EXCLUDE_SYMBOLS =\r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or\r
+# directories that contain example code fragments that are included (see\r
+# the \include command).\r
+\r
+EXAMPLE_PATH =\r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the\r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS =\r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\r
+# searched for input files to be used with the \include or \dontinclude\r
+# commands irrespective of the value of the RECURSIVE tag.\r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or\r
+# directories that contain image that are included in the documentation (see\r
+# the \image command).\r
+\r
+IMAGE_PATH = images\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should\r
+# invoke to filter for each input file. Doxygen will invoke the filter program\r
+# by executing (via popen()) the command <filter> <input-file>, where <filter>\r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an\r
+# input file. Doxygen will then use the output that the filter program writes\r
+# to standard output.\r
+# If FILTER_PATTERNS is specified, this tag will be\r
+# ignored.\r
+\r
+INPUT_FILTER =\r
+\r
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\r
+# basis.\r
+# Doxygen will compare the file name with each pattern and apply the\r
+# filter if there is a match.\r
+# The filters are a list of the form:\r
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further\r
+# info on how filters are used. If FILTER_PATTERNS is empty or if\r
+# non of the patterns match the file name, INPUT_FILTER is applied.\r
+\r
+FILTER_PATTERNS =\r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\r
+# INPUT_FILTER) will be used to filter the input files when producing source\r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES = NO\r
+\r
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\r
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)\r
+# and it is also possible to disable source filtering for a specific pattern\r
+# using *.ext= (so without naming a filter). This option only has effect when\r
+# FILTER_SOURCE_FILES is enabled.\r
+\r
+FILTER_SOURCE_PATTERNS =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will\r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+# Note: To get rid of all source code in the generated output, make sure also\r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body\r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct\r
+# doxygen to hide any special comment blocks from generated source code\r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES\r
+# then for each documented function all documented\r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = NO\r
+\r
+# If the REFERENCES_RELATION tag is set to YES\r
+# then for each documented function all documented entities\r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION = NO\r
+\r
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\r
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\r
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\r
+# link to the source code.\r
+# Otherwise they will link to the documentation.\r
+\r
+REFERENCES_LINK_SOURCE = NO\r
+\r
+# If the USE_HTAGS tag is set to YES then the references to source code\r
+# will point to the HTML generated by the htags(1) tool instead of doxygen\r
+# built-in source browser. The htags tool is part of GNU's global source\r
+# tagging system (see http://www.gnu.org/software/global/global.html). You\r
+# will need version 4.8.6 or higher.\r
+\r
+USE_HTAGS = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen\r
+# will generate a verbatim copy of the header file for each class for\r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index\r
+# of all compounds will be generated. Enable this if the project\r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then\r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns\r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX = 5\r
+\r
+# In case all classes in a project start with a common prefix, all\r
+# classes will be put under the same header in the alphabetical index.\r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that\r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will\r
+# generate HTML output.\r
+\r
+GENERATE_HTML = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT = apidocs\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for\r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank\r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard header. Note that when using a custom header you are responsible\r
+# for the proper inclusion of any scripts and style sheets that doxygen\r
+# needs, which is dependent on the configuration options used.\r
+# It is adviced to generate a default header using "doxygen -w html\r
+# header.html footer.html stylesheet.css YourConfigFile" and then modify\r
+# that header. Note that the header is subject to change so you typically\r
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!\r
+\r
+HTML_HEADER =\r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard footer.\r
+\r
+HTML_FOOTER = footer.html\r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading\r
+# style sheet that is used by each HTML page. It can be used to\r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen\r
+# will generate a default style sheet. Note that doxygen will try to copy\r
+# the style sheet file to the HTML output directory, so don't put your own\r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET = Tizen.css\r
+\r
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\r
+# other source files which should be copied to the HTML output directory. Note\r
+# that these files will be copied to the base HTML output directory. Use the\r
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\r
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that\r
+# the files will be copied as-is; there are no commands or markers available.\r
+\r
+HTML_EXTRA_FILES =\r
+\r
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.\r
+# Doxygen will adjust the colors in the stylesheet and background images\r
+# according to this color. Hue is specified as an angle on a colorwheel,\r
+# see http://en.wikipedia.org/wiki/Hue for more information.\r
+# For instance the value 0 represents red, 60 is yellow, 120 is green,\r
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.\r
+# The allowed range is 0 to 359.\r
+\r
+HTML_COLORSTYLE_HUE = 220\r
+\r
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of\r
+# the colors in the HTML output. For a value of 0 the output will use\r
+# grayscales only. A value of 255 will produce the most vivid colors.\r
+\r
+HTML_COLORSTYLE_SAT = 100\r
+\r
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to\r
+# the luminance component of the colors in the HTML output. Values below\r
+# 100 gradually make the output lighter, whereas values above 100 make\r
+# the output darker. The value divided by 100 is the actual gamma applied,\r
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,\r
+# and 100 does not change the gamma.\r
+\r
+HTML_COLORSTYLE_GAMMA = 80\r
+\r
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\r
+# page will contain the date and time when the page was generated. Setting\r
+# this to NO can help when comparing the output of multiple runs.\r
+\r
+HTML_TIMESTAMP = YES\r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,\r
+# files or namespaces will be aligned in HTML using tables. If set to\r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS = YES\r
+\r
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\r
+# documentation will contain sections that can be hidden and shown after the\r
+# page has loaded. For this to work a browser that supports\r
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox\r
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).\r
+\r
+HTML_DYNAMIC_SECTIONS = NO\r
+\r
+# If the GENERATE_DOCSET tag is set to YES, additional index files\r
+# will be generated that can be used as input for Apple's Xcode 3\r
+# integrated development environment, introduced with OSX 10.5 (Leopard).\r
+# To create a documentation set, doxygen will generate a Makefile in the\r
+# HTML output directory. Running make will produce the docset in that\r
+# directory and running "make install" will install the docset in\r
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find\r
+# it at startup.\r
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html\r
+# for more information.\r
+\r
+GENERATE_DOCSET = NO\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the\r
+# feed. A documentation feed provides an umbrella under which multiple\r
+# documentation sets from a single provider (such as a company or product suite)\r
+# can be grouped.\r
+\r
+DOCSET_FEEDNAME = "Doxygen generated docs"\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that\r
+# should uniquely identify the documentation set bundle. This should be a\r
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen\r
+# will append .docset to the name.\r
+\r
+DOCSET_BUNDLE_ID = org.doxygen.Project\r
+\r
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify\r
+# the documentation publisher. This should be a reverse domain-name style\r
+# string, e.g. com.mycompany.MyDocSet.documentation.\r
+\r
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher\r
+\r
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.\r
+\r
+DOCSET_PUBLISHER_NAME = Publisher\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files\r
+# will be generated that can be used as input for tools like the\r
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)\r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can\r
+# be used to specify the file name of the resulting .chm file. You\r
+# can add a path in front of the file if the result should not be\r
+# written to the html output directory.\r
+\r
+CHM_FILE =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can\r
+# be used to specify the location (absolute path including file name) of\r
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run\r
+# the HTML help compiler on the generated index.hhp.\r
+\r
+HHC_LOCATION =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag\r
+# controls if a separate .chi index file is generated (YES) or that\r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\r
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file\r
+# content.\r
+\r
+CHM_INDEX_ENCODING =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag\r
+# controls whether a binary table of contents is generated (YES) or a\r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC = YES\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members\r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND = YES\r
+\r
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\r
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated\r
+# that can be used as input for Qt's qhelpgenerator to generate a\r
+# Qt Compressed Help (.qch) of the generated HTML documentation.\r
+\r
+GENERATE_QHP = NO\r
+\r
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can\r
+# be used to specify the file name of the resulting .qch file.\r
+# The path specified is relative to the HTML output folder.\r
+\r
+QCH_FILE =\r
+\r
+# The QHP_NAMESPACE tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#namespace\r
+\r
+QHP_NAMESPACE = org.doxygen.Project\r
+\r
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders\r
+\r
+QHP_VIRTUAL_FOLDER = doc\r
+\r
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to\r
+# add. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#custom-filters\r
+\r
+QHP_CUST_FILTER_NAME =\r
+\r
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the\r
+# custom filter to add. For more information please see\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">\r
+# Qt Help Project / Custom Filters</a>.\r
+\r
+QHP_CUST_FILTER_ATTRS =\r
+\r
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\r
+# project's\r
+# filter section matches.\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">\r
+# Qt Help Project / Filter Attributes</a>.\r
+\r
+QHP_SECT_FILTER_ATTRS =\r
+\r
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can\r
+# be used to specify the location of Qt's qhelpgenerator.\r
+# If non-empty doxygen will try to run qhelpgenerator on the generated\r
+# .qhp file.\r
+\r
+QHG_LOCATION =\r
+\r
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files\r
+# will be generated, which together with the HTML files, form an Eclipse help\r
+# plugin. To install this plugin and make it available under the help contents\r
+# menu in Eclipse, the contents of the directory containing the HTML and XML\r
+# files needs to be copied into the plugins directory of eclipse. The name of\r
+# the directory within the plugins directory should be the same as\r
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before\r
+# the help appears.\r
+\r
+GENERATE_ECLIPSEHELP = YES\r
+\r
+# A unique identifier for the eclipse help plugin. When installing the plugin\r
+# the directory name containing the HTML and XML files should also have\r
+# this name.\r
+\r
+ECLIPSE_DOC_ID = org.doxygen.Project\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at\r
+# top of each HTML page. The value NO (the default) enables the index and\r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX = NO\r
+\r
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values\r
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML\r
+# documentation. Note that a value of 0 will completely suppress the enum\r
+# values from appearing in the overview section.\r
+\r
+ENUM_VALUES_PER_LINE = 4\r
+\r
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\r
+# structure should be generated to display hierarchical information.\r
+# If the tag value is set to YES, a side panel will be generated\r
+# containing a tree-like index structure (just like the one that\r
+# is generated for HTML Help). For this to work a browser that supports\r
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).\r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW = NO\r
+\r
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,\r
+# and Class Hierarchy pages using a tree view instead of an ordered list.\r
+\r
+USE_INLINE_TREES = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be\r
+# used to set the initial width (in pixels) of the frame in which the tree\r
+# is shown.\r
+\r
+TREEVIEW_WIDTH = 250\r
+\r
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open\r
+# links to external symbols imported via tag files in a separate window.\r
+\r
+EXT_LINKS_IN_WINDOW = NO\r
+\r
+# Use this tag to change the font size of Latex formulas included\r
+# as images in the HTML documentation. The default is 10. Note that\r
+# when you change the font size after a successful doxygen run you need\r
+# to manually remove any form_*.png images from the HTML output directory\r
+# to force them to be regenerated.\r
+\r
+FORMULA_FONTSIZE = 10\r
+\r
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images\r
+# generated for formulas are transparent PNGs. Transparent PNGs are\r
+# not supported properly for IE 6.0, but are supported on all modern browsers.\r
+# Note that when changing this option you need to delete any form_*.png files\r
+# in the HTML output before the changes have effect.\r
+\r
+FORMULA_TRANSPARENT = YES\r
+\r
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax\r
+# (see http://www.mathjax.org) which uses client side Javascript for the\r
+# rendering instead of using prerendered bitmaps. Use this if you do not\r
+# have LaTeX installed or if you want to formulas look prettier in the HTML\r
+# output. When enabled you also need to install MathJax separately and\r
+# configure the path to it using the MATHJAX_RELPATH option.\r
+\r
+USE_MATHJAX = NO\r
+\r
+# When MathJax is enabled you need to specify the location relative to the\r
+# HTML output directory using the MATHJAX_RELPATH option. The destination\r
+# directory should contain the MathJax.js script. For instance, if the mathjax\r
+# directory is located at the same level as the HTML output directory, then\r
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the\r
+# mathjax.org site, so you can quickly see the result without installing\r
+# MathJax, but it is strongly recommended to install a local copy of MathJax\r
+# before deployment.\r
+\r
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax\r
+\r
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box\r
+# for the HTML output. The underlying search engine uses javascript\r
+# and DHTML and should work on any modern browser. Note that when using\r
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets\r
+# (GENERATE_DOCSET) there is already a search function so this one should\r
+# typically be disabled. For large projects the javascript based search engine\r
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.\r
+\r
+SEARCHENGINE = NO\r
+\r
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be\r
+# implemented using a PHP enabled web server instead of at the web client\r
+# using Javascript. Doxygen will generate the search PHP script and index\r
+# file to put on the web server. The advantage of the server\r
+# based approach is that it scales better to large projects and allows\r
+# full text search. The disadvantages are that it is more difficult to setup\r
+# and does not have live searching capabilities.\r
+\r
+SERVER_BASED_SEARCH = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will\r
+# generate Latex output.\r
+\r
+GENERATE_LATEX = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be\r
+# invoked. If left blank `latex' will be used as the default command name.\r
+# Note that when enabling USE_PDFLATEX this option is only used for\r
+# generating bitmaps for formulas in the HTML output, but not in the\r
+# Makefile that is written to the output directory.\r
+\r
+LATEX_CMD_NAME = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to\r
+# generate index for LaTeX. If left blank `makeindex' will be used as the\r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact\r
+# LaTeX documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_LATEX = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used\r
+# by the printer. Possible values are: a4, letter, legal and\r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX\r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES =\r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for\r
+# the generated latex document. The header should contain everything until\r
+# the first chapter. If it is left blank doxygen will generate a\r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER =\r
+\r
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for\r
+# the generated latex document. The footer should contain everything after\r
+# the last chapter. If it is left blank doxygen will generate a\r
+# standard footer. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_FOOTER =\r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated\r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will\r
+# contain links (just like the HTML output) instead of page references\r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of\r
+# plain latex in the generated Makefile. Set this option to YES to get a\r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.\r
+# command to the generated LaTeX files. This will instruct LaTeX to keep\r
+# running if errors occur, instead of asking the user for help.\r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not\r
+# include the index chapters (such as File Index, Compound Index, etc.)\r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES = NO\r
+\r
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include\r
+# source code with syntax highlighting in the LaTeX output.\r
+# Note that which sources are shown also depends on other settings\r
+# such as SOURCE_BROWSER.\r
+\r
+LATEX_SOURCE_CODE = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output\r
+# The RTF output is optimized for Word 97 and may not look very pretty with\r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact\r
+# RTF documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_RTF = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated\r
+# will contain hyperlink fields. The RTF file will\r
+# contain links (just like the HTML output) instead of page references.\r
+# This makes the output suitable for online browsing using WORD or other\r
+# programs which support those fields.\r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's\r
+# config file, i.e. a series of assignments. You only have to provide\r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE =\r
+\r
+# Set optional variables used in the generation of an rtf document.\r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will\r
+# generate man pages\r
+\r
+GENERATE_MAN = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to\r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,\r
+# then it will generate one additional man file for each entity\r
+# documented in the real man page(s). These additional files\r
+# only source the real man page, but without them the man command\r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will\r
+# generate an XML file that captures the structure of\r
+# the code including all documentation.\r
+\r
+GENERATE_XML = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT = _xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA =\r
+\r
+# The XML_DTD tag can be used to specify an XML DTD,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_DTD =\r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will\r
+# dump the program listings (including syntax highlighting\r
+# and cross-referencing information) to the XML output. Note that\r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will\r
+# generate an AutoGen Definitions (see autogen.sf.net) file\r
+# that captures the structure of the code including all\r
+# documentation. Note that this feature is still experimental\r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will\r
+# generate a Perl module file that captures the structure of\r
+# the code including all documentation. Note that this\r
+# feature is still experimental and incomplete at the\r
+# moment.\r
+\r
+GENERATE_PERLMOD = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate\r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able\r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be\r
+# nicely formatted so it can be parsed by a human reader.\r
+# This is useful\r
+# if you want to understand what is going on.\r
+# On the other hand, if this\r
+# tag is set to NO the size of the Perl module output will be much smaller\r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file\r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.\r
+# This is useful so different doxyrules.make files included by the same\r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will\r
+# evaluate all C-preprocessor directives found in the sources and include\r
+# files.\r
+\r
+ENABLE_PREPROCESSING = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro\r
+# names in the source code. If set to NO (the default) only conditional\r
+# compilation will be performed. Macro expansion can be done in a controlled\r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES\r
+# then the macro expansion is limited to the macros specified with the\r
+# PREDEFINED and EXPAND_AS_DEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF = YES\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files\r
+# pointed to by INCLUDE_PATH will be searched when a #include is found.\r
+\r
+SEARCH_INCLUDES = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that\r
+# contain include files that are not input files but should be processed by\r
+# the preprocessor.\r
+\r
+INCLUDE_PATH =\r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard\r
+# patterns (like *.h and *.hpp) to filter out the header-files in the\r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will\r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS =\r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that\r
+# are defined before the preprocessor is started (similar to the -D option of\r
+# gcc). The argument of the tag is a list of macros of the form: name\r
+# or name=definition (no spaces). If the definition and the = are\r
+# omitted =1 is assumed. To prevent a macro definition from being\r
+# undefined via #undef or recursively expanded use the := operator\r
+# instead of the = operator.\r
+\r
+PREDEFINED = LIBXML_OUTPUT_ENABLED LIBXML_PUSH_ENABLED LIBXML_TREE_ENABLED LIBXML_HTML_ENABLED GL_API GL_APICALL _OSP_EXPORT_= _OSP_LOCAL_=\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then\r
+# this tag can be used to specify a list of macro names that should be expanded.\r
+# The macro definition that is found in the sources will be used.\r
+# Use the PREDEFINED tag if you want to use a different macro definition that\r
+# overrules the definition found in the source code.\r
+\r
+EXPAND_AS_DEFINED =\r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then\r
+# doxygen's preprocessor will remove all references to function-like macros\r
+# that are alone on a line, have an all uppercase name, and do not end with a\r
+# semicolon, because these will confuse the parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::additions related to external references\r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles.\r
+# Optionally an initial location of the external documentation\r
+# can be added for each tagfile. The format of a tag file without\r
+# this location is as follows:\r
+#\r
+# TAGFILES = file1 file2 ...\r
+# Adding location for the tag files is done as follows:\r
+#\r
+# TAGFILES = file1=loc1 "file2 = loc2" ...\r
+# where "loc1" and "loc2" can be relative or absolute paths or\r
+# URLs. If a location is present for each tag, the installdox tool\r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen\r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES =\r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create\r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE =\r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed\r
+# in the class index. If set to NO only the inherited external classes\r
+# will be listed.\r
+\r
+ALLEXTERNALS = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed\r
+# in the modules index. If set to NO, only the current project's groups will\r
+# be listed.\r
+\r
+EXTERNAL_GROUPS = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script\r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool\r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will\r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base\r
+# or super classes. Setting the tag to NO turns the diagrams off. Note that\r
+# this option also works with HAVE_DOT disabled, but it is recommended to\r
+# install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS = YES\r
+\r
+# You can define message sequence charts within doxygen comments using the \msc\r
+# command. Doxygen will then run the mscgen tool (see\r
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the\r
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where\r
+# the mscgen tool resides. If left empty the tool is assumed to be found in the\r
+# default search path.\r
+\r
+MSCGEN_PATH =\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide\r
+# inheritance and usage relations if the target is undocumented\r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\r
+# available from the path. This tool is part of Graphviz, a graph visualization\r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section\r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT = NO\r
+\r
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is\r
+# allowed to run in parallel. When set to 0 (the default) doxygen will\r
+# base this on the number of processors available in the system. You can set it\r
+# explicitly to a value larger than 0 to get control over the balance\r
+# between CPU load and processing speed.\r
+\r
+DOT_NUM_THREADS = 0\r
+\r
+# By default doxygen will write a font called Helvetica to the output\r
+# directory and reference it in all dot files that doxygen generates.\r
+# When you want a differently looking font you can specify the font name\r
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,\r
+# which can be done by putting it in a standard location or by setting the\r
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory\r
+# containing the font.\r
+\r
+DOT_FONTNAME = FreeSans\r
+\r
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.\r
+# The default size is 10pt.\r
+\r
+DOT_FONTSIZE = 10\r
+\r
+# By default doxygen will tell dot to use the output directory to look for the\r
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a\r
+# different font using DOT_FONTNAME you can set the path where dot\r
+# can find it using this tag.\r
+\r
+DOT_FONTPATH =\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect inheritance relations. Setting this tag to YES will force the\r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect implementation dependencies (inheritance, containment, and\r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH = YES\r
+\r
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for groups, showing the direct groups dependencies\r
+\r
+GROUP_GRAPHS = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and\r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling\r
+# Language.\r
+\r
+UML_LOOK = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the\r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT\r
+# tags are set to YES then doxygen will generate a graph for each documented\r
+# file showing the direct and indirect include dependencies of the file with\r
+# other documented files.\r
+\r
+INCLUDE_GRAPH = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and\r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each\r
+# documented header file showing the documented files that directly or\r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then\r
+# doxygen will generate a call dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable call graphs\r
+# for selected functions only using the \callgraph command.\r
+\r
+CALL_GRAPH = NO\r
+\r
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then\r
+# doxygen will generate a caller dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable caller\r
+# graphs for selected functions only using the \callergraph command.\r
+\r
+CALLER_GRAPH = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY = YES\r
+\r
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES\r
+# then doxygen will show the dependencies a directory has on other directories\r
+# in a graphical way. The dependency relations are determined by the #include\r
+# relations between the files in the directories.\r
+\r
+DIRECTORY_GRAPH = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\r
+# generated by dot. Possible values are svg, png, jpg, or gif.\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be\r
+# found. If left blank, it is assumed the dot tool can be found in the path.\r
+\r
+DOT_PATH =\r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that\r
+# contain dot files that are included in the documentation (see the\r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS =\r
+\r
+# The MSCFILE_DIRS tag can be used to specify one or more directories that\r
+# contain msc files that are included in the documentation (see the\r
+# \mscfile command).\r
+\r
+MSCFILE_DIRS =\r
+\r
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of\r
+# nodes that will be shown in the graph. If the number of nodes in a graph\r
+# becomes larger than this value, doxygen will truncate the graph, which is\r
+# visualized by representing a node as a red box. Note that doxygen if the\r
+# number of direct children of the root node in a graph is already larger than\r
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note\r
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\r
+\r
+DOT_GRAPH_MAX_NODES = 50\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the\r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable\r
+# from the root by following a path via at most 3 edges will be shown. Nodes\r
+# that lay further from the root node will be omitted. Note that setting this\r
+# option to 1 or 2 may greatly reduce the computation time needed for large\r
+# code bases. Also note that the size of a graph can be further restricted by\r
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\r
+\r
+MAX_DOT_GRAPH_DEPTH = 0\r
+\r
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent\r
+# background. This is disabled by default, because dot on Windows does not\r
+# seem to support this out of the box. Warning: Depending on the platform used,\r
+# enabling this option may lead to badly anti-aliased labels on the edges of\r
+# a graph (i.e. they become hard to read).\r
+\r
+DOT_TRANSPARENT = NO\r
+\r
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output\r
+# files in one run (i.e. multiple -o and -T options on the command line). This\r
+# makes dot run faster, but since only newer versions of dot (>1.8.10)\r
+# support this, this feature is disabled by default.\r
+\r
+DOT_MULTI_TARGETS = NO\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will\r
+# generate a legend page explaining the meaning of the various boxes and\r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will\r
+# remove the intermediate dot files that are used to generate\r
+# the various graphs.\r
+\r
+DOT_CLEANUP = YES\r
--- /dev/null
+//
+// Open Service Platform
+// Copyright (c) 2012 Samsung Electronics Co., Ltd.
+//
+// Licensed under the Apache License, Version 2.0 (the License);
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+/*
+ *
+ * @file eglibc.h
+ * @brief This is the header file for the must-include files.
+ *
+ * This header file defines the must-include files.
+ */
+
+
+#ifndef eglibc_h
+#define eglibc_h
+
+
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @defgroup libeglibc Standard EGLIBC Library
+ *
+ * The %Tizen C++ application supports a complete set of standard EGLIBC library APIs.
+ *
+ * EGLIBC (Embedded GLIBC) is a variant of the GNU C Library (GLIBC) that is designed for embedded systems. @n
+ *
+ * EGLIBC library includes APIs for math, and pthread functionalities. @n
+ *
+ * For more information, refer to the glibc manual on this <a href="http://www.gnu.org/software/libc/manual/html_mono/libc.html" target="_blank">Web site</a>.
+ *
+ * @since 2.0
+ */
+
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // eglibc_h
--- /dev/null
+/*
+ *
+ * @file libxml2.h
+ * @brief This is the header file for Libxml2.
+ *
+ * This header file defines Libxml2.
+ */
+
+#ifndef libxml2_h
+#define libxml2_h
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @defgroup libxml2 Libxml2
+ *
+ * The %Tizen native framework supports the Libxml2 library.
+ *
+ * For more information, refer to the <a href="http://www.xmlsoft.org" target="_blank">xmlsoft Web site</a>
+ *
+ * @since 2.0
+ *
+ * @code
+ // Sample data - map.xml
+ <?xml version="1.0" encoding="ISO-8859-1" ?>
+ <map>
+ <item>
+ <country>United Arab Emirates</country>
+ <capital>Abu Dhabi</capital>
+ </item>
+
+ <item>
+ <country>Nigeria</country>
+ <capital>Abuja</capital>
+ </item>
+
+ <item>
+ <country>Ghana</country>
+ <capital>Accra</capital>
+ </item>
+
+ <item>
+ <country>Pitcairn Islands</country>
+ <capital>Adamstown</capital>
+ </item>
+ </map>
+ * @endcode
+ *
+ * @code
+ // Sample code for XmlSample.h
+ #include <FBase.h>
+ #include <FUi.h>
+
+ classXmlSample :
+ public Tizen::Ui::Controls::Form
+ {
+ // Construction
+ public:
+ XmlSample(void);
+ ~XmlSample(void);
+
+ public:
+ virtual result OnInitializing(void);
+ };
+ * @endcode
+ *
+ * @code
+ // Sample code for XmlSample.cpp
+ #include <libxml/parser.h>
+ #include "XmlSample.h"
+
+ using namespace Tizen::Base;
+
+ result
+ XmlSample::OnInitializing(void)
+ {
+ xmlDocPtrpDocument = null;
+ xmlNodePtrpRoot = null;
+ xmlNodePtrpCurrentElement = null;
+
+ // Creates an XML document
+ pDocument = xmlParseFile("/Home/map.xml");
+ pRoot = xmlDocGetRootElement(pDocument);
+
+ for(pCurrentElement = pRoot->children; pCurrentElement; pCurrentElement = pCurrentElement->next)
+ {
+ String countryName;
+ xmlNodePtrpChildElement = null;
+
+ if(pCurrentElement->type == XML_ELEMENT_NODE)
+ {
+ // Gets the <country> element from the <item> element
+ pChildElement = pCurrentElement->children->next;
+
+ if(pChildElement)
+ {
+ // Gets the content from XML_TEXT_NODE
+ Tizen::Base::Utility::StringUtil::Utf8ToString ((char*)pChildElement->children->content, countryName);
+ AppLog("country : %S\n", countryName.GetPointer());
+ }
+ }
+ }
+
+ xmlFreeDoc(pDocument);
+ return E_SUCCESS;
+ }
+ * @endcode
+ */
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // libxml2_h
--- /dev/null
+// \r
+// Open Service Platform\r
+// Copyright (c) 2012 Samsung Electronics Co., Ltd. \r
+// \r
+// Licensed under the Apache License, Version 2.0 (the License);\r
+// you may not use this file except in compliance with the License.\r
+// You may obtain a copy of the License at\r
+//\r
+// http://www.apache.org/licenses/LICENSE-2.0\r
+//\r
+// Unless required by applicable law or agreed to in writing, software\r
+// distributed under the License is distributed on an "AS IS" BASIS,\r
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
+// See the License for the specific language governing permissions and\r
+// limitations under the License.\r
+//\r
+/* \r
+* \r
+* @file Misc.h\r
+* @brief This is the header file for utility services including standard libraries.\r
+*\r
+* This header file defines utility services including standard libraries.\r
+*/\r
+\r
+#ifndef Misc_h\r
+#define Misc_h\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+extern "C" {\r
+#endif // __cplusplus\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @ingroup Newliblibc\r
+ * @defgroup NewliblibcMisc Misc\r
+ *\r
+ * @brief %Tizen provides a subset of newlib's Misc APIs. @n\r
+ * For more information, refer to the description below.\r
+ *\r
+ * @endif\r
+ */\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @addtogroup NewliblibcMisc\r
+ * @{\r
+ */\r
+\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#unctrl" target="_blank">newlib</a> website.\r
+ */\r
+ int unctrllen(int c);\r
+\r
+\r
+ /** \r
+ * @} \r
+ * @endif\r
+ */\r
+\r
+#ifdef __cplusplus\r
+}\r
+#endif // __cplusplus\r
+\r
+#endif // Misc.h\r
--- /dev/null
+// \r
+// Open Service Platform\r
+// Copyright (c) 2012 Samsung Electronics Co., Ltd. \r
+// \r
+// Licensed under the Apache License, Version 2.0 (the License);\r
+// you may not use this file except in compliance with the License.\r
+// You may obtain a copy of the License at\r
+//\r
+// http://www.apache.org/licenses/LICENSE-2.0\r
+//\r
+// Unless required by applicable law or agreed to in writing, software\r
+// distributed under the License is distributed on an "AS IS" BASIS,\r
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
+// See the License for the specific language governing permissions and\r
+// limitations under the License.\r
+//\r
+/*\r
+ * \r
+ * @file Stdio.h\r
+ * @brief This is the header file for utility services including standard libraries.\r
+ *\r
+ * This header file defines utility services including standard libraries.\r
+ * \r
+ */\r
+\r
+#ifndef Stdio_h\r
+#define Stdio_h\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+extern "C" {\r
+#endif // __cplusplus\r
+\r
+ /**\r
+ * @if OSPCOMPAT \r
+ * @ingroup Newliblibc\r
+ * @defgroup NewliblibcStdio Stdio\r
+ * \r
+ *\r
+ *\r
+ * @brief %Tizen provides a subset of newlib's Stdio APIs. @n\r
+ * For more information, refer to the description below.\r
+ *\r
+ * @endif\r
+ */\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @addtogroup NewliblibcStdio \r
+ * @{\r
+ */\r
+\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#funopen" target="_blank">newlib</a> website.\r
+ */\r
+ FILE *funopen(const void *cookie, int (*readfn) (void *cookie, char *buf, int n), \r
+ int (*writefn) (void *cookie, const char *buf, int n), \r
+ fpos_t (*seekfn) (void *cookie, fpos_t off, int whence), int (*closefn) (void *cookie));\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int sniprintf(char *str, size_t size, const char *format, ...);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siprintf" target="_blank">newlib</a> website.\r
+ */\r
+ char *asniprintf(char *str, size_t *size, const char *format, ...);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#sprintf" target="_blank">newlib</a> website.\r
+ */\r
+ char *asnprintf(char *str, size_t *size, const char *format, ...);\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#vfprintf" target="_blank">newlib</a> website.\r
+ */\r
+ char *vasnprintf(char *str, size_t *size, const char *fmt, va_list list);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int vsniprintf(char *str, size_t size, const char *fmt, va_list list);\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ char *vasniprintf(char *str, size_t *size, const char *fmt, va_list list);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#diprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int diprintf(int fd, const char *format, ...);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#diprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int vdiprintf(int fd, const char *format, va_list ap);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int iprintf(const char *format, ...);\r
+\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int viprintf(const char *fmt, va_list list);\r
+ \r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int fiprintf(FILE *fd, const char *format , ...);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int siprintf(char *str, const char *format, ...);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int asiprintf(char **strp, const char *format, ...);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siscanf" target="_blank">newlib</a> website.\r
+ */\r
+ int fiscanf(FILE *fd, const char *format, ...);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#siscanf" target="_blank">newlib</a> website.\r
+ */\r
+ int siscanf(const char *str, const char *format, ...);\r
+ \r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int vfiprintf(FILE *fp, const char *fmt, va_list list);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int vsiprintf(char *str, const char *fmt, va_list list);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viprintf" target="_blank">newlib</a> website.\r
+ */\r
+ int vasiprintf(char **strp, const char *fmt, va_list list);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viscanf" target="_blank">newlib</a> website.\r
+ */\r
+ int vfiscanf(FILE *fp, const char *fmt, va_list list);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#viscanf" target="_blank">newlib</a> website.\r
+ */\r
+ int vsiscanf(const char *str, const char *fmt, va_list list);\r
+ \r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#funopen" target="_blank">newlib</a> website.\r
+ */\r
+ FILE *fropen(const void *cookie, int (*readfn) (void *cookie, char *buf, int n));\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#funopen" target="_blank">newlib</a> website.\r
+ */\r
+ FILE *fwopen(const void *cookie, int (*writefn) (void *cookie, const char *buf, int n));\r
+ \r
+\r
+ /** \r
+ * @} \r
+ * @endif\r
+ */\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+}\r
+#endif // __cplusplus\r
+\r
+#endif // Stdio.h\r
--- /dev/null
+// \r
+// Open Service Platform\r
+// Copyright (c) 2012 Samsung Electronics Co., Ltd. \r
+// \r
+// Licensed under the Apache License, Version 2.0 (the License);\r
+// you may not use this file except in compliance with the License.\r
+// You may obtain a copy of the License at\r
+//\r
+// http://www.apache.org/licenses/LICENSE-2.0\r
+//\r
+// Unless required by applicable law or agreed to in writing, software\r
+// distributed under the License is distributed on an "AS IS" BASIS,\r
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
+// See the License for the specific language governing permissions and\r
+// limitations under the License.\r
+//\r
+/*\r
+ * \r
+ * @file Stdlib.h\r
+ * @brief This is the header file for utility services including standard libraries.\r
+ *\r
+ * This header file defines utility services including standard libraries.\r
+ */\r
+\r
+#ifndef Stdlib_h\r
+#define Stdlib_h\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+extern "C" {\r
+#endif // __cplusplus\r
+\r
+ /**\r
+ * @if OSPCOMPAT \r
+ * @ingroup Newliblibc\r
+ * @defgroup NewliblibcStdlib Stdlib\r
+ *\r
+ * @brief %Tizen provides a subset of newlib's Stdlib APIs. @n\r
+ * For more information, refer to the description below.\r
+ *\r
+ * @endif \r
+ */\r
+\r
+ /**\r
+ * @if OSPCOMPAT \r
+ * @addtogroup NewliblibcStdlib \r
+ * @{\r
+ */\r
+\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#atof" target="_blank">newlib</a>website.\r
+ */\r
+ float atoff(const char *s);\r
+\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#gvcvt" target="_blank">newlib</a>website.\r
+ */\r
+ char *gcvtf(float val, int precision, char *buf);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#ecvtbuf" target="_blank">newlib</a> website.\r
+ */\r
+ char *ecvtbuf(double val, int chars, int *decpt, int *sgn, char *buf);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#ecvtbuf" target="_blank">newlib</a> website.\r
+ */\r
+ char *fcvtbuf(double val, int decimals, int *decpt, int *sgn, char *buf);\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#ecvt" target="_blank">newlib</a> website.\r
+ */\r
+ char *ecvtf(float val, int chars, int *decpt, int *sgn);\r
+\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#ecvt" target="_blank">newlib</a> website.\r
+ */\r
+ char *fcvtf(float val, int decimals, int *decpt, int *sgn);\r
+\r
+ \r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#malloc" target="_blank">newlib</a> website.\r
+ */\r
+ void *reallocf(void *aptr, size_t nbytes);\r
+ \r
+ \r
+\r
+ /** \r
+ * @} \r
+ * @endif\r
+ */\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+}\r
+#endif // __cplusplus\r
+\r
+#endif // Stdio.h\r
--- /dev/null
+// \r
+// Open Service Platform\r
+// Copyright (c) 2012 Samsung Electronics Co., Ltd. \r
+// \r
+// Licensed under the Apache License, Version 2.0 (the License);\r
+// you may not use this file except in compliance with the License.\r
+// You may obtain a copy of the License at\r
+//\r
+// http://www.apache.org/licenses/LICENSE-2.0\r
+//\r
+// Unless required by applicable law or agreed to in writing, software\r
+// distributed under the License is distributed on an "AS IS" BASIS,\r
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
+// See the License for the specific language governing permissions and\r
+// limitations under the License.\r
+//\r
+/* \r
+ * \r
+ * @file Strings.h\r
+ * @brief This is the header file for utility services including standard libraries.\r
+ *\r
+ * This header file defines utility services including standard libraries.\r
+ *\r
+ */\r
+\r
+#ifndef Strings_h\r
+#define Strings_h\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+extern "C" {\r
+#endif // __cplusplus\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @ingroup Newliblibc\r
+ * @defgroup NewliblibcStrings Strings\r
+ *\r
+ *\r
+ * @brief %Tizen provides a subset of the newlib's Strings APIs. @n\r
+ * For more information, refer to the description below. \r
+ *\r
+ * @endif\r
+ */\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @addtogroup NewliblibcStrings\r
+ * @{\r
+ */\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#strlwr" target="_blank">newlib</a> website.\r
+ */ \r
+ char *strlwr(char *a);\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#strupr" target="_blank">newlib</a> website.\r
+ */ \r
+ char *strupr(char *a);\r
+\r
+\r
+ /** \r
+ * @} \r
+ * @endif\r
+ */\r
+\r
+#ifdef __cplusplus\r
+}\r
+#endif // __cplusplus\r
+\r
+#endif // Strings.h\r
--- /dev/null
+// \r
+// Open Service Platform\r
+// Copyright (c) 2012 Samsung Electronics Co., Ltd. \r
+// \r
+// Licensed under the Apache License, Version 2.0 (the License);\r
+// you may not use this file except in compliance with the License.\r
+// You may obtain a copy of the License at\r
+//\r
+// http://www.apache.org/licenses/LICENSE-2.0\r
+//\r
+// Unless required by applicable law or agreed to in writing, software\r
+// distributed under the License is distributed on an "AS IS" BASIS,\r
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
+// See the License for the specific language governing permissions and\r
+// limitations under the License.\r
+//\r
+/*\r
+ * \r
+ * @file WcharStrings.h\r
+ * @brief This is the header file for utility services including standard libraries.\r
+ *\r
+ * This header file defines utility services including standard libraries.\r
+ */\r
+\r
+#ifndef WcharStrings_h\r
+#define WcharStrings_h\r
+\r
+\r
+\r
+#ifdef __cplusplus\r
+extern "C" {\r
+#endif // __cplusplus\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @ingroup Newliblibc\r
+ * @defgroup NewliblibcWcharStrings WcharStrings\r
+ *\r
+ * @brief %Tizen provides a subset of newlib's Wchar String APIs. @n\r
+ * For more information, refer to the description below.\r
+ *\r
+ * @endif\r
+ */\r
+\r
+ /**\r
+ * @if OSPCOMPAT\r
+ * @addtogroup NewliblibcWcharStrings\r
+ * @{\r
+ */\r
+\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#wcslcat" target="_blank">newlib</a> website.\r
+ */ \r
+ size_t wcslcat(wchar_t *dst, const wchar_t *src, size_t siz);\r
+ /**\r
+ * Refer to the <a href="http://sourceware.org/newlib/libc.html#wcslcpy" target="_blank">newlib</a> website.\r
+ */ \r
+ size_t wcslcpy(wchar_t *dst, const wchar_t *src, size_t siz);\r
+\r
+\r
+ /** \r
+ * @} \r
+ * @endif\r
+ */\r
+\r
+#ifdef __cplusplus\r
+}\r
+#endif // __cplusplus\r
+\r
+#endif // WcharStrings.h\r
--- /dev/null
+//
+// Open Service Platform
+// Copyright (c) 2012 Samsung Electronics Co., Ltd.
+//
+// Licensed under the Apache License, Version 2.0 (the License);
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+/*
+ *
+ * @file libc.h
+ * @brief This is the header file for utility services including standard libraries.
+ *
+ * This header file defines utility services including standard libraries.
+ */
+
+#ifndef libc_h
+#define libc_h
+
+#include <Misc.h>
+#include <Stdio.h>
+#include <Stdlib.h>
+#include <Strings.h>
+#include <WcharStrings.h>
+
+
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @if OSPCOMPAT
+ * @ingroup Newlib
+ * @defgroup Newliblib Newlib
+ * @endif
+ */
+
+ /**
+ * @if OSPCOMPAT
+ * @addtogroup Newliblib
+ *
+ * @brief %Tizen supports a subset of newlib API to support source level compatibility. @n
+ * The following newlib APIs are supported: %Misc, %Stdio, %Stdlib, %Strings, and %WcharStrings.
+ *
+ *
+ * @{
+ */
+
+ /**
+ * @}
+ * @endif
+ */
+
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // libm.h
--- /dev/null
+/*
+ *
+ * @file openal.h
+ * @brief This is the header file for OpenAL.
+ *
+ * This header file defines OpenAL.
+ */
+
+#ifndef openal_h
+#define openal_h
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @defgroup openal OpenAL®
+ *
+ * %OpenAL(R) is a cross-platform, three-dimensional audio method. It can also be referred as a software interface to an audio hardware. @n
+ * The primary purpose of %OpenAL(R) is to allow an application to position audio sources in three-dimensional spaces around a listener and produce reasonable spatialization of the sources for the audio system. @n
+ * Although %OpenAL(R) is appropriate for many audio applications, it is specifically designed for gaming audio.
+ *
+ * For more information, see the <a href="http://connect.creativelabs.com/openal/default.aspx" target="_blank">Creative Labs Web site</a>.
+ *
+ * @since 2.0
+ */
+
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // openal_h
--- /dev/null
+/*
+ *
+ * @file opengl.h
+ * @brief This is the header file for OpenGL.
+ *
+ * This header file defines OpenGL.
+ */
+
+#ifndef opengl_h
+#define opengl_h
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @defgroup opengl OpenGL®
+ *
+ * The %Tizen native framework supports the OpenGL library, which is an API for for rendering high performance 2D and 3D graphic objects. For more information on %Tizen, see Tizen::Graphics::Opengl.
+ * - <a href ="group__opengles.html"> OpenGL® ES</a>
+ * - <a href ="group__opengles__1__1.html"> OpenGL® ES 1.1 </a>
+ * - <a href ="group__opengles__2__0.html"> OpenGL® ES 2.0 </a>
+ *
+ * @since 2.0
+ */
+
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // opengl_h
--- /dev/null
+//
+// Open Service Platform
+// Copyright (c) 2012 Samsung Electronics Co., Ltd.
+//
+// Licensed under the Apache License, Version 2.0 (the License);
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+/*
+ *
+ * @file openmp.h
+ * @brief This is the header file for OpenMP.
+ *
+ * This header file defines OpenMP.
+ */
+
+#ifndef openmp_h
+#define openmp_h
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @defgroup openmp OpenMP®
+ *
+ * The %Tizen native framework supports the OpenMP library, which is an API for shared memory multiprocessing programming.
+ * For more information, see <a href = "../../topic/org.tizen.native.appprogramming/html/guide/libraries/openmp.htm">OpenMP Guide</a>.
+ *
+ * More specifically, %Tizen uses the <a href="http://gcc.gnu.org/projects/gomp/"
+target="_blank" >GOMP project</a> which has developed an implementation of OpenMP. GOMP includes a <a href="http://gcc.gnu.org/onlinedocs/libgomp/" target="_blank" >libgomp</a>.
+ *
+ * @since 2.0
+ */
+
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // openmp_h
--- /dev/null
+//
+// Open Service Platform
+// Copyright (c) 2012 Samsung Electronics Co., Ltd.
+//
+// Licensed under the Apache License, Version 2.0 (the License);
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+/*
+ *
+ * @file stdc++.h
+ * @brief This is the header file for the must-include files.
+ *
+ * This header file defines the must-include files.
+ */
+
+
+#ifndef stdc++_h
+#define stdc++_h
+
+
+
+#ifdef __cplusplus
+extern "C" {
+#endif // __cplusplus
+
+ /**
+ * @defgroup Cplusplus Standard C++ Library
+ *
+ * The %Tizen C++ application supports C++ based on the Standard C++ ANSI ISO 14882 2003, which includes
+ * the Standard Template Library (STL). This helps developers migrate the pre-existing standard
+ * library based applications to the %Tizen platform with minimum effort.
+ *
+ * More specifically, %Tizen supports complete set of libstdc++v3 comprising of standard C++ functions
+ * specified in the Standard C++ ANSI ISO 14882 2003 and the entire Standard Template Library
+ * (http://www.sgi.com/tech/stl/).
+ *
+ * - These methods can be used by including the relevant header file in a standard manner,
+ * for example, "#include <stdio>".
+ *
+ *
+ * - Support for standard C++ library extended to complete set of libstdc++v3 modules, namespaces and classes. @n
+ * For more information, refer to this <a href="http://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-api-4.5/index.html" target="_blank">Web site</a>.
+ *
+ * @remarks The locale based feature is not supported in %Tizen.
+ */
+
+#ifdef __cplusplus
+}
+#endif // __cplusplus
+
+#endif // stdc++_h
--- /dev/null
+# Doxyfile 1.7.4\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project.\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored.\r
+# The format is:\r
+# TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+# TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ").\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# This tag specifies the encoding used for all characters in the config file\r
+# that follow. The default is UTF-8 which is also the encoding used for all\r
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the\r
+# iconv built into libc) for the transcoding. See\r
+# http://www.gnu.org/software/libiconv for the list of possible encodings.\r
+\r
+DOXYFILE_ENCODING = UTF-8\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded\r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME = \r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.\r
+# This could be handy for archiving the generated documentation or\r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER =\r
+\r
+# Using the PROJECT_BRIEF tag one can provide an optional one line description\r
+# for a project that appears at the top of each page and should give viewer\r
+# a quick idea about the purpose of the project. Keep the description short.\r
+\r
+PROJECT_BRIEF =\r
+\r
+# With the PROJECT_LOGO tag one can specify an logo or icon that is\r
+# included in the documentation. The maximum height of the logo should not\r
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.\r
+# Doxygen will copy the logo to the output directory.\r
+\r
+PROJECT_LOGO =\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)\r
+# base path where the generated documentation will be put.\r
+# If a relative path is entered, it will be relative to the location\r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY = \r
+\r
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create\r
+# 4096 sub-directories (in 2 levels) under the output directory of each output\r
+# format and will distribute the generated files over these directories.\r
+# Enabling this option can be useful when feeding doxygen a huge amount of\r
+# source files, where putting all generated files in the same directory would\r
+# otherwise cause performance problems for the file system.\r
+\r
+CREATE_SUBDIRS = NO\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all\r
+# documentation generated by doxygen is written. Doxygen will use this\r
+# information to generate all constant output in the proper language.\r
+# The default language is English, other supported languages are:\r
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,\r
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,\r
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English\r
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,\r
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,\r
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.\r
+\r
+OUTPUT_LANGUAGE = English\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will\r
+# include brief member descriptions after the members that are listed in\r
+# the file and class documentation (similar to JavaDoc).\r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend\r
+# the brief description of a member or function before the detailed description.\r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF = NO\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator\r
+# that is used to form the text in various listings. Each string\r
+# in this list, if found as the leading text of the brief description, will be\r
+# stripped from the text and the result after processing the whole list, is\r
+# used as the annotated text. Otherwise, the brief description is used as-is.\r
+# If left blank, the following values are used ("$name" is automatically\r
+# replaced with the name of the entity): "The $name class" "The $name widget"\r
+# "The $name file" "is" "provides" "specifies" "contains"\r
+# "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF =\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\r
+# Doxygen will generate a detailed section even if there is only a brief\r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC = YES\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\r
+# inherited members of a class in the documentation of that class as if those\r
+# members were ordinary class members. Constructors, destructors and assignment\r
+# operators of the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full\r
+# path before files name in the file list and in the header files. If set\r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag\r
+# can be used to strip a user-defined part of the path. Stripping is\r
+# only done if one of the specified strings matches the left-hand part of\r
+# the path. The tag can be used to show relative paths in the file list.\r
+# If left blank the directory from which doxygen is run is used as the\r
+# path to strip.\r
+\r
+STRIP_FROM_PATH =\r
+\r
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of\r
+# the path mentioned in the documentation of a class, which tells\r
+# the reader which header file to include in order to use a class.\r
+# If left blank only the name of the header file containing the class\r
+# definition is used. Otherwise one should specify the include paths that\r
+# are normally passed to the compiler using the -I flag.\r
+\r
+STRIP_FROM_INC_PATH =\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter\r
+# (but less readable) file names. This can be useful if your file system\r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen\r
+# will interpret the first line (until the first dot) of a JavaDoc-style\r
+# comment as the brief description. If set to NO, the JavaDoc\r
+# comments will behave just like regular Qt-style comments\r
+# (thus requiring an explicit @brief command for a brief description.)\r
+\r
+JAVADOC_AUTOBRIEF = NO\r
+\r
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will\r
+# interpret the first line (until the first dot) of a Qt-style\r
+# comment as the brief description. If set to NO, the comments\r
+# will behave just like regular Qt-style comments (thus requiring\r
+# an explicit \brief command for a brief description.)\r
+\r
+QT_AUTOBRIEF = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen\r
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///\r
+# comments) as a brief description. This used to be the default behaviour.\r
+# The new default is to treat a multi-line C++ comment block as a detailed\r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented\r
+# member inherits the documentation from any documented member that it\r
+# re-implements.\r
+\r
+INHERIT_DOCS = NO\r
+\r
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce\r
+# a new page for each member. If set to NO, the documentation of a member will\r
+# be part of the file/class/namespace that contains it.\r
+\r
+SEPARATE_MEMBER_PAGES = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.\r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts\r
+# as commands in the documentation. An alias has the form "name=value".\r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to\r
+# put the command \sideeffect (or @sideeffect) in the documentation, which\r
+# will result in a user-defined paragraph with heading "Side Effects:".\r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES = "prototype = @b Warning: This is a prototype" \\r
+ "privlevel = @xrefitem privlevel \"Privlevel\" \"Privlevel\"" \\r
+ "privilege = @xrefitem privilege \"Privilege\" \"Privilege\"" \\r
+ "compatibility = @xrefitem compatibility \"Compatibility\" \"Compatibility \"" \\r
+ "final=\par Final:\n @xmlonly <pcheck-final>final</pcheck-final> @endxmlonly "\r
+\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C\r
+# sources only. Doxygen will then generate output that is more tailored for C.\r
+# For instance, some of the names that are used will be different. The list\r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Java. For instance, namespaces will be presented as packages, qualified\r
+# scopes will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA = NO\r
+\r
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Fortran.\r
+\r
+OPTIMIZE_FOR_FORTRAN = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\r
+# sources. Doxygen will then generate output that is tailored for\r
+# VHDL.\r
+\r
+OPTIMIZE_OUTPUT_VHDL = NO\r
+\r
+# Doxygen selects the parser to use depending on the extension of the files it\r
+# parses. With this tag you can assign which parser to use for a given extension.\r
+# Doxygen has a built-in mapping, but you can override or extend it using this\r
+# tag. The format is ext=language, where ext is a file extension, and language\r
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,\r
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make\r
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C\r
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions\r
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.\r
+\r
+EXTENSION_MAPPING =\r
+\r
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\r
+# to include (a tag file for) the STL sources as input, then you should\r
+# set this tag to YES in order to let doxygen match functions declarations and\r
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.\r
+# func(std::string) {}). This also makes the inheritance and collaboration\r
+# diagrams that involve STL classes more complete and accurate.\r
+\r
+BUILTIN_STL_SUPPORT = NO\r
+\r
+# If you use Microsoft's C++/CLI language, you should set this option to YES to\r
+# enable parsing support.\r
+\r
+CPP_CLI_SUPPORT = NO\r
+\r
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.\r
+# Doxygen will parse them like normal C++ but will assume all classes use public\r
+# instead of private inheritance when no explicit protection keyword is present.\r
+\r
+SIP_SUPPORT = NO\r
+\r
+# For Microsoft's IDL there are propget and propput attributes to indicate getter\r
+# and setter methods for a property. Setting this option to YES (the default)\r
+# will make doxygen replace the get and set methods by a property in the\r
+# documentation. This will only work if the methods are indeed getting or\r
+# setting a simple type. If this is not the case, or you want to show the\r
+# methods anyway, you should set this option to NO.\r
+\r
+IDL_PROPERTY_SUPPORT = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\r
+# tag is set to YES, then doxygen will reuse the documentation of the first\r
+# member in the group (if any) for the other members of the group. By default\r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of\r
+# the same type (for instance a group of public functions) to be put as a\r
+# subgroup of that type (e.g. under the Public Functions section). Set it to\r
+# NO to prevent subgrouping. Alternatively, this can be done per class using\r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING = YES\r
+\r
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and\r
+# unions are shown inside the group in which they are included (e.g. using\r
+# @ingroup) instead of on a separate page (for HTML and Man pages) or\r
+# section (for LaTeX and RTF).\r
+\r
+INLINE_GROUPED_CLASSES = NO\r
+\r
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum\r
+# is documented as struct, union, or enum with the name of the typedef. So\r
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\r
+# with name TypeT. When disabled the typedef will appear as a member of a file,\r
+# namespace, or class. And the struct will be named TypeS. This can typically\r
+# be useful for C code in case the coding convention dictates that all compound\r
+# types are typedef'ed and only the typedef is referenced, never the tag name.\r
+\r
+TYPEDEF_HIDES_STRUCT = NO\r
+\r
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to\r
+# determine which symbols to keep in memory and which to flush to disk.\r
+# When the cache is full, less often used symbols will be written to disk.\r
+# For small to medium size projects (<1000 input files) the default value is\r
+# probably good enough. For larger projects a too small cache size can cause\r
+# doxygen to be busy swapping symbols to and from disk most of the time\r
+# causing a significant performance penalty.\r
+# If the system has enough physical memory increasing the cache will improve the\r
+# performance by keeping more symbols in memory. Note that the value works on\r
+# a logarithmic scale so increasing the size by one will roughly double the\r
+# memory usage. The cache size is given by this formula:\r
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,\r
+# corresponding to a cache size of 2^16 = 65536 symbols\r
+\r
+SYMBOL_CACHE_SIZE = 0\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in\r
+# documentation are documented, even if no documentation was available.\r
+# Private class members and static file members will be hidden unless\r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class\r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file\r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC = YES\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)\r
+# defined locally in source files will be included in the documentation.\r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES = NO\r
+\r
+# This flag is only useful for Objective-C code. When set to YES local\r
+# methods, which are defined in the implementation section but not in\r
+# the interface are included in the documentation.\r
+# If set to NO (the default) only methods in the interface are included.\r
+\r
+EXTRACT_LOCAL_METHODS = NO\r
+\r
+# If this flag is set to YES, the members of anonymous namespaces will be\r
+# extracted and appear in the documentation as a namespace called\r
+# 'anonymous_namespace{file}', where file will be replaced with the base\r
+# name of the file that contains the anonymous namespace. By default\r
+# anonymous namespaces are hidden.\r
+\r
+EXTRACT_ANON_NSPACES = NO\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\r
+# undocumented members of documented classes, files or namespaces.\r
+# If set to NO (the default) these members will be included in the\r
+# various overviews, but no documentation section is generated.\r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS = YES\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\r
+# undocumented classes that are normally visible in the class hierarchy.\r
+# If set to NO (the default) these classes will be included in the various\r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES = YES\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all\r
+# friend (class|struct|union) declarations.\r
+# If set to NO (the default) these declarations will be included in the\r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS = YES\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\r
+# documentation blocks found inside the body of a function.\r
+# If set to NO (the default) these blocks will be appended to the\r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS = YES\r
+\r
+# The INTERNAL_DOCS tag determines if documentation\r
+# that is typed after a \internal command is included. If the tag is set\r
+# to NO (the default) then the documentation will be excluded.\r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate\r
+# file names in lower-case letters. If set to YES upper-case letters are also\r
+# allowed. This is useful if you have classes or files whose names only differ\r
+# in case and if your file system supports case sensitive file names. Windows\r
+# and Mac users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen\r
+# will show members with their full class and namespace scopes in the\r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen\r
+# will put a list of the files that are included by a file in the documentation\r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES = NO\r
+\r
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen\r
+# will list include files with double quotes in the documentation\r
+# rather than with sharp brackets.\r
+\r
+FORCE_LOCAL_INCLUDES = NO\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]\r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen\r
+# will sort the (detailed) documentation of file and class members\r
+# alphabetically by member name. If set to NO the members will appear in\r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS = YES\r
+\r
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the\r
+# brief documentation of file, namespace and class members alphabetically\r
+# by member name. If set to NO (the default) the members will appear in\r
+# declaration order.\r
+\r
+SORT_BRIEF_DOCS = YES\r
+\r
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen\r
+# will sort the (brief and detailed) documentation of class members so that\r
+# constructors and destructors are listed first. If set to NO (the default)\r
+# the constructors will appear in the respective orders defined by\r
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.\r
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO\r
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.\r
+\r
+SORT_MEMBERS_CTORS_1ST = NO\r
+\r
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the\r
+# hierarchy of group names into alphabetical order. If set to NO (the default)\r
+# the group names will appear in their defined order.\r
+\r
+SORT_GROUP_NAMES = NO\r
+\r
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be\r
+# sorted by fully-qualified names, including namespaces. If set to\r
+# NO (the default), the class list will be sorted only by class name,\r
+# not including the namespace part.\r
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\r
+# Note: This option applies only to the class list, not to the\r
+# alphabetical list.\r
+\r
+SORT_BY_SCOPE_NAME = YES\r
+\r
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to\r
+# do proper type resolution of all parameters of a function it will reject a\r
+# match between the prototype and the implementation of a member function even\r
+# if there is only one candidate or it is obvious which candidate to choose\r
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen\r
+# will still accept a match between prototype and implementation in such cases.\r
+\r
+STRICT_PROTO_MATCHING = NO\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or\r
+# disable (NO) the todo list. This list is created by putting \todo\r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or\r
+# disable (NO) the test list. This list is created by putting \test\r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or\r
+# disable (NO) the bug list. This list is created by putting \bug\r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST = NO\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or\r
+# disable (NO) the deprecated list. This list is created by putting\r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional\r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines\r
+# the initial value of a variable or macro consists of for it to appear in\r
+# the documentation. If the initializer consists of more lines than specified\r
+# here it will be hidden. Use a value of 0 to hide initializers completely.\r
+# The appearance of the initializer of individual variables and macros in the\r
+# documentation can be controlled using \showinitializer or \hideinitializer\r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated\r
+# at the bottom of the documentation of classes and structs. If set to YES the\r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES = NO\r
+\r
+# If the sources in your project are distributed over multiple directories\r
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy\r
+# in the documentation. The default is NO.\r
+\r
+SHOW_DIRECTORIES = NO\r
+\r
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.\r
+# This will remove the Files entry from the Quick Index and from the\r
+# Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_FILES = YES\r
+\r
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the\r
+# Namespaces page.\r
+# This will remove the Namespaces entry from the Quick Index\r
+# and from the Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_NAMESPACES = YES\r
+\r
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that\r
+# doxygen should invoke to get the current version for each file (typically from\r
+# the version control system). Doxygen will invoke the program by executing (via\r
+# popen()) the command <command> <input-file>, where <command> is the value of\r
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file\r
+# provided by doxygen. Whatever the program writes to standard output\r
+# is used as the file version. See the manual for examples.\r
+\r
+FILE_VERSION_FILTER =\r
+\r
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\r
+# by doxygen. The layout file controls the global structure of the generated\r
+# output files in an output format independent way. The create the layout file\r
+# that represents doxygen's defaults, run doxygen with the -l option.\r
+# You can optionally specify a file name after the option, if omitted\r
+# DoxygenLayout.xml will be used as the name of the layout file.\r
+\r
+LAYOUT_FILE = DoxygenLayout.xml\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated\r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are\r
+# generated by doxygen. Possible values are YES and NO. If left blank\r
+# NO is used.\r
+\r
+WARNINGS = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings\r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will\r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED = YES\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for\r
+# potential errors in the documentation, such as not documenting some\r
+# parameters in a documented function, or documenting parameters that\r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR = YES\r
+\r
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for\r
+# functions that are documented, but have no documentation for their parameters\r
+# or return value. If set to NO (the default) doxygen will only warn about\r
+# wrong or incomplete parameter documentation, but not about the absence of\r
+# documentation.\r
+\r
+WARN_NO_PARAMDOC = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that\r
+# doxygen can produce. The string should contain the $file, $line, and $text\r
+# tags, which will be replaced by the file and line number from which the\r
+# warning originated and the warning text. Optionally the format may contain\r
+# $version, which will be replaced by the version of the file (if it could\r
+# be obtained via FILE_VERSION_FILTER)\r
+\r
+WARN_FORMAT = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning\r
+# and error messages should be written. If left blank the output is written\r
+# to stderr.\r
+\r
+WARN_LOGFILE = warning-public-platform.txt\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain\r
+# documented source files. You may enter file names like "myfile.cpp" or\r
+# directories like "/usr/src/myproject". Separate the files or directories\r
+# with spaces.\r
+\r
+INPUT = ../../../../framework/osp/osp-appfw/inc/FBaseSysLog.h \r
+\r
+# This tag can be used to specify the character encoding of the source files\r
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is\r
+# also the default input encoding. Doxygen uses libiconv (or the iconv built\r
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for\r
+# the list of possible encodings.\r
+\r
+INPUT_ENCODING = UTF-8\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank the following patterns are tested:\r
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh\r
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py\r
+# *.f90 *.f *.for *.vhd *.vhdl\r
+\r
+FILE_PATTERNS = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories\r
+# should be searched for input files as well. Possible values are YES and NO.\r
+# If left blank NO is used.\r
+\r
+RECURSIVE = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should\r
+# excluded from the INPUT source files. This way you can easily exclude a\r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE = \r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or\r
+# directories that are symbolic links (a Unix file system feature) are excluded\r
+# from the input.\r
+\r
+EXCLUDE_SYMLINKS = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\r
+# certain files from those directories. Note that the wildcards are matched\r
+# against the file with absolute path, so to exclude all test directories\r
+# for example use the pattern */test/*\r
+\r
+EXCLUDE_PATTERNS = \r
+\r
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\r
+# (namespaces, classes, functions, etc.) that should be excluded from the\r
+# output. The symbol name can be a fully qualified name, a word, or if the\r
+# wildcard * is used, a substring. Examples: ANamespace, AClass,\r
+# AClass::ANamespace, ANamespace::*Test\r
+\r
+EXCLUDE_SYMBOLS =\r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or\r
+# directories that contain example code fragments that are included (see\r
+# the \include command).\r
+\r
+EXAMPLE_PATH =\r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the\r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS =\r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\r
+# searched for input files to be used with the \include or \dontinclude\r
+# commands irrespective of the value of the RECURSIVE tag.\r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or\r
+# directories that contain image that are included in the documentation (see\r
+# the \image command).\r
+\r
+IMAGE_PATH = public-platform-developer/images\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should\r
+# invoke to filter for each input file. Doxygen will invoke the filter program\r
+# by executing (via popen()) the command <filter> <input-file>, where <filter>\r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an\r
+# input file. Doxygen will then use the output that the filter program writes\r
+# to standard output.\r
+# If FILTER_PATTERNS is specified, this tag will be\r
+# ignored.\r
+\r
+INPUT_FILTER =\r
+\r
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\r
+# basis.\r
+# Doxygen will compare the file name with each pattern and apply the\r
+# filter if there is a match.\r
+# The filters are a list of the form:\r
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further\r
+# info on how filters are used. If FILTER_PATTERNS is empty or if\r
+# non of the patterns match the file name, INPUT_FILTER is applied.\r
+\r
+FILTER_PATTERNS =\r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\r
+# INPUT_FILTER) will be used to filter the input files when producing source\r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES = NO\r
+\r
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\r
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)\r
+# and it is also possible to disable source filtering for a specific pattern\r
+# using *.ext= (so without naming a filter). This option only has effect when\r
+# FILTER_SOURCE_FILES is enabled.\r
+\r
+FILTER_SOURCE_PATTERNS =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will\r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+# Note: To get rid of all source code in the generated output, make sure also\r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body\r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct\r
+# doxygen to hide any special comment blocks from generated source code\r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES\r
+# then for each documented function all documented\r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = NO\r
+\r
+# If the REFERENCES_RELATION tag is set to YES\r
+# then for each documented function all documented entities\r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION = NO\r
+\r
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\r
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\r
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\r
+# link to the source code.\r
+# Otherwise they will link to the documentation.\r
+\r
+REFERENCES_LINK_SOURCE = NO\r
+\r
+# If the USE_HTAGS tag is set to YES then the references to source code\r
+# will point to the HTML generated by the htags(1) tool instead of doxygen\r
+# built-in source browser. The htags tool is part of GNU's global source\r
+# tagging system (see http://www.gnu.org/software/global/global.html). You\r
+# will need version 4.8.6 or higher.\r
+\r
+USE_HTAGS = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen\r
+# will generate a verbatim copy of the header file for each class for\r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index\r
+# of all compounds will be generated. Enable this if the project\r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then\r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns\r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX = 5\r
+\r
+# In case all classes in a project start with a common prefix, all\r
+# classes will be put under the same header in the alphabetical index.\r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that\r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will\r
+# generate HTML output.\r
+\r
+GENERATE_HTML = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT = apidocs-platform\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for\r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank\r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard header. Note that when using a custom header you are responsible\r
+# for the proper inclusion of any scripts and style sheets that doxygen\r
+# needs, which is dependent on the configuration options used.\r
+# It is adviced to generate a default header using "doxygen -w html\r
+# header.html footer.html stylesheet.css YourConfigFile" and then modify\r
+# that header. Note that the header is subject to change so you typically\r
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!\r
+\r
+HTML_HEADER =\r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard footer.\r
+\r
+HTML_FOOTER = footer.html\r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading\r
+# style sheet that is used by each HTML page. It can be used to\r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen\r
+# will generate a default style sheet. Note that doxygen will try to copy\r
+# the style sheet file to the HTML output directory, so don't put your own\r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET = Tizen.css\r
+\r
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\r
+# other source files which should be copied to the HTML output directory. Note\r
+# that these files will be copied to the base HTML output directory. Use the\r
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\r
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that\r
+# the files will be copied as-is; there are no commands or markers available.\r
+\r
+HTML_EXTRA_FILES =\r
+\r
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.\r
+# Doxygen will adjust the colors in the stylesheet and background images\r
+# according to this color. Hue is specified as an angle on a colorwheel,\r
+# see http://en.wikipedia.org/wiki/Hue for more information.\r
+# For instance the value 0 represents red, 60 is yellow, 120 is green,\r
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.\r
+# The allowed range is 0 to 359.\r
+\r
+HTML_COLORSTYLE_HUE = 220\r
+\r
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of\r
+# the colors in the HTML output. For a value of 0 the output will use\r
+# grayscales only. A value of 255 will produce the most vivid colors.\r
+\r
+HTML_COLORSTYLE_SAT = 100\r
+\r
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to\r
+# the luminance component of the colors in the HTML output. Values below\r
+# 100 gradually make the output lighter, whereas values above 100 make\r
+# the output darker. The value divided by 100 is the actual gamma applied,\r
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,\r
+# and 100 does not change the gamma.\r
+\r
+HTML_COLORSTYLE_GAMMA = 80\r
+\r
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\r
+# page will contain the date and time when the page was generated. Setting\r
+# this to NO can help when comparing the output of multiple runs.\r
+\r
+HTML_TIMESTAMP = YES\r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,\r
+# files or namespaces will be aligned in HTML using tables. If set to\r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS = YES\r
+\r
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\r
+# documentation will contain sections that can be hidden and shown after the\r
+# page has loaded. For this to work a browser that supports\r
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox\r
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).\r
+\r
+HTML_DYNAMIC_SECTIONS = NO\r
+\r
+# If the GENERATE_DOCSET tag is set to YES, additional index files\r
+# will be generated that can be used as input for Apple's Xcode 3\r
+# integrated development environment, introduced with OSX 10.5 (Leopard).\r
+# To create a documentation set, doxygen will generate a Makefile in the\r
+# HTML output directory. Running make will produce the docset in that\r
+# directory and running "make install" will install the docset in\r
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find\r
+# it at startup.\r
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html\r
+# for more information.\r
+\r
+GENERATE_DOCSET = NO\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the\r
+# feed. A documentation feed provides an umbrella under which multiple\r
+# documentation sets from a single provider (such as a company or product suite)\r
+# can be grouped.\r
+\r
+DOCSET_FEEDNAME = "Doxygen generated docs"\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that\r
+# should uniquely identify the documentation set bundle. This should be a\r
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen\r
+# will append .docset to the name.\r
+\r
+DOCSET_BUNDLE_ID = org.doxygen.Project\r
+\r
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify\r
+# the documentation publisher. This should be a reverse domain-name style\r
+# string, e.g. com.mycompany.MyDocSet.documentation.\r
+\r
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher\r
+\r
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.\r
+\r
+DOCSET_PUBLISHER_NAME = Publisher\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files\r
+# will be generated that can be used as input for tools like the\r
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)\r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can\r
+# be used to specify the file name of the resulting .chm file. You\r
+# can add a path in front of the file if the result should not be\r
+# written to the html output directory.\r
+\r
+CHM_FILE =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can\r
+# be used to specify the location (absolute path including file name) of\r
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run\r
+# the HTML help compiler on the generated index.hhp.\r
+\r
+HHC_LOCATION =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag\r
+# controls if a separate .chi index file is generated (YES) or that\r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\r
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file\r
+# content.\r
+\r
+CHM_INDEX_ENCODING =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag\r
+# controls whether a binary table of contents is generated (YES) or a\r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC = YES\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members\r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND = YES\r
+\r
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\r
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated\r
+# that can be used as input for Qt's qhelpgenerator to generate a\r
+# Qt Compressed Help (.qch) of the generated HTML documentation.\r
+\r
+GENERATE_QHP = NO\r
+\r
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can\r
+# be used to specify the file name of the resulting .qch file.\r
+# The path specified is relative to the HTML output folder.\r
+\r
+QCH_FILE =\r
+\r
+# The QHP_NAMESPACE tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#namespace\r
+\r
+QHP_NAMESPACE = org.doxygen.Project\r
+\r
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders\r
+\r
+QHP_VIRTUAL_FOLDER = doc\r
+\r
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to\r
+# add. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#custom-filters\r
+\r
+QHP_CUST_FILTER_NAME =\r
+\r
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the\r
+# custom filter to add. For more information please see\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">\r
+# Qt Help Project / Custom Filters</a>.\r
+\r
+QHP_CUST_FILTER_ATTRS =\r
+\r
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\r
+# project's\r
+# filter section matches.\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">\r
+# Qt Help Project / Filter Attributes</a>.\r
+\r
+QHP_SECT_FILTER_ATTRS =\r
+\r
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can\r
+# be used to specify the location of Qt's qhelpgenerator.\r
+# If non-empty doxygen will try to run qhelpgenerator on the generated\r
+# .qhp file.\r
+\r
+QHG_LOCATION =\r
+\r
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files\r
+# will be generated, which together with the HTML files, form an Eclipse help\r
+# plugin. To install this plugin and make it available under the help contents\r
+# menu in Eclipse, the contents of the directory containing the HTML and XML\r
+# files needs to be copied into the plugins directory of eclipse. The name of\r
+# the directory within the plugins directory should be the same as\r
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before\r
+# the help appears.\r
+\r
+GENERATE_ECLIPSEHELP = YES\r
+\r
+# A unique identifier for the eclipse help plugin. When installing the plugin\r
+# the directory name containing the HTML and XML files should also have\r
+# this name.\r
+\r
+ECLIPSE_DOC_ID = org.doxygen.Project\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at\r
+# top of each HTML page. The value NO (the default) enables the index and\r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX = NO\r
+\r
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values\r
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML\r
+# documentation. Note that a value of 0 will completely suppress the enum\r
+# values from appearing in the overview section.\r
+\r
+ENUM_VALUES_PER_LINE = 4\r
+\r
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\r
+# structure should be generated to display hierarchical information.\r
+# If the tag value is set to YES, a side panel will be generated\r
+# containing a tree-like index structure (just like the one that\r
+# is generated for HTML Help). For this to work a browser that supports\r
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).\r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW = NO\r
+\r
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,\r
+# and Class Hierarchy pages using a tree view instead of an ordered list.\r
+\r
+USE_INLINE_TREES = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be\r
+# used to set the initial width (in pixels) of the frame in which the tree\r
+# is shown.\r
+\r
+TREEVIEW_WIDTH = 250\r
+\r
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open\r
+# links to external symbols imported via tag files in a separate window.\r
+\r
+EXT_LINKS_IN_WINDOW = NO\r
+\r
+# Use this tag to change the font size of Latex formulas included\r
+# as images in the HTML documentation. The default is 10. Note that\r
+# when you change the font size after a successful doxygen run you need\r
+# to manually remove any form_*.png images from the HTML output directory\r
+# to force them to be regenerated.\r
+\r
+FORMULA_FONTSIZE = 10\r
+\r
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images\r
+# generated for formulas are transparent PNGs. Transparent PNGs are\r
+# not supported properly for IE 6.0, but are supported on all modern browsers.\r
+# Note that when changing this option you need to delete any form_*.png files\r
+# in the HTML output before the changes have effect.\r
+\r
+FORMULA_TRANSPARENT = YES\r
+\r
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax\r
+# (see http://www.mathjax.org) which uses client side Javascript for the\r
+# rendering instead of using prerendered bitmaps. Use this if you do not\r
+# have LaTeX installed or if you want to formulas look prettier in the HTML\r
+# output. When enabled you also need to install MathJax separately and\r
+# configure the path to it using the MATHJAX_RELPATH option.\r
+\r
+USE_MATHJAX = NO\r
+\r
+# When MathJax is enabled you need to specify the location relative to the\r
+# HTML output directory using the MATHJAX_RELPATH option. The destination\r
+# directory should contain the MathJax.js script. For instance, if the mathjax\r
+# directory is located at the same level as the HTML output directory, then\r
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the\r
+# mathjax.org site, so you can quickly see the result without installing\r
+# MathJax, but it is strongly recommended to install a local copy of MathJax\r
+# before deployment.\r
+\r
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax\r
+\r
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box\r
+# for the HTML output. The underlying search engine uses javascript\r
+# and DHTML and should work on any modern browser. Note that when using\r
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets\r
+# (GENERATE_DOCSET) there is already a search function so this one should\r
+# typically be disabled. For large projects the javascript based search engine\r
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.\r
+\r
+SEARCHENGINE = NO\r
+\r
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be\r
+# implemented using a PHP enabled web server instead of at the web client\r
+# using Javascript. Doxygen will generate the search PHP script and index\r
+# file to put on the web server. The advantage of the server\r
+# based approach is that it scales better to large projects and allows\r
+# full text search. The disadvantages are that it is more difficult to setup\r
+# and does not have live searching capabilities.\r
+\r
+SERVER_BASED_SEARCH = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will\r
+# generate Latex output.\r
+\r
+GENERATE_LATEX = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be\r
+# invoked. If left blank `latex' will be used as the default command name.\r
+# Note that when enabling USE_PDFLATEX this option is only used for\r
+# generating bitmaps for formulas in the HTML output, but not in the\r
+# Makefile that is written to the output directory.\r
+\r
+LATEX_CMD_NAME = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to\r
+# generate index for LaTeX. If left blank `makeindex' will be used as the\r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact\r
+# LaTeX documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_LATEX = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used\r
+# by the printer. Possible values are: a4, letter, legal and\r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX\r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES =\r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for\r
+# the generated latex document. The header should contain everything until\r
+# the first chapter. If it is left blank doxygen will generate a\r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER =\r
+\r
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for\r
+# the generated latex document. The footer should contain everything after\r
+# the last chapter. If it is left blank doxygen will generate a\r
+# standard footer. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_FOOTER =\r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated\r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will\r
+# contain links (just like the HTML output) instead of page references\r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of\r
+# plain latex in the generated Makefile. Set this option to YES to get a\r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.\r
+# command to the generated LaTeX files. This will instruct LaTeX to keep\r
+# running if errors occur, instead of asking the user for help.\r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not\r
+# include the index chapters (such as File Index, Compound Index, etc.)\r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES = NO\r
+\r
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include\r
+# source code with syntax highlighting in the LaTeX output.\r
+# Note that which sources are shown also depends on other settings\r
+# such as SOURCE_BROWSER.\r
+\r
+LATEX_SOURCE_CODE = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output\r
+# The RTF output is optimized for Word 97 and may not look very pretty with\r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact\r
+# RTF documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_RTF = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated\r
+# will contain hyperlink fields. The RTF file will\r
+# contain links (just like the HTML output) instead of page references.\r
+# This makes the output suitable for online browsing using WORD or other\r
+# programs which support those fields.\r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's\r
+# config file, i.e. a series of assignments. You only have to provide\r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE =\r
+\r
+# Set optional variables used in the generation of an rtf document.\r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will\r
+# generate man pages\r
+\r
+GENERATE_MAN = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to\r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,\r
+# then it will generate one additional man file for each entity\r
+# documented in the real man page(s). These additional files\r
+# only source the real man page, but without them the man command\r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will\r
+# generate an XML file that captures the structure of\r
+# the code including all documentation.\r
+\r
+GENERATE_XML = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT = xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA =\r
+\r
+# The XML_DTD tag can be used to specify an XML DTD,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_DTD =\r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will\r
+# dump the program listings (including syntax highlighting\r
+# and cross-referencing information) to the XML output. Note that\r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will\r
+# generate an AutoGen Definitions (see autogen.sf.net) file\r
+# that captures the structure of the code including all\r
+# documentation. Note that this feature is still experimental\r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will\r
+# generate a Perl module file that captures the structure of\r
+# the code including all documentation. Note that this\r
+# feature is still experimental and incomplete at the\r
+# moment.\r
+\r
+GENERATE_PERLMOD = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate\r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able\r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be\r
+# nicely formatted so it can be parsed by a human reader.\r
+# This is useful\r
+# if you want to understand what is going on.\r
+# On the other hand, if this\r
+# tag is set to NO the size of the Perl module output will be much smaller\r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file\r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.\r
+# This is useful so different doxyrules.make files included by the same\r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will\r
+# evaluate all C-preprocessor directives found in the sources and include\r
+# files.\r
+\r
+ENABLE_PREPROCESSING = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro\r
+# names in the source code. If set to NO (the default) only conditional\r
+# compilation will be performed. Macro expansion can be done in a controlled\r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES\r
+# then the macro expansion is limited to the macros specified with the\r
+# PREDEFINED and EXPAND_AS_DEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF = NO\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files\r
+# pointed to by INCLUDE_PATH will be searched when a #include is found.\r
+\r
+SEARCH_INCLUDES = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that\r
+# contain include files that are not input files but should be processed by\r
+# the preprocessor.\r
+\r
+INCLUDE_PATH =\r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard\r
+# patterns (like *.h and *.hpp) to filter out the header-files in the\r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will\r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS =\r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that\r
+# are defined before the preprocessor is started (similar to the -D option of\r
+# gcc). The argument of the tag is a list of macros of the form: name\r
+# or name=definition (no spaces). If the definition and the = are\r
+# omitted =1 is assumed. To prevent a macro definition from being\r
+# undefined via #undef or recursively expanded use the := operator\r
+# instead of the = operator.\r
+\r
+PREDEFINED = LIBXML_OUTPUT_ENABLED LIBXML_PUSH_ENABLED LIBXML_TREE_ENABLED LIBXML_HTML_ENABLED _OSP_EXPORT_= _OSP_LOCAL_=\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then\r
+# this tag can be used to specify a list of macro names that should be expanded.\r
+# The macro definition that is found in the sources will be used.\r
+# Use the PREDEFINED tag if you want to use a different macro definition that\r
+# overrules the definition found in the source code.\r
+\r
+EXPAND_AS_DEFINED =\r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then\r
+# doxygen's preprocessor will remove all references to function-like macros\r
+# that are alone on a line, have an all uppercase name, and do not end with a\r
+# semicolon, because these will confuse the parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::additions related to external references\r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles.\r
+# Optionally an initial location of the external documentation\r
+# can be added for each tagfile. The format of a tag file without\r
+# this location is as follows:\r
+#\r
+# TAGFILES = file1 file2 ...\r
+# Adding location for the tag files is done as follows:\r
+#\r
+# TAGFILES = file1=loc1 "file2 = loc2" ...\r
+# where "loc1" and "loc2" can be relative or absolute paths or\r
+# URLs. If a location is present for each tag, the installdox tool\r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen\r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES =\r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create\r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE =\r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed\r
+# in the class index. If set to NO only the inherited external classes\r
+# will be listed.\r
+\r
+ALLEXTERNALS = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed\r
+# in the modules index. If set to NO, only the current project's groups will\r
+# be listed.\r
+\r
+EXTERNAL_GROUPS = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script\r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool\r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will\r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base\r
+# or super classes. Setting the tag to NO turns the diagrams off. Note that\r
+# this option also works with HAVE_DOT disabled, but it is recommended to\r
+# install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS = YES\r
+\r
+# You can define message sequence charts within doxygen comments using the \msc\r
+# command. Doxygen will then run the mscgen tool (see\r
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the\r
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where\r
+# the mscgen tool resides. If left empty the tool is assumed to be found in the\r
+# default search path.\r
+\r
+MSCGEN_PATH =\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide\r
+# inheritance and usage relations if the target is undocumented\r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\r
+# available from the path. This tool is part of Graphviz, a graph visualization\r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section\r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT = NO\r
+\r
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is\r
+# allowed to run in parallel. When set to 0 (the default) doxygen will\r
+# base this on the number of processors available in the system. You can set it\r
+# explicitly to a value larger than 0 to get control over the balance\r
+# between CPU load and processing speed.\r
+\r
+DOT_NUM_THREADS = 0\r
+\r
+# By default doxygen will write a font called Helvetica to the output\r
+# directory and reference it in all dot files that doxygen generates.\r
+# When you want a differently looking font you can specify the font name\r
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,\r
+# which can be done by putting it in a standard location or by setting the\r
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory\r
+# containing the font.\r
+\r
+DOT_FONTNAME = FreeSans\r
+\r
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.\r
+# The default size is 10pt.\r
+\r
+DOT_FONTSIZE = 10\r
+\r
+# By default doxygen will tell dot to use the output directory to look for the\r
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a\r
+# different font using DOT_FONTNAME you can set the path where dot\r
+# can find it using this tag.\r
+\r
+DOT_FONTPATH =\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect inheritance relations. Setting this tag to YES will force the\r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect implementation dependencies (inheritance, containment, and\r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH = YES\r
+\r
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for groups, showing the direct groups dependencies\r
+\r
+GROUP_GRAPHS = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and\r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling\r
+# Language.\r
+\r
+UML_LOOK = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the\r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT\r
+# tags are set to YES then doxygen will generate a graph for each documented\r
+# file showing the direct and indirect include dependencies of the file with\r
+# other documented files.\r
+\r
+INCLUDE_GRAPH = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and\r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each\r
+# documented header file showing the documented files that directly or\r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then\r
+# doxygen will generate a call dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable call graphs\r
+# for selected functions only using the \callgraph command.\r
+\r
+CALL_GRAPH = NO\r
+\r
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then\r
+# doxygen will generate a caller dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable caller\r
+# graphs for selected functions only using the \callergraph command.\r
+\r
+CALLER_GRAPH = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY = YES\r
+\r
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES\r
+# then doxygen will show the dependencies a directory has on other directories\r
+# in a graphical way. The dependency relations are determined by the #include\r
+# relations between the files in the directories.\r
+\r
+DIRECTORY_GRAPH = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\r
+# generated by dot. Possible values are svg, png, jpg, or gif.\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be\r
+# found. If left blank, it is assumed the dot tool can be found in the path.\r
+\r
+DOT_PATH =\r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that\r
+# contain dot files that are included in the documentation (see the\r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS =\r
+\r
+# The MSCFILE_DIRS tag can be used to specify one or more directories that\r
+# contain msc files that are included in the documentation (see the\r
+# \mscfile command).\r
+\r
+MSCFILE_DIRS =\r
+\r
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of\r
+# nodes that will be shown in the graph. If the number of nodes in a graph\r
+# becomes larger than this value, doxygen will truncate the graph, which is\r
+# visualized by representing a node as a red box. Note that doxygen if the\r
+# number of direct children of the root node in a graph is already larger than\r
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note\r
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\r
+\r
+DOT_GRAPH_MAX_NODES = 50\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the\r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable\r
+# from the root by following a path via at most 3 edges will be shown. Nodes\r
+# that lay further from the root node will be omitted. Note that setting this\r
+# option to 1 or 2 may greatly reduce the computation time needed for large\r
+# code bases. Also note that the size of a graph can be further restricted by\r
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\r
+\r
+MAX_DOT_GRAPH_DEPTH = 0\r
+\r
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent\r
+# background. This is disabled by default, because dot on Windows does not\r
+# seem to support this out of the box. Warning: Depending on the platform used,\r
+# enabling this option may lead to badly anti-aliased labels on the edges of\r
+# a graph (i.e. they become hard to read).\r
+\r
+DOT_TRANSPARENT = NO\r
+\r
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output\r
+# files in one run (i.e. multiple -o and -T options on the command line). This\r
+# makes dot run faster, but since only newer versions of dot (>1.8.10)\r
+# support this, this feature is disabled by default.\r
+\r
+DOT_MULTI_TARGETS = NO\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will\r
+# generate a legend page explaining the meaning of the various boxes and\r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will\r
+# remove the intermediate dot files that are used to generate\r
+# the various graphs.\r
+\r
+DOT_CLEANUP = YES\r
--- /dev/null
+# Doxyfile 1.7.4\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project.\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored.\r
+# The format is:\r
+# TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+# TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ").\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# This tag specifies the encoding used for all characters in the config file\r
+# that follow. The default is UTF-8 which is also the encoding used for all\r
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the\r
+# iconv built into libc) for the transcoding. See\r
+# http://www.gnu.org/software/libiconv for the list of possible encodings.\r
+\r
+DOXYFILE_ENCODING = UTF-8\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded\r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME = \r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.\r
+# This could be handy for archiving the generated documentation or\r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER =\r
+\r
+# Using the PROJECT_BRIEF tag one can provide an optional one line description\r
+# for a project that appears at the top of each page and should give viewer\r
+# a quick idea about the purpose of the project. Keep the description short.\r
+\r
+PROJECT_BRIEF =\r
+\r
+# With the PROJECT_LOGO tag one can specify an logo or icon that is\r
+# included in the documentation. The maximum height of the logo should not\r
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.\r
+# Doxygen will copy the logo to the output directory.\r
+\r
+PROJECT_LOGO =\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)\r
+# base path where the generated documentation will be put.\r
+# If a relative path is entered, it will be relative to the location\r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY = \r
+\r
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create\r
+# 4096 sub-directories (in 2 levels) under the output directory of each output\r
+# format and will distribute the generated files over these directories.\r
+# Enabling this option can be useful when feeding doxygen a huge amount of\r
+# source files, where putting all generated files in the same directory would\r
+# otherwise cause performance problems for the file system.\r
+\r
+CREATE_SUBDIRS = NO\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all\r
+# documentation generated by doxygen is written. Doxygen will use this\r
+# information to generate all constant output in the proper language.\r
+# The default language is English, other supported languages are:\r
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,\r
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,\r
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English\r
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,\r
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,\r
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.\r
+\r
+OUTPUT_LANGUAGE = English\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will\r
+# include brief member descriptions after the members that are listed in\r
+# the file and class documentation (similar to JavaDoc).\r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend\r
+# the brief description of a member or function before the detailed description.\r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF = NO\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator\r
+# that is used to form the text in various listings. Each string\r
+# in this list, if found as the leading text of the brief description, will be\r
+# stripped from the text and the result after processing the whole list, is\r
+# used as the annotated text. Otherwise, the brief description is used as-is.\r
+# If left blank, the following values are used ("$name" is automatically\r
+# replaced with the name of the entity): "The $name class" "The $name widget"\r
+# "The $name file" "is" "provides" "specifies" "contains"\r
+# "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF =\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\r
+# Doxygen will generate a detailed section even if there is only a brief\r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC = YES\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\r
+# inherited members of a class in the documentation of that class as if those\r
+# members were ordinary class members. Constructors, destructors and assignment\r
+# operators of the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full\r
+# path before files name in the file list and in the header files. If set\r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag\r
+# can be used to strip a user-defined part of the path. Stripping is\r
+# only done if one of the specified strings matches the left-hand part of\r
+# the path. The tag can be used to show relative paths in the file list.\r
+# If left blank the directory from which doxygen is run is used as the\r
+# path to strip.\r
+\r
+STRIP_FROM_PATH =\r
+\r
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of\r
+# the path mentioned in the documentation of a class, which tells\r
+# the reader which header file to include in order to use a class.\r
+# If left blank only the name of the header file containing the class\r
+# definition is used. Otherwise one should specify the include paths that\r
+# are normally passed to the compiler using the -I flag.\r
+\r
+STRIP_FROM_INC_PATH =\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter\r
+# (but less readable) file names. This can be useful if your file system\r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen\r
+# will interpret the first line (until the first dot) of a JavaDoc-style\r
+# comment as the brief description. If set to NO, the JavaDoc\r
+# comments will behave just like regular Qt-style comments\r
+# (thus requiring an explicit @brief command for a brief description.)\r
+\r
+JAVADOC_AUTOBRIEF = NO\r
+\r
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will\r
+# interpret the first line (until the first dot) of a Qt-style\r
+# comment as the brief description. If set to NO, the comments\r
+# will behave just like regular Qt-style comments (thus requiring\r
+# an explicit \brief command for a brief description.)\r
+\r
+QT_AUTOBRIEF = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen\r
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///\r
+# comments) as a brief description. This used to be the default behaviour.\r
+# The new default is to treat a multi-line C++ comment block as a detailed\r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented\r
+# member inherits the documentation from any documented member that it\r
+# re-implements.\r
+\r
+INHERIT_DOCS = NO\r
+\r
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce\r
+# a new page for each member. If set to NO, the documentation of a member will\r
+# be part of the file/class/namespace that contains it.\r
+\r
+SEPARATE_MEMBER_PAGES = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.\r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts\r
+# as commands in the documentation. An alias has the form "name=value".\r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to\r
+# put the command \sideeffect (or @sideeffect) in the documentation, which\r
+# will result in a user-defined paragraph with heading "Side Effects:".\r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES = "prototype = @b Warning: This is a prototype" \\r
+ "privlevel = @xrefitem privlevel \"Privlevel\" \"Privlevel\"" \\r
+ "privilege = @xrefitem privilege \"Privilege\" \"Privilege\"" \\r
+ "compatibility = @xrefitem compatibility \"Compatibility\" \"Compatibility \"" \\r
+ "final=\par Final:\n @xmlonly <pcheck-final>final</pcheck-final> @endxmlonly "\r
+\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C\r
+# sources only. Doxygen will then generate output that is more tailored for C.\r
+# For instance, some of the names that are used will be different. The list\r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Java. For instance, namespaces will be presented as packages, qualified\r
+# scopes will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA = NO\r
+\r
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Fortran.\r
+\r
+OPTIMIZE_FOR_FORTRAN = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\r
+# sources. Doxygen will then generate output that is tailored for\r
+# VHDL.\r
+\r
+OPTIMIZE_OUTPUT_VHDL = NO\r
+\r
+# Doxygen selects the parser to use depending on the extension of the files it\r
+# parses. With this tag you can assign which parser to use for a given extension.\r
+# Doxygen has a built-in mapping, but you can override or extend it using this\r
+# tag. The format is ext=language, where ext is a file extension, and language\r
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,\r
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make\r
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C\r
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions\r
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.\r
+\r
+EXTENSION_MAPPING =\r
+\r
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\r
+# to include (a tag file for) the STL sources as input, then you should\r
+# set this tag to YES in order to let doxygen match functions declarations and\r
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.\r
+# func(std::string) {}). This also makes the inheritance and collaboration\r
+# diagrams that involve STL classes more complete and accurate.\r
+\r
+BUILTIN_STL_SUPPORT = NO\r
+\r
+# If you use Microsoft's C++/CLI language, you should set this option to YES to\r
+# enable parsing support.\r
+\r
+CPP_CLI_SUPPORT = NO\r
+\r
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.\r
+# Doxygen will parse them like normal C++ but will assume all classes use public\r
+# instead of private inheritance when no explicit protection keyword is present.\r
+\r
+SIP_SUPPORT = NO\r
+\r
+# For Microsoft's IDL there are propget and propput attributes to indicate getter\r
+# and setter methods for a property. Setting this option to YES (the default)\r
+# will make doxygen replace the get and set methods by a property in the\r
+# documentation. This will only work if the methods are indeed getting or\r
+# setting a simple type. If this is not the case, or you want to show the\r
+# methods anyway, you should set this option to NO.\r
+\r
+IDL_PROPERTY_SUPPORT = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\r
+# tag is set to YES, then doxygen will reuse the documentation of the first\r
+# member in the group (if any) for the other members of the group. By default\r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of\r
+# the same type (for instance a group of public functions) to be put as a\r
+# subgroup of that type (e.g. under the Public Functions section). Set it to\r
+# NO to prevent subgrouping. Alternatively, this can be done per class using\r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING = YES\r
+\r
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and\r
+# unions are shown inside the group in which they are included (e.g. using\r
+# @ingroup) instead of on a separate page (for HTML and Man pages) or\r
+# section (for LaTeX and RTF).\r
+\r
+INLINE_GROUPED_CLASSES = NO\r
+\r
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum\r
+# is documented as struct, union, or enum with the name of the typedef. So\r
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\r
+# with name TypeT. When disabled the typedef will appear as a member of a file,\r
+# namespace, or class. And the struct will be named TypeS. This can typically\r
+# be useful for C code in case the coding convention dictates that all compound\r
+# types are typedef'ed and only the typedef is referenced, never the tag name.\r
+\r
+TYPEDEF_HIDES_STRUCT = NO\r
+\r
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to\r
+# determine which symbols to keep in memory and which to flush to disk.\r
+# When the cache is full, less often used symbols will be written to disk.\r
+# For small to medium size projects (<1000 input files) the default value is\r
+# probably good enough. For larger projects a too small cache size can cause\r
+# doxygen to be busy swapping symbols to and from disk most of the time\r
+# causing a significant performance penalty.\r
+# If the system has enough physical memory increasing the cache will improve the\r
+# performance by keeping more symbols in memory. Note that the value works on\r
+# a logarithmic scale so increasing the size by one will roughly double the\r
+# memory usage. The cache size is given by this formula:\r
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,\r
+# corresponding to a cache size of 2^16 = 65536 symbols\r
+\r
+SYMBOL_CACHE_SIZE = 0\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in\r
+# documentation are documented, even if no documentation was available.\r
+# Private class members and static file members will be hidden unless\r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class\r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file\r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC = YES\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)\r
+# defined locally in source files will be included in the documentation.\r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES = NO\r
+\r
+# This flag is only useful for Objective-C code. When set to YES local\r
+# methods, which are defined in the implementation section but not in\r
+# the interface are included in the documentation.\r
+# If set to NO (the default) only methods in the interface are included.\r
+\r
+EXTRACT_LOCAL_METHODS = NO\r
+\r
+# If this flag is set to YES, the members of anonymous namespaces will be\r
+# extracted and appear in the documentation as a namespace called\r
+# 'anonymous_namespace{file}', where file will be replaced with the base\r
+# name of the file that contains the anonymous namespace. By default\r
+# anonymous namespaces are hidden.\r
+\r
+EXTRACT_ANON_NSPACES = NO\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\r
+# undocumented members of documented classes, files or namespaces.\r
+# If set to NO (the default) these members will be included in the\r
+# various overviews, but no documentation section is generated.\r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS = YES\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\r
+# undocumented classes that are normally visible in the class hierarchy.\r
+# If set to NO (the default) these classes will be included in the various\r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES = YES\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all\r
+# friend (class|struct|union) declarations.\r
+# If set to NO (the default) these declarations will be included in the\r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS = YES\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\r
+# documentation blocks found inside the body of a function.\r
+# If set to NO (the default) these blocks will be appended to the\r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS = YES\r
+\r
+# The INTERNAL_DOCS tag determines if documentation\r
+# that is typed after a \internal command is included. If the tag is set\r
+# to NO (the default) then the documentation will be excluded.\r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate\r
+# file names in lower-case letters. If set to YES upper-case letters are also\r
+# allowed. This is useful if you have classes or files whose names only differ\r
+# in case and if your file system supports case sensitive file names. Windows\r
+# and Mac users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen\r
+# will show members with their full class and namespace scopes in the\r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen\r
+# will put a list of the files that are included by a file in the documentation\r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES = NO\r
+\r
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen\r
+# will list include files with double quotes in the documentation\r
+# rather than with sharp brackets.\r
+\r
+FORCE_LOCAL_INCLUDES = NO\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]\r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen\r
+# will sort the (detailed) documentation of file and class members\r
+# alphabetically by member name. If set to NO the members will appear in\r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS = YES\r
+\r
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the\r
+# brief documentation of file, namespace and class members alphabetically\r
+# by member name. If set to NO (the default) the members will appear in\r
+# declaration order.\r
+\r
+SORT_BRIEF_DOCS = YES\r
+\r
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen\r
+# will sort the (brief and detailed) documentation of class members so that\r
+# constructors and destructors are listed first. If set to NO (the default)\r
+# the constructors will appear in the respective orders defined by\r
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.\r
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO\r
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.\r
+\r
+SORT_MEMBERS_CTORS_1ST = NO\r
+\r
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the\r
+# hierarchy of group names into alphabetical order. If set to NO (the default)\r
+# the group names will appear in their defined order.\r
+\r
+SORT_GROUP_NAMES = NO\r
+\r
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be\r
+# sorted by fully-qualified names, including namespaces. If set to\r
+# NO (the default), the class list will be sorted only by class name,\r
+# not including the namespace part.\r
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\r
+# Note: This option applies only to the class list, not to the\r
+# alphabetical list.\r
+\r
+SORT_BY_SCOPE_NAME = YES\r
+\r
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to\r
+# do proper type resolution of all parameters of a function it will reject a\r
+# match between the prototype and the implementation of a member function even\r
+# if there is only one candidate or it is obvious which candidate to choose\r
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen\r
+# will still accept a match between prototype and implementation in such cases.\r
+\r
+STRICT_PROTO_MATCHING = NO\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or\r
+# disable (NO) the todo list. This list is created by putting \todo\r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or\r
+# disable (NO) the test list. This list is created by putting \test\r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or\r
+# disable (NO) the bug list. This list is created by putting \bug\r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST = NO\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or\r
+# disable (NO) the deprecated list. This list is created by putting\r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional\r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines\r
+# the initial value of a variable or macro consists of for it to appear in\r
+# the documentation. If the initializer consists of more lines than specified\r
+# here it will be hidden. Use a value of 0 to hide initializers completely.\r
+# The appearance of the initializer of individual variables and macros in the\r
+# documentation can be controlled using \showinitializer or \hideinitializer\r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated\r
+# at the bottom of the documentation of classes and structs. If set to YES the\r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES = NO\r
+\r
+# If the sources in your project are distributed over multiple directories\r
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy\r
+# in the documentation. The default is NO.\r
+\r
+SHOW_DIRECTORIES = NO\r
+\r
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.\r
+# This will remove the Files entry from the Quick Index and from the\r
+# Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_FILES = YES\r
+\r
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the\r
+# Namespaces page.\r
+# This will remove the Namespaces entry from the Quick Index\r
+# and from the Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_NAMESPACES = YES\r
+\r
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that\r
+# doxygen should invoke to get the current version for each file (typically from\r
+# the version control system). Doxygen will invoke the program by executing (via\r
+# popen()) the command <command> <input-file>, where <command> is the value of\r
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file\r
+# provided by doxygen. Whatever the program writes to standard output\r
+# is used as the file version. See the manual for examples.\r
+\r
+FILE_VERSION_FILTER =\r
+\r
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\r
+# by doxygen. The layout file controls the global structure of the generated\r
+# output files in an output format independent way. The create the layout file\r
+# that represents doxygen's defaults, run doxygen with the -l option.\r
+# You can optionally specify a file name after the option, if omitted\r
+# DoxygenLayout.xml will be used as the name of the layout file.\r
+\r
+LAYOUT_FILE = DoxygenLayout.xml\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated\r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are\r
+# generated by doxygen. Possible values are YES and NO. If left blank\r
+# NO is used.\r
+\r
+WARNINGS = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings\r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will\r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED = YES\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for\r
+# potential errors in the documentation, such as not documenting some\r
+# parameters in a documented function, or documenting parameters that\r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR = YES\r
+\r
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for\r
+# functions that are documented, but have no documentation for their parameters\r
+# or return value. If set to NO (the default) doxygen will only warn about\r
+# wrong or incomplete parameter documentation, but not about the absence of\r
+# documentation.\r
+\r
+WARN_NO_PARAMDOC = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that\r
+# doxygen can produce. The string should contain the $file, $line, and $text\r
+# tags, which will be replaced by the file and line number from which the\r
+# warning originated and the warning text. Optionally the format may contain\r
+# $version, which will be replaced by the version of the file (if it could\r
+# be obtained via FILE_VERSION_FILTER)\r
+\r
+WARN_FORMAT = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning\r
+# and error messages should be written. If left blank the output is written\r
+# to stderr.\r
+\r
+WARN_LOGFILE = warning-public-platform.txt\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain\r
+# documented source files. You may enter file names like "myfile.cpp" or\r
+# directories like "/usr/src/myproject". Separate the files or directories\r
+# with spaces.\r
+\r
+INPUT = ../../../../../osp/FBaseSysLog.h \r
+\r
+# This tag can be used to specify the character encoding of the source files\r
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is\r
+# also the default input encoding. Doxygen uses libiconv (or the iconv built\r
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for\r
+# the list of possible encodings.\r
+\r
+INPUT_ENCODING = UTF-8\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank the following patterns are tested:\r
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh\r
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py\r
+# *.f90 *.f *.for *.vhd *.vhdl\r
+\r
+FILE_PATTERNS = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories\r
+# should be searched for input files as well. Possible values are YES and NO.\r
+# If left blank NO is used.\r
+\r
+RECURSIVE = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should\r
+# excluded from the INPUT source files. This way you can easily exclude a\r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE = \r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or\r
+# directories that are symbolic links (a Unix file system feature) are excluded\r
+# from the input.\r
+\r
+EXCLUDE_SYMLINKS = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\r
+# certain files from those directories. Note that the wildcards are matched\r
+# against the file with absolute path, so to exclude all test directories\r
+# for example use the pattern */test/*\r
+\r
+EXCLUDE_PATTERNS = \r
+\r
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\r
+# (namespaces, classes, functions, etc.) that should be excluded from the\r
+# output. The symbol name can be a fully qualified name, a word, or if the\r
+# wildcard * is used, a substring. Examples: ANamespace, AClass,\r
+# AClass::ANamespace, ANamespace::*Test\r
+\r
+EXCLUDE_SYMBOLS =\r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or\r
+# directories that contain example code fragments that are included (see\r
+# the \include command).\r
+\r
+EXAMPLE_PATH =\r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the\r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS =\r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\r
+# searched for input files to be used with the \include or \dontinclude\r
+# commands irrespective of the value of the RECURSIVE tag.\r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or\r
+# directories that contain image that are included in the documentation (see\r
+# the \image command).\r
+\r
+IMAGE_PATH = public-platform-developer/images\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should\r
+# invoke to filter for each input file. Doxygen will invoke the filter program\r
+# by executing (via popen()) the command <filter> <input-file>, where <filter>\r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an\r
+# input file. Doxygen will then use the output that the filter program writes\r
+# to standard output.\r
+# If FILTER_PATTERNS is specified, this tag will be\r
+# ignored.\r
+\r
+INPUT_FILTER =\r
+\r
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\r
+# basis.\r
+# Doxygen will compare the file name with each pattern and apply the\r
+# filter if there is a match.\r
+# The filters are a list of the form:\r
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further\r
+# info on how filters are used. If FILTER_PATTERNS is empty or if\r
+# non of the patterns match the file name, INPUT_FILTER is applied.\r
+\r
+FILTER_PATTERNS =\r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\r
+# INPUT_FILTER) will be used to filter the input files when producing source\r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES = NO\r
+\r
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\r
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)\r
+# and it is also possible to disable source filtering for a specific pattern\r
+# using *.ext= (so without naming a filter). This option only has effect when\r
+# FILTER_SOURCE_FILES is enabled.\r
+\r
+FILTER_SOURCE_PATTERNS =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will\r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+# Note: To get rid of all source code in the generated output, make sure also\r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body\r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct\r
+# doxygen to hide any special comment blocks from generated source code\r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES\r
+# then for each documented function all documented\r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = NO\r
+\r
+# If the REFERENCES_RELATION tag is set to YES\r
+# then for each documented function all documented entities\r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION = NO\r
+\r
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\r
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\r
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\r
+# link to the source code.\r
+# Otherwise they will link to the documentation.\r
+\r
+REFERENCES_LINK_SOURCE = NO\r
+\r
+# If the USE_HTAGS tag is set to YES then the references to source code\r
+# will point to the HTML generated by the htags(1) tool instead of doxygen\r
+# built-in source browser. The htags tool is part of GNU's global source\r
+# tagging system (see http://www.gnu.org/software/global/global.html). You\r
+# will need version 4.8.6 or higher.\r
+\r
+USE_HTAGS = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen\r
+# will generate a verbatim copy of the header file for each class for\r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index\r
+# of all compounds will be generated. Enable this if the project\r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then\r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns\r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX = 5\r
+\r
+# In case all classes in a project start with a common prefix, all\r
+# classes will be put under the same header in the alphabetical index.\r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that\r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will\r
+# generate HTML output.\r
+\r
+GENERATE_HTML = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT = apidocs-platform\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for\r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank\r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard header. Note that when using a custom header you are responsible\r
+# for the proper inclusion of any scripts and style sheets that doxygen\r
+# needs, which is dependent on the configuration options used.\r
+# It is adviced to generate a default header using "doxygen -w html\r
+# header.html footer.html stylesheet.css YourConfigFile" and then modify\r
+# that header. Note that the header is subject to change so you typically\r
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!\r
+\r
+HTML_HEADER =\r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard footer.\r
+\r
+HTML_FOOTER = footer.html\r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading\r
+# style sheet that is used by each HTML page. It can be used to\r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen\r
+# will generate a default style sheet. Note that doxygen will try to copy\r
+# the style sheet file to the HTML output directory, so don't put your own\r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET = Tizen.css\r
+\r
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\r
+# other source files which should be copied to the HTML output directory. Note\r
+# that these files will be copied to the base HTML output directory. Use the\r
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\r
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that\r
+# the files will be copied as-is; there are no commands or markers available.\r
+\r
+HTML_EXTRA_FILES =\r
+\r
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.\r
+# Doxygen will adjust the colors in the stylesheet and background images\r
+# according to this color. Hue is specified as an angle on a colorwheel,\r
+# see http://en.wikipedia.org/wiki/Hue for more information.\r
+# For instance the value 0 represents red, 60 is yellow, 120 is green,\r
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.\r
+# The allowed range is 0 to 359.\r
+\r
+HTML_COLORSTYLE_HUE = 220\r
+\r
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of\r
+# the colors in the HTML output. For a value of 0 the output will use\r
+# grayscales only. A value of 255 will produce the most vivid colors.\r
+\r
+HTML_COLORSTYLE_SAT = 100\r
+\r
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to\r
+# the luminance component of the colors in the HTML output. Values below\r
+# 100 gradually make the output lighter, whereas values above 100 make\r
+# the output darker. The value divided by 100 is the actual gamma applied,\r
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,\r
+# and 100 does not change the gamma.\r
+\r
+HTML_COLORSTYLE_GAMMA = 80\r
+\r
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\r
+# page will contain the date and time when the page was generated. Setting\r
+# this to NO can help when comparing the output of multiple runs.\r
+\r
+HTML_TIMESTAMP = YES\r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,\r
+# files or namespaces will be aligned in HTML using tables. If set to\r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS = YES\r
+\r
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\r
+# documentation will contain sections that can be hidden and shown after the\r
+# page has loaded. For this to work a browser that supports\r
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox\r
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).\r
+\r
+HTML_DYNAMIC_SECTIONS = NO\r
+\r
+# If the GENERATE_DOCSET tag is set to YES, additional index files\r
+# will be generated that can be used as input for Apple's Xcode 3\r
+# integrated development environment, introduced with OSX 10.5 (Leopard).\r
+# To create a documentation set, doxygen will generate a Makefile in the\r
+# HTML output directory. Running make will produce the docset in that\r
+# directory and running "make install" will install the docset in\r
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find\r
+# it at startup.\r
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html\r
+# for more information.\r
+\r
+GENERATE_DOCSET = NO\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the\r
+# feed. A documentation feed provides an umbrella under which multiple\r
+# documentation sets from a single provider (such as a company or product suite)\r
+# can be grouped.\r
+\r
+DOCSET_FEEDNAME = "Doxygen generated docs"\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that\r
+# should uniquely identify the documentation set bundle. This should be a\r
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen\r
+# will append .docset to the name.\r
+\r
+DOCSET_BUNDLE_ID = org.doxygen.Project\r
+\r
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify\r
+# the documentation publisher. This should be a reverse domain-name style\r
+# string, e.g. com.mycompany.MyDocSet.documentation.\r
+\r
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher\r
+\r
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.\r
+\r
+DOCSET_PUBLISHER_NAME = Publisher\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files\r
+# will be generated that can be used as input for tools like the\r
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)\r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can\r
+# be used to specify the file name of the resulting .chm file. You\r
+# can add a path in front of the file if the result should not be\r
+# written to the html output directory.\r
+\r
+CHM_FILE =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can\r
+# be used to specify the location (absolute path including file name) of\r
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run\r
+# the HTML help compiler on the generated index.hhp.\r
+\r
+HHC_LOCATION =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag\r
+# controls if a separate .chi index file is generated (YES) or that\r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\r
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file\r
+# content.\r
+\r
+CHM_INDEX_ENCODING =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag\r
+# controls whether a binary table of contents is generated (YES) or a\r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC = YES\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members\r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND = YES\r
+\r
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\r
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated\r
+# that can be used as input for Qt's qhelpgenerator to generate a\r
+# Qt Compressed Help (.qch) of the generated HTML documentation.\r
+\r
+GENERATE_QHP = NO\r
+\r
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can\r
+# be used to specify the file name of the resulting .qch file.\r
+# The path specified is relative to the HTML output folder.\r
+\r
+QCH_FILE =\r
+\r
+# The QHP_NAMESPACE tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#namespace\r
+\r
+QHP_NAMESPACE = org.doxygen.Project\r
+\r
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders\r
+\r
+QHP_VIRTUAL_FOLDER = doc\r
+\r
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to\r
+# add. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#custom-filters\r
+\r
+QHP_CUST_FILTER_NAME =\r
+\r
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the\r
+# custom filter to add. For more information please see\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">\r
+# Qt Help Project / Custom Filters</a>.\r
+\r
+QHP_CUST_FILTER_ATTRS =\r
+\r
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\r
+# project's\r
+# filter section matches.\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">\r
+# Qt Help Project / Filter Attributes</a>.\r
+\r
+QHP_SECT_FILTER_ATTRS =\r
+\r
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can\r
+# be used to specify the location of Qt's qhelpgenerator.\r
+# If non-empty doxygen will try to run qhelpgenerator on the generated\r
+# .qhp file.\r
+\r
+QHG_LOCATION =\r
+\r
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files\r
+# will be generated, which together with the HTML files, form an Eclipse help\r
+# plugin. To install this plugin and make it available under the help contents\r
+# menu in Eclipse, the contents of the directory containing the HTML and XML\r
+# files needs to be copied into the plugins directory of eclipse. The name of\r
+# the directory within the plugins directory should be the same as\r
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before\r
+# the help appears.\r
+\r
+GENERATE_ECLIPSEHELP = YES\r
+\r
+# A unique identifier for the eclipse help plugin. When installing the plugin\r
+# the directory name containing the HTML and XML files should also have\r
+# this name.\r
+\r
+ECLIPSE_DOC_ID = org.doxygen.Project\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at\r
+# top of each HTML page. The value NO (the default) enables the index and\r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX = NO\r
+\r
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values\r
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML\r
+# documentation. Note that a value of 0 will completely suppress the enum\r
+# values from appearing in the overview section.\r
+\r
+ENUM_VALUES_PER_LINE = 4\r
+\r
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\r
+# structure should be generated to display hierarchical information.\r
+# If the tag value is set to YES, a side panel will be generated\r
+# containing a tree-like index structure (just like the one that\r
+# is generated for HTML Help). For this to work a browser that supports\r
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).\r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW = NO\r
+\r
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,\r
+# and Class Hierarchy pages using a tree view instead of an ordered list.\r
+\r
+USE_INLINE_TREES = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be\r
+# used to set the initial width (in pixels) of the frame in which the tree\r
+# is shown.\r
+\r
+TREEVIEW_WIDTH = 250\r
+\r
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open\r
+# links to external symbols imported via tag files in a separate window.\r
+\r
+EXT_LINKS_IN_WINDOW = NO\r
+\r
+# Use this tag to change the font size of Latex formulas included\r
+# as images in the HTML documentation. The default is 10. Note that\r
+# when you change the font size after a successful doxygen run you need\r
+# to manually remove any form_*.png images from the HTML output directory\r
+# to force them to be regenerated.\r
+\r
+FORMULA_FONTSIZE = 10\r
+\r
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images\r
+# generated for formulas are transparent PNGs. Transparent PNGs are\r
+# not supported properly for IE 6.0, but are supported on all modern browsers.\r
+# Note that when changing this option you need to delete any form_*.png files\r
+# in the HTML output before the changes have effect.\r
+\r
+FORMULA_TRANSPARENT = YES\r
+\r
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax\r
+# (see http://www.mathjax.org) which uses client side Javascript for the\r
+# rendering instead of using prerendered bitmaps. Use this if you do not\r
+# have LaTeX installed or if you want to formulas look prettier in the HTML\r
+# output. When enabled you also need to install MathJax separately and\r
+# configure the path to it using the MATHJAX_RELPATH option.\r
+\r
+USE_MATHJAX = NO\r
+\r
+# When MathJax is enabled you need to specify the location relative to the\r
+# HTML output directory using the MATHJAX_RELPATH option. The destination\r
+# directory should contain the MathJax.js script. For instance, if the mathjax\r
+# directory is located at the same level as the HTML output directory, then\r
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the\r
+# mathjax.org site, so you can quickly see the result without installing\r
+# MathJax, but it is strongly recommended to install a local copy of MathJax\r
+# before deployment.\r
+\r
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax\r
+\r
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box\r
+# for the HTML output. The underlying search engine uses javascript\r
+# and DHTML and should work on any modern browser. Note that when using\r
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets\r
+# (GENERATE_DOCSET) there is already a search function so this one should\r
+# typically be disabled. For large projects the javascript based search engine\r
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.\r
+\r
+SEARCHENGINE = NO\r
+\r
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be\r
+# implemented using a PHP enabled web server instead of at the web client\r
+# using Javascript. Doxygen will generate the search PHP script and index\r
+# file to put on the web server. The advantage of the server\r
+# based approach is that it scales better to large projects and allows\r
+# full text search. The disadvantages are that it is more difficult to setup\r
+# and does not have live searching capabilities.\r
+\r
+SERVER_BASED_SEARCH = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will\r
+# generate Latex output.\r
+\r
+GENERATE_LATEX = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be\r
+# invoked. If left blank `latex' will be used as the default command name.\r
+# Note that when enabling USE_PDFLATEX this option is only used for\r
+# generating bitmaps for formulas in the HTML output, but not in the\r
+# Makefile that is written to the output directory.\r
+\r
+LATEX_CMD_NAME = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to\r
+# generate index for LaTeX. If left blank `makeindex' will be used as the\r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact\r
+# LaTeX documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_LATEX = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used\r
+# by the printer. Possible values are: a4, letter, legal and\r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX\r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES =\r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for\r
+# the generated latex document. The header should contain everything until\r
+# the first chapter. If it is left blank doxygen will generate a\r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER =\r
+\r
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for\r
+# the generated latex document. The footer should contain everything after\r
+# the last chapter. If it is left blank doxygen will generate a\r
+# standard footer. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_FOOTER =\r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated\r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will\r
+# contain links (just like the HTML output) instead of page references\r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of\r
+# plain latex in the generated Makefile. Set this option to YES to get a\r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.\r
+# command to the generated LaTeX files. This will instruct LaTeX to keep\r
+# running if errors occur, instead of asking the user for help.\r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not\r
+# include the index chapters (such as File Index, Compound Index, etc.)\r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES = NO\r
+\r
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include\r
+# source code with syntax highlighting in the LaTeX output.\r
+# Note that which sources are shown also depends on other settings\r
+# such as SOURCE_BROWSER.\r
+\r
+LATEX_SOURCE_CODE = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output\r
+# The RTF output is optimized for Word 97 and may not look very pretty with\r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact\r
+# RTF documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_RTF = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated\r
+# will contain hyperlink fields. The RTF file will\r
+# contain links (just like the HTML output) instead of page references.\r
+# This makes the output suitable for online browsing using WORD or other\r
+# programs which support those fields.\r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's\r
+# config file, i.e. a series of assignments. You only have to provide\r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE =\r
+\r
+# Set optional variables used in the generation of an rtf document.\r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will\r
+# generate man pages\r
+\r
+GENERATE_MAN = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to\r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,\r
+# then it will generate one additional man file for each entity\r
+# documented in the real man page(s). These additional files\r
+# only source the real man page, but without them the man command\r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will\r
+# generate an XML file that captures the structure of\r
+# the code including all documentation.\r
+\r
+GENERATE_XML = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT = xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA =\r
+\r
+# The XML_DTD tag can be used to specify an XML DTD,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_DTD =\r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will\r
+# dump the program listings (including syntax highlighting\r
+# and cross-referencing information) to the XML output. Note that\r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will\r
+# generate an AutoGen Definitions (see autogen.sf.net) file\r
+# that captures the structure of the code including all\r
+# documentation. Note that this feature is still experimental\r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will\r
+# generate a Perl module file that captures the structure of\r
+# the code including all documentation. Note that this\r
+# feature is still experimental and incomplete at the\r
+# moment.\r
+\r
+GENERATE_PERLMOD = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate\r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able\r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be\r
+# nicely formatted so it can be parsed by a human reader.\r
+# This is useful\r
+# if you want to understand what is going on.\r
+# On the other hand, if this\r
+# tag is set to NO the size of the Perl module output will be much smaller\r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file\r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.\r
+# This is useful so different doxyrules.make files included by the same\r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will\r
+# evaluate all C-preprocessor directives found in the sources and include\r
+# files.\r
+\r
+ENABLE_PREPROCESSING = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro\r
+# names in the source code. If set to NO (the default) only conditional\r
+# compilation will be performed. Macro expansion can be done in a controlled\r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES\r
+# then the macro expansion is limited to the macros specified with the\r
+# PREDEFINED and EXPAND_AS_DEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF = NO\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files\r
+# pointed to by INCLUDE_PATH will be searched when a #include is found.\r
+\r
+SEARCH_INCLUDES = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that\r
+# contain include files that are not input files but should be processed by\r
+# the preprocessor.\r
+\r
+INCLUDE_PATH =\r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard\r
+# patterns (like *.h and *.hpp) to filter out the header-files in the\r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will\r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS =\r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that\r
+# are defined before the preprocessor is started (similar to the -D option of\r
+# gcc). The argument of the tag is a list of macros of the form: name\r
+# or name=definition (no spaces). If the definition and the = are\r
+# omitted =1 is assumed. To prevent a macro definition from being\r
+# undefined via #undef or recursively expanded use the := operator\r
+# instead of the = operator.\r
+\r
+PREDEFINED = LIBXML_OUTPUT_ENABLED LIBXML_PUSH_ENABLED LIBXML_TREE_ENABLED LIBXML_HTML_ENABLED _OSP_EXPORT_= _OSP_LOCAL_=\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then\r
+# this tag can be used to specify a list of macro names that should be expanded.\r
+# The macro definition that is found in the sources will be used.\r
+# Use the PREDEFINED tag if you want to use a different macro definition that\r
+# overrules the definition found in the source code.\r
+\r
+EXPAND_AS_DEFINED =\r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then\r
+# doxygen's preprocessor will remove all references to function-like macros\r
+# that are alone on a line, have an all uppercase name, and do not end with a\r
+# semicolon, because these will confuse the parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::additions related to external references\r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles.\r
+# Optionally an initial location of the external documentation\r
+# can be added for each tagfile. The format of a tag file without\r
+# this location is as follows:\r
+#\r
+# TAGFILES = file1 file2 ...\r
+# Adding location for the tag files is done as follows:\r
+#\r
+# TAGFILES = file1=loc1 "file2 = loc2" ...\r
+# where "loc1" and "loc2" can be relative or absolute paths or\r
+# URLs. If a location is present for each tag, the installdox tool\r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen\r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES =\r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create\r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE =\r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed\r
+# in the class index. If set to NO only the inherited external classes\r
+# will be listed.\r
+\r
+ALLEXTERNALS = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed\r
+# in the modules index. If set to NO, only the current project's groups will\r
+# be listed.\r
+\r
+EXTERNAL_GROUPS = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script\r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool\r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will\r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base\r
+# or super classes. Setting the tag to NO turns the diagrams off. Note that\r
+# this option also works with HAVE_DOT disabled, but it is recommended to\r
+# install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS = YES\r
+\r
+# You can define message sequence charts within doxygen comments using the \msc\r
+# command. Doxygen will then run the mscgen tool (see\r
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the\r
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where\r
+# the mscgen tool resides. If left empty the tool is assumed to be found in the\r
+# default search path.\r
+\r
+MSCGEN_PATH =\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide\r
+# inheritance and usage relations if the target is undocumented\r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\r
+# available from the path. This tool is part of Graphviz, a graph visualization\r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section\r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT = NO\r
+\r
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is\r
+# allowed to run in parallel. When set to 0 (the default) doxygen will\r
+# base this on the number of processors available in the system. You can set it\r
+# explicitly to a value larger than 0 to get control over the balance\r
+# between CPU load and processing speed.\r
+\r
+DOT_NUM_THREADS = 0\r
+\r
+# By default doxygen will write a font called Helvetica to the output\r
+# directory and reference it in all dot files that doxygen generates.\r
+# When you want a differently looking font you can specify the font name\r
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,\r
+# which can be done by putting it in a standard location or by setting the\r
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory\r
+# containing the font.\r
+\r
+DOT_FONTNAME = FreeSans\r
+\r
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.\r
+# The default size is 10pt.\r
+\r
+DOT_FONTSIZE = 10\r
+\r
+# By default doxygen will tell dot to use the output directory to look for the\r
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a\r
+# different font using DOT_FONTNAME you can set the path where dot\r
+# can find it using this tag.\r
+\r
+DOT_FONTPATH =\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect inheritance relations. Setting this tag to YES will force the\r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect implementation dependencies (inheritance, containment, and\r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH = YES\r
+\r
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for groups, showing the direct groups dependencies\r
+\r
+GROUP_GRAPHS = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and\r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling\r
+# Language.\r
+\r
+UML_LOOK = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the\r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT\r
+# tags are set to YES then doxygen will generate a graph for each documented\r
+# file showing the direct and indirect include dependencies of the file with\r
+# other documented files.\r
+\r
+INCLUDE_GRAPH = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and\r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each\r
+# documented header file showing the documented files that directly or\r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then\r
+# doxygen will generate a call dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable call graphs\r
+# for selected functions only using the \callgraph command.\r
+\r
+CALL_GRAPH = NO\r
+\r
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then\r
+# doxygen will generate a caller dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable caller\r
+# graphs for selected functions only using the \callergraph command.\r
+\r
+CALLER_GRAPH = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY = YES\r
+\r
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES\r
+# then doxygen will show the dependencies a directory has on other directories\r
+# in a graphical way. The dependency relations are determined by the #include\r
+# relations between the files in the directories.\r
+\r
+DIRECTORY_GRAPH = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\r
+# generated by dot. Possible values are svg, png, jpg, or gif.\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be\r
+# found. If left blank, it is assumed the dot tool can be found in the path.\r
+\r
+DOT_PATH =\r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that\r
+# contain dot files that are included in the documentation (see the\r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS =\r
+\r
+# The MSCFILE_DIRS tag can be used to specify one or more directories that\r
+# contain msc files that are included in the documentation (see the\r
+# \mscfile command).\r
+\r
+MSCFILE_DIRS =\r
+\r
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of\r
+# nodes that will be shown in the graph. If the number of nodes in a graph\r
+# becomes larger than this value, doxygen will truncate the graph, which is\r
+# visualized by representing a node as a red box. Note that doxygen if the\r
+# number of direct children of the root node in a graph is already larger than\r
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note\r
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\r
+\r
+DOT_GRAPH_MAX_NODES = 50\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the\r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable\r
+# from the root by following a path via at most 3 edges will be shown. Nodes\r
+# that lay further from the root node will be omitted. Note that setting this\r
+# option to 1 or 2 may greatly reduce the computation time needed for large\r
+# code bases. Also note that the size of a graph can be further restricted by\r
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\r
+\r
+MAX_DOT_GRAPH_DEPTH = 0\r
+\r
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent\r
+# background. This is disabled by default, because dot on Windows does not\r
+# seem to support this out of the box. Warning: Depending on the platform used,\r
+# enabling this option may lead to badly anti-aliased labels on the edges of\r
+# a graph (i.e. they become hard to read).\r
+\r
+DOT_TRANSPARENT = NO\r
+\r
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output\r
+# files in one run (i.e. multiple -o and -T options on the command line). This\r
+# makes dot run faster, but since only newer versions of dot (>1.8.10)\r
+# support this, this feature is disabled by default.\r
+\r
+DOT_MULTI_TARGETS = NO\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will\r
+# generate a legend page explaining the meaning of the various boxes and\r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will\r
+# remove the intermediate dot files that are used to generate\r
+# the various graphs.\r
+\r
+DOT_CLEANUP = YES\r
--- /dev/null
+Manifest-Version: 1.0\rBundle-ManifestVersion: 1\rBundle-Name: Tizen Platform Native API Reference\rBundle-SymbolicName: org.tizen.platform.native.apireference ;singleton="true"\rBundle-Version: 2.2.1\rBundle-Vendor: The Linux Foundation\r\r
\ No newline at end of file
--- /dev/null
+<toc label="Doxygen generated documentation" topic="index.html">
+ <topic label="Debugging Macros" href="group__GroupMacros.html">
+ </topic>
+</toc>
--- /dev/null
+# Doxyfile 1.7.4\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project.\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored.\r
+# The format is:\r
+# TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+# TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ").\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# This tag specifies the encoding used for all characters in the config file\r
+# that follow. The default is UTF-8 which is also the encoding used for all\r
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the\r
+# iconv built into libc) for the transcoding. See\r
+# http://www.gnu.org/software/libiconv for the list of possible encodings.\r
+\r
+DOXYFILE_ENCODING = UTF-8\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded\r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME = \r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.\r
+# This could be handy for archiving the generated documentation or\r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER =\r
+\r
+# Using the PROJECT_BRIEF tag one can provide an optional one line description\r
+# for a project that appears at the top of each page and should give viewer\r
+# a quick idea about the purpose of the project. Keep the description short.\r
+\r
+PROJECT_BRIEF =\r
+\r
+# With the PROJECT_LOGO tag one can specify an logo or icon that is\r
+# included in the documentation. The maximum height of the logo should not\r
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.\r
+# Doxygen will copy the logo to the output directory.\r
+\r
+PROJECT_LOGO =\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)\r
+# base path where the generated documentation will be put.\r
+# If a relative path is entered, it will be relative to the location\r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY = \r
+\r
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create\r
+# 4096 sub-directories (in 2 levels) under the output directory of each output\r
+# format and will distribute the generated files over these directories.\r
+# Enabling this option can be useful when feeding doxygen a huge amount of\r
+# source files, where putting all generated files in the same directory would\r
+# otherwise cause performance problems for the file system.\r
+\r
+CREATE_SUBDIRS = NO\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all\r
+# documentation generated by doxygen is written. Doxygen will use this\r
+# information to generate all constant output in the proper language.\r
+# The default language is English, other supported languages are:\r
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,\r
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,\r
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English\r
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,\r
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,\r
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.\r
+\r
+OUTPUT_LANGUAGE = English\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will\r
+# include brief member descriptions after the members that are listed in\r
+# the file and class documentation (similar to JavaDoc).\r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend\r
+# the brief description of a member or function before the detailed description.\r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF = NO\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator\r
+# that is used to form the text in various listings. Each string\r
+# in this list, if found as the leading text of the brief description, will be\r
+# stripped from the text and the result after processing the whole list, is\r
+# used as the annotated text. Otherwise, the brief description is used as-is.\r
+# If left blank, the following values are used ("$name" is automatically\r
+# replaced with the name of the entity): "The $name class" "The $name widget"\r
+# "The $name file" "is" "provides" "specifies" "contains"\r
+# "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF =\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\r
+# Doxygen will generate a detailed section even if there is only a brief\r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC = YES\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\r
+# inherited members of a class in the documentation of that class as if those\r
+# members were ordinary class members. Constructors, destructors and assignment\r
+# operators of the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full\r
+# path before files name in the file list and in the header files. If set\r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag\r
+# can be used to strip a user-defined part of the path. Stripping is\r
+# only done if one of the specified strings matches the left-hand part of\r
+# the path. The tag can be used to show relative paths in the file list.\r
+# If left blank the directory from which doxygen is run is used as the\r
+# path to strip.\r
+\r
+STRIP_FROM_PATH =\r
+\r
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of\r
+# the path mentioned in the documentation of a class, which tells\r
+# the reader which header file to include in order to use a class.\r
+# If left blank only the name of the header file containing the class\r
+# definition is used. Otherwise one should specify the include paths that\r
+# are normally passed to the compiler using the -I flag.\r
+\r
+STRIP_FROM_INC_PATH =\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter\r
+# (but less readable) file names. This can be useful if your file system\r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen\r
+# will interpret the first line (until the first dot) of a JavaDoc-style\r
+# comment as the brief description. If set to NO, the JavaDoc\r
+# comments will behave just like regular Qt-style comments\r
+# (thus requiring an explicit @brief command for a brief description.)\r
+\r
+JAVADOC_AUTOBRIEF = NO\r
+\r
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will\r
+# interpret the first line (until the first dot) of a Qt-style\r
+# comment as the brief description. If set to NO, the comments\r
+# will behave just like regular Qt-style comments (thus requiring\r
+# an explicit \brief command for a brief description.)\r
+\r
+QT_AUTOBRIEF = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen\r
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///\r
+# comments) as a brief description. This used to be the default behaviour.\r
+# The new default is to treat a multi-line C++ comment block as a detailed\r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented\r
+# member inherits the documentation from any documented member that it\r
+# re-implements.\r
+\r
+INHERIT_DOCS = NO\r
+\r
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce\r
+# a new page for each member. If set to NO, the documentation of a member will\r
+# be part of the file/class/namespace that contains it.\r
+\r
+SEPARATE_MEMBER_PAGES = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.\r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts\r
+# as commands in the documentation. An alias has the form "name=value".\r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to\r
+# put the command \sideeffect (or @sideeffect) in the documentation, which\r
+# will result in a user-defined paragraph with heading "Side Effects:".\r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES = "prototype = @b Warning: This is a prototype" \\r
+ "privlevel = @xrefitem privlevel \"Privilege level\" \"Privilege Level\"" \\r
+ "privilege = @xrefitem privilege \"Privilege\" \"Privilege\"" \\r
+ "compatibility = @xrefitem compatibility \"Compatibility\" \"Compatibility \"" \\r
+ "feature = @xrefitem feature \"Required feature\" \"Required Feature \"" \\r
+ "final=\par Final:\n @xmlonly <pcheck-final>final</pcheck-final> @endxmlonly "\r
+ \r
+\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C\r
+# sources only. Doxygen will then generate output that is more tailored for C.\r
+# For instance, some of the names that are used will be different. The list\r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Java. For instance, namespaces will be presented as packages, qualified\r
+# scopes will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA = NO\r
+\r
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Fortran.\r
+\r
+OPTIMIZE_FOR_FORTRAN = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\r
+# sources. Doxygen will then generate output that is tailored for\r
+# VHDL.\r
+\r
+OPTIMIZE_OUTPUT_VHDL = NO\r
+\r
+# Doxygen selects the parser to use depending on the extension of the files it\r
+# parses. With this tag you can assign which parser to use for a given extension.\r
+# Doxygen has a built-in mapping, but you can override or extend it using this\r
+# tag. The format is ext=language, where ext is a file extension, and language\r
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,\r
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make\r
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C\r
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions\r
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.\r
+\r
+EXTENSION_MAPPING =\r
+\r
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\r
+# to include (a tag file for) the STL sources as input, then you should\r
+# set this tag to YES in order to let doxygen match functions declarations and\r
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.\r
+# func(std::string) {}). This also makes the inheritance and collaboration\r
+# diagrams that involve STL classes more complete and accurate.\r
+\r
+BUILTIN_STL_SUPPORT = NO\r
+\r
+# If you use Microsoft's C++/CLI language, you should set this option to YES to\r
+# enable parsing support.\r
+\r
+CPP_CLI_SUPPORT = NO\r
+\r
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.\r
+# Doxygen will parse them like normal C++ but will assume all classes use public\r
+# instead of private inheritance when no explicit protection keyword is present.\r
+\r
+SIP_SUPPORT = NO\r
+\r
+# For Microsoft's IDL there are propget and propput attributes to indicate getter\r
+# and setter methods for a property. Setting this option to YES (the default)\r
+# will make doxygen replace the get and set methods by a property in the\r
+# documentation. This will only work if the methods are indeed getting or\r
+# setting a simple type. If this is not the case, or you want to show the\r
+# methods anyway, you should set this option to NO.\r
+\r
+IDL_PROPERTY_SUPPORT = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\r
+# tag is set to YES, then doxygen will reuse the documentation of the first\r
+# member in the group (if any) for the other members of the group. By default\r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of\r
+# the same type (for instance a group of public functions) to be put as a\r
+# subgroup of that type (e.g. under the Public Functions section). Set it to\r
+# NO to prevent subgrouping. Alternatively, this can be done per class using\r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING = YES\r
+\r
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and\r
+# unions are shown inside the group in which they are included (e.g. using\r
+# @ingroup) instead of on a separate page (for HTML and Man pages) or\r
+# section (for LaTeX and RTF).\r
+\r
+INLINE_GROUPED_CLASSES = NO\r
+\r
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum\r
+# is documented as struct, union, or enum with the name of the typedef. So\r
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\r
+# with name TypeT. When disabled the typedef will appear as a member of a file,\r
+# namespace, or class. And the struct will be named TypeS. This can typically\r
+# be useful for C code in case the coding convention dictates that all compound\r
+# types are typedef'ed and only the typedef is referenced, never the tag name.\r
+\r
+TYPEDEF_HIDES_STRUCT = NO\r
+\r
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to\r
+# determine which symbols to keep in memory and which to flush to disk.\r
+# When the cache is full, less often used symbols will be written to disk.\r
+# For small to medium size projects (<1000 input files) the default value is\r
+# probably good enough. For larger projects a too small cache size can cause\r
+# doxygen to be busy swapping symbols to and from disk most of the time\r
+# causing a significant performance penalty.\r
+# If the system has enough physical memory increasing the cache will improve the\r
+# performance by keeping more symbols in memory. Note that the value works on\r
+# a logarithmic scale so increasing the size by one will roughly double the\r
+# memory usage. The cache size is given by this formula:\r
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,\r
+# corresponding to a cache size of 2^16 = 65536 symbols\r
+\r
+SYMBOL_CACHE_SIZE = 0\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in\r
+# documentation are documented, even if no documentation was available.\r
+# Private class members and static file members will be hidden unless\r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class\r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file\r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC = YES\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)\r
+# defined locally in source files will be included in the documentation.\r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES = NO\r
+\r
+# This flag is only useful for Objective-C code. When set to YES local\r
+# methods, which are defined in the implementation section but not in\r
+# the interface are included in the documentation.\r
+# If set to NO (the default) only methods in the interface are included.\r
+\r
+EXTRACT_LOCAL_METHODS = NO\r
+\r
+# If this flag is set to YES, the members of anonymous namespaces will be\r
+# extracted and appear in the documentation as a namespace called\r
+# 'anonymous_namespace{file}', where file will be replaced with the base\r
+# name of the file that contains the anonymous namespace. By default\r
+# anonymous namespaces are hidden.\r
+\r
+EXTRACT_ANON_NSPACES = NO\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\r
+# undocumented members of documented classes, files or namespaces.\r
+# If set to NO (the default) these members will be included in the\r
+# various overviews, but no documentation section is generated.\r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS = YES\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\r
+# undocumented classes that are normally visible in the class hierarchy.\r
+# If set to NO (the default) these classes will be included in the various\r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES = YES\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all\r
+# friend (class|struct|union) declarations.\r
+# If set to NO (the default) these declarations will be included in the\r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS = YES\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\r
+# documentation blocks found inside the body of a function.\r
+# If set to NO (the default) these blocks will be appended to the\r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS = YES\r
+\r
+# The INTERNAL_DOCS tag determines if documentation\r
+# that is typed after a \internal command is included. If the tag is set\r
+# to NO (the default) then the documentation will be excluded.\r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate\r
+# file names in lower-case letters. If set to YES upper-case letters are also\r
+# allowed. This is useful if you have classes or files whose names only differ\r
+# in case and if your file system supports case sensitive file names. Windows\r
+# and Mac users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen\r
+# will show members with their full class and namespace scopes in the\r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen\r
+# will put a list of the files that are included by a file in the documentation\r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES = NO\r
+\r
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen\r
+# will list include files with double quotes in the documentation\r
+# rather than with sharp brackets.\r
+\r
+FORCE_LOCAL_INCLUDES = NO\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]\r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen\r
+# will sort the (detailed) documentation of file and class members\r
+# alphabetically by member name. If set to NO the members will appear in\r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS = YES\r
+\r
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the\r
+# brief documentation of file, namespace and class members alphabetically\r
+# by member name. If set to NO (the default) the members will appear in\r
+# declaration order.\r
+\r
+SORT_BRIEF_DOCS = YES\r
+\r
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen\r
+# will sort the (brief and detailed) documentation of class members so that\r
+# constructors and destructors are listed first. If set to NO (the default)\r
+# the constructors will appear in the respective orders defined by\r
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.\r
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO\r
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.\r
+\r
+SORT_MEMBERS_CTORS_1ST = NO\r
+\r
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the\r
+# hierarchy of group names into alphabetical order. If set to NO (the default)\r
+# the group names will appear in their defined order.\r
+\r
+SORT_GROUP_NAMES = NO\r
+\r
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be\r
+# sorted by fully-qualified names, including namespaces. If set to\r
+# NO (the default), the class list will be sorted only by class name,\r
+# not including the namespace part.\r
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\r
+# Note: This option applies only to the class list, not to the\r
+# alphabetical list.\r
+\r
+SORT_BY_SCOPE_NAME = YES\r
+\r
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to\r
+# do proper type resolution of all parameters of a function it will reject a\r
+# match between the prototype and the implementation of a member function even\r
+# if there is only one candidate or it is obvious which candidate to choose\r
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen\r
+# will still accept a match between prototype and implementation in such cases.\r
+\r
+STRICT_PROTO_MATCHING = NO\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or\r
+# disable (NO) the todo list. This list is created by putting \todo\r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or\r
+# disable (NO) the test list. This list is created by putting \test\r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or\r
+# disable (NO) the bug list. This list is created by putting \bug\r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST = NO\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or\r
+# disable (NO) the deprecated list. This list is created by putting\r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional\r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines\r
+# the initial value of a variable or macro consists of for it to appear in\r
+# the documentation. If the initializer consists of more lines than specified\r
+# here it will be hidden. Use a value of 0 to hide initializers completely.\r
+# The appearance of the initializer of individual variables and macros in the\r
+# documentation can be controlled using \showinitializer or \hideinitializer\r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated\r
+# at the bottom of the documentation of classes and structs. If set to YES the\r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES = NO\r
+\r
+# If the sources in your project are distributed over multiple directories\r
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy\r
+# in the documentation. The default is NO.\r
+\r
+SHOW_DIRECTORIES = NO\r
+\r
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.\r
+# This will remove the Files entry from the Quick Index and from the\r
+# Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_FILES = YES\r
+\r
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the\r
+# Namespaces page.\r
+# This will remove the Namespaces entry from the Quick Index\r
+# and from the Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_NAMESPACES = YES\r
+\r
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that\r
+# doxygen should invoke to get the current version for each file (typically from\r
+# the version control system). Doxygen will invoke the program by executing (via\r
+# popen()) the command <command> <input-file>, where <command> is the value of\r
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file\r
+# provided by doxygen. Whatever the program writes to standard output\r
+# is used as the file version. See the manual for examples.\r
+\r
+FILE_VERSION_FILTER =\r
+\r
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\r
+# by doxygen. The layout file controls the global structure of the generated\r
+# output files in an output format independent way. The create the layout file\r
+# that represents doxygen's defaults, run doxygen with the -l option.\r
+# You can optionally specify a file name after the option, if omitted\r
+# DoxygenLayout.xml will be used as the name of the layout file.\r
+\r
+LAYOUT_FILE = DoxygenLayout.xml\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated\r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are\r
+# generated by doxygen. Possible values are YES and NO. If left blank\r
+# NO is used.\r
+\r
+WARNINGS = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings\r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will\r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED = YES\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for\r
+# potential errors in the documentation, such as not documenting some\r
+# parameters in a documented function, or documenting parameters that\r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR = YES\r
+\r
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for\r
+# functions that are documented, but have no documentation for their parameters\r
+# or return value. If set to NO (the default) doxygen will only warn about\r
+# wrong or incomplete parameter documentation, but not about the absence of\r
+# documentation.\r
+\r
+WARN_NO_PARAMDOC = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that\r
+# doxygen can produce. The string should contain the $file, $line, and $text\r
+# tags, which will be replaced by the file and line number from which the\r
+# warning originated and the warning text. Optionally the format may contain\r
+# $version, which will be replaced by the version of the file (if it could\r
+# be obtained via FILE_VERSION_FILTER)\r
+\r
+WARN_FORMAT = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning\r
+# and error messages should be written. If left blank the output is written\r
+# to stderr.\r
+\r
+WARN_LOGFILE = warning.txt\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain\r
+# documented source files. You may enter file names like "myfile.cpp" or\r
+# directories like "/usr/src/myproject". Separate the files or directories\r
+# with spaces.\r
+\r
+INPUT = ../../../../framework/osp/osp-appfw/inc \\r
+ ../../../../framework/osp/osp-bluetooth/inc \\r
+ ../../../../framework/osp/osp-content/inc \\r
+ ../../../../framework/osp/osp-face/inc \\r
+ ../../../../framework/osp/osp-image/inc \\r
+ ../../../../framework/osp/osp-image-core/inc \\r
+ ../../../../framework/osp/osp-ime/inc \\r
+ ../../../../framework/osp/osp-json/inc \\r
+ ../../../../framework/osp/osp-locations/inc \\r
+ ../../../../framework/osp/osp-media/inc \\r
+ ../../../../framework/osp/osp-messaging/inc \\r
+ ../../../../framework/osp/osp-net/inc \\r
+ ../../../../framework/osp/osp-nfc/inc \\r
+ ../../../../framework/osp/osp-shell/inc \\r
+ ../../../../framework/osp/osp-social/inc \\r
+ ../../../../framework/osp/osp-speech/inc \\r
+ ../../../../framework/osp/osp-telephony/inc \\r
+ ../../../../framework/osp/osp-uifw/inc \\r
+ ../../../../framework/osp/osp-uix/inc \\r
+ ../../../../framework/osp/osp-vision/inc \\r
+ ../../../../framework/osp/osp-web/inc \\r
+ ./libraries \r
+ \r
+\r
+# This tag can be used to specify the character encoding of the source files\r
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is\r
+# also the default input encoding. Doxygen uses libiconv (or the iconv built\r
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for\r
+# the list of possible encodings.\r
+\r
+INPUT_ENCODING = UTF-8\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank the following patterns are tested:\r
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh\r
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py\r
+# *.f90 *.f *.for *.vhd *.vhdl\r
+\r
+FILE_PATTERNS = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories\r
+# should be searched for input files as well. Possible values are YES and NO.\r
+# If left blank NO is used.\r
+\r
+RECURSIVE = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should\r
+# excluded from the INPUT source files. This way you can easily exclude a\r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE = ../../../../framework/osp/osp-appfw/inc/FBaseSysLog.h\r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or\r
+# directories that are symbolic links (a Unix file system feature) are excluded\r
+# from the input.\r
+\r
+EXCLUDE_SYMLINKS = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\r
+# certain files from those directories. Note that the wildcards are matched\r
+# against the file with absolute path, so to exclude all test directories\r
+# for example use the pattern */test/*\r
+\r
+EXCLUDE_PATTERNS = \r
+\r
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\r
+# (namespaces, classes, functions, etc.) that should be excluded from the\r
+# output. The symbol name can be a fully qualified name, a word, or if the\r
+# wildcard * is used, a substring. Examples: ANamespace, AClass,\r
+# AClass::ANamespace, ANamespace::*Test\r
+\r
+EXCLUDE_SYMBOLS =\r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or\r
+# directories that contain example code fragments that are included (see\r
+# the \include command).\r
+\r
+EXAMPLE_PATH =\r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the\r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS =\r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\r
+# searched for input files to be used with the \include or \dontinclude\r
+# commands irrespective of the value of the RECURSIVE tag.\r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or\r
+# directories that contain image that are included in the documentation (see\r
+# the \image command).\r
+\r
+IMAGE_PATH = public/images\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should\r
+# invoke to filter for each input file. Doxygen will invoke the filter program\r
+# by executing (via popen()) the command <filter> <input-file>, where <filter>\r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an\r
+# input file. Doxygen will then use the output that the filter program writes\r
+# to standard output.\r
+# If FILTER_PATTERNS is specified, this tag will be\r
+# ignored.\r
+\r
+INPUT_FILTER =\r
+\r
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\r
+# basis.\r
+# Doxygen will compare the file name with each pattern and apply the\r
+# filter if there is a match.\r
+# The filters are a list of the form:\r
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further\r
+# info on how filters are used. If FILTER_PATTERNS is empty or if\r
+# non of the patterns match the file name, INPUT_FILTER is applied.\r
+\r
+FILTER_PATTERNS =\r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\r
+# INPUT_FILTER) will be used to filter the input files when producing source\r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES = NO\r
+\r
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\r
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)\r
+# and it is also possible to disable source filtering for a specific pattern\r
+# using *.ext= (so without naming a filter). This option only has effect when\r
+# FILTER_SOURCE_FILES is enabled.\r
+\r
+FILTER_SOURCE_PATTERNS =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will\r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+# Note: To get rid of all source code in the generated output, make sure also\r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body\r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct\r
+# doxygen to hide any special comment blocks from generated source code\r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES\r
+# then for each documented function all documented\r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = NO\r
+\r
+# If the REFERENCES_RELATION tag is set to YES\r
+# then for each documented function all documented entities\r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION = NO\r
+\r
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\r
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\r
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\r
+# link to the source code.\r
+# Otherwise they will link to the documentation.\r
+\r
+REFERENCES_LINK_SOURCE = NO\r
+\r
+# If the USE_HTAGS tag is set to YES then the references to source code\r
+# will point to the HTML generated by the htags(1) tool instead of doxygen\r
+# built-in source browser. The htags tool is part of GNU's global source\r
+# tagging system (see http://www.gnu.org/software/global/global.html). You\r
+# will need version 4.8.6 or higher.\r
+\r
+USE_HTAGS = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen\r
+# will generate a verbatim copy of the header file for each class for\r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index\r
+# of all compounds will be generated. Enable this if the project\r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then\r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns\r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX = 5\r
+\r
+# In case all classes in a project start with a common prefix, all\r
+# classes will be put under the same header in the alphabetical index.\r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that\r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will\r
+# generate HTML output.\r
+\r
+GENERATE_HTML = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT = apidocs\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for\r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank\r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard header. Note that when using a custom header you are responsible\r
+# for the proper inclusion of any scripts and style sheets that doxygen\r
+# needs, which is dependent on the configuration options used.\r
+# It is adviced to generate a default header using "doxygen -w html\r
+# header.html footer.html stylesheet.css YourConfigFile" and then modify\r
+# that header. Note that the header is subject to change so you typically\r
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!\r
+\r
+HTML_HEADER =\r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard footer.\r
+\r
+HTML_FOOTER = footer.html\r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading\r
+# style sheet that is used by each HTML page. It can be used to\r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen\r
+# will generate a default style sheet. Note that doxygen will try to copy\r
+# the style sheet file to the HTML output directory, so don't put your own\r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET = Tizen.css\r
+\r
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\r
+# other source files which should be copied to the HTML output directory. Note\r
+# that these files will be copied to the base HTML output directory. Use the\r
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\r
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that\r
+# the files will be copied as-is; there are no commands or markers available.\r
+\r
+HTML_EXTRA_FILES =\r
+\r
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.\r
+# Doxygen will adjust the colors in the stylesheet and background images\r
+# according to this color. Hue is specified as an angle on a colorwheel,\r
+# see http://en.wikipedia.org/wiki/Hue for more information.\r
+# For instance the value 0 represents red, 60 is yellow, 120 is green,\r
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.\r
+# The allowed range is 0 to 359.\r
+\r
+HTML_COLORSTYLE_HUE = 220\r
+\r
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of\r
+# the colors in the HTML output. For a value of 0 the output will use\r
+# grayscales only. A value of 255 will produce the most vivid colors.\r
+\r
+HTML_COLORSTYLE_SAT = 100\r
+\r
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to\r
+# the luminance component of the colors in the HTML output. Values below\r
+# 100 gradually make the output lighter, whereas values above 100 make\r
+# the output darker. The value divided by 100 is the actual gamma applied,\r
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,\r
+# and 100 does not change the gamma.\r
+\r
+HTML_COLORSTYLE_GAMMA = 80\r
+\r
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\r
+# page will contain the date and time when the page was generated. Setting\r
+# this to NO can help when comparing the output of multiple runs.\r
+\r
+HTML_TIMESTAMP = YES\r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,\r
+# files or namespaces will be aligned in HTML using tables. If set to\r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS = YES\r
+\r
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\r
+# documentation will contain sections that can be hidden and shown after the\r
+# page has loaded. For this to work a browser that supports\r
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox\r
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).\r
+\r
+HTML_DYNAMIC_SECTIONS = NO\r
+\r
+# If the GENERATE_DOCSET tag is set to YES, additional index files\r
+# will be generated that can be used as input for Apple's Xcode 3\r
+# integrated development environment, introduced with OSX 10.5 (Leopard).\r
+# To create a documentation set, doxygen will generate a Makefile in the\r
+# HTML output directory. Running make will produce the docset in that\r
+# directory and running "make install" will install the docset in\r
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find\r
+# it at startup.\r
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html\r
+# for more information.\r
+\r
+GENERATE_DOCSET = NO\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the\r
+# feed. A documentation feed provides an umbrella under which multiple\r
+# documentation sets from a single provider (such as a company or product suite)\r
+# can be grouped.\r
+\r
+DOCSET_FEEDNAME = "Doxygen generated docs"\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that\r
+# should uniquely identify the documentation set bundle. This should be a\r
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen\r
+# will append .docset to the name.\r
+\r
+DOCSET_BUNDLE_ID = org.doxygen.Project\r
+\r
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify\r
+# the documentation publisher. This should be a reverse domain-name style\r
+# string, e.g. com.mycompany.MyDocSet.documentation.\r
+\r
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher\r
+\r
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.\r
+\r
+DOCSET_PUBLISHER_NAME = Publisher\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files\r
+# will be generated that can be used as input for tools like the\r
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)\r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can\r
+# be used to specify the file name of the resulting .chm file. You\r
+# can add a path in front of the file if the result should not be\r
+# written to the html output directory.\r
+\r
+CHM_FILE =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can\r
+# be used to specify the location (absolute path including file name) of\r
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run\r
+# the HTML help compiler on the generated index.hhp.\r
+\r
+HHC_LOCATION =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag\r
+# controls if a separate .chi index file is generated (YES) or that\r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\r
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file\r
+# content.\r
+\r
+CHM_INDEX_ENCODING =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag\r
+# controls whether a binary table of contents is generated (YES) or a\r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC = YES\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members\r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND = YES\r
+\r
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\r
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated\r
+# that can be used as input for Qt's qhelpgenerator to generate a\r
+# Qt Compressed Help (.qch) of the generated HTML documentation.\r
+\r
+GENERATE_QHP = NO\r
+\r
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can\r
+# be used to specify the file name of the resulting .qch file.\r
+# The path specified is relative to the HTML output folder.\r
+\r
+QCH_FILE =\r
+\r
+# The QHP_NAMESPACE tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#namespace\r
+\r
+QHP_NAMESPACE = org.doxygen.Project\r
+\r
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders\r
+\r
+QHP_VIRTUAL_FOLDER = doc\r
+\r
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to\r
+# add. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#custom-filters\r
+\r
+QHP_CUST_FILTER_NAME =\r
+\r
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the\r
+# custom filter to add. For more information please see\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">\r
+# Qt Help Project / Custom Filters</a>.\r
+\r
+QHP_CUST_FILTER_ATTRS =\r
+\r
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\r
+# project's\r
+# filter section matches.\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">\r
+# Qt Help Project / Filter Attributes</a>.\r
+\r
+QHP_SECT_FILTER_ATTRS =\r
+\r
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can\r
+# be used to specify the location of Qt's qhelpgenerator.\r
+# If non-empty doxygen will try to run qhelpgenerator on the generated\r
+# .qhp file.\r
+\r
+QHG_LOCATION =\r
+\r
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files\r
+# will be generated, which together with the HTML files, form an Eclipse help\r
+# plugin. To install this plugin and make it available under the help contents\r
+# menu in Eclipse, the contents of the directory containing the HTML and XML\r
+# files needs to be copied into the plugins directory of eclipse. The name of\r
+# the directory within the plugins directory should be the same as\r
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before\r
+# the help appears.\r
+\r
+GENERATE_ECLIPSEHELP = YES\r
+\r
+# A unique identifier for the eclipse help plugin. When installing the plugin\r
+# the directory name containing the HTML and XML files should also have\r
+# this name.\r
+\r
+ECLIPSE_DOC_ID = org.doxygen.Project\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at\r
+# top of each HTML page. The value NO (the default) enables the index and\r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX = NO\r
+\r
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values\r
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML\r
+# documentation. Note that a value of 0 will completely suppress the enum\r
+# values from appearing in the overview section.\r
+\r
+ENUM_VALUES_PER_LINE = 4\r
+\r
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\r
+# structure should be generated to display hierarchical information.\r
+# If the tag value is set to YES, a side panel will be generated\r
+# containing a tree-like index structure (just like the one that\r
+# is generated for HTML Help). For this to work a browser that supports\r
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).\r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW = NO\r
+\r
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,\r
+# and Class Hierarchy pages using a tree view instead of an ordered list.\r
+\r
+USE_INLINE_TREES = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be\r
+# used to set the initial width (in pixels) of the frame in which the tree\r
+# is shown.\r
+\r
+TREEVIEW_WIDTH = 250\r
+\r
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open\r
+# links to external symbols imported via tag files in a separate window.\r
+\r
+EXT_LINKS_IN_WINDOW = NO\r
+\r
+# Use this tag to change the font size of Latex formulas included\r
+# as images in the HTML documentation. The default is 10. Note that\r
+# when you change the font size after a successful doxygen run you need\r
+# to manually remove any form_*.png images from the HTML output directory\r
+# to force them to be regenerated.\r
+\r
+FORMULA_FONTSIZE = 10\r
+\r
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images\r
+# generated for formulas are transparent PNGs. Transparent PNGs are\r
+# not supported properly for IE 6.0, but are supported on all modern browsers.\r
+# Note that when changing this option you need to delete any form_*.png files\r
+# in the HTML output before the changes have effect.\r
+\r
+FORMULA_TRANSPARENT = YES\r
+\r
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax\r
+# (see http://www.mathjax.org) which uses client side Javascript for the\r
+# rendering instead of using prerendered bitmaps. Use this if you do not\r
+# have LaTeX installed or if you want to formulas look prettier in the HTML\r
+# output. When enabled you also need to install MathJax separately and\r
+# configure the path to it using the MATHJAX_RELPATH option.\r
+\r
+USE_MATHJAX = NO\r
+\r
+# When MathJax is enabled you need to specify the location relative to the\r
+# HTML output directory using the MATHJAX_RELPATH option. The destination\r
+# directory should contain the MathJax.js script. For instance, if the mathjax\r
+# directory is located at the same level as the HTML output directory, then\r
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the\r
+# mathjax.org site, so you can quickly see the result without installing\r
+# MathJax, but it is strongly recommended to install a local copy of MathJax\r
+# before deployment.\r
+\r
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax\r
+\r
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box\r
+# for the HTML output. The underlying search engine uses javascript\r
+# and DHTML and should work on any modern browser. Note that when using\r
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets\r
+# (GENERATE_DOCSET) there is already a search function so this one should\r
+# typically be disabled. For large projects the javascript based search engine\r
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.\r
+\r
+SEARCHENGINE = NO\r
+\r
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be\r
+# implemented using a PHP enabled web server instead of at the web client\r
+# using Javascript. Doxygen will generate the search PHP script and index\r
+# file to put on the web server. The advantage of the server\r
+# based approach is that it scales better to large projects and allows\r
+# full text search. The disadvantages are that it is more difficult to setup\r
+# and does not have live searching capabilities.\r
+\r
+SERVER_BASED_SEARCH = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will\r
+# generate Latex output.\r
+\r
+GENERATE_LATEX = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be\r
+# invoked. If left blank `latex' will be used as the default command name.\r
+# Note that when enabling USE_PDFLATEX this option is only used for\r
+# generating bitmaps for formulas in the HTML output, but not in the\r
+# Makefile that is written to the output directory.\r
+\r
+LATEX_CMD_NAME = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to\r
+# generate index for LaTeX. If left blank `makeindex' will be used as the\r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact\r
+# LaTeX documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_LATEX = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used\r
+# by the printer. Possible values are: a4, letter, legal and\r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX\r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES =\r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for\r
+# the generated latex document. The header should contain everything until\r
+# the first chapter. If it is left blank doxygen will generate a\r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER =\r
+\r
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for\r
+# the generated latex document. The footer should contain everything after\r
+# the last chapter. If it is left blank doxygen will generate a\r
+# standard footer. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_FOOTER =\r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated\r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will\r
+# contain links (just like the HTML output) instead of page references\r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of\r
+# plain latex in the generated Makefile. Set this option to YES to get a\r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.\r
+# command to the generated LaTeX files. This will instruct LaTeX to keep\r
+# running if errors occur, instead of asking the user for help.\r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not\r
+# include the index chapters (such as File Index, Compound Index, etc.)\r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES = NO\r
+\r
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include\r
+# source code with syntax highlighting in the LaTeX output.\r
+# Note that which sources are shown also depends on other settings\r
+# such as SOURCE_BROWSER.\r
+\r
+LATEX_SOURCE_CODE = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output\r
+# The RTF output is optimized for Word 97 and may not look very pretty with\r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact\r
+# RTF documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_RTF = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated\r
+# will contain hyperlink fields. The RTF file will\r
+# contain links (just like the HTML output) instead of page references.\r
+# This makes the output suitable for online browsing using WORD or other\r
+# programs which support those fields.\r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's\r
+# config file, i.e. a series of assignments. You only have to provide\r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE =\r
+\r
+# Set optional variables used in the generation of an rtf document.\r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will\r
+# generate man pages\r
+\r
+GENERATE_MAN = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to\r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,\r
+# then it will generate one additional man file for each entity\r
+# documented in the real man page(s). These additional files\r
+# only source the real man page, but without them the man command\r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will\r
+# generate an XML file that captures the structure of\r
+# the code including all documentation.\r
+\r
+GENERATE_XML = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT = _xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA =\r
+\r
+# The XML_DTD tag can be used to specify an XML DTD,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_DTD =\r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will\r
+# dump the program listings (including syntax highlighting\r
+# and cross-referencing information) to the XML output. Note that\r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will\r
+# generate an AutoGen Definitions (see autogen.sf.net) file\r
+# that captures the structure of the code including all\r
+# documentation. Note that this feature is still experimental\r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will\r
+# generate a Perl module file that captures the structure of\r
+# the code including all documentation. Note that this\r
+# feature is still experimental and incomplete at the\r
+# moment.\r
+\r
+GENERATE_PERLMOD = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate\r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able\r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be\r
+# nicely formatted so it can be parsed by a human reader.\r
+# This is useful\r
+# if you want to understand what is going on.\r
+# On the other hand, if this\r
+# tag is set to NO the size of the Perl module output will be much smaller\r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file\r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.\r
+# This is useful so different doxyrules.make files included by the same\r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will\r
+# evaluate all C-preprocessor directives found in the sources and include\r
+# files.\r
+\r
+ENABLE_PREPROCESSING = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro\r
+# names in the source code. If set to NO (the default) only conditional\r
+# compilation will be performed. Macro expansion can be done in a controlled\r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES\r
+# then the macro expansion is limited to the macros specified with the\r
+# PREDEFINED and EXPAND_AS_DEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF = YES\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files\r
+# pointed to by INCLUDE_PATH will be searched when a #include is found.\r
+\r
+SEARCH_INCLUDES = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that\r
+# contain include files that are not input files but should be processed by\r
+# the preprocessor.\r
+\r
+INCLUDE_PATH =\r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard\r
+# patterns (like *.h and *.hpp) to filter out the header-files in the\r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will\r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS =\r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that\r
+# are defined before the preprocessor is started (similar to the -D option of\r
+# gcc). The argument of the tag is a list of macros of the form: name\r
+# or name=definition (no spaces). If the definition and the = are\r
+# omitted =1 is assumed. To prevent a macro definition from being\r
+# undefined via #undef or recursively expanded use the := operator\r
+# instead of the = operator.\r
+\r
+PREDEFINED = LIBXML_OUTPUT_ENABLED LIBXML_PUSH_ENABLED LIBXML_TREE_ENABLED LIBXML_HTML_ENABLED _OSP_EXPORT_= _OSP_LOCAL_=\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then\r
+# this tag can be used to specify a list of macro names that should be expanded.\r
+# The macro definition that is found in the sources will be used.\r
+# Use the PREDEFINED tag if you want to use a different macro definition that\r
+# overrules the definition found in the source code.\r
+\r
+EXPAND_AS_DEFINED =\r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then\r
+# doxygen's preprocessor will remove all references to function-like macros\r
+# that are alone on a line, have an all uppercase name, and do not end with a\r
+# semicolon, because these will confuse the parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::additions related to external references\r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles.\r
+# Optionally an initial location of the external documentation\r
+# can be added for each tagfile. The format of a tag file without\r
+# this location is as follows:\r
+#\r
+# TAGFILES = file1 file2 ...\r
+# Adding location for the tag files is done as follows:\r
+#\r
+# TAGFILES = file1=loc1 "file2 = loc2" ...\r
+# where "loc1" and "loc2" can be relative or absolute paths or\r
+# URLs. If a location is present for each tag, the installdox tool\r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen\r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES =\r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create\r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE =\r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed\r
+# in the class index. If set to NO only the inherited external classes\r
+# will be listed.\r
+\r
+ALLEXTERNALS = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed\r
+# in the modules index. If set to NO, only the current project's groups will\r
+# be listed.\r
+\r
+EXTERNAL_GROUPS = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script\r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool\r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will\r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base\r
+# or super classes. Setting the tag to NO turns the diagrams off. Note that\r
+# this option also works with HAVE_DOT disabled, but it is recommended to\r
+# install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS = YES\r
+\r
+# You can define message sequence charts within doxygen comments using the \msc\r
+# command. Doxygen will then run the mscgen tool (see\r
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the\r
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where\r
+# the mscgen tool resides. If left empty the tool is assumed to be found in the\r
+# default search path.\r
+\r
+MSCGEN_PATH =\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide\r
+# inheritance and usage relations if the target is undocumented\r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\r
+# available from the path. This tool is part of Graphviz, a graph visualization\r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section\r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT = NO\r
+\r
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is\r
+# allowed to run in parallel. When set to 0 (the default) doxygen will\r
+# base this on the number of processors available in the system. You can set it\r
+# explicitly to a value larger than 0 to get control over the balance\r
+# between CPU load and processing speed.\r
+\r
+DOT_NUM_THREADS = 0\r
+\r
+# By default doxygen will write a font called Helvetica to the output\r
+# directory and reference it in all dot files that doxygen generates.\r
+# When you want a differently looking font you can specify the font name\r
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,\r
+# which can be done by putting it in a standard location or by setting the\r
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory\r
+# containing the font.\r
+\r
+DOT_FONTNAME = FreeSans\r
+\r
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.\r
+# The default size is 10pt.\r
+\r
+DOT_FONTSIZE = 10\r
+\r
+# By default doxygen will tell dot to use the output directory to look for the\r
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a\r
+# different font using DOT_FONTNAME you can set the path where dot\r
+# can find it using this tag.\r
+\r
+DOT_FONTPATH =\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect inheritance relations. Setting this tag to YES will force the\r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect implementation dependencies (inheritance, containment, and\r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH = YES\r
+\r
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for groups, showing the direct groups dependencies\r
+\r
+GROUP_GRAPHS = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and\r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling\r
+# Language.\r
+\r
+UML_LOOK = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the\r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT\r
+# tags are set to YES then doxygen will generate a graph for each documented\r
+# file showing the direct and indirect include dependencies of the file with\r
+# other documented files.\r
+\r
+INCLUDE_GRAPH = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and\r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each\r
+# documented header file showing the documented files that directly or\r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then\r
+# doxygen will generate a call dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable call graphs\r
+# for selected functions only using the \callgraph command.\r
+\r
+CALL_GRAPH = NO\r
+\r
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then\r
+# doxygen will generate a caller dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable caller\r
+# graphs for selected functions only using the \callergraph command.\r
+\r
+CALLER_GRAPH = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY = YES\r
+\r
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES\r
+# then doxygen will show the dependencies a directory has on other directories\r
+# in a graphical way. The dependency relations are determined by the #include\r
+# relations between the files in the directories.\r
+\r
+DIRECTORY_GRAPH = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\r
+# generated by dot. Possible values are svg, png, jpg, or gif.\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be\r
+# found. If left blank, it is assumed the dot tool can be found in the path.\r
+\r
+DOT_PATH =\r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that\r
+# contain dot files that are included in the documentation (see the\r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS =\r
+\r
+# The MSCFILE_DIRS tag can be used to specify one or more directories that\r
+# contain msc files that are included in the documentation (see the\r
+# \mscfile command).\r
+\r
+MSCFILE_DIRS =\r
+\r
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of\r
+# nodes that will be shown in the graph. If the number of nodes in a graph\r
+# becomes larger than this value, doxygen will truncate the graph, which is\r
+# visualized by representing a node as a red box. Note that doxygen if the\r
+# number of direct children of the root node in a graph is already larger than\r
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note\r
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\r
+\r
+DOT_GRAPH_MAX_NODES = 50\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the\r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable\r
+# from the root by following a path via at most 3 edges will be shown. Nodes\r
+# that lay further from the root node will be omitted. Note that setting this\r
+# option to 1 or 2 may greatly reduce the computation time needed for large\r
+# code bases. Also note that the size of a graph can be further restricted by\r
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\r
+\r
+MAX_DOT_GRAPH_DEPTH = 0\r
+\r
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent\r
+# background. This is disabled by default, because dot on Windows does not\r
+# seem to support this out of the box. Warning: Depending on the platform used,\r
+# enabling this option may lead to badly anti-aliased labels on the edges of\r
+# a graph (i.e. they become hard to read).\r
+\r
+DOT_TRANSPARENT = NO\r
+\r
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output\r
+# files in one run (i.e. multiple -o and -T options on the command line). This\r
+# makes dot run faster, but since only newer versions of dot (>1.8.10)\r
+# support this, this feature is disabled by default.\r
+\r
+DOT_MULTI_TARGETS = NO\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will\r
+# generate a legend page explaining the meaning of the various boxes and\r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will\r
+# remove the intermediate dot files that are used to generate\r
+# the various graphs.\r
+\r
+DOT_CLEANUP = YES\r
--- /dev/null
+# Doxyfile 1.7.4\r
+\r
+# This file describes the settings to be used by the documentation system\r
+# doxygen (www.doxygen.org) for a project.\r
+#\r
+# All text after a hash (#) is considered a comment and will be ignored.\r
+# The format is:\r
+# TAG = value [value, ...]\r
+# For lists items can also be appended using:\r
+# TAG += value [value, ...]\r
+# Values that contain spaces should be placed between quotes (" ").\r
+\r
+#---------------------------------------------------------------------------\r
+# Project related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# This tag specifies the encoding used for all characters in the config file\r
+# that follow. The default is UTF-8 which is also the encoding used for all\r
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the\r
+# iconv built into libc) for the transcoding. See\r
+# http://www.gnu.org/software/libiconv for the list of possible encodings.\r
+\r
+DOXYFILE_ENCODING = UTF-8\r
+\r
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded\r
+# by quotes) that should identify the project.\r
+\r
+PROJECT_NAME = \r
+\r
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.\r
+# This could be handy for archiving the generated documentation or\r
+# if some version control system is used.\r
+\r
+PROJECT_NUMBER =\r
+\r
+# Using the PROJECT_BRIEF tag one can provide an optional one line description\r
+# for a project that appears at the top of each page and should give viewer\r
+# a quick idea about the purpose of the project. Keep the description short.\r
+\r
+PROJECT_BRIEF =\r
+\r
+# With the PROJECT_LOGO tag one can specify an logo or icon that is\r
+# included in the documentation. The maximum height of the logo should not\r
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.\r
+# Doxygen will copy the logo to the output directory.\r
+\r
+PROJECT_LOGO =\r
+\r
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)\r
+# base path where the generated documentation will be put.\r
+# If a relative path is entered, it will be relative to the location\r
+# where doxygen was started. If left blank the current directory will be used.\r
+\r
+OUTPUT_DIRECTORY = \r
+\r
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create\r
+# 4096 sub-directories (in 2 levels) under the output directory of each output\r
+# format and will distribute the generated files over these directories.\r
+# Enabling this option can be useful when feeding doxygen a huge amount of\r
+# source files, where putting all generated files in the same directory would\r
+# otherwise cause performance problems for the file system.\r
+\r
+CREATE_SUBDIRS = NO\r
+\r
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all\r
+# documentation generated by doxygen is written. Doxygen will use this\r
+# information to generate all constant output in the proper language.\r
+# The default language is English, other supported languages are:\r
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,\r
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,\r
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English\r
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,\r
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,\r
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.\r
+\r
+OUTPUT_LANGUAGE = English\r
+\r
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will\r
+# include brief member descriptions after the members that are listed in\r
+# the file and class documentation (similar to JavaDoc).\r
+# Set to NO to disable this.\r
+\r
+BRIEF_MEMBER_DESC = YES\r
+\r
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend\r
+# the brief description of a member or function before the detailed description.\r
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\r
+# brief descriptions will be completely suppressed.\r
+\r
+REPEAT_BRIEF = NO\r
+\r
+# This tag implements a quasi-intelligent brief description abbreviator\r
+# that is used to form the text in various listings. Each string\r
+# in this list, if found as the leading text of the brief description, will be\r
+# stripped from the text and the result after processing the whole list, is\r
+# used as the annotated text. Otherwise, the brief description is used as-is.\r
+# If left blank, the following values are used ("$name" is automatically\r
+# replaced with the name of the entity): "The $name class" "The $name widget"\r
+# "The $name file" "is" "provides" "specifies" "contains"\r
+# "represents" "a" "an" "the"\r
+\r
+ABBREVIATE_BRIEF =\r
+\r
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\r
+# Doxygen will generate a detailed section even if there is only a brief\r
+# description.\r
+\r
+ALWAYS_DETAILED_SEC = YES\r
+\r
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\r
+# inherited members of a class in the documentation of that class as if those\r
+# members were ordinary class members. Constructors, destructors and assignment\r
+# operators of the base classes will not be shown.\r
+\r
+INLINE_INHERITED_MEMB = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full\r
+# path before files name in the file list and in the header files. If set\r
+# to NO the shortest path that makes the file name unique will be used.\r
+\r
+FULL_PATH_NAMES = NO\r
+\r
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag\r
+# can be used to strip a user-defined part of the path. Stripping is\r
+# only done if one of the specified strings matches the left-hand part of\r
+# the path. The tag can be used to show relative paths in the file list.\r
+# If left blank the directory from which doxygen is run is used as the\r
+# path to strip.\r
+\r
+STRIP_FROM_PATH =\r
+\r
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of\r
+# the path mentioned in the documentation of a class, which tells\r
+# the reader which header file to include in order to use a class.\r
+# If left blank only the name of the header file containing the class\r
+# definition is used. Otherwise one should specify the include paths that\r
+# are normally passed to the compiler using the -I flag.\r
+\r
+STRIP_FROM_INC_PATH =\r
+\r
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter\r
+# (but less readable) file names. This can be useful if your file system\r
+# doesn't support long names like on DOS, Mac, or CD-ROM.\r
+\r
+SHORT_NAMES = NO\r
+\r
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen\r
+# will interpret the first line (until the first dot) of a JavaDoc-style\r
+# comment as the brief description. If set to NO, the JavaDoc\r
+# comments will behave just like regular Qt-style comments\r
+# (thus requiring an explicit @brief command for a brief description.)\r
+\r
+JAVADOC_AUTOBRIEF = NO\r
+\r
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will\r
+# interpret the first line (until the first dot) of a Qt-style\r
+# comment as the brief description. If set to NO, the comments\r
+# will behave just like regular Qt-style comments (thus requiring\r
+# an explicit \brief command for a brief description.)\r
+\r
+QT_AUTOBRIEF = NO\r
+\r
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen\r
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///\r
+# comments) as a brief description. This used to be the default behaviour.\r
+# The new default is to treat a multi-line C++ comment block as a detailed\r
+# description. Set this tag to YES if you prefer the old behaviour instead.\r
+\r
+MULTILINE_CPP_IS_BRIEF = NO\r
+\r
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented\r
+# member inherits the documentation from any documented member that it\r
+# re-implements.\r
+\r
+INHERIT_DOCS = NO\r
+\r
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce\r
+# a new page for each member. If set to NO, the documentation of a member will\r
+# be part of the file/class/namespace that contains it.\r
+\r
+SEPARATE_MEMBER_PAGES = NO\r
+\r
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.\r
+# Doxygen uses this value to replace tabs by spaces in code fragments.\r
+\r
+TAB_SIZE = 4\r
+\r
+# This tag can be used to specify a number of aliases that acts\r
+# as commands in the documentation. An alias has the form "name=value".\r
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to\r
+# put the command \sideeffect (or @sideeffect) in the documentation, which\r
+# will result in a user-defined paragraph with heading "Side Effects:".\r
+# You can put \n's in the value part of an alias to insert newlines.\r
+\r
+ALIASES = "prototype = @b Warning: This is a prototype" \\r
+ "privlevel = @xrefitem privlevel \"Privilege level\" \"Privilege Level\"" \\r
+ "privilege = @xrefitem privilege \"Privilege\" \"Privilege\"" \\r
+ "compatibility = @xrefitem compatibility \"Compatibility\" \"Compatibility \"" \\r
+ "feature = @xrefitem feature \"Required feature\" \"Required Feature \"" \\r
+ "final=\par Final:\n @xmlonly <pcheck-final>final</pcheck-final> @endxmlonly "\r
+\r
+\r
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C\r
+# sources only. Doxygen will then generate output that is more tailored for C.\r
+# For instance, some of the names that are used will be different. The list\r
+# of all members will be omitted, etc.\r
+\r
+OPTIMIZE_OUTPUT_FOR_C = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Java. For instance, namespaces will be presented as packages, qualified\r
+# scopes will look different, etc.\r
+\r
+OPTIMIZE_OUTPUT_JAVA = NO\r
+\r
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\r
+# sources only. Doxygen will then generate output that is more tailored for\r
+# Fortran.\r
+\r
+OPTIMIZE_FOR_FORTRAN = NO\r
+\r
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\r
+# sources. Doxygen will then generate output that is tailored for\r
+# VHDL.\r
+\r
+OPTIMIZE_OUTPUT_VHDL = NO\r
+\r
+# Doxygen selects the parser to use depending on the extension of the files it\r
+# parses. With this tag you can assign which parser to use for a given extension.\r
+# Doxygen has a built-in mapping, but you can override or extend it using this\r
+# tag. The format is ext=language, where ext is a file extension, and language\r
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,\r
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make\r
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C\r
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions\r
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.\r
+\r
+EXTENSION_MAPPING =\r
+\r
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\r
+# to include (a tag file for) the STL sources as input, then you should\r
+# set this tag to YES in order to let doxygen match functions declarations and\r
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.\r
+# func(std::string) {}). This also makes the inheritance and collaboration\r
+# diagrams that involve STL classes more complete and accurate.\r
+\r
+BUILTIN_STL_SUPPORT = NO\r
+\r
+# If you use Microsoft's C++/CLI language, you should set this option to YES to\r
+# enable parsing support.\r
+\r
+CPP_CLI_SUPPORT = NO\r
+\r
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.\r
+# Doxygen will parse them like normal C++ but will assume all classes use public\r
+# instead of private inheritance when no explicit protection keyword is present.\r
+\r
+SIP_SUPPORT = NO\r
+\r
+# For Microsoft's IDL there are propget and propput attributes to indicate getter\r
+# and setter methods for a property. Setting this option to YES (the default)\r
+# will make doxygen replace the get and set methods by a property in the\r
+# documentation. This will only work if the methods are indeed getting or\r
+# setting a simple type. If this is not the case, or you want to show the\r
+# methods anyway, you should set this option to NO.\r
+\r
+IDL_PROPERTY_SUPPORT = YES\r
+\r
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\r
+# tag is set to YES, then doxygen will reuse the documentation of the first\r
+# member in the group (if any) for the other members of the group. By default\r
+# all members of a group must be documented explicitly.\r
+\r
+DISTRIBUTE_GROUP_DOC = NO\r
+\r
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of\r
+# the same type (for instance a group of public functions) to be put as a\r
+# subgroup of that type (e.g. under the Public Functions section). Set it to\r
+# NO to prevent subgrouping. Alternatively, this can be done per class using\r
+# the \nosubgrouping command.\r
+\r
+SUBGROUPING = YES\r
+\r
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and\r
+# unions are shown inside the group in which they are included (e.g. using\r
+# @ingroup) instead of on a separate page (for HTML and Man pages) or\r
+# section (for LaTeX and RTF).\r
+\r
+INLINE_GROUPED_CLASSES = NO\r
+\r
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum\r
+# is documented as struct, union, or enum with the name of the typedef. So\r
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\r
+# with name TypeT. When disabled the typedef will appear as a member of a file,\r
+# namespace, or class. And the struct will be named TypeS. This can typically\r
+# be useful for C code in case the coding convention dictates that all compound\r
+# types are typedef'ed and only the typedef is referenced, never the tag name.\r
+\r
+TYPEDEF_HIDES_STRUCT = NO\r
+\r
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to\r
+# determine which symbols to keep in memory and which to flush to disk.\r
+# When the cache is full, less often used symbols will be written to disk.\r
+# For small to medium size projects (<1000 input files) the default value is\r
+# probably good enough. For larger projects a too small cache size can cause\r
+# doxygen to be busy swapping symbols to and from disk most of the time\r
+# causing a significant performance penalty.\r
+# If the system has enough physical memory increasing the cache will improve the\r
+# performance by keeping more symbols in memory. Note that the value works on\r
+# a logarithmic scale so increasing the size by one will roughly double the\r
+# memory usage. The cache size is given by this formula:\r
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,\r
+# corresponding to a cache size of 2^16 = 65536 symbols\r
+\r
+SYMBOL_CACHE_SIZE = 0\r
+\r
+#---------------------------------------------------------------------------\r
+# Build related configuration options\r
+#---------------------------------------------------------------------------\r
+\r
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in\r
+# documentation are documented, even if no documentation was available.\r
+# Private class members and static file members will be hidden unless\r
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES\r
+\r
+EXTRACT_ALL = NO\r
+\r
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class\r
+# will be included in the documentation.\r
+\r
+EXTRACT_PRIVATE = NO\r
+\r
+# If the EXTRACT_STATIC tag is set to YES all static members of a file\r
+# will be included in the documentation.\r
+\r
+EXTRACT_STATIC = YES\r
+\r
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)\r
+# defined locally in source files will be included in the documentation.\r
+# If set to NO only classes defined in header files are included.\r
+\r
+EXTRACT_LOCAL_CLASSES = NO\r
+\r
+# This flag is only useful for Objective-C code. When set to YES local\r
+# methods, which are defined in the implementation section but not in\r
+# the interface are included in the documentation.\r
+# If set to NO (the default) only methods in the interface are included.\r
+\r
+EXTRACT_LOCAL_METHODS = NO\r
+\r
+# If this flag is set to YES, the members of anonymous namespaces will be\r
+# extracted and appear in the documentation as a namespace called\r
+# 'anonymous_namespace{file}', where file will be replaced with the base\r
+# name of the file that contains the anonymous namespace. By default\r
+# anonymous namespaces are hidden.\r
+\r
+EXTRACT_ANON_NSPACES = NO\r
+\r
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\r
+# undocumented members of documented classes, files or namespaces.\r
+# If set to NO (the default) these members will be included in the\r
+# various overviews, but no documentation section is generated.\r
+# This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_MEMBERS = YES\r
+\r
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\r
+# undocumented classes that are normally visible in the class hierarchy.\r
+# If set to NO (the default) these classes will be included in the various\r
+# overviews. This option has no effect if EXTRACT_ALL is enabled.\r
+\r
+HIDE_UNDOC_CLASSES = YES\r
+\r
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all\r
+# friend (class|struct|union) declarations.\r
+# If set to NO (the default) these declarations will be included in the\r
+# documentation.\r
+\r
+HIDE_FRIEND_COMPOUNDS = YES\r
+\r
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\r
+# documentation blocks found inside the body of a function.\r
+# If set to NO (the default) these blocks will be appended to the\r
+# function's detailed documentation block.\r
+\r
+HIDE_IN_BODY_DOCS = YES\r
+\r
+# The INTERNAL_DOCS tag determines if documentation\r
+# that is typed after a \internal command is included. If the tag is set\r
+# to NO (the default) then the documentation will be excluded.\r
+# Set it to YES to include the internal documentation.\r
+\r
+INTERNAL_DOCS = NO\r
+\r
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate\r
+# file names in lower-case letters. If set to YES upper-case letters are also\r
+# allowed. This is useful if you have classes or files whose names only differ\r
+# in case and if your file system supports case sensitive file names. Windows\r
+# and Mac users are advised to set this option to NO.\r
+\r
+CASE_SENSE_NAMES = YES\r
+\r
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen\r
+# will show members with their full class and namespace scopes in the\r
+# documentation. If set to YES the scope will be hidden.\r
+\r
+HIDE_SCOPE_NAMES = NO\r
+\r
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen\r
+# will put a list of the files that are included by a file in the documentation\r
+# of that file.\r
+\r
+SHOW_INCLUDE_FILES = NO\r
+\r
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen\r
+# will list include files with double quotes in the documentation\r
+# rather than with sharp brackets.\r
+\r
+FORCE_LOCAL_INCLUDES = NO\r
+\r
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]\r
+# is inserted in the documentation for inline members.\r
+\r
+INLINE_INFO = YES\r
+\r
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen\r
+# will sort the (detailed) documentation of file and class members\r
+# alphabetically by member name. If set to NO the members will appear in\r
+# declaration order.\r
+\r
+SORT_MEMBER_DOCS = YES\r
+\r
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the\r
+# brief documentation of file, namespace and class members alphabetically\r
+# by member name. If set to NO (the default) the members will appear in\r
+# declaration order.\r
+\r
+SORT_BRIEF_DOCS = YES\r
+\r
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen\r
+# will sort the (brief and detailed) documentation of class members so that\r
+# constructors and destructors are listed first. If set to NO (the default)\r
+# the constructors will appear in the respective orders defined by\r
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.\r
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO\r
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.\r
+\r
+SORT_MEMBERS_CTORS_1ST = NO\r
+\r
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the\r
+# hierarchy of group names into alphabetical order. If set to NO (the default)\r
+# the group names will appear in their defined order.\r
+\r
+SORT_GROUP_NAMES = NO\r
+\r
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be\r
+# sorted by fully-qualified names, including namespaces. If set to\r
+# NO (the default), the class list will be sorted only by class name,\r
+# not including the namespace part.\r
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\r
+# Note: This option applies only to the class list, not to the\r
+# alphabetical list.\r
+\r
+SORT_BY_SCOPE_NAME = YES\r
+\r
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to\r
+# do proper type resolution of all parameters of a function it will reject a\r
+# match between the prototype and the implementation of a member function even\r
+# if there is only one candidate or it is obvious which candidate to choose\r
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen\r
+# will still accept a match between prototype and implementation in such cases.\r
+\r
+STRICT_PROTO_MATCHING = NO\r
+\r
+# The GENERATE_TODOLIST tag can be used to enable (YES) or\r
+# disable (NO) the todo list. This list is created by putting \todo\r
+# commands in the documentation.\r
+\r
+GENERATE_TODOLIST = YES\r
+\r
+# The GENERATE_TESTLIST tag can be used to enable (YES) or\r
+# disable (NO) the test list. This list is created by putting \test\r
+# commands in the documentation.\r
+\r
+GENERATE_TESTLIST = NO\r
+\r
+# The GENERATE_BUGLIST tag can be used to enable (YES) or\r
+# disable (NO) the bug list. This list is created by putting \bug\r
+# commands in the documentation.\r
+\r
+GENERATE_BUGLIST = NO\r
+\r
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or\r
+# disable (NO) the deprecated list. This list is created by putting\r
+# \deprecated commands in the documentation.\r
+\r
+GENERATE_DEPRECATEDLIST= YES\r
+\r
+# The ENABLED_SECTIONS tag can be used to enable conditional\r
+# documentation sections, marked by \if sectionname ... \endif.\r
+\r
+ENABLED_SECTIONS = \r
+\r
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines\r
+# the initial value of a variable or macro consists of for it to appear in\r
+# the documentation. If the initializer consists of more lines than specified\r
+# here it will be hidden. Use a value of 0 to hide initializers completely.\r
+# The appearance of the initializer of individual variables and macros in the\r
+# documentation can be controlled using \showinitializer or \hideinitializer\r
+# command in the documentation regardless of this setting.\r
+\r
+MAX_INITIALIZER_LINES = 30\r
+\r
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated\r
+# at the bottom of the documentation of classes and structs. If set to YES the\r
+# list will mention the files that were used to generate the documentation.\r
+\r
+SHOW_USED_FILES = NO\r
+\r
+# If the sources in your project are distributed over multiple directories\r
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy\r
+# in the documentation. The default is NO.\r
+\r
+SHOW_DIRECTORIES = NO\r
+\r
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.\r
+# This will remove the Files entry from the Quick Index and from the\r
+# Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_FILES = YES\r
+\r
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the\r
+# Namespaces page.\r
+# This will remove the Namespaces entry from the Quick Index\r
+# and from the Folder Tree View (if specified). The default is YES.\r
+\r
+SHOW_NAMESPACES = YES\r
+\r
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that\r
+# doxygen should invoke to get the current version for each file (typically from\r
+# the version control system). Doxygen will invoke the program by executing (via\r
+# popen()) the command <command> <input-file>, where <command> is the value of\r
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file\r
+# provided by doxygen. Whatever the program writes to standard output\r
+# is used as the file version. See the manual for examples.\r
+\r
+FILE_VERSION_FILTER =\r
+\r
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\r
+# by doxygen. The layout file controls the global structure of the generated\r
+# output files in an output format independent way. The create the layout file\r
+# that represents doxygen's defaults, run doxygen with the -l option.\r
+# You can optionally specify a file name after the option, if omitted\r
+# DoxygenLayout.xml will be used as the name of the layout file.\r
+\r
+LAYOUT_FILE = DoxygenLayout.xml\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to warning and progress messages\r
+#---------------------------------------------------------------------------\r
+\r
+# The QUIET tag can be used to turn on/off the messages that are generated\r
+# by doxygen. Possible values are YES and NO. If left blank NO is used.\r
+\r
+QUIET = YES\r
+\r
+# The WARNINGS tag can be used to turn on/off the warning messages that are\r
+# generated by doxygen. Possible values are YES and NO. If left blank\r
+# NO is used.\r
+\r
+WARNINGS = YES\r
+\r
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings\r
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will\r
+# automatically be disabled.\r
+\r
+WARN_IF_UNDOCUMENTED = YES\r
+\r
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for\r
+# potential errors in the documentation, such as not documenting some\r
+# parameters in a documented function, or documenting parameters that\r
+# don't exist or using markup commands wrongly.\r
+\r
+WARN_IF_DOC_ERROR = YES\r
+\r
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for\r
+# functions that are documented, but have no documentation for their parameters\r
+# or return value. If set to NO (the default) doxygen will only warn about\r
+# wrong or incomplete parameter documentation, but not about the absence of\r
+# documentation.\r
+\r
+WARN_NO_PARAMDOC = NO\r
+\r
+# The WARN_FORMAT tag determines the format of the warning messages that\r
+# doxygen can produce. The string should contain the $file, $line, and $text\r
+# tags, which will be replaced by the file and line number from which the\r
+# warning originated and the warning text. Optionally the format may contain\r
+# $version, which will be replaced by the version of the file (if it could\r
+# be obtained via FILE_VERSION_FILTER)\r
+\r
+WARN_FORMAT = "$file:$line: $text"\r
+\r
+# The WARN_LOGFILE tag can be used to specify a file to which warning\r
+# and error messages should be written. If left blank the output is written\r
+# to stderr.\r
+\r
+WARN_LOGFILE = warning.txt\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the input files\r
+#---------------------------------------------------------------------------\r
+\r
+# The INPUT tag can be used to specify the files and/or directories that contain\r
+# documented source files. You may enter file names like "myfile.cpp" or\r
+# directories like "/usr/src/myproject". Separate the files or directories\r
+# with spaces.\r
+\r
+INPUT = ../../../../../osp \\r
+ ./libraries \r
+ \r
+\r
+# This tag can be used to specify the character encoding of the source files\r
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is\r
+# also the default input encoding. Doxygen uses libiconv (or the iconv built\r
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for\r
+# the list of possible encodings.\r
+\r
+INPUT_ENCODING = UTF-8\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank the following patterns are tested:\r
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh\r
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py\r
+# *.f90 *.f *.for *.vhd *.vhdl\r
+\r
+FILE_PATTERNS = *.h\r
+\r
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories\r
+# should be searched for input files as well. Possible values are YES and NO.\r
+# If left blank NO is used.\r
+\r
+RECURSIVE = YES\r
+\r
+# The EXCLUDE tag can be used to specify files and/or directories that should\r
+# excluded from the INPUT source files. This way you can easily exclude a\r
+# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
+\r
+EXCLUDE = ../../../../../osp/FBaseSysLog.h\r
+\r
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or\r
+# directories that are symbolic links (a Unix file system feature) are excluded\r
+# from the input.\r
+\r
+EXCLUDE_SYMLINKS = NO\r
+\r
+# If the value of the INPUT tag contains directories, you can use the\r
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\r
+# certain files from those directories. Note that the wildcards are matched\r
+# against the file with absolute path, so to exclude all test directories\r
+# for example use the pattern */test/*\r
+\r
+EXCLUDE_PATTERNS = \r
+\r
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\r
+# (namespaces, classes, functions, etc.) that should be excluded from the\r
+# output. The symbol name can be a fully qualified name, a word, or if the\r
+# wildcard * is used, a substring. Examples: ANamespace, AClass,\r
+# AClass::ANamespace, ANamespace::*Test\r
+\r
+EXCLUDE_SYMBOLS =\r
+\r
+# The EXAMPLE_PATH tag can be used to specify one or more files or\r
+# directories that contain example code fragments that are included (see\r
+# the \include command).\r
+\r
+EXAMPLE_PATH =\r
+\r
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the\r
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp\r
+# and *.h) to filter out the source-files in the directories. If left\r
+# blank all files are included.\r
+\r
+EXAMPLE_PATTERNS =\r
+\r
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\r
+# searched for input files to be used with the \include or \dontinclude\r
+# commands irrespective of the value of the RECURSIVE tag.\r
+# Possible values are YES and NO. If left blank NO is used.\r
+\r
+EXAMPLE_RECURSIVE = NO\r
+\r
+# The IMAGE_PATH tag can be used to specify one or more files or\r
+# directories that contain image that are included in the documentation (see\r
+# the \image command).\r
+\r
+IMAGE_PATH = public/images\r
+\r
+# The INPUT_FILTER tag can be used to specify a program that doxygen should\r
+# invoke to filter for each input file. Doxygen will invoke the filter program\r
+# by executing (via popen()) the command <filter> <input-file>, where <filter>\r
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an\r
+# input file. Doxygen will then use the output that the filter program writes\r
+# to standard output.\r
+# If FILTER_PATTERNS is specified, this tag will be\r
+# ignored.\r
+\r
+INPUT_FILTER =\r
+\r
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\r
+# basis.\r
+# Doxygen will compare the file name with each pattern and apply the\r
+# filter if there is a match.\r
+# The filters are a list of the form:\r
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further\r
+# info on how filters are used. If FILTER_PATTERNS is empty or if\r
+# non of the patterns match the file name, INPUT_FILTER is applied.\r
+\r
+FILTER_PATTERNS =\r
+\r
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\r
+# INPUT_FILTER) will be used to filter the input files when producing source\r
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).\r
+\r
+FILTER_SOURCE_FILES = NO\r
+\r
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\r
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)\r
+# and it is also possible to disable source filtering for a specific pattern\r
+# using *.ext= (so without naming a filter). This option only has effect when\r
+# FILTER_SOURCE_FILES is enabled.\r
+\r
+FILTER_SOURCE_PATTERNS =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to source browsing\r
+#---------------------------------------------------------------------------\r
+\r
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will\r
+# be generated. Documented entities will be cross-referenced with these sources.\r
+# Note: To get rid of all source code in the generated output, make sure also\r
+# VERBATIM_HEADERS is set to NO.\r
+\r
+SOURCE_BROWSER = NO\r
+\r
+# Setting the INLINE_SOURCES tag to YES will include the body\r
+# of functions and classes directly in the documentation.\r
+\r
+INLINE_SOURCES = NO\r
+\r
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct\r
+# doxygen to hide any special comment blocks from generated source code\r
+# fragments. Normal C and C++ comments will always remain visible.\r
+\r
+STRIP_CODE_COMMENTS = YES\r
+\r
+# If the REFERENCED_BY_RELATION tag is set to YES\r
+# then for each documented function all documented\r
+# functions referencing it will be listed.\r
+\r
+REFERENCED_BY_RELATION = NO\r
+\r
+# If the REFERENCES_RELATION tag is set to YES\r
+# then for each documented function all documented entities\r
+# called/used by that function will be listed.\r
+\r
+REFERENCES_RELATION = NO\r
+\r
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)\r
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from\r
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will\r
+# link to the source code.\r
+# Otherwise they will link to the documentation.\r
+\r
+REFERENCES_LINK_SOURCE = NO\r
+\r
+# If the USE_HTAGS tag is set to YES then the references to source code\r
+# will point to the HTML generated by the htags(1) tool instead of doxygen\r
+# built-in source browser. The htags tool is part of GNU's global source\r
+# tagging system (see http://www.gnu.org/software/global/global.html). You\r
+# will need version 4.8.6 or higher.\r
+\r
+USE_HTAGS = NO\r
+\r
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen\r
+# will generate a verbatim copy of the header file for each class for\r
+# which an include is specified. Set to NO to disable this.\r
+\r
+VERBATIM_HEADERS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the alphabetical class index\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index\r
+# of all compounds will be generated. Enable this if the project\r
+# contains a lot of classes, structs, unions or interfaces.\r
+\r
+ALPHABETICAL_INDEX = YES\r
+\r
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then\r
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns\r
+# in which this list will be split (can be a number in the range [1..20])\r
+\r
+COLS_IN_ALPHA_INDEX = 5\r
+\r
+# In case all classes in a project start with a common prefix, all\r
+# classes will be put under the same header in the alphabetical index.\r
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that\r
+# should be ignored while generating the index headers.\r
+\r
+IGNORE_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the HTML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will\r
+# generate HTML output.\r
+\r
+GENERATE_HTML = YES\r
+\r
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `html' will be used as the default path.\r
+\r
+HTML_OUTPUT = apidocs\r
+\r
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for\r
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank\r
+# doxygen will generate files with .html extension.\r
+\r
+HTML_FILE_EXTENSION = .html\r
+\r
+# The HTML_HEADER tag can be used to specify a personal HTML header for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard header. Note that when using a custom header you are responsible\r
+# for the proper inclusion of any scripts and style sheets that doxygen\r
+# needs, which is dependent on the configuration options used.\r
+# It is adviced to generate a default header using "doxygen -w html\r
+# header.html footer.html stylesheet.css YourConfigFile" and then modify\r
+# that header. Note that the header is subject to change so you typically\r
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!\r
+\r
+HTML_HEADER =\r
+\r
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for\r
+# each generated HTML page. If it is left blank doxygen will generate a\r
+# standard footer.\r
+\r
+HTML_FOOTER = footer.html\r
+\r
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading\r
+# style sheet that is used by each HTML page. It can be used to\r
+# fine-tune the look of the HTML output. If the tag is left blank doxygen\r
+# will generate a default style sheet. Note that doxygen will try to copy\r
+# the style sheet file to the HTML output directory, so don't put your own\r
+# stylesheet in the HTML output directory as well, or it will be erased!\r
+\r
+HTML_STYLESHEET = Tizen.css\r
+\r
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\r
+# other source files which should be copied to the HTML output directory. Note\r
+# that these files will be copied to the base HTML output directory. Use the\r
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\r
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that\r
+# the files will be copied as-is; there are no commands or markers available.\r
+\r
+HTML_EXTRA_FILES =\r
+\r
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.\r
+# Doxygen will adjust the colors in the stylesheet and background images\r
+# according to this color. Hue is specified as an angle on a colorwheel,\r
+# see http://en.wikipedia.org/wiki/Hue for more information.\r
+# For instance the value 0 represents red, 60 is yellow, 120 is green,\r
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.\r
+# The allowed range is 0 to 359.\r
+\r
+HTML_COLORSTYLE_HUE = 220\r
+\r
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of\r
+# the colors in the HTML output. For a value of 0 the output will use\r
+# grayscales only. A value of 255 will produce the most vivid colors.\r
+\r
+HTML_COLORSTYLE_SAT = 100\r
+\r
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to\r
+# the luminance component of the colors in the HTML output. Values below\r
+# 100 gradually make the output lighter, whereas values above 100 make\r
+# the output darker. The value divided by 100 is the actual gamma applied,\r
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,\r
+# and 100 does not change the gamma.\r
+\r
+HTML_COLORSTYLE_GAMMA = 80\r
+\r
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\r
+# page will contain the date and time when the page was generated. Setting\r
+# this to NO can help when comparing the output of multiple runs.\r
+\r
+HTML_TIMESTAMP = YES\r
+\r
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,\r
+# files or namespaces will be aligned in HTML using tables. If set to\r
+# NO a bullet list will be used.\r
+\r
+HTML_ALIGN_MEMBERS = YES\r
+\r
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\r
+# documentation will contain sections that can be hidden and shown after the\r
+# page has loaded. For this to work a browser that supports\r
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox\r
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).\r
+\r
+HTML_DYNAMIC_SECTIONS = NO\r
+\r
+# If the GENERATE_DOCSET tag is set to YES, additional index files\r
+# will be generated that can be used as input for Apple's Xcode 3\r
+# integrated development environment, introduced with OSX 10.5 (Leopard).\r
+# To create a documentation set, doxygen will generate a Makefile in the\r
+# HTML output directory. Running make will produce the docset in that\r
+# directory and running "make install" will install the docset in\r
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find\r
+# it at startup.\r
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html\r
+# for more information.\r
+\r
+GENERATE_DOCSET = NO\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the\r
+# feed. A documentation feed provides an umbrella under which multiple\r
+# documentation sets from a single provider (such as a company or product suite)\r
+# can be grouped.\r
+\r
+DOCSET_FEEDNAME = "Doxygen generated docs"\r
+\r
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that\r
+# should uniquely identify the documentation set bundle. This should be a\r
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen\r
+# will append .docset to the name.\r
+\r
+DOCSET_BUNDLE_ID = org.doxygen.Project\r
+\r
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify\r
+# the documentation publisher. This should be a reverse domain-name style\r
+# string, e.g. com.mycompany.MyDocSet.documentation.\r
+\r
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher\r
+\r
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.\r
+\r
+DOCSET_PUBLISHER_NAME = Publisher\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files\r
+# will be generated that can be used as input for tools like the\r
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)\r
+# of the generated HTML documentation.\r
+\r
+GENERATE_HTMLHELP = YES\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can\r
+# be used to specify the file name of the resulting .chm file. You\r
+# can add a path in front of the file if the result should not be\r
+# written to the html output directory.\r
+\r
+CHM_FILE =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can\r
+# be used to specify the location (absolute path including file name) of\r
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run\r
+# the HTML help compiler on the generated index.hhp.\r
+\r
+HHC_LOCATION =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag\r
+# controls if a separate .chi index file is generated (YES) or that\r
+# it should be included in the master .chm file (NO).\r
+\r
+GENERATE_CHI = NO\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING\r
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file\r
+# content.\r
+\r
+CHM_INDEX_ENCODING =\r
+\r
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag\r
+# controls whether a binary table of contents is generated (YES) or a\r
+# normal table of contents (NO) in the .chm file.\r
+\r
+BINARY_TOC = YES\r
+\r
+# The TOC_EXPAND flag can be set to YES to add extra items for group members\r
+# to the contents of the HTML help documentation and to the tree view.\r
+\r
+TOC_EXPAND = YES\r
+\r
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\r
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated\r
+# that can be used as input for Qt's qhelpgenerator to generate a\r
+# Qt Compressed Help (.qch) of the generated HTML documentation.\r
+\r
+GENERATE_QHP = NO\r
+\r
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can\r
+# be used to specify the file name of the resulting .qch file.\r
+# The path specified is relative to the HTML output folder.\r
+\r
+QCH_FILE =\r
+\r
+# The QHP_NAMESPACE tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#namespace\r
+\r
+QHP_NAMESPACE = org.doxygen.Project\r
+\r
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating\r
+# Qt Help Project output. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders\r
+\r
+QHP_VIRTUAL_FOLDER = doc\r
+\r
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to\r
+# add. For more information please see\r
+# http://doc.trolltech.com/qthelpproject.html#custom-filters\r
+\r
+QHP_CUST_FILTER_NAME =\r
+\r
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the\r
+# custom filter to add. For more information please see\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">\r
+# Qt Help Project / Custom Filters</a>.\r
+\r
+QHP_CUST_FILTER_ATTRS =\r
+\r
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\r
+# project's\r
+# filter section matches.\r
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">\r
+# Qt Help Project / Filter Attributes</a>.\r
+\r
+QHP_SECT_FILTER_ATTRS =\r
+\r
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can\r
+# be used to specify the location of Qt's qhelpgenerator.\r
+# If non-empty doxygen will try to run qhelpgenerator on the generated\r
+# .qhp file.\r
+\r
+QHG_LOCATION =\r
+\r
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files\r
+# will be generated, which together with the HTML files, form an Eclipse help\r
+# plugin. To install this plugin and make it available under the help contents\r
+# menu in Eclipse, the contents of the directory containing the HTML and XML\r
+# files needs to be copied into the plugins directory of eclipse. The name of\r
+# the directory within the plugins directory should be the same as\r
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before\r
+# the help appears.\r
+\r
+GENERATE_ECLIPSEHELP = YES\r
+\r
+# A unique identifier for the eclipse help plugin. When installing the plugin\r
+# the directory name containing the HTML and XML files should also have\r
+# this name.\r
+\r
+ECLIPSE_DOC_ID = org.doxygen.Project\r
+\r
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at\r
+# top of each HTML page. The value NO (the default) enables the index and\r
+# the value YES disables it.\r
+\r
+DISABLE_INDEX = NO\r
+\r
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values\r
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML\r
+# documentation. Note that a value of 0 will completely suppress the enum\r
+# values from appearing in the overview section.\r
+\r
+ENUM_VALUES_PER_LINE = 4\r
+\r
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\r
+# structure should be generated to display hierarchical information.\r
+# If the tag value is set to YES, a side panel will be generated\r
+# containing a tree-like index structure (just like the one that\r
+# is generated for HTML Help). For this to work a browser that supports\r
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).\r
+# Windows users are probably better off using the HTML help feature.\r
+\r
+GENERATE_TREEVIEW = NO\r
+\r
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,\r
+# and Class Hierarchy pages using a tree view instead of an ordered list.\r
+\r
+USE_INLINE_TREES = NO\r
+\r
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be\r
+# used to set the initial width (in pixels) of the frame in which the tree\r
+# is shown.\r
+\r
+TREEVIEW_WIDTH = 250\r
+\r
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open\r
+# links to external symbols imported via tag files in a separate window.\r
+\r
+EXT_LINKS_IN_WINDOW = NO\r
+\r
+# Use this tag to change the font size of Latex formulas included\r
+# as images in the HTML documentation. The default is 10. Note that\r
+# when you change the font size after a successful doxygen run you need\r
+# to manually remove any form_*.png images from the HTML output directory\r
+# to force them to be regenerated.\r
+\r
+FORMULA_FONTSIZE = 10\r
+\r
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images\r
+# generated for formulas are transparent PNGs. Transparent PNGs are\r
+# not supported properly for IE 6.0, but are supported on all modern browsers.\r
+# Note that when changing this option you need to delete any form_*.png files\r
+# in the HTML output before the changes have effect.\r
+\r
+FORMULA_TRANSPARENT = YES\r
+\r
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax\r
+# (see http://www.mathjax.org) which uses client side Javascript for the\r
+# rendering instead of using prerendered bitmaps. Use this if you do not\r
+# have LaTeX installed or if you want to formulas look prettier in the HTML\r
+# output. When enabled you also need to install MathJax separately and\r
+# configure the path to it using the MATHJAX_RELPATH option.\r
+\r
+USE_MATHJAX = NO\r
+\r
+# When MathJax is enabled you need to specify the location relative to the\r
+# HTML output directory using the MATHJAX_RELPATH option. The destination\r
+# directory should contain the MathJax.js script. For instance, if the mathjax\r
+# directory is located at the same level as the HTML output directory, then\r
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the\r
+# mathjax.org site, so you can quickly see the result without installing\r
+# MathJax, but it is strongly recommended to install a local copy of MathJax\r
+# before deployment.\r
+\r
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax\r
+\r
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box\r
+# for the HTML output. The underlying search engine uses javascript\r
+# and DHTML and should work on any modern browser. Note that when using\r
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets\r
+# (GENERATE_DOCSET) there is already a search function so this one should\r
+# typically be disabled. For large projects the javascript based search engine\r
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.\r
+\r
+SEARCHENGINE = NO\r
+\r
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be\r
+# implemented using a PHP enabled web server instead of at the web client\r
+# using Javascript. Doxygen will generate the search PHP script and index\r
+# file to put on the web server. The advantage of the server\r
+# based approach is that it scales better to large projects and allows\r
+# full text search. The disadvantages are that it is more difficult to setup\r
+# and does not have live searching capabilities.\r
+\r
+SERVER_BASED_SEARCH = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the LaTeX output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will\r
+# generate Latex output.\r
+\r
+GENERATE_LATEX = NO\r
+\r
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `latex' will be used as the default path.\r
+\r
+LATEX_OUTPUT = latex\r
+\r
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be\r
+# invoked. If left blank `latex' will be used as the default command name.\r
+# Note that when enabling USE_PDFLATEX this option is only used for\r
+# generating bitmaps for formulas in the HTML output, but not in the\r
+# Makefile that is written to the output directory.\r
+\r
+LATEX_CMD_NAME = latex\r
+\r
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to\r
+# generate index for LaTeX. If left blank `makeindex' will be used as the\r
+# default command name.\r
+\r
+MAKEINDEX_CMD_NAME = makeindex\r
+\r
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact\r
+# LaTeX documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_LATEX = NO\r
+\r
+# The PAPER_TYPE tag can be used to set the paper type that is used\r
+# by the printer. Possible values are: a4, letter, legal and\r
+# executive. If left blank a4wide will be used.\r
+\r
+PAPER_TYPE = a4wide\r
+\r
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX\r
+# packages that should be included in the LaTeX output.\r
+\r
+EXTRA_PACKAGES =\r
+\r
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for\r
+# the generated latex document. The header should contain everything until\r
+# the first chapter. If it is left blank doxygen will generate a\r
+# standard header. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_HEADER =\r
+\r
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for\r
+# the generated latex document. The footer should contain everything after\r
+# the last chapter. If it is left blank doxygen will generate a\r
+# standard footer. Notice: only use this tag if you know what you are doing!\r
+\r
+LATEX_FOOTER =\r
+\r
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated\r
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will\r
+# contain links (just like the HTML output) instead of page references\r
+# This makes the output suitable for online browsing using a pdf viewer.\r
+\r
+PDF_HYPERLINKS = NO\r
+\r
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of\r
+# plain latex in the generated Makefile. Set this option to YES to get a\r
+# higher quality PDF documentation.\r
+\r
+USE_PDFLATEX = NO\r
+\r
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.\r
+# command to the generated LaTeX files. This will instruct LaTeX to keep\r
+# running if errors occur, instead of asking the user for help.\r
+# This option is also used when generating formulas in HTML.\r
+\r
+LATEX_BATCHMODE = NO\r
+\r
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not\r
+# include the index chapters (such as File Index, Compound Index, etc.)\r
+# in the output.\r
+\r
+LATEX_HIDE_INDICES = NO\r
+\r
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include\r
+# source code with syntax highlighting in the LaTeX output.\r
+# Note that which sources are shown also depends on other settings\r
+# such as SOURCE_BROWSER.\r
+\r
+LATEX_SOURCE_CODE = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the RTF output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output\r
+# The RTF output is optimized for Word 97 and may not look very pretty with\r
+# other RTF readers or editors.\r
+\r
+GENERATE_RTF = NO\r
+\r
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `rtf' will be used as the default path.\r
+\r
+RTF_OUTPUT = rtf\r
+\r
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact\r
+# RTF documents. This may be useful for small projects and may help to\r
+# save some trees in general.\r
+\r
+COMPACT_RTF = NO\r
+\r
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated\r
+# will contain hyperlink fields. The RTF file will\r
+# contain links (just like the HTML output) instead of page references.\r
+# This makes the output suitable for online browsing using WORD or other\r
+# programs which support those fields.\r
+# Note: wordpad (write) and others do not support links.\r
+\r
+RTF_HYPERLINKS = NO\r
+\r
+# Load stylesheet definitions from file. Syntax is similar to doxygen's\r
+# config file, i.e. a series of assignments. You only have to provide\r
+# replacements, missing definitions are set to their default value.\r
+\r
+RTF_STYLESHEET_FILE =\r
+\r
+# Set optional variables used in the generation of an rtf document.\r
+# Syntax is similar to doxygen's config file.\r
+\r
+RTF_EXTENSIONS_FILE =\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the man page output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will\r
+# generate man pages\r
+\r
+GENERATE_MAN = NO\r
+\r
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `man' will be used as the default path.\r
+\r
+MAN_OUTPUT = man\r
+\r
+# The MAN_EXTENSION tag determines the extension that is added to\r
+# the generated man pages (default is the subroutine's section .3)\r
+\r
+MAN_EXTENSION = .3\r
+\r
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,\r
+# then it will generate one additional man file for each entity\r
+# documented in the real man page(s). These additional files\r
+# only source the real man page, but without them the man command\r
+# would be unable to find the correct page. The default is NO.\r
+\r
+MAN_LINKS = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the XML output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_XML tag is set to YES Doxygen will\r
+# generate an XML file that captures the structure of\r
+# the code including all documentation.\r
+\r
+GENERATE_XML = NO\r
+\r
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.\r
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be\r
+# put in front of it. If left blank `xml' will be used as the default path.\r
+\r
+XML_OUTPUT = _xml\r
+\r
+# The XML_SCHEMA tag can be used to specify an XML schema,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_SCHEMA =\r
+\r
+# The XML_DTD tag can be used to specify an XML DTD,\r
+# which can be used by a validating XML parser to check the\r
+# syntax of the XML files.\r
+\r
+XML_DTD =\r
+\r
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will\r
+# dump the program listings (including syntax highlighting\r
+# and cross-referencing information) to the XML output. Note that\r
+# enabling this will significantly increase the size of the XML output.\r
+\r
+XML_PROGRAMLISTING = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options for the AutoGen Definitions output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will\r
+# generate an AutoGen Definitions (see autogen.sf.net) file\r
+# that captures the structure of the code including all\r
+# documentation. Note that this feature is still experimental\r
+# and incomplete at the moment.\r
+\r
+GENERATE_AUTOGEN_DEF = NO\r
+\r
+#---------------------------------------------------------------------------\r
+# configuration options related to the Perl module output\r
+#---------------------------------------------------------------------------\r
+\r
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will\r
+# generate a Perl module file that captures the structure of\r
+# the code including all documentation. Note that this\r
+# feature is still experimental and incomplete at the\r
+# moment.\r
+\r
+GENERATE_PERLMOD = NO\r
+\r
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate\r
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able\r
+# to generate PDF and DVI output from the Perl module output.\r
+\r
+PERLMOD_LATEX = NO\r
+\r
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be\r
+# nicely formatted so it can be parsed by a human reader.\r
+# This is useful\r
+# if you want to understand what is going on.\r
+# On the other hand, if this\r
+# tag is set to NO the size of the Perl module output will be much smaller\r
+# and Perl will parse it just the same.\r
+\r
+PERLMOD_PRETTY = YES\r
+\r
+# The names of the make variables in the generated doxyrules.make file\r
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.\r
+# This is useful so different doxyrules.make files included by the same\r
+# Makefile don't overwrite each other's variables.\r
+\r
+PERLMOD_MAKEVAR_PREFIX =\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the preprocessor\r
+#---------------------------------------------------------------------------\r
+\r
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will\r
+# evaluate all C-preprocessor directives found in the sources and include\r
+# files.\r
+\r
+ENABLE_PREPROCESSING = YES\r
+\r
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro\r
+# names in the source code. If set to NO (the default) only conditional\r
+# compilation will be performed. Macro expansion can be done in a controlled\r
+# way by setting EXPAND_ONLY_PREDEF to YES.\r
+\r
+MACRO_EXPANSION = YES\r
+\r
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES\r
+# then the macro expansion is limited to the macros specified with the\r
+# PREDEFINED and EXPAND_AS_DEFINED tags.\r
+\r
+EXPAND_ONLY_PREDEF = YES\r
+\r
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files\r
+# pointed to by INCLUDE_PATH will be searched when a #include is found.\r
+\r
+SEARCH_INCLUDES = YES\r
+\r
+# The INCLUDE_PATH tag can be used to specify one or more directories that\r
+# contain include files that are not input files but should be processed by\r
+# the preprocessor.\r
+\r
+INCLUDE_PATH =\r
+\r
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard\r
+# patterns (like *.h and *.hpp) to filter out the header-files in the\r
+# directories. If left blank, the patterns specified with FILE_PATTERNS will\r
+# be used.\r
+\r
+INCLUDE_FILE_PATTERNS =\r
+\r
+# The PREDEFINED tag can be used to specify one or more macro names that\r
+# are defined before the preprocessor is started (similar to the -D option of\r
+# gcc). The argument of the tag is a list of macros of the form: name\r
+# or name=definition (no spaces). If the definition and the = are\r
+# omitted =1 is assumed. To prevent a macro definition from being\r
+# undefined via #undef or recursively expanded use the := operator\r
+# instead of the = operator.\r
+\r
+PREDEFINED = LIBXML_OUTPUT_ENABLED LIBXML_PUSH_ENABLED LIBXML_TREE_ENABLED LIBXML_HTML_ENABLED _OSP_EXPORT_= _OSP_LOCAL_=\r
+\r
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then\r
+# this tag can be used to specify a list of macro names that should be expanded.\r
+# The macro definition that is found in the sources will be used.\r
+# Use the PREDEFINED tag if you want to use a different macro definition that\r
+# overrules the definition found in the source code.\r
+\r
+EXPAND_AS_DEFINED =\r
+\r
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then\r
+# doxygen's preprocessor will remove all references to function-like macros\r
+# that are alone on a line, have an all uppercase name, and do not end with a\r
+# semicolon, because these will confuse the parser if not removed.\r
+\r
+SKIP_FUNCTION_MACROS = YES\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration::additions related to external references\r
+#---------------------------------------------------------------------------\r
+\r
+# The TAGFILES option can be used to specify one or more tagfiles.\r
+# Optionally an initial location of the external documentation\r
+# can be added for each tagfile. The format of a tag file without\r
+# this location is as follows:\r
+#\r
+# TAGFILES = file1 file2 ...\r
+# Adding location for the tag files is done as follows:\r
+#\r
+# TAGFILES = file1=loc1 "file2 = loc2" ...\r
+# where "loc1" and "loc2" can be relative or absolute paths or\r
+# URLs. If a location is present for each tag, the installdox tool\r
+# does not have to be run to correct the links.\r
+# Note that each tag file must have a unique name\r
+# (where the name does NOT include the path)\r
+# If a tag file is not located in the directory in which doxygen\r
+# is run, you must also specify the path to the tagfile here.\r
+\r
+TAGFILES =\r
+\r
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create\r
+# a tag file that is based on the input files it reads.\r
+\r
+GENERATE_TAGFILE =\r
+\r
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed\r
+# in the class index. If set to NO only the inherited external classes\r
+# will be listed.\r
+\r
+ALLEXTERNALS = NO\r
+\r
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed\r
+# in the modules index. If set to NO, only the current project's groups will\r
+# be listed.\r
+\r
+EXTERNAL_GROUPS = YES\r
+\r
+# The PERL_PATH should be the absolute path and name of the perl script\r
+# interpreter (i.e. the result of `which perl').\r
+\r
+PERL_PATH = /usr/bin/perl\r
+\r
+#---------------------------------------------------------------------------\r
+# Configuration options related to the dot tool\r
+#---------------------------------------------------------------------------\r
+\r
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will\r
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base\r
+# or super classes. Setting the tag to NO turns the diagrams off. Note that\r
+# this option also works with HAVE_DOT disabled, but it is recommended to\r
+# install and use dot, since it yields more powerful graphs.\r
+\r
+CLASS_DIAGRAMS = YES\r
+\r
+# You can define message sequence charts within doxygen comments using the \msc\r
+# command. Doxygen will then run the mscgen tool (see\r
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the\r
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where\r
+# the mscgen tool resides. If left empty the tool is assumed to be found in the\r
+# default search path.\r
+\r
+MSCGEN_PATH =\r
+\r
+# If set to YES, the inheritance and collaboration graphs will hide\r
+# inheritance and usage relations if the target is undocumented\r
+# or is not a class.\r
+\r
+HIDE_UNDOC_RELATIONS = YES\r
+\r
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\r
+# available from the path. This tool is part of Graphviz, a graph visualization\r
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section\r
+# have no effect if this option is set to NO (the default)\r
+\r
+HAVE_DOT = NO\r
+\r
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is\r
+# allowed to run in parallel. When set to 0 (the default) doxygen will\r
+# base this on the number of processors available in the system. You can set it\r
+# explicitly to a value larger than 0 to get control over the balance\r
+# between CPU load and processing speed.\r
+\r
+DOT_NUM_THREADS = 0\r
+\r
+# By default doxygen will write a font called Helvetica to the output\r
+# directory and reference it in all dot files that doxygen generates.\r
+# When you want a differently looking font you can specify the font name\r
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,\r
+# which can be done by putting it in a standard location or by setting the\r
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory\r
+# containing the font.\r
+\r
+DOT_FONTNAME = FreeSans\r
+\r
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.\r
+# The default size is 10pt.\r
+\r
+DOT_FONTSIZE = 10\r
+\r
+# By default doxygen will tell dot to use the output directory to look for the\r
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a\r
+# different font using DOT_FONTNAME you can set the path where dot\r
+# can find it using this tag.\r
+\r
+DOT_FONTPATH =\r
+\r
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect inheritance relations. Setting this tag to YES will force the\r
+# the CLASS_DIAGRAMS tag to NO.\r
+\r
+CLASS_GRAPH = YES\r
+\r
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for each documented class showing the direct and\r
+# indirect implementation dependencies (inheritance, containment, and\r
+# class references variables) of the class with other documented classes.\r
+\r
+COLLABORATION_GRAPH = YES\r
+\r
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graph for groups, showing the direct groups dependencies\r
+\r
+GROUP_GRAPHS = YES\r
+\r
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and\r
+# collaboration diagrams in a style similar to the OMG's Unified Modeling\r
+# Language.\r
+\r
+UML_LOOK = NO\r
+\r
+# If set to YES, the inheritance and collaboration graphs will show the\r
+# relations between templates and their instances.\r
+\r
+TEMPLATE_RELATIONS = NO\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT\r
+# tags are set to YES then doxygen will generate a graph for each documented\r
+# file showing the direct and indirect include dependencies of the file with\r
+# other documented files.\r
+\r
+INCLUDE_GRAPH = YES\r
+\r
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and\r
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each\r
+# documented header file showing the documented files that directly or\r
+# indirectly include this file.\r
+\r
+INCLUDED_BY_GRAPH = YES\r
+\r
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then\r
+# doxygen will generate a call dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable call graphs\r
+# for selected functions only using the \callgraph command.\r
+\r
+CALL_GRAPH = NO\r
+\r
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then\r
+# doxygen will generate a caller dependency graph for every global function\r
+# or class method. Note that enabling this option will significantly increase\r
+# the time of a run. So in most cases it will be better to enable caller\r
+# graphs for selected functions only using the \callergraph command.\r
+\r
+CALLER_GRAPH = NO\r
+\r
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen\r
+# will generate a graphical hierarchy of all classes instead of a textual one.\r
+\r
+GRAPHICAL_HIERARCHY = YES\r
+\r
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES\r
+# then doxygen will show the dependencies a directory has on other directories\r
+# in a graphical way. The dependency relations are determined by the #include\r
+# relations between the files in the directories.\r
+\r
+DIRECTORY_GRAPH = YES\r
+\r
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\r
+# generated by dot. Possible values are svg, png, jpg, or gif.\r
+# If left blank png will be used.\r
+\r
+DOT_IMAGE_FORMAT = png\r
+\r
+# The tag DOT_PATH can be used to specify the path where the dot tool can be\r
+# found. If left blank, it is assumed the dot tool can be found in the path.\r
+\r
+DOT_PATH =\r
+\r
+# The DOTFILE_DIRS tag can be used to specify one or more directories that\r
+# contain dot files that are included in the documentation (see the\r
+# \dotfile command).\r
+\r
+DOTFILE_DIRS =\r
+\r
+# The MSCFILE_DIRS tag can be used to specify one or more directories that\r
+# contain msc files that are included in the documentation (see the\r
+# \mscfile command).\r
+\r
+MSCFILE_DIRS =\r
+\r
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of\r
+# nodes that will be shown in the graph. If the number of nodes in a graph\r
+# becomes larger than this value, doxygen will truncate the graph, which is\r
+# visualized by representing a node as a red box. Note that doxygen if the\r
+# number of direct children of the root node in a graph is already larger than\r
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note\r
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\r
+\r
+DOT_GRAPH_MAX_NODES = 50\r
+\r
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the\r
+# graphs generated by dot. A depth value of 3 means that only nodes reachable\r
+# from the root by following a path via at most 3 edges will be shown. Nodes\r
+# that lay further from the root node will be omitted. Note that setting this\r
+# option to 1 or 2 may greatly reduce the computation time needed for large\r
+# code bases. Also note that the size of a graph can be further restricted by\r
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.\r
+\r
+MAX_DOT_GRAPH_DEPTH = 0\r
+\r
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent\r
+# background. This is disabled by default, because dot on Windows does not\r
+# seem to support this out of the box. Warning: Depending on the platform used,\r
+# enabling this option may lead to badly anti-aliased labels on the edges of\r
+# a graph (i.e. they become hard to read).\r
+\r
+DOT_TRANSPARENT = NO\r
+\r
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output\r
+# files in one run (i.e. multiple -o and -T options on the command line). This\r
+# makes dot run faster, but since only newer versions of dot (>1.8.10)\r
+# support this, this feature is disabled by default.\r
+\r
+DOT_MULTI_TARGETS = NO\r
+\r
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will\r
+# generate a legend page explaining the meaning of the various boxes and\r
+# arrows in the dot generated graphs.\r
+\r
+GENERATE_LEGEND = YES\r
+\r
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will\r
+# remove the intermediate dot files that are used to generate\r
+# the various graphs.\r
+\r
+DOT_CLEANUP = YES\r
--- /dev/null
+Manifest-Version: 1.0\rBundle-ManifestVersion: 1\rBundle-Name: Tizen Native API Reference\rBundle-SymbolicName: org.tizen.native.apireference ;singleton="true"\rBundle-Version: 2.2.1\rBundle-Vendor: The Linux Foundation\r\r
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
+<meta http-equiv="X-UA-Compatible" content="IE=9"/>
+
+<title>Main Page</title>
+<link href="tabs.css" rel="stylesheet" type="text/css"/>
+<link href="Tizen.css" rel="stylesheet" type="text/css" />
+
+
+
+</head>
+<body>
+<div id="top"><!-- do not remove this div! -->
+
+
+<!-- Generated by Doxygen 1.7.4 -->
+ <div id="navrow1" class="tabs">
+ <ul class="tablist">
+ <li class="current"><a href="index.html"><span>Main Page</span></a></li>
+ <li><a href="pages.html"><span>Related Pages</span></a></li>
+ <li><a href="modules.html"><span>Libraries</span></a></li>
+ <li><a href="namespaces.html"><span>Namespaces</span></a></li>
+ <li><a href="annotated.html"><span>Classes</span></a></li>
+ <li><a href="files.html"><span>Files</span></a></li>
+ </ul>
+ </div>
+</div>
+<div class="header">
+ <div class="headertitle">
+<div class="title">Tizen native API Reference</div> </div>
+</div><!--header-->
+<div class="contents">
+<p>The Tizen native API Reference provides descriptions for all the Tizen C++ namespaces, classes, and methods. Tizen is the root namespace that
+ encompasses all other namespaces in the Tizen native framework.
+</p>
+<p>The following information is given for each namespace:</p>
+<ul>
+<li>Detailed description
+ <ul type="square">
+ <li>Required header file and libraries</li>
+ <li>Namespace description</li>
+ <li>Class diagram</li>
+ </ul>
+</li>
+ <li>Sub-namespaces (if they exist)</li>
+ <li>Variables and enumerations</li>
+</ul>
+<p>The following information is given for each class:</p>
+<ul>
+ <li>Inheritance diagram</li>
+ <li>Class description</li>
+ <li>Sub-classes (if they exist)</li>
+ <li>Member functions </li>
+ </ul>
+<p>The following subsections give information on how to use the Tizen native API Reference:</p>
+<ol>
+ <li><a href="#Structure">Structure of Method Descriptions</a></li>
+ <li><a href="#Use_API">Using an API</a></li>
+ <li><a href="#Use_Pre">Using a Privileged API</a></li>
+ <li><a href="#Use_Feature">Using a Featured API</a></li>
+ <!-- <li><a href="#SignIn">Using Sign-in</a></li> -->
+</ol>
+
+ <h3 id="Structure">Structure of Method Descriptions</h3>
+ <p>In the member functions documentation for each class, the methods are described using a unified structure, illustrated
+ in the below example.
+ </p>
+ <div class="memitem">
+ <div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">Tizen::Namespace::Class::Method ( type param1, type param2 )</td>
+ </tr>
+ </table>
+ </div>
+ <div class="memdoc">
+ <p>A brief description of the method.
+ <dl>
+ <dt><b>Since: </b></dt>
+ <dd>2.0</dd>
+ </dl>
+ <dl>
+ <dt><b>Compatibility : </b></dt>
+ <dd>Describes compatibility issues between different Tizen API versions.
+ </dd>
+ </dl>
+ <dl>
+ <dt><b>Privilege level:</b></dt>
+ <dd>Defines the privilege level (such as public) which is an access level for the APIs, based on their influence on the public, partner, or platform.</dd>
+ </dl>
+ <dl>
+ <dt><b>Privilege:</b></dt>
+ <dd>Defines the privilege (such as http://tizen.org/privilege/setting) that must be declared in the manifest file of an application that uses this method.</dd>
+ </dl>
+ <dl>
+ <dt><b>Precondition: </b></dt>
+ <dd>Describes restrictions about using this method.</dd>
+ </dl>
+ <dl class="return">
+ <dt><b>Returns:</b></dt>
+ <dd>Describes the return values.</dd>
+ </dl>
+ <dl>
+ <dt><b>Parameters: </b></dt>
+ <dd>
+ <table border="0" cellspacing="2" cellpadding="0">
+ <tr>
+ <td valign="top"><tt>[in]</tt> </td><td valign="top"><em>param1 </em> </td><td>Description of param1</td>
+ </tr>
+ </table>
+ </dd>
+ <dd>
+ <table border="0" cellspacing="2" cellpadding="0">
+ <tr>
+ <td valign="top"><tt>[out]</tt> </td><td valign="top"><em>param2</em> </td><td> Description of param2</td>
+ </tr>
+ </table>
+
+ </dd>
+ </dl>
+ <dl>
+ <dt><b>Exceptions: </b></dt>
+ <dd>
+ <table border="0" cellspacing="2" cellpadding="0">
+ <tr>
+ <td valign="top"></td><td valign="top"><em>EXCEPTION1</em> </td><td>Description of exception1.</td>
+ </tr>
+ </table>
+ </dd>
+
+ <dd>
+ <table border="0" cellspacing="2" cellpadding="0">
+ <tr>
+ <td valign="top"></td><td valign="top"><em>EXCEPTION2</em> </td><td>Description of exception2.</td>
+ </tr>
+ </table>
+ </dd>
+
+ </dl>
+ <dl class="remark">
+ <dt><b>Remarks: </b></dt>
+ <dd>Gives important information regarding the use of the method.<br>
+ For example: The specific error code can be accessed using the GetLastResult() method.</br>
+ </dd>
+ </dl>
+ <dl>
+ <dt><b>See also: </b></dt>
+ <dd>Gives links to other methods.
+ For example: Tizen::namespace::Class::Method()
+ </dd>
+ </dl>
+ </p>
+ </div>
+ </div>
+
+<p></p>
+ <h3 id="Use_API">Using an API</h3></li>
+ <p>To be able to use an API, you need to perform the following steps:</p>
+ <ol>
+ <p><li>Check the required header file.</li></p>
+ <p>To use a specific API in a project, include its header file. The required include files are listed under
+ <b>Remarks</b> in the Tizen native API Reference. For example, if an application uses the <span style="font-family: Courier New,Courier,monospace">Tizen::App::AppControl</span>
+ class, you must include <span style="font-family: Courier New,Courier,monospace">FApp.h</span> instead of <span style="font-family: Courier New,Courier,monospace">FAppAppControl.h</span> as shown under <b>Remarks</b> on the <b>Tizen::App</b> page.</p>
+ <p><center><img src="Intro_using_an_api.png" border="0" alt=""/></center></p>
+ <p><li>Add the required header file in the source code.</li></p>
+ <p>For example, to use the <span style="font-family: Courier New,Courier,monospace">Tizen::App::AppControl</span> class, you must include the <span style="font-family: Courier New,Courier,monospace">FApp.h</span> file in the source code as illustrated below.</p>
+ <p><center><img src="Intro_add_header_file.png" border="0" alt=""/></center></p>
+ <p><li>Add the required libraries and library search paths in the application properties.</li></p>
+ <p>In addition to the header file, it is also necessary to include the required libraries and their search paths in the application properties. The required libraries are listed under <b>Remarks</b> in the Tizen native API Reference.
+ <!--For more information, see the <a href="../com.osp.documentation.help/html/app_dev_process/adding_libraries_and_library_search_paths.htm">bada Developer Guide</a>.</p>-->
+ </ol>
+ <h3 id="Use_Pre">Using a Privileged API</h3></li>
+ <p>Some of the Tizen native APIs require privileges for security sensitive operations, and the privileges are categorized into three levels. When <b>Privilege level</b> and <b>Privilege</b> are included in a method description as shown below, declare the privilege and its level in the <span style="font-family: Courier New,Courier,monospace">manifest.xml</span> file. For more information, see <a href="../org.tizen.gettingstarted/html/tizen_overview/security.htm">Security Architecture</a>.</p>
+
+ <p><center><img src="Intro_using_a_privileged_api.png" border="0" alt=""/></center></p>
+ <!-- <p>Moreover, you must select <b>SOCKET</b> in <b>My Applications > Application Manager</b> on the bada developer site. </p>-->
+ <!-- <p><center><img src="Intro_privileged_api_group.png" border="0" alt=""/></center></p> -->
+
+ <h3 id="Use_Feature">Using a Featured API</h3></li>
+ <p>Some of the Tizen native APIs require features to prevent your application from being shown in the application list on the Tizen application store. When <b>Required feature</b> is included in a method description as shown below, declare the feature in the <span style="font-family: Courier New,Courier,monospace">manifest.xml</span> file. For more information, see <a href="../org.tizen.gettingstarted/html/tizen_overview/application_filtering.htm">Application Filtering</a>.</p>
+
+ <p><center><img src="Intro_using_a_featured_api.png" border="0" alt=""/></center></p>
+ <!-- <li><h3><a name="SignIn" id="SignIn">Using Sign-in</a></h3></li>
+ <p>An application can sign in to the bada Server using the sign-in application control. The sign in process includes user authentication. Therefore, the user of the application must have a user profile on the bada Server identified by a password.
+ The sign-in application control supports single sign-on, which means that the user needs to sign in only once and can also use other applications that access the bada Server without signing in again.
+ The authentication remains valid until the phone is shut down.</p>
+ <p>The precondition for using the sign-in application control in a method is given below.</p>
+
+ <div class="memitem">
+ <div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname"> </td>
+ </tr>
+ </table>
+ </div>
+ <div class="memdoc">
+ <p>
+ <dl>
+ <dt><b>Precondition: </b></dt>
+ <dd>User should be authenticated.<br>
+ For more information, see the sign-in application control (Tizen::App::APPCONTROL_PROVIDER_SIGNIN).</br></dd>
+ </dl>
+ </p>
+ </div>
+ </div>
+
+<p>The following code snippet illustrates how to use the sign-in application control:</p>
+<div class="fragment">
+<pre class="fragment">
+ <span class="keywordtype">void</span>
+ MyAppClass::AppControlSignInSample(<span class="keywordtype">void</span>)
+ {
+ ArrayList* pDataList = null;
+ AppControl* pAc = AppManager::FindAppControlN(<a class="code" href="namespaceOsp_1_1App.html#a801511da4f9e36a47a4d69fa32b44b6a">APPCONTROL_PROVIDER_SIGNIN</a>,
+ <a class="code" href="namespaceOsp_1_1App.html#adab037972f557473da236beff2bd1882">APPCONTROL_OPERATION_SIGNIN</a>);
+ <span class="keywordflow">if</span>(pAc)
+ {
+ pAc->Start(null, <span class="keyword">this</span>);
+ <span class="keyword">delete</span> pAc;
+ }
+ }
+ </pre>
+ </div>
+</ol>
+-->
+</div>
+
+<hr size="1"> </hr>
+<center>
+<small>Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a>
+and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>. </small>
+</center>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-15055292-3']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
+<title>Libraries</title>
+<link href="tabs.css" rel="stylesheet" type="text/css"/>
+<link href="Tizen.css" rel="stylesheet" type="text/css"/>
+</head>
+<body>
+<!-- Generated by Doxygen 1.7.4 -->
+<div id="top">
+ <div id="navrow1" class="tabs">
+ <ul class="tablist">
+ <li><a href="index.html"><span>Main Page</span></a></li>
+ <li><a href="pages.html"><span>Related Pages</span></a></li>
+ <li class="current"><a href="modules.html"><span>Libraries</span></a></li>
+ <li><a href="namespaces.html"><span>Namespaces</span></a></li>
+ <li><a href="annotated.html"><span>Classes</span></a></li>
+ <li><a href="files.html"><span>Files</span></a></li>
+ </ul>
+ </div>
+</div>
+<div class="header">
+ <div class="headertitle">
+<div class="title">Libraries</div> </div>
+</div>
+<div class="contents">
+<div class="textblock">Here is a list of all libraries:</div><ul>
+<li><a class="el" href="group__libxml2.html">Libxml2</a></li>
+<li><a class="el" href="group__libeglibc.html">Standard EGLIBC Library</a></li>
+<li><a class="el" href="group__Cplusplus.html">Standard C++ Library</a></li>
+<li><a class="el" href="group__openal.html">OpenAL®</a></li>
+<li><a class="el" href="group__opengl.html">OpenGL®</a></li>
+<li><a class="el" href="group__openmp.html">OpenMP®</a></li>
+</ul>
+</div>
+<hr size="1"> </hr>
+<center>
+<small>Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a>
+and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>. </small>
+</center>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-15055292-3']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
+<title>Tizen::Net::Wifi Namespace Reference</title>
+<link href="tabs.css" rel="stylesheet" type="text/css"/>
+<link href="Tizen.css" rel="stylesheet" type="text/css"/>
+</head>
+<body>
+<!-- Generated by Doxygen 1.7.4 -->
+<div id="top">
+ <div id="navrow1" class="tabs">
+ <ul class="tablist">
+ <li><a href="index.html"><span>Main Page</span></a></li>
+ <li><a href="pages.html"><span>Related Pages</span></a></li>
+ <li><a href="modules.html"><span>Libraries</span></a></li>
+ <li class="current"><a href="namespaces.html"><span>Namespaces</span></a></li>
+ <li><a href="annotated.html"><span>Classes</span></a></li>
+ <li><a href="files.html"><span>Files</span></a></li>
+ </ul>
+ </div>
+ <div id="navrow2" class="tabs2">
+ <ul class="tablist">
+ <li><a href="namespaces.html"><span>Namespace List</span></a></li>
+ <li><a href="namespacemembers.html"><span>Namespace Members</span></a></li>
+ </ul>
+ </div>
+ <div id="nav-path" class="navpath">
+ <ul>
+ <li class="navelem"><a class="el" href="namespaceTizen.html">Tizen</a> </li>
+ <li class="navelem"><a class="el" href="namespaceTizen_1_1Net.html">Net</a> </li>
+ <li class="navelem"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html">Wifi</a> </li>
+ </ul>
+ </div>
+</div>
+<div class="header">
+ <div class="summary">
+<a href="#nested-classes">Classes</a> |
+<a href="#typedef-members">Typedefs</a> |
+<a href="#enum-members">Enumerations</a> |
+<a href="#var-members">Variables</a> </div>
+ <div class="headertitle">
+<div class="title">Tizen::Net::Wifi Namespace Reference</div> </div>
+</div>
+<div class="contents">
+<a name="details" id="details"></a><h2> </h2>
+<div class="textblock"><dl class="since"><dt><b>Since:</b></dt><dd>2.0</dd></dl>
+<dl class="remark"><dt><b>Remarks:</b></dt><dd><b>Header</b> <b>file</b>: <b>#include</b> <b><<a class="el" href="FNet_8h.html" title="This is the header file for the Net namespace.">FNet.h</a>></b> <br/>
+ <b>Library</b> : <b>osp-wifi</b> <br/>
+</dd></dl>
+<p>The Net::Wifi namespace contains the classes and interfaces for Wi-Fi management and Wi-Fi Direct functionalities. It provides a rich set of methods to manage the Wi-Fi devices and accounts, and to communicate over a Wi-Fi channel. Additionally, the Wi-Fi Direct functionalities are provided to manage the Wi-Fi Direct device, create a Wi-Fi Direct group, scan Wi-Fi Direct devices, associate to a Wi-Fi Direct group owner, get the WifiDirectGroupOwner or the WifiDirectGroupClient instance, and allow the listener to get the events related to Wi-Fi Direct device and group.</p>
+<p>This namespace provides the Wi-Fi and Wi-Fi Direct functionalities. The Wi-Fi related operations are provided by classes like <a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiManager.html" title="This class provides methods for the local Wi-Fi device management.">WifiManager</a> and <a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiSecurityInfo.html" title="This class provides methods to manage the security information of a Wi-Fi network.">WifiSecurityInfo</a>. The Wi-Fi Direct related operations are provided by classes like <a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDevice.html" title="This class provides methods for the Wi-Fi Direct device.">WifiDirectDevice</a>.</p>
+<p>For more information on the Wifi namespace features, see <a href="../org.tizen.native.appprogramming/html/guide/net/wi-fi_connectivity.htm">Wi-Fi Connectivity</a> and <a href="../org.tizen.native.appprogramming/html/guide/net/wi-fi_direct_connectivity.htm">Wi-Fi Direct Connectivity</a>.</p>
+<p>The following diagram illustrates the relationships between the Wi-Fi classes belonging to the Wifi namespace. </p>
+<div class="image">
+<img src="net_wi-fi_using_the_apis_classdiagram.png" alt="net_wi-fi_using_the_apis_classdiagram.png"/>
+</div>
+<p>The following diagram illustrates the relationships between the Wi-Fi Direct classes belonging to the Wifi namespace. </p>
+<div class="image">
+<img src="net_wi-fi_direct_using_the_apis_classdiagram.png" alt="net_wi-fi_direct_using_the_apis_classdiagram.png"/>
+</div>
+ </div><table class="memberdecls">
+<tr><td colspan="2"><h2><a name="nested-classes"></a>
+Wi-Fi Classes</h2></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">interface  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1IWifiManagerEventListener.html">IWifiManagerEventListener</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This interface provides the listeners for <a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiManager.html" title="This class provides methods for the local Wi-Fi device management.">WifiManager</a> events. <a href="classTizen_1_1Net_1_1Wifi_1_1IWifiManagerEventListener.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">interface  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1IWifiSystemMonitoringEventListener.html">IWifiSystemMonitoringEventListener</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This interface provides the listeners for monitoring the Wi-Fi underlying system. <a href="classTizen_1_1Net_1_1Wifi_1_1IWifiSystemMonitoringEventListener.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiBssInfo.html">WifiBssInfo</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods for managing the BSS information of a Wi-Fi network. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiBssInfo.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiManager.html">WifiManager</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods for the local Wi-Fi device management. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiManager.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiNetAccountInfo.html">WifiNetAccountInfo</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides the functionality to control the WLAN network accounts. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiNetAccountInfo.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiSecurityInfo.html">WifiSecurityInfo</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods to manage the security information of a Wi-Fi network. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiSecurityInfo.html#details">More...</a><br/></td></tr>
+<tr><td colspan="2"><h2><a name="nested-classes"></a>
+Wi-Fi Direct Classes</h2></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">interface  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1IWifiDirectDeviceListener.html">IWifiDirectDeviceListener</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This interface implements listeners for the <a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDevice.html" title="This class provides methods for the Wi-Fi Direct device.">WifiDirectDevice</a> events. <a href="classTizen_1_1Net_1_1Wifi_1_1IWifiDirectDeviceListener.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDevice.html">WifiDirectDevice</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods for the Wi-Fi Direct device. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDevice.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDeviceInfo.html">WifiDirectDeviceInfo</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods for the Wi-Fi Direct device information. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDeviceInfo.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDeviceManager.html">WifiDirectDeviceManager</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods for the Wi-Fi Direct device management. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectDeviceManager.html#details">More...</a><br/></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">class  </td><td class="memItemRight" valign="bottom"><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectGroupInfo.html">WifiDirectGroupInfo</a></td></tr>
+<tr><td class="mdescLeft"> </td><td class="mdescRight">This class provides methods for the Wi-Fi Direct group information. <a href="classTizen_1_1Net_1_1Wifi_1_1WifiDirectGroupInfo.html#details">More...</a><br/></td></tr>
+<tr><td colspan="2"><h2><a name="typedef-members"></a>
+Typedefs</h2></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">typedef int </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a9d218cd982dda27bd7b4727327b60404">WifiDirectDeviceId</a></td></tr>
+<tr><td colspan="2"><h2><a name="enum-members"></a>
+Enumerations</h2></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeb">WifiAuthenticationType</a> { <br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beebaff29206ce4c71a89954b994b694e3ca0">WIFI_AUTHENTICATION_OPEN</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beebac32439d24cebea9fcfa008e82d928281">WIFI_AUTHENTICATION_SHARED</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeba1068b91d07a91936f97f053ba660e7a4">WIFI_AUTHENTICATION_WPA</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeba1d85c99153ce60840a29de8f96ef2321">WIFI_AUTHENTICATION_WPA_PSK</a>,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeba027079a509ac266e8a8e21af8a27f98a">WIFI_AUTHENTICATION_WPA2</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeba403c42c358790741a9237d3dc73d7693">WIFI_AUTHENTICATION_WPA2_PSK</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeba8b3cc87e3d61e5d096fedd54e6ca2c2a">WIFI_AUTHENTICATION_WPA_WPA2_MIXED_PSK</a>
+<br/>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#aad52b065bd137bf6879e51b46e2dbb5b">WifiBssType</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#aad52b065bd137bf6879e51b46e2dbb5ba4a87d242b28dd801c532e88524fbb8ec">WIFI_BSS_TYPE_INFRASTRUCTURE</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#aad52b065bd137bf6879e51b46e2dbb5ba6e0f8498b87b447b1fb45a35bac9d560">WIFI_BSS_TYPE_INDEPENDENT</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#aad52b065bd137bf6879e51b46e2dbb5ba68bd209d7e0581657371cc066dd98a86">WIFI_BSS_TYPE_ANY</a>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7ef219e48b5f35ef7731f384c4c5c0cf">WifiConnectionState</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7ef219e48b5f35ef7731f384c4c5c0cfacb8da7b0abe9416f0b47994e68285ea4">WIFI_CONN_STATE_NOT_CONNECTED</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7ef219e48b5f35ef7731f384c4c5c0cfade1c004e43faac4087812a324ff0a35c">WIFI_CONN_STATE_ASSOCIATING</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7ef219e48b5f35ef7731f384c4c5c0cfab14eb166d2b653d86e7adb2edc441d5c">WIFI_CONN_STATE_CONFIGURING</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7ef219e48b5f35ef7731f384c4c5c0cfa487ba57127be1c099f1bfe27a1b2f3f0">WIFI_CONN_STATE_CONNECTED</a>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a919f1763ad68a2ffa7e0177eb6108b2a">WifiDirectDeviceStatus</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a919f1763ad68a2ffa7e0177eb6108b2aa421f25ba86ee1c0aaa14c95d6cba46e6">WIFI_DIRECT_DEVICE_DEACTIVATED</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a919f1763ad68a2ffa7e0177eb6108b2aa67b7c8581edfaafc64a3e717d09f955a">WIFI_DIRECT_DEVICE_ACTIVATED</a>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417f">WifiDirectDeviceTypeCategory</a> { <br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa12e303a574f0e5d8d917db7288562b1c">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_COMPUTER</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa6e1e1ba3d53f57029a4705a1f65c3753">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_INPUT_DEVICE</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa3b05b8a848a7d29be9032a98f40f9dee">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_PRINTER_SCANNER_FAX_COPIER</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa20a96aedf2ee3cf233c0c32f18e3d84d">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_CAMERA</a>,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa8a137e4f79c97d48d4a3765f7b44c932">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_STORAGE</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa47d5631c691a0eb482ee76d973d53c1f">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_NETWORK_INFRASTRUCTURE</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417faef6284601c5b7014a0abc6220ae4eade">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_DISPLAY</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa0c29a9ac9fd93eb0e1b3f3adaca26f71">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_MULTIMEDIA_DEVICE</a>,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417facc7b1bfbdcd343a5f831223243a53831">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_GAMING_DEVICE</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa06351d252b4c12dc6296111ef546da67">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_TELEPHONE</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fab54edcf9fdba772414d2a3458beb4935">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_AUDIO_DEVICE</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417fa6b216339232fa21518c4170af830a259">WIFI_DIRECT_DEVICE_TYPE_CATEGORY_OTHERS</a> = 255
+<br/>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a50db3cab1ca1450dddfb3445ca3298f8">WifiDirectGroupMemberType</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a50db3cab1ca1450dddfb3445ca3298f8a064e076b801077eaed467825e8697672">WIFI_DIRECT_GROUP_MEMBER_TYPE_NONE</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a50db3cab1ca1450dddfb3445ca3298f8a9c85046c4bf3d647c3f5353b58a0a486">WIFI_DIRECT_GROUP_MEMBER_TYPE_OWNER</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a50db3cab1ca1450dddfb3445ca3298f8ab81e6a31d1398e620d7dfa7d4fc5f2aa">WIFI_DIRECT_GROUP_MEMBER_TYPE_CLIENT</a>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3">WifiEapType</a> { <br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3a57aa80ee0c0b6ba94c9bf2e050515e71">WIFI_EAP_NONE</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3a3ad20b5064707fd0262bb919c1d16ef9">WIFI_EAP_SIM</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3a455a24b48383e17544dbc1d95f23247e">WIFI_EAP_AKA</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3ac61f90e178b30d78a2069fb11f33b1fd">WIFI_EAP_TTLS_MSCHAPV2</a>,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3ad2a446b586d0d21ccd20116d3c9cadcc">WIFI_EAP_PEAP_MSCHAPV2</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3a57c069e28105e138bd8a9571939791d4">WIFI_EAP_PEAP_GTC</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3a9ebc212a135b663d0396f8f537bebfb2">WIFI_EAP_TLS</a>
+<br/>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367ea">WifiEncryptionType</a> { <br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367eaaa96837ea85ceb6b6a52b46078ac2c5da">WIFI_ENCRYPTION_NONE</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367eaa0599e9744b3c104ff7f5e525b992e3e7">WIFI_ENCRYPTION_WEP</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367eaa1f978559bcedb4e3edbb382f3c91827f">WIFI_ENCRYPTION_TKIP</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367eaa8d19d83e2cafa50cb665c47a90746185">WIFI_ENCRYPTION_AES</a>,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367eaa7c9781031a56b11b6f2644c000342b72">WIFI_ENCRYPTION_TKIP_AES_MIXED</a>
+<br/>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7a41dda7c615025d7453371ab4962939">WifiPowerStatus</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7a41dda7c615025d7453371ab4962939abc35fabe4419edbb926ebf54d36a2dcf">WIFI_POWER_STATUS_OFF</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7a41dda7c615025d7453371ab4962939aff8f33b33f2ef8eabee0c0bd089620a5">WIFI_POWER_STATUS_ON</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7a41dda7c615025d7453371ab4962939a76f5c87d7341273f0d96a4b718a8d905">WIFI_POWER_STATUS_DEEP_SLEEP</a>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bba">WifiRadioChannel</a> { <br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa5fe6bb8adb608266de31bb551b2f3e50">WIFI_RADIO_CHANNEL_1</a> = 1,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa0e07adabfa29aa76bf4526ca9c493b86">WIFI_RADIO_CHANNEL_2</a> = 2,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaad42d111b555964e216b070a0a6e17117">WIFI_RADIO_CHANNEL_3</a> = 4,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaaacb28d4580151e0caf5e57f28c61ce8e">WIFI_RADIO_CHANNEL_4</a> = 8,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaad228a7ec67dde96261c606522cbe0130">WIFI_RADIO_CHANNEL_5</a> = 16,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa2226c81b8fa6342d836965431bd74871">WIFI_RADIO_CHANNEL_6</a> = 32,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaad119c81c58da01eb415fdf64863a627e">WIFI_RADIO_CHANNEL_7</a> = 64,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa8773df4997093865e024abce518fbfa4">WIFI_RADIO_CHANNEL_8</a> = 128,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa153a249217b2c7679f7fe8b3066aba76">WIFI_RADIO_CHANNEL_9</a> = 256,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa5c0ba8cc440bf1ccd1d6c04fb2117690">WIFI_RADIO_CHANNEL_10</a> = 512,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa48e1d4d7259c6da0cfc70280da65c263">WIFI_RADIO_CHANNEL_11</a> = 1024,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa87ff32f62f94fd2fae20575ecdbb8468">WIFI_RADIO_CHANNEL_12</a> = 2048,
+<br/>
+  <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaa529c28657bba9896c32d932783bdb69c">WIFI_RADIO_CHANNEL_13</a> = 4096,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bbaac244309002df3be8fe773eca08a4f4e0">WIFI_RADIO_CHANNEL_14</a> = 8192
+<br/>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a973ab104af6700ad0cfd12b8a187160a">WifiSystemScanMode</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a973ab104af6700ad0cfd12b8a187160aadef71332347c3a04afe252810b2a172d">WIFI_SYSTEM_SCAN_MODE_ACTIVE</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a973ab104af6700ad0cfd12b8a187160aa0d4f6ae736da875cc1dfe28377628fac">WIFI_SYSTEM_SCAN_MODE_PASSIVE</a>
+ }</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">enum  </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4db6527f42ae930a10f43e8f886e4d9c">WifiWpsConfigurationMode</a> { <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4db6527f42ae930a10f43e8f886e4d9ca71eee5d7034246ee8a30d40b772211be">WIFI_WPS_CONFIG_MODE_NONE</a> = 0,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4db6527f42ae930a10f43e8f886e4d9cad7d891519e554b612bd681c10274647d">WIFI_WPS_CONFIG_MODE_PIN_DISPLAY</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4db6527f42ae930a10f43e8f886e4d9cad2c8930fda9c31cfe2f07be341a306a1">WIFI_WPS_CONFIG_MODE_PIN_KEYPAD</a>,
+<a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4db6527f42ae930a10f43e8f886e4d9ca0480cc48b7fb4a25d881aa3bea6eb5e8">WIFI_WPS_CONFIG_MODE_PBC</a>
+ }</td></tr>
+<tr><td colspan="2"><h2><a name="var-members"></a>
+Variables</h2></td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">static const int </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a92f8f2a828eac61fd7fa980a27c82a6c">MAX_WIFI_DIRECT_CONNECTED_CLIENTS</a> = 8</td></tr>
+<tr><td class="memItemLeft" align="right" valign="top">static const int </td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a70bec40531f1569ac02c6d7bbe95afea">MAX_WIFI_DIRECT_GROUP_OWNER_INTENT</a> = 15</td></tr>
+</table>
+<hr/><h2>Typedef Documentation</h2>
+<a class="anchor" id="a9d218cd982dda27bd7b4727327b60404"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiDirectDeviceId" ref="a9d218cd982dda27bd7b4727327b60404" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">typedef int <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a9d218cd982dda27bd7b4727327b60404">Tizen::Net::Wifi::WifiDirectDeviceId</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>The Wi-Fi Direct Device ID.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+
+</div>
+</div>
+<hr/><h2>Enumeration Type Documentation</h2>
+<a class="anchor" id="a0636415048a4a3620112b6ab6dd9beeb"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiAuthenticationType" ref="a0636415048a4a3620112b6ab6dd9beeb" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a0636415048a4a3620112b6ab6dd9beeb">Tizen::Net::Wifi::WifiAuthenticationType</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines IEEE 802.11 authentication. <br/>
+ IEEE 802.11 authentication operates at the link level between IEEE 802.11 stations (STAs). IEEE 802.11 does not provide end-to-end (message origin to message destination) or user-to-user authentication.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beebaff29206ce4c71a89954b994b694e3ca0"></a><!-- doxytag: member="WIFI_AUTHENTICATION_OPEN" ref="a0636415048a4a3620112b6ab6dd9beebaff29206ce4c71a89954b994b694e3ca0" args="" -->WIFI_AUTHENTICATION_OPEN</em> </td><td>
+<p>The Open System Authentication that admits any STA to the DS </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beebac32439d24cebea9fcfa008e82d928281"></a><!-- doxytag: member="WIFI_AUTHENTICATION_SHARED" ref="a0636415048a4a3620112b6ab6dd9beebac32439d24cebea9fcfa008e82d928281" args="" -->WIFI_AUTHENTICATION_SHARED</em> </td><td>
+<p>The Shared Key Authentication relies on the WEP to demonstrate knowledge of a WEP encryption key </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beeba1068b91d07a91936f97f053ba660e7a4"></a><!-- doxytag: member="WIFI_AUTHENTICATION_WPA" ref="a0636415048a4a3620112b6ab6dd9beeba1068b91d07a91936f97f053ba660e7a4" args="" -->WIFI_AUTHENTICATION_WPA</em> </td><td>
+<p>The Enterprise Authentication that supports WPA (Wi-Fi Protected Access) </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beeba1d85c99153ce60840a29de8f96ef2321"></a><!-- doxytag: member="WIFI_AUTHENTICATION_WPA_PSK" ref="a0636415048a4a3620112b6ab6dd9beeba1d85c99153ce60840a29de8f96ef2321" args="" -->WIFI_AUTHENTICATION_WPA_PSK</em> </td><td>
+<p>The Personal Authentication that supports WPA; PSK stands for PreShared Key </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beeba027079a509ac266e8a8e21af8a27f98a"></a><!-- doxytag: member="WIFI_AUTHENTICATION_WPA2" ref="a0636415048a4a3620112b6ab6dd9beeba027079a509ac266e8a8e21af8a27f98a" args="" -->WIFI_AUTHENTICATION_WPA2</em> </td><td>
+<p>The Enterprise Authentication that supports WPA2 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beeba403c42c358790741a9237d3dc73d7693"></a><!-- doxytag: member="WIFI_AUTHENTICATION_WPA2_PSK" ref="a0636415048a4a3620112b6ab6dd9beeba403c42c358790741a9237d3dc73d7693" args="" -->WIFI_AUTHENTICATION_WPA2_PSK</em> </td><td>
+<p>The Personal Authentication that supports WPA2; PSK stands for PreShared Key </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a0636415048a4a3620112b6ab6dd9beeba8b3cc87e3d61e5d096fedd54e6ca2c2a"></a><!-- doxytag: member="WIFI_AUTHENTICATION_WPA_WPA2_MIXED_PSK" ref="a0636415048a4a3620112b6ab6dd9beeba8b3cc87e3d61e5d096fedd54e6ca2c2a" args="" -->WIFI_AUTHENTICATION_WPA_WPA2_MIXED_PSK</em> </td><td>
+<p>The Personal Authentication that supports both WPA and WPA2; PSK stands for PreShared Key </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="aad52b065bd137bf6879e51b46e2dbb5b"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiBssType" ref="aad52b065bd137bf6879e51b46e2dbb5b" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#aad52b065bd137bf6879e51b46e2dbb5b">Tizen::Net::Wifi::WifiBssType</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the type of Basic Service Set (BSS).</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="aad52b065bd137bf6879e51b46e2dbb5ba4a87d242b28dd801c532e88524fbb8ec"></a><!-- doxytag: member="WIFI_BSS_TYPE_INFRASTRUCTURE" ref="aad52b065bd137bf6879e51b46e2dbb5ba4a87d242b28dd801c532e88524fbb8ec" args="" -->WIFI_BSS_TYPE_INFRASTRUCTURE</em> </td><td>
+<p>The infrastructure type which usually consists of a single Access Point (AP) <br/>
+ However, in order to provide sufficient coverage, it could be necessary to use two or more APs. <br/>
+ Logically, there needs to be an interconnection among APs, and this concept is called Distribution System (DS). <br/>
+ Connecting with multiple APs through DS creates a wireless network of an arbitrary size. <br/>
+ This is called Extended Service Set (ESS). Finally, a logical connection point to the wired LAN is supported by a concept designated as Portal. </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="aad52b065bd137bf6879e51b46e2dbb5ba6e0f8498b87b447b1fb45a35bac9d560"></a><!-- doxytag: member="WIFI_BSS_TYPE_INDEPENDENT" ref="aad52b065bd137bf6879e51b46e2dbb5ba6e0f8498b87b447b1fb45a35bac9d560" args="" -->WIFI_BSS_TYPE_INDEPENDENT</em> </td><td>
+<p>The simplest Wi-Fi configuration is called as Independent Basic Service Set (IBSS) or ad hoc <br/>
+ The IBSS is a self-contained network that only supports direct communication between Stations (STAs) that belong to the same BSS. <br/>
+ The most common example of this connection is the use of Wi-Fi to establish peer-to-peer network connection between two STAs. </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="aad52b065bd137bf6879e51b46e2dbb5ba68bd209d7e0581657371cc066dd98a86"></a><!-- doxytag: member="WIFI_BSS_TYPE_ANY" ref="aad52b065bd137bf6879e51b46e2dbb5ba68bd209d7e0581657371cc066dd98a86" args="" -->WIFI_BSS_TYPE_ANY</em> </td><td>
+<p>The type with no specification </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a7ef219e48b5f35ef7731f384c4c5c0cf"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiConnectionState" ref="a7ef219e48b5f35ef7731f384c4c5c0cf" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7ef219e48b5f35ef7731f384c4c5c0cf">Tizen::Net::Wifi::WifiConnectionState</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the state of the Wi-Fi connection.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a7ef219e48b5f35ef7731f384c4c5c0cfacb8da7b0abe9416f0b47994e68285ea4"></a><!-- doxytag: member="WIFI_CONN_STATE_NOT_CONNECTED" ref="a7ef219e48b5f35ef7731f384c4c5c0cfacb8da7b0abe9416f0b47994e68285ea4" args="" -->WIFI_CONN_STATE_NOT_CONNECTED</em> </td><td>
+<p>The local device is not connected </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7ef219e48b5f35ef7731f384c4c5c0cfade1c004e43faac4087812a324ff0a35c"></a><!-- doxytag: member="WIFI_CONN_STATE_ASSOCIATING" ref="a7ef219e48b5f35ef7731f384c4c5c0cfade1c004e43faac4087812a324ff0a35c" args="" -->WIFI_CONN_STATE_ASSOCIATING</em> </td><td>
+<p>The local device is associating with an AP </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7ef219e48b5f35ef7731f384c4c5c0cfab14eb166d2b653d86e7adb2edc441d5c"></a><!-- doxytag: member="WIFI_CONN_STATE_CONFIGURING" ref="a7ef219e48b5f35ef7731f384c4c5c0cfab14eb166d2b653d86e7adb2edc441d5c" args="" -->WIFI_CONN_STATE_CONFIGURING</em> </td><td>
+<p>The local device is configuring after association </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7ef219e48b5f35ef7731f384c4c5c0cfa487ba57127be1c099f1bfe27a1b2f3f0"></a><!-- doxytag: member="WIFI_CONN_STATE_CONNECTED" ref="a7ef219e48b5f35ef7731f384c4c5c0cfa487ba57127be1c099f1bfe27a1b2f3f0" args="" -->WIFI_CONN_STATE_CONNECTED</em> </td><td>
+<p>The local device is completely connected after configuration </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a919f1763ad68a2ffa7e0177eb6108b2a"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiDirectDeviceStatus" ref="a919f1763ad68a2ffa7e0177eb6108b2a" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a919f1763ad68a2ffa7e0177eb6108b2a">Tizen::Net::Wifi::WifiDirectDeviceStatus</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the status of a Wi-Fi Direct device.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a919f1763ad68a2ffa7e0177eb6108b2aa421f25ba86ee1c0aaa14c95d6cba46e6"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_DEACTIVATED" ref="a919f1763ad68a2ffa7e0177eb6108b2aa421f25ba86ee1c0aaa14c95d6cba46e6" args="" -->WIFI_DIRECT_DEVICE_DEACTIVATED</em> </td><td>
+<p>The Wi-Fi interface is deactivated </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a919f1763ad68a2ffa7e0177eb6108b2aa67b7c8581edfaafc64a3e717d09f955a"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_ACTIVATED" ref="a919f1763ad68a2ffa7e0177eb6108b2aa67b7c8581edfaafc64a3e717d09f955a" args="" -->WIFI_DIRECT_DEVICE_ACTIVATED</em> </td><td>
+<p>The Wi-Fi interface is activated </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417f"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiDirectDeviceTypeCategory" ref="a91f99ce0acd12b14ce04fa1728da417f" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a91f99ce0acd12b14ce04fa1728da417f">Tizen::Net::Wifi::WifiDirectDeviceTypeCategory</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the category of the Wi-Fi Direct device type.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa12e303a574f0e5d8d917db7288562b1c"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_COMPUTER" ref="a91f99ce0acd12b14ce04fa1728da417fa12e303a574f0e5d8d917db7288562b1c" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_COMPUTER</em> </td><td>
+<p>The PC, Server, Media Center, UMPC, Notebook, Desktop, MID, Netbook, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa6e1e1ba3d53f57029a4705a1f65c3753"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_INPUT_DEVICE" ref="a91f99ce0acd12b14ce04fa1728da417fa6e1e1ba3d53f57029a4705a1f65c3753" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_INPUT_DEVICE</em> </td><td>
+<p>The Keyboard, Mouse, Joystick, Trackball, Gaming controller, Remote, Touchscreen, Biometric reader, Barcode reader, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa3b05b8a848a7d29be9032a98f40f9dee"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_PRINTER_SCANNER_FAX_COPIER" ref="a91f99ce0acd12b14ce04fa1728da417fa3b05b8a848a7d29be9032a98f40f9dee" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_PRINTER_SCANNER_FAX_COPIER</em> </td><td>
+<p>The Printer, Print Server, Scanner, Fax, Copier, All-in-one, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa20a96aedf2ee3cf233c0c32f18e3d84d"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_CAMERA" ref="a91f99ce0acd12b14ce04fa1728da417fa20a96aedf2ee3cf233c0c32f18e3d84d" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_CAMERA</em> </td><td>
+<p>The Digital still camera, Video camera, Web camera, Security camera, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa8a137e4f79c97d48d4a3765f7b44c932"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_STORAGE" ref="a91f99ce0acd12b14ce04fa1728da417fa8a137e4f79c97d48d4a3765f7b44c932" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_STORAGE</em> </td><td>
+<p>The NAS </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa47d5631c691a0eb482ee76d973d53c1f"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_NETWORK_INFRASTRUCTURE" ref="a91f99ce0acd12b14ce04fa1728da417fa47d5631c691a0eb482ee76d973d53c1f" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_NETWORK_INFRASTRUCTURE</em> </td><td>
+<p>The AP, Router, Switch, Gateway, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417faef6284601c5b7014a0abc6220ae4eade"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_DISPLAY" ref="a91f99ce0acd12b14ce04fa1728da417faef6284601c5b7014a0abc6220ae4eade" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_DISPLAY</em> </td><td>
+<p>The Television, Electronic picture frame, Projector, Monitor, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa0c29a9ac9fd93eb0e1b3f3adaca26f71"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_MULTIMEDIA_DEVICE" ref="a91f99ce0acd12b14ce04fa1728da417fa0c29a9ac9fd93eb0e1b3f3adaca26f71" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_MULTIMEDIA_DEVICE</em> </td><td>
+<p>The DAR, PVR, MCX, Set-top box, Media server, Media adapter, Media extender, Portable video player, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417facc7b1bfbdcd343a5f831223243a53831"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_GAMING_DEVICE" ref="a91f99ce0acd12b14ce04fa1728da417facc7b1bfbdcd343a5f831223243a53831" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_GAMING_DEVICE</em> </td><td>
+<p>The Xbox, Playstation, Game console, Game console adaptor, Portable gaming device, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa06351d252b4c12dc6296111ef546da67"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_TELEPHONE" ref="a91f99ce0acd12b14ce04fa1728da417fa06351d252b4c12dc6296111ef546da67" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_TELEPHONE</em> </td><td>
+<p>The Windows Mobile, Phone, Smartphone, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fab54edcf9fdba772414d2a3458beb4935"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_AUDIO_DEVICE" ref="a91f99ce0acd12b14ce04fa1728da417fab54edcf9fdba772414d2a3458beb4935" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_AUDIO_DEVICE</em> </td><td>
+<p>The Audio tuner, Audio receiver, Speaker, Portable Music Player, Headset, Headphone, Microphone, and so on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a91f99ce0acd12b14ce04fa1728da417fa6b216339232fa21518c4170af830a259"></a><!-- doxytag: member="WIFI_DIRECT_DEVICE_TYPE_CATEGORY_OTHERS" ref="a91f99ce0acd12b14ce04fa1728da417fa6b216339232fa21518c4170af830a259" args="" -->WIFI_DIRECT_DEVICE_TYPE_CATEGORY_OTHERS</em> </td><td>
+<p>A device which is not classified into the above types </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a50db3cab1ca1450dddfb3445ca3298f8"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiDirectGroupMemberType" ref="a50db3cab1ca1450dddfb3445ca3298f8" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a50db3cab1ca1450dddfb3445ca3298f8">Tizen::Net::Wifi::WifiDirectGroupMemberType</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the type of a Wi-Fi Direct device.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a50db3cab1ca1450dddfb3445ca3298f8a064e076b801077eaed467825e8697672"></a><!-- doxytag: member="WIFI_DIRECT_GROUP_MEMBER_TYPE_NONE" ref="a50db3cab1ca1450dddfb3445ca3298f8a064e076b801077eaed467825e8697672" args="" -->WIFI_DIRECT_GROUP_MEMBER_TYPE_NONE</em> </td><td>
+<p>The Wi-Fi Direct Group Non-member <br/>
+ That is, the device does not belong to any group. </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a50db3cab1ca1450dddfb3445ca3298f8a9c85046c4bf3d647c3f5353b58a0a486"></a><!-- doxytag: member="WIFI_DIRECT_GROUP_MEMBER_TYPE_OWNER" ref="a50db3cab1ca1450dddfb3445ca3298f8a9c85046c4bf3d647c3f5353b58a0a486" args="" -->WIFI_DIRECT_GROUP_MEMBER_TYPE_OWNER</em> </td><td>
+<p>The Wi-Fi Direct Group Owner </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a50db3cab1ca1450dddfb3445ca3298f8ab81e6a31d1398e620d7dfa7d4fc5f2aa"></a><!-- doxytag: member="WIFI_DIRECT_GROUP_MEMBER_TYPE_CLIENT" ref="a50db3cab1ca1450dddfb3445ca3298f8ab81e6a31d1398e620d7dfa7d4fc5f2aa" args="" -->WIFI_DIRECT_GROUP_MEMBER_TYPE_CLIENT</em> </td><td>
+<p>The Wi-Fi Direct Group Client </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiEapType" ref="af2a74c05bd2786eeacf7601b593d1eb3" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#af2a74c05bd2786eeacf7601b593d1eb3">Tizen::Net::Wifi::WifiEapType</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the Extensible Authentication Protocol (EAP) method types that provide a specific authentication mechanism.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3a57aa80ee0c0b6ba94c9bf2e050515e71"></a><!-- doxytag: member="WIFI_EAP_NONE" ref="af2a74c05bd2786eeacf7601b593d1eb3a57aa80ee0c0b6ba94c9bf2e050515e71" args="" -->WIFI_EAP_NONE</em> </td><td>
+<p>The method type where no EAP method is used </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3a3ad20b5064707fd0262bb919c1d16ef9"></a><!-- doxytag: member="WIFI_EAP_SIM" ref="af2a74c05bd2786eeacf7601b593d1eb3a3ad20b5064707fd0262bb919c1d16ef9" args="" -->WIFI_EAP_SIM</em> </td><td>
+<p>The EAP-SIM; EAP for GSM Subscriber Identity </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3a455a24b48383e17544dbc1d95f23247e"></a><!-- doxytag: member="WIFI_EAP_AKA" ref="af2a74c05bd2786eeacf7601b593d1eb3a455a24b48383e17544dbc1d95f23247e" args="" -->WIFI_EAP_AKA</em> </td><td>
+<p>The EAP-AKA; EAP for UMTS Authentication and Key Agreement </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3ac61f90e178b30d78a2069fb11f33b1fd"></a><!-- doxytag: member="WIFI_EAP_TTLS_MSCHAPV2" ref="af2a74c05bd2786eeacf7601b593d1eb3ac61f90e178b30d78a2069fb11f33b1fd" args="" -->WIFI_EAP_TTLS_MSCHAPV2</em> </td><td>
+<p>The EAP-TTLS/MSCHAPv2; Tunnel MSCHAPv2 through TTLS(Tunneled Transport Layer Security) </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3ad2a446b586d0d21ccd20116d3c9cadcc"></a><!-- doxytag: member="WIFI_EAP_PEAP_MSCHAPV2" ref="af2a74c05bd2786eeacf7601b593d1eb3ad2a446b586d0d21ccd20116d3c9cadcc" args="" -->WIFI_EAP_PEAP_MSCHAPV2</em> </td><td>
+<p>The PEAPv0/EAP-MSCHAPv2; Tunnel MSCHAPv2 through PEAP(Protected Extensible Authentication Protocol) </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3a57c069e28105e138bd8a9571939791d4"></a><!-- doxytag: member="WIFI_EAP_PEAP_GTC" ref="af2a74c05bd2786eeacf7601b593d1eb3a57c069e28105e138bd8a9571939791d4" args="" -->WIFI_EAP_PEAP_GTC</em> </td><td>
+<p>The PEAPv1/EAP-GTC; Tunnel GTC through PEAP(Protected Extensible Authentication Protocol) </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="af2a74c05bd2786eeacf7601b593d1eb3a9ebc212a135b663d0396f8f537bebfb2"></a><!-- doxytag: member="WIFI_EAP_TLS" ref="af2a74c05bd2786eeacf7601b593d1eb3a9ebc212a135b663d0396f8f537bebfb2" args="" -->WIFI_EAP_TLS</em> </td><td>
+<p>The EAP-TLS, Not supported yet </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a7b23506205f2f92368c2c064694367ea"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiEncryptionType" ref="a7b23506205f2f92368c2c064694367ea" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7b23506205f2f92368c2c064694367ea">Tizen::Net::Wifi::WifiEncryptionType</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the IEEE 802.11 encryption that provides the data confidentiality aspects of a closed wired media.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a7b23506205f2f92368c2c064694367eaaa96837ea85ceb6b6a52b46078ac2c5da"></a><!-- doxytag: member="WIFI_ENCRYPTION_NONE" ref="a7b23506205f2f92368c2c064694367eaaa96837ea85ceb6b6a52b46078ac2c5da" args="" -->WIFI_ENCRYPTION_NONE</em> </td><td>
+<p>The type with no encryption </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7b23506205f2f92368c2c064694367eaa0599e9744b3c104ff7f5e525b992e3e7"></a><!-- doxytag: member="WIFI_ENCRYPTION_WEP" ref="a7b23506205f2f92368c2c064694367eaa0599e9744b3c104ff7f5e525b992e3e7" args="" -->WIFI_ENCRYPTION_WEP</em> </td><td>
+<p>The Wired Equivalent Privacy <br/>
+ This is only used for open and shared methods. </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7b23506205f2f92368c2c064694367eaa1f978559bcedb4e3edbb382f3c91827f"></a><!-- doxytag: member="WIFI_ENCRYPTION_TKIP" ref="a7b23506205f2f92368c2c064694367eaa1f978559bcedb4e3edbb382f3c91827f" args="" -->WIFI_ENCRYPTION_TKIP</em> </td><td>
+<p>The Temporal Key Integrity Protocol </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7b23506205f2f92368c2c064694367eaa8d19d83e2cafa50cb665c47a90746185"></a><!-- doxytag: member="WIFI_ENCRYPTION_AES" ref="a7b23506205f2f92368c2c064694367eaa8d19d83e2cafa50cb665c47a90746185" args="" -->WIFI_ENCRYPTION_AES</em> </td><td>
+<p>The Advanced Encryption Standard </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7b23506205f2f92368c2c064694367eaa7c9781031a56b11b6f2644c000342b72"></a><!-- doxytag: member="WIFI_ENCRYPTION_TKIP_AES_MIXED" ref="a7b23506205f2f92368c2c064694367eaa7c9781031a56b11b6f2644c000342b72" args="" -->WIFI_ENCRYPTION_TKIP_AES_MIXED</em> </td><td>
+<p>The TKIP and AES are both supported </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a7a41dda7c615025d7453371ab4962939"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiPowerStatus" ref="a7a41dda7c615025d7453371ab4962939" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a7a41dda7c615025d7453371ab4962939">Tizen::Net::Wifi::WifiPowerStatus</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the power status of the local Wi-Fi device.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl class="see"><dt><b>See also:</b></dt><dd><a class="el" href="classTizen_1_1Net_1_1Wifi_1_1WifiManager.html#adccf44db7cc01121d1f1edd23d4f3a87">WifiManager::GetPowerStatus()</a> </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a7a41dda7c615025d7453371ab4962939abc35fabe4419edbb926ebf54d36a2dcf"></a><!-- doxytag: member="WIFI_POWER_STATUS_OFF" ref="a7a41dda7c615025d7453371ab4962939abc35fabe4419edbb926ebf54d36a2dcf" args="" -->WIFI_POWER_STATUS_OFF</em> </td><td>
+<p>The local Wi-Fi device is turned off </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7a41dda7c615025d7453371ab4962939aff8f33b33f2ef8eabee0c0bd089620a5"></a><!-- doxytag: member="WIFI_POWER_STATUS_ON" ref="a7a41dda7c615025d7453371ab4962939aff8f33b33f2ef8eabee0c0bd089620a5" args="" -->WIFI_POWER_STATUS_ON</em> </td><td>
+<p>The local Wi-Fi device is turned on </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a7a41dda7c615025d7453371ab4962939a76f5c87d7341273f0d96a4b718a8d905"></a><!-- doxytag: member="WIFI_POWER_STATUS_DEEP_SLEEP" ref="a7a41dda7c615025d7453371ab4962939a76f5c87d7341273f0d96a4b718a8d905" args="" -->WIFI_POWER_STATUS_DEEP_SLEEP</em> </td><td>
+<p>The local Wi-Fi device enters deep sleep mode </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a4560e0756cabe8519a32123d01c25bba"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiRadioChannel" ref="a4560e0756cabe8519a32123d01c25bba" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4560e0756cabe8519a32123d01c25bba">Tizen::Net::Wifi::WifiRadioChannel</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the BSS radio channel.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa5fe6bb8adb608266de31bb551b2f3e50"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_1" ref="a4560e0756cabe8519a32123d01c25bbaa5fe6bb8adb608266de31bb551b2f3e50" args="" -->WIFI_RADIO_CHANNEL_1</em> </td><td>
+<p>The Radio Channel 1 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa0e07adabfa29aa76bf4526ca9c493b86"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_2" ref="a4560e0756cabe8519a32123d01c25bbaa0e07adabfa29aa76bf4526ca9c493b86" args="" -->WIFI_RADIO_CHANNEL_2</em> </td><td>
+<p>The Radio Channel 2 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaad42d111b555964e216b070a0a6e17117"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_3" ref="a4560e0756cabe8519a32123d01c25bbaad42d111b555964e216b070a0a6e17117" args="" -->WIFI_RADIO_CHANNEL_3</em> </td><td>
+<p>The Radio Channel 3 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaaacb28d4580151e0caf5e57f28c61ce8e"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_4" ref="a4560e0756cabe8519a32123d01c25bbaaacb28d4580151e0caf5e57f28c61ce8e" args="" -->WIFI_RADIO_CHANNEL_4</em> </td><td>
+<p>The Radio Channel 4 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaad228a7ec67dde96261c606522cbe0130"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_5" ref="a4560e0756cabe8519a32123d01c25bbaad228a7ec67dde96261c606522cbe0130" args="" -->WIFI_RADIO_CHANNEL_5</em> </td><td>
+<p>The Radio Channel 5 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa2226c81b8fa6342d836965431bd74871"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_6" ref="a4560e0756cabe8519a32123d01c25bbaa2226c81b8fa6342d836965431bd74871" args="" -->WIFI_RADIO_CHANNEL_6</em> </td><td>
+<p>The Radio Channel 6 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaad119c81c58da01eb415fdf64863a627e"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_7" ref="a4560e0756cabe8519a32123d01c25bbaad119c81c58da01eb415fdf64863a627e" args="" -->WIFI_RADIO_CHANNEL_7</em> </td><td>
+<p>The Radio Channel 7 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa8773df4997093865e024abce518fbfa4"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_8" ref="a4560e0756cabe8519a32123d01c25bbaa8773df4997093865e024abce518fbfa4" args="" -->WIFI_RADIO_CHANNEL_8</em> </td><td>
+<p>The Radio Channel 8 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa153a249217b2c7679f7fe8b3066aba76"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_9" ref="a4560e0756cabe8519a32123d01c25bbaa153a249217b2c7679f7fe8b3066aba76" args="" -->WIFI_RADIO_CHANNEL_9</em> </td><td>
+<p>The Radio Channel 9 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa5c0ba8cc440bf1ccd1d6c04fb2117690"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_10" ref="a4560e0756cabe8519a32123d01c25bbaa5c0ba8cc440bf1ccd1d6c04fb2117690" args="" -->WIFI_RADIO_CHANNEL_10</em> </td><td>
+<p>The Radio Channel 10 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa48e1d4d7259c6da0cfc70280da65c263"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_11" ref="a4560e0756cabe8519a32123d01c25bbaa48e1d4d7259c6da0cfc70280da65c263" args="" -->WIFI_RADIO_CHANNEL_11</em> </td><td>
+<p>The Radio Channel 11 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa87ff32f62f94fd2fae20575ecdbb8468"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_12" ref="a4560e0756cabe8519a32123d01c25bbaa87ff32f62f94fd2fae20575ecdbb8468" args="" -->WIFI_RADIO_CHANNEL_12</em> </td><td>
+<p>The Radio Channel 12 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaa529c28657bba9896c32d932783bdb69c"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_13" ref="a4560e0756cabe8519a32123d01c25bbaa529c28657bba9896c32d932783bdb69c" args="" -->WIFI_RADIO_CHANNEL_13</em> </td><td>
+<p>The Radio Channel 13 </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4560e0756cabe8519a32123d01c25bbaac244309002df3be8fe773eca08a4f4e0"></a><!-- doxytag: member="WIFI_RADIO_CHANNEL_14" ref="a4560e0756cabe8519a32123d01c25bbaac244309002df3be8fe773eca08a4f4e0" args="" -->WIFI_RADIO_CHANNEL_14</em> </td><td>
+<p>The Radio Channel 14 </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a973ab104af6700ad0cfd12b8a187160a"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiSystemScanMode" ref="a973ab104af6700ad0cfd12b8a187160a" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a973ab104af6700ad0cfd12b8a187160a">Tizen::Net::Wifi::WifiSystemScanMode</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the mode of the Wi-Fi background system behaviors, mainly about background scanning.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a973ab104af6700ad0cfd12b8a187160aadef71332347c3a04afe252810b2a172d"></a><!-- doxytag: member="WIFI_SYSTEM_SCAN_MODE_ACTIVE" ref="a973ab104af6700ad0cfd12b8a187160aadef71332347c3a04afe252810b2a172d" args="" -->WIFI_SYSTEM_SCAN_MODE_ACTIVE</em> </td><td>
+<p>The background scanning is performed with the short and fixed time interval (10 seconds) during which the Wi-Fi connection is not established <br/>
+ The Wi-Fi target picker popup for connection is not launched when Wi-Fi is turned on. <br/>
+ Generally, this mode is for the case that the Wi-Fi setting app is running on foreground. </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a973ab104af6700ad0cfd12b8a187160aa0d4f6ae736da875cc1dfe28377628fac"></a><!-- doxytag: member="WIFI_SYSTEM_SCAN_MODE_PASSIVE" ref="a973ab104af6700ad0cfd12b8a187160aa0d4f6ae736da875cc1dfe28377628fac" args="" -->WIFI_SYSTEM_SCAN_MODE_PASSIVE</em> </td><td>
+<p>The background scanning is performed with the exponential backoff time interval (8, 16, ..., and finally 128 seconds) during which the Wi-Fi connection is not established <br/>
+ The Wi-Fi target picker popup for connection is launched when Wi-Fi is turned on. <br/>
+ Generally, this mode is for the both cases that the Wi-Fi setting app is running on background and terminated. </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<a class="anchor" id="a4db6527f42ae930a10f43e8f886e4d9c"></a><!-- doxytag: member="Tizen::Net::Wifi::WifiWpsConfigurationMode" ref="a4db6527f42ae930a10f43e8f886e4d9c" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">enum <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a4db6527f42ae930a10f43e8f886e4d9c">Tizen::Net::Wifi::WifiWpsConfigurationMode</a></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>Defines the configuration method for the Wi-Fi Protected Setup (WPS).</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+<dl><dt><b>Enumerator: </b></dt><dd><table border="0" cellspacing="2" cellpadding="0">
+<tr><td valign="top"><em><a class="anchor" id="a4db6527f42ae930a10f43e8f886e4d9ca71eee5d7034246ee8a30d40b772211be"></a><!-- doxytag: member="WIFI_WPS_CONFIG_MODE_NONE" ref="a4db6527f42ae930a10f43e8f886e4d9ca71eee5d7034246ee8a30d40b772211be" args="" -->WIFI_WPS_CONFIG_MODE_NONE</em> </td><td>
+<p>The configuration mode with no method to be provided </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4db6527f42ae930a10f43e8f886e4d9cad7d891519e554b612bd681c10274647d"></a><!-- doxytag: member="WIFI_WPS_CONFIG_MODE_PIN_DISPLAY" ref="a4db6527f42ae930a10f43e8f886e4d9cad7d891519e554b612bd681c10274647d" args="" -->WIFI_WPS_CONFIG_MODE_PIN_DISPLAY</em> </td><td>
+<p>A method to display the PIN code </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4db6527f42ae930a10f43e8f886e4d9cad2c8930fda9c31cfe2f07be341a306a1"></a><!-- doxytag: member="WIFI_WPS_CONFIG_MODE_PIN_KEYPAD" ref="a4db6527f42ae930a10f43e8f886e4d9cad2c8930fda9c31cfe2f07be341a306a1" args="" -->WIFI_WPS_CONFIG_MODE_PIN_KEYPAD</em> </td><td>
+<p>A method to provide the keypad to input the PIN </p>
+</td></tr>
+<tr><td valign="top"><em><a class="anchor" id="a4db6527f42ae930a10f43e8f886e4d9ca0480cc48b7fb4a25d881aa3bea6eb5e8"></a><!-- doxytag: member="WIFI_WPS_CONFIG_MODE_PBC" ref="a4db6527f42ae930a10f43e8f886e4d9ca0480cc48b7fb4a25d881aa3bea6eb5e8" args="" -->WIFI_WPS_CONFIG_MODE_PBC</em> </td><td>
+<p>A method of Push Button Configuration (PBC) </p>
+</td></tr>
+</table>
+</dd>
+</dl>
+
+</div>
+</div>
+<hr/><h2>Variable Documentation</h2>
+<a class="anchor" id="a92f8f2a828eac61fd7fa980a27c82a6c"></a><!-- doxytag: member="Tizen::Net::Wifi::MAX_WIFI_DIRECT_CONNECTED_CLIENTS" ref="a92f8f2a828eac61fd7fa980a27c82a6c" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">const int <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a92f8f2a828eac61fd7fa980a27c82a6c">Tizen::Net::Wifi::MAX_WIFI_DIRECT_CONNECTED_CLIENTS</a> = 8<code> [static]</code></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>The maximum number of associated clients.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+
+</div>
+</div>
+<a class="anchor" id="a70bec40531f1569ac02c6d7bbe95afea"></a><!-- doxytag: member="Tizen::Net::Wifi::MAX_WIFI_DIRECT_GROUP_OWNER_INTENT" ref="a70bec40531f1569ac02c6d7bbe95afea" args="" -->
+<div class="memitem">
+<div class="memproto">
+ <table class="memname">
+ <tr>
+ <td class="memname">const int <a class="el" href="namespaceTizen_1_1Net_1_1Wifi.html#a70bec40531f1569ac02c6d7bbe95afea">Tizen::Net::Wifi::MAX_WIFI_DIRECT_GROUP_OWNER_INTENT</a> = 15<code> [static]</code></td>
+ </tr>
+ </table>
+</div>
+<div class="memdoc">
+<p>The maximum number of group owners intent for negotiation.</p>
+<dl class="since"><dt><b>Since:</b></dt><dd>2.0 </dd></dl>
+
+</div>
+</div>
+</div>
+<hr size="1"> </hr>
+<center>
+<small>Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a>
+and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>. </small>
+</center>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-15055292-3']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+</html>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
+<meta http-equiv="X-UA-Compatible" content="IE=9"/>
+
+<title>Related Pages</title>
+<link href="tabs.css" rel="stylesheet" type="text/css"/>
+<link href="Tizen.css" rel="stylesheet" type="text/css" />
+
+
+
+</head>
+<body>
+<div id="top"><!-- do not remove this div! -->
+
+
+<!-- Generated by Doxygen 1.7.4 -->
+ <div id="navrow1" class="tabs">
+ <ul class="tablist">
+ <li><a href="index.html"><span>Main Page</span></a></li>
+ <li class="current"><a href="pages.html"><span>Related Pages</span></a></li>
+ <li><a href="modules.html"><span>Libraries</span></a></li>
+ <li><a href="namespaces.html"><span>Namespaces</span></a></li>
+ <li><a href="annotated.html"><span>Classes</span></a></li>
+ <li><a href="files.html"><span>Files</span></a></li>
+ </ul>
+ </div>
+</div>
+<div class="header">
+ <div class="headertitle">
+<div class="title">Related Pages</div> </div>
+</div><!--header-->
+<div class="contents">
+<div class="textblock">Here is a list of all related documentation pages:</div>
+<ul>
+<li><a class="el" href="compatibility.html">Compatibility</a>
+</li>
+<li><a class="el" href="deprecated.html">Deprecated List</a>
+</li>
+<li><a class="el" href="privilegeintro.html">Privilege</a>
+ <ul type="tablist">
+ <li><a class="el" href="privlevel.html">Privilege Level</a></li>
+ <li><a class="el" href="privilege.html">Privilege</a></li>
+ </ul>
+</li>
+<li><a class="el" href="feature.html">Required Feature</a>
+</li>
+</ul>
+</div><!-- contents -->
+<hr size="1"> </hr>
+<center>
+<small>Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a>
+and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>. </small>
+</center>
+
+<script type="text/javascript">
+var _gaq = _gaq || [];
+_gaq.push(['_setAccount', 'UA-15055292-3']);
+_gaq.push(['_trackPageview']);
+(function() {
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+})();
+</script>
+
+</body>
+</html>
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>\r
+<?eclipse version="3.4"?>\r
+<plugin>\r
+ <extension point="org.eclipse.help.toc">\r
+ <toc file="toc.xml" primary="true" />\r
+ </extension>\r
+</plugin>\r
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<html>\r
+<head>\r
+<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>\r
+<meta http-equiv="X-UA-Compatible" content="IE=9"/>\r
+\r
+<title>Privilege Pages</title>\r
+<link href="tabs.css" rel="stylesheet" type="text/css"/>\r
+<link href="Tizen.css" rel="stylesheet" type="text/css" />\r
+\r
+\r
+\r
+</head>\r
+<body>\r
+<div id="top"><!-- do not remove this div! -->\r
+\r
+\r
+<!-- Generated by Doxygen 1.7.4 -->\r
+ <div id="navrow1" class="tabs">\r
+ <ul class="tablist">\r
+ <li><a href="index.html"><span>Main Page</span></a></li>\r
+ <li class="current"><a href="pages.html"><span>Related Pages</span></a></li>\r
+ <li><a href="modules.html"><span>Libraries</span></a></li>\r
+ <li><a href="namespaces.html"><span>Namespaces</span></a></li>\r
+ <li><a href="annotated.html"><span>Classes</span></a></li>\r
+ <li><a href="files.html"><span>Files</span></a></li>\r
+ </ul>\r
+ </div>\r
+</div>\r
+<div class="header">\r
+ <div class="headertitle">\r
+<div class="title">Privilege Pages</div> </div>\r
+</div>\r
+<div class="contents">\r
+An API that handles platform and user-sensitive data has privacy, \r
+security, and stability implications.\r
+\r
+<p> Following are the descriptions for privilege level and privilege: </p>\r
+<ul>\r
+<li><a class="el" href="privlevel.html">Privilege Level</a> </li>\r
+ <p> A defined access level for the APIs, based on their influence on the public, partner, or platform. </p>\r
+<li><a class="el" href="privilege.html">Privilege</a> </li>\r
+ <p> A predefined collection of privileged APIs that can be assigned to the application to allow it to call the privileged APIs. </p>\r
+</ul>\r
+</div>\r
+\r
+<hr size="1"> </hr>\r
+<center>\r
+<small>Except as noted, this content - excluding the Code Examples - is licensed under <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank">Creative Commons Attribution 3.0</a>\r
+and all of the Code Examples contained herein are licensed under <a href="https://www.tizen.org/bsd-3-clause-license" target="_blank">BSD-3-Clause</a>.<br>For details, see the <a href="https://www.tizen.org/content-license" target="_blank">Content License</a>. </small>\r
+</center>\r
+\r
+<script type="text/javascript">\r
+var _gaq = _gaq || [];\r
+_gaq.push(['_setAccount', 'UA-15055292-3']);\r
+_gaq.push(['_trackPageview']);\r
+(function() {\r
+var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;\r
+ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';\r
+var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);\r
+})();\r
+</script>\r
+\r
+</body>\r
+</html>\r
--- /dev/null
+
+#script.pl -i ./annotation ../org.tizen.native.apireference/ -d ./work -o ./output
+
+$DEBUG_LEVEL = 0;
+
+sub debug
+{
+ my ($line) = shift;
+ if ($DEBUG_LEVEL >= 3)
+ {
+ print $line;
+ print "\n";
+ }
+}
+
+sub logwrite
+{
+ my ($line) = shift;
+ print $line . "\n";
+}
+
+my $INPUT_FILE;
+my $WORK_DIR;
+my $BASICOBJECT_DIR;
+my $BASICOBJECTLINK_DIR = "";
+my $OUTPUT_DIR;
+my $TEMP_DIR = "temp";
+
+my @annoObj;
+
+#------------------------------------------------------------------------------
+# arguments parsing
+#------------------------------------------------------------------------------
+while ($ARG=shift)
+{
+ debug("arg:$ARG");
+ if ($ARG =~ m/^-i/)
+ {
+ $BASICOBJECT_DIR = shift;
+ $INPUT_FILE = $BASICOBJECT_DIR . "/" . "annotated.html";
+ $BASICOBJECTLINK_DIR = shift;
+ debug ("INPUT_FILE:$INPUT_FILE");
+ }
+ elsif ($ARG =~ m/^-d/)
+ {
+ $WORK_DIR = shift;
+ debug ("WORK_DIR:$WORK_DIR");
+ }
+# elsif ($ARG =~ m/^-bod/)
+# {
+# $BASICOBJECT_DIR = shift;
+# debug ("BASICOBJECT_DIR:$BASICOBJECT_DIR");
+# }
+# elsif ($ARG =~ m/^-ln/)
+# {
+# $BASICOBJECTLINK_DIR = shift;
+# debug ("BASICOBJECTLINK_DIR:$BASICOBJECTLINK_DIR");
+# }
+ elsif ($ARG =~ m/^-o/)
+ {
+ $OUTPUT_DIR = shift;
+ debug ("OUTPUT_DIR:$OUTPUT_DIR");
+ }
+}
+
+if($BASICOBJECTLINK_DIR eq "")
+{
+ $BASICOBJECTLINK_DIR = $BASICOBJECT_DIR;
+}
+
+if($OUTPUT_DIR eq "")
+{
+ $OUTPUT_DIR = $WORK_DIR;
+}
+
+#------------------------------------------------------------------------------
+# arguments check
+#------------------------------------------------------------------------------
+if (-f $INPUT_FILE)
+{
+}
+else
+{
+ print "file not found ($INPUT_FILE)";
+}
+
+if (-d $WORK_DIR)
+{
+}
+else
+{
+ print STDERR "directory not found ($WORK_DIR)\n";
+ die;
+}
+
+if (-d $BASICOBJECT_DIR)
+{
+}
+else
+{
+ print STDERR "directory not found ($BASICOBJECT_DIR)\n";
+}
+
+#------------------------------------------------------------------------------
+# temp copy
+#------------------------------------------------------------------------------
+mkdir $TEMP_DIR, 0755 || die "can't create temp directory";
+
+opendir DH, $WORK_DIR or die "Couldn't open the current directory : $WORK_DIR";
+while($_ = readdir(DH))
+{
+ next if $_ =~ /^\.\.?$/;
+ #if ($_ =~ m/^class/)
+ if ($_ =~ m/html$/)
+ {
+ next if $_ =~ /classes.html/;
+ next if $_ =~ /index.html/;
+ debug($_);
+
+ open(FILEHDL, $WORK_DIR . "/" . $_) || die ("Error d'ouverture de $_");
+ open (OUTPUT_FH, '>', $TEMP_DIR . "/" . $_) or die "Could not open $_";
+ while ($line = <FILEHDL>)
+ {
+ print OUTPUT_FH $line;
+ }
+ close (OUTPUT_FH);
+ close (FILEHDL);
+ }
+}
+closedir DH;
+
+
+#------------------------------------------------------------------------------
+# html parse
+#------------------------------------------------------------------------------
+
+if (open(FILEHDL, $INPUT_FILE))
+{
+ while ($line = <FILEHDL>)
+ {
+ if ($line =~ m/<a .+href=\"([a-zA-Z0-9\._]+)\">([^<]+)<\/a>/)
+ {
+ #<a class="el" href="classOsp_1_1App_1_1AppManager.html">Osp::App::AppManager</a>
+ my $tmp = ObjectItem->new($2, $1);
+ push(@annoObj, $tmp);
+
+ #file check
+ if (-f $BASICOBJECT_DIR . "/" . $tmp->{html})
+ {
+ }
+ else
+ {
+ logwrite("file not found : " . $BASICOBJECT_DIR . "/" . $tmp->{html} );
+ }
+ }
+ }
+ close (FILEHDL);
+}
+
+
+#------------------------------------------------------------------------------
+# work
+#------------------------------------------------------------------------------
+opendir DH, $TEMP_DIR or die "Couldn't open the current directory : $TEMP_DIR";
+while($_ = readdir(DH))
+{
+ next if $_ =~ /^\.\.?$/;
+ #if ($_ =~ m/^class/)
+ if ($_ =~ m/html$/)
+ {
+ #next if $_ =~ /classes.html/;
+ local $/ = undef;
+ open(FILEHDL, $TEMP_DIR . "/" . $_) || die ("Error d'ouverture de $_");
+ $allLines = <FILEHDL>;
+ close (FILEHDL);
+
+ my $filename = $_;
+
+ #my $pre;
+ #if($allLines =~ m/(<pre[\S\s]+<\/pre>)/)
+ #{
+ # $pre = $1;
+ #}
+
+ #$allLines =~ s/<pre[\S\s]+<\/pre>/@@@@/;
+
+ foreach(@annoObj)
+ {
+ my $tag = "<a href=\"" . $BASICOBJECTLINK_DIR . $_->{html}. "\" class=\"public_api\">" . $_->{objname} . "</a>";
+ my $keyword = "\\b" . $_->{objname} . "\\b";
+
+ #print $tag . "\n";
+
+ if($allLines =~ m/$keyword/)
+ {
+ #logwrite("[" . $filename . "] " . $_->{objname} . " : " . $_->{html});
+ }
+
+ $allLines =~ s/$keyword/$tag/g;
+
+ #print $_->{objname} . "\n";
+ }
+
+ #$allLines =~ s/@@@@/$pre/;
+
+ open (OUTPUT_FH, '>', $TEMP_DIR . "/" . $_) or die "Could not open $_";
+ print OUTPUT_FH $allLines;
+ }
+
+ close (OUTPUT_FH);
+ #print $allLines;
+}
+closedir DH;
+
+
+#------------------------------------------------------------------------------
+# finally temp copy
+#------------------------------------------------------------------------------
+mkdir $OUTPUT_DIR, 0755 || die "can't create temp directory";
+
+opendir DH, $TEMP_DIR or die "Couldn't open the current directory : $TEMP_DIR";
+while($_ = readdir(DH))
+{
+ next if $_ =~ /^\.\.?$/;
+ #if ($_ =~ m/^class/)
+ if ($_ =~ m/html$/)
+ {
+ open(FILEHDL, $TEMP_DIR . "/" . $_) || die ("Error d'ouverture de $_");
+ open (OUTPUT_FH, '>', $OUTPUT_DIR . "/" . $_) or die "Could not open $_";
+ while ($line = <FILEHDL>)
+ {
+ print OUTPUT_FH $line;
+ }
+ close (OUTPUT_FH);
+ close (FILEHDL);
+ }
+}
+closedir DH;
+
+
+#------------------------------------------------------------------------------
+# temp delete
+#------------------------------------------------------------------------------
+opendir DH, $TEMP_DIR or die "Couldn't open the current directory : $TEMP_DIR";
+while($_ = readdir(DH))
+{
+ next if $_ =~ /^\.\.?$/;
+ #unlink $TEMP_DIR . "/" . $_;
+}
+closedir DH;
+#rmdir $TEMP_DIR;
+
+
+
+
+#------------------------------------------------------------------------------
+# ObjectItem
+#------------------------------------------------------------------------------
+
+package ObjectItem;
+
+sub new {
+ my ($class, $objname, $html) = @_;
+
+ my $self = {objname => $objname, html => $html };
+
+ bless $self, $class;
+
+ return $self;
+}
--- /dev/null
+#!/usr/bin/perl\r
+#------------------------------------------------------------------------------\r
+# Tizen_Feature.pl -i ./ -o ./output -d ./feature_desc.txt\r
+#------------------------------------------------------------------------------\r
+\r
+\r
+#------------------------------------------------------------------------------\r
+# Global Data declaration\r
+#------------------------------------------------------------------------------\r
+$DEBUG_LEVEL = 0;\r
+$INPUTDIR = "";\r
+$OUTPUTDIR = "";\r
+$DESCFILE = "";\r
+my @listFeature = ();\r
+my @listOthers = ();\r
+\r
+my @groupdesc = ();\r
+\r
+sub debug\r
+{\r
+ my ($line) = shift;\r
+ if ($DEBUG_LEVEL >= 3)\r
+ {\r
+ print $line;\r
+ print "\n";\r
+ }\r
+}\r
+\r
+sub trim {\r
+ my @result = @_;\r
+\r
+ foreach (@result) {\r
+ s/^\s+//; \r
+ s/\s+$//; \r
+ }\r
+\r
+ return wantarray ? @result : $result[0];\r
+}\r
+\r
+sub zero_fill\r
+{\r
+ my $pad_len = $_[1];\r
+ my $padded = sprintf("%0${pad_len}d", $_[0]);\r
+ return $padded;\r
+}\r
+\r
+sub getKeyFeature {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+ my $inter = $_[2];\r
+\r
+ foreach (@$arr) {\r
+ if($_->{privilege} eq $keyname) {\r
+ return $_;\r
+ }\r
+ }\r
+\r
+ my $ng = new node($keyname);\r
+ push(@$arr, $ng); # addkey\r
+\r
+ return $ng;\r
+}\r
+\r
+sub getgroupdesc {\r
+ if($DESCFILE eq "") {\r
+ $DESCFILE = "feature_desc.txt";\r
+ }\r
+\r
+ open FILE, $DESCFILE;\r
+ my @lines = <FILE>;\r
+ close FILE;\r
+\r
+ my $name = "";\r
+ my $desc = "";\r
+\r
+ foreach(@lines) {\r
+ if(trim($name) eq "") {\r
+ $name = trim($_);\r
+ } elsif(trim($_) eq "") {\r
+ my $gd = new groupdesc($name, trim($desc));\r
+ push(@groupdesc, $gd);\r
+\r
+ $name = "";\r
+ $desc = "";\r
+ } else {\r
+ if(trim($desc) eq "") {\r
+ $desc = $_;\r
+ } else {\r
+ $desc .= $_ . "<br/>";\r
+ }\r
+ }\r
+ }\r
+}\r
+\r
+sub addkey {\r
+ my $arr = $_[0];\r
+ push(@$arr, $_[1]);\r
+}\r
+\r
+sub containskey {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ if($_->{$variable} eq $keyname) {\r
+ return 1;\r
+ }\r
+ }\r
+\r
+ return 0;\r
+}\r
+\r
+sub creathtmltop {\r
+ my $html = "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">" . "\n"\r
+ . "<html><head>" . "\n"\r
+ . "<meta http-equiv=\"Content-Type\" content=\"text/xhtml;charset=UTF-8\"/>" . "\n"\r
+ . "<title>$_[0]</title>" . "\n"\r
+ . "<link href=\"tabs.css\" rel=\"stylesheet\" type=\"text/css\"/>" . "\n"\r
+ . "<link href=\"Tizen.css\" rel=\"stylesheet\" type=\"text/css\"/>" . "\n"\r
+ . " <style type=\"text/css\">" . "\n"\r
+ . " <!--" . "\n"\r
+ . "body, table, div, p, dl {" . "\n"\r
+ . " font-family: Lucida Grande, Verdana, Geneva, Arial, sans-serif;" . "\n"\r
+ . " font-size: 12px;" . "\n"\r
+ . "}" . "\n"\r
+ . "a {" . "\n"\r
+ . " color: #3D578C;" . "\n"\r
+ . " font-weight: normal;" . "\n"\r
+ . " text-decoration: none;" . "\n"\r
+ . "}" . "\n"\r
+ . ".contents a:visited {" . "\n"\r
+ . " color: #4665A2;" . "\n"\r
+ . "}" . "\n"\r
+ . "a:hover {" . "\n"\r
+ . " text-decoration: underline;" . "\n"\r
+ . "}" . "\n"\r
+ . "a.el {" . "\n"\r
+ . " font-weight: bold;" . "\n"\r
+ . "}" . "\n"\r
+ . ".title {" . "\n"\r
+ . " font-size: 150%;" . "\n"\r
+ . " font-weight: bold;" . "\n"\r
+ . " margin: 10px 2px;" . "\n"\r
+ . "}" . "\n"\r
+ . "h2 {" . "\n"\r
+ . " font-size: 120%;" . "\n"\r
+ . "}" . "\n"\r
+ . "h3 {" . "\n"\r
+ . " font-size: 100%;" . "\n"\r
+ . "}" . "\n"\r
+ . ".memitem {" . "\n"\r
+ . " padding: 0;" . "\n"\r
+ . " margin-bottom: 10px;" . "\n"\r
+ . " margin-right: 5px;" . "\n"\r
+ . "}" . "\n"\r
+ . "" . "\n"\r
+ . ".memname {" . "\n"\r
+ . " white-space: nowrap;" . "\n"\r
+ . " font-weight: bold;" . "\n"\r
+ . " margin-left: 6px;" . "\n"\r
+ . "}" . "\n"\r
+ . "" . "\n"\r
+ . ".memproto {" . "\n"\r
+ . " border-top: 1px solid #A8B8D9;" . "\n"\r
+ . " border-left: 1px solid #A8B8D9;" . "\n"\r
+ . " border-right: 1px solid #A8B8D9;" . "\n"\r
+ . " padding: 6px 0px 6px 0px;" . "\n"\r
+ . " color: #253555;" . "\n"\r
+ . " font-weight: bold;" . "\n"\r
+ . " text-shadow: 0px 1px 1px rgba(255, 255, 255, 0.9);" . "\n"\r
+ . " /* opera specific markup */" . "\n"\r
+ . " box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);" . "\n"\r
+ . " border-top-right-radius: 8px;" . "\n"\r
+ . " border-top-left-radius: 8px;" . "\n"\r
+ . " /* firefox specific markup */" . "\n"\r
+ . " -moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;" . "\n"\r
+ . " -moz-border-radius-topright: 8px;" . "\n"\r
+ . " -moz-border-radius-topleft: 8px;" . "\n"\r
+ . " /* webkit specific markup */" . "\n"\r
+ . " -webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);" . "\n"\r
+ . " -webkit-border-top-right-radius: 8px;" . "\n"\r
+ . " -webkit-border-top-left-radius: 8px;" . "\n"\r
+ . " background-image:url('nav_f.png');" . "\n"\r
+ . " background-repeat:repeat-x;" . "\n"\r
+ . " background-color: #E2E8F2;" . "\n"\r
+ . "" . "\n"\r
+ . "}" . "\n"\r
+ . "" . "\n"\r
+ . ".memdoc {" . "\n"\r
+ . " border-bottom: 1px solid #A8B8D9; " . "\n"\r
+ . " border-left: 1px solid #A8B8D9; " . "\n"\r
+ . " border-right: 1px solid #A8B8D9; " . "\n"\r
+ . " padding: 2px 5px;" . "\n"\r
+ . " background-color: #FBFCFD;" . "\n"\r
+ . " border-top-width: 0;" . "\n"\r
+ . " /* opera specific markup */" . "\n"\r
+ . " border-bottom-left-radius: 8px;" . "\n"\r
+ . " border-bottom-right-radius: 8px;" . "\n"\r
+ . " box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);" . "\n"\r
+ . " /* firefox specific markup */" . "\n"\r
+ . " -moz-border-radius-bottomleft: 8px;" . "\n"\r
+ . " -moz-border-radius-bottomright: 8px;" . "\n"\r
+ . " -moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;" . "\n"\r
+ . " background-image: -moz-linear-gradient(center top, #FFFFFF 0%, #FFFFFF 60%, #F7F8FB 95%, #EEF1F7);" . "\n"\r
+ . " /* webkit specific markup */" . "\n"\r
+ . " -webkit-border-bottom-left-radius: 8px;" . "\n"\r
+ . " -webkit-border-bottom-right-radius: 8px;" . "\n"\r
+ . " -webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);" . "\n"\r
+ . " 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));" . "\n"\r
+ . "}" . "\n"\r
+ . "//-->" . "\n"\r
+ . " </style>" . "\n"\r
+ . "" . "\n"\r
+ . "</head>" . "\n"\r
+ . "<body>" . "\n"\r
+ . "<div id=\"top\">" . "\n"\r
+ . " <div id=\"navrow1\" class=\"tabs\">" . "\n"\r
+ . " <ul class=\"tablist\">" . "\n"\r
+ . " <li><a href=\"index.html\"><span>Main Page</span></a></li>" . "\n"\r
+ . " <li class=\"current\"><a href=\"pages.html\"><span>Related Pages</span></a></li>" . "\n";\r
+\r
+ if(-f $INPUTDIR . "/modules.html") {\r
+ $html .= " <li><a href=\"modules.html\"><span>Libraries</span></a></li>" . "\n";\r
+ }\r
+\r
+ if(-f $INPUTDIR . "/namespaces.html") {\r
+ $html .= " <li><a href=\"namespaces.html\"><span>Namespaces</span></a></li>" . "\n";\r
+ }\r
+\r
+ if(-f $INPUTDIR . "/annotated.html") {\r
+ $html .= " <li><a href=\"annotated.html\"><span>Classes</span></a></li>" . "\n";\r
+ }\r
+\r
+ if(-f $INPUTDIR . "/files.html") {\r
+ $html .= " <li><a href=\"files.html\"><span>Files</span></a></li>" . "\n";\r
+ }\r
+\r
+ $html .= " </ul>" . "\n"\r
+ . " </div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "<div class=\"header\">" . "\n"\r
+ . " <div class=\"headertitle\">" . "\n"\r
+ . "<div class=\"title\">$_[0] </div> </div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "<div class=\"contents\">" . "\n"\r
+ . "<div class=\"textblock\"><p><a class=\"anchor\" id=\"_privilege000002\"></a> </p>" . "\n"\r
+ . "<script type=\"text/javascript\">" . "\n"\r
+ . "//<![CDATA[" . "\n"\r
+ . " function divshow(id) {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + id);" . "\n"\r
+ . " var ediv = document.getElementById(\"div_\" + id);" . "\n"\r
+ . " if(eicon.innerHTML == \"-\") {" . "\n"\r
+ . " ediv.style.display = \"none\";" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " } else {" . "\n"\r
+ . " ediv.style.display = \"\";" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " function divallshow(istrue) {" . "\n"\r
+ . " var ediv = document.getElementsByTagName(\"div\");" . "\n"\r
+ . " if(istrue == true) {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " ediv[cnt].style.display = \"\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " } else {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " ediv[cnt].style.display = \"none\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . "//]]>" . "\n"\r
+ . "</script>" . "\n"\r
+ . "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\" style=\"border-bottom: 1px solid #A8B8D9; height: 15px;\">" . "\n"\r
+ . "<div class=\"memname\" style=\"float: right;\">" . "\n"\r
+ . "<a href=\"javascript:divallshow(true)\" class=\"el\">All Expand</a> " . "\n"\r
+ . "<a href=\"javascript:divallshow(false)\" class=\"el\">All Collapse</a> " . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+ return $html;\r
+}\r
+\r
+sub creathtmlbottom {\r
+ my $html = "";\r
+ open( FILEHDL, $INPUTDIR . "/feature.html") or die "Couldn't open the input directory : $INPUTDIR";\r
+ $footer = 0;\r
+ while($line = <FILEHDL>)\r
+ {\r
+ if($footer == 1)\r
+ {\r
+ $html .= $line;\r
+ }\r
+ elsif ($line =~ m/\<hr size=\"1\"\>\s*\<\/hr\>/)\r
+ {\r
+ $html .= $line;\r
+ $footer = 1;\r
+ }\r
+ }\r
+\r
+ return $html;\r
+}\r
+\r
+\r
+#------------------------------------------------------------------------------\r
+# arguments parsing\r
+#------------------------------------------------------------------------------\r
+while ($ARG=shift)\r
+{\r
+ debug("arg:$ARG");\r
+ if ($ARG =~ m/^-i/)\r
+ {\r
+ $INPUTDIR = shift;\r
+ debug ("INPUTDIR:$INPUTDIR");\r
+ }\r
+ elsif ($ARG =~ m/^-o/)\r
+ {\r
+ $OUTPUTDIR = shift;\r
+ debug ("OUTPUTDIR:$OUTPUTDIR");\r
+ }\r
+ elsif ($ARG =~ m/^-d/)\r
+ {\r
+ $DESCFILE = shift;\r
+ debug ("DESCFILE:$DESCFILE");\r
+ }\r
+ else\r
+ {\r
+ $INPUTDIR = $ARG;\r
+ debug ("INPUT_FILE:$INPUT_FILE");\r
+ }\r
+}\r
+\r
+if($INPUTDIR eq "") {\r
+ $INPUTDIR = "./";\r
+}\r
+if($OUTPUTDIR eq "") {\r
+ $OUTPUTDIR = $INPUTDIR;\r
+}\r
+\r
+#------------------------------------------------------------------------------\r
+# Privilege Description search\r
+#------------------------------------------------------------------------------\r
+getgroupdesc();\r
+\r
+#------------------------------------------------------------------------------\r
+# file search\r
+#------------------------------------------------------------------------------\r
+open( FILEHDL, $INPUTDIR . "/feature.html") or die "Couldn't open the input directory : $INPUTDIR";\r
+$dl = 0;\r
+$dt = "";\r
+$dd = "";\r
+while($line = <FILEHDL>)\r
+{\r
+ if ($line =~ m/\<dl\>/)\r
+ {\r
+ $dl = 1;\r
+ }\r
+ elsif ($line =~ m/\<dt\>(.+)\<\/dt\>/ && $dl == 1)\r
+ {\r
+ $dt = trim($1);\r
+ }\r
+ elsif ($line =~ m/\<dd\>(.+)\<\/dd\>/ && $dl == 1)\r
+ {\r
+ $dd = trim($1);\r
+ }\r
+ elsif ($line =~ m/\<dd\>(.+)\<br\/>/ && $dl == 1)\r
+ {\r
+ #<dd>http://tizen.org/feature/network.nfc and http://tizen.org/feature/network.nfc.reserved_push <br/>\r
+ # Both the features are required.</dd>\r
+ $dd = trim($1) . "<br/>";\r
+ while(1) {\r
+ $line = <FILEHDL>;\r
+ if($line =~ m/(.+)\<\/dd\>/) {\r
+ $dd .= $1;\r
+ last;\r
+ } else {\r
+ $dd .= $line\r
+ }\r
+ } \r
+ }\r
+ elsif ($line =~ m/\<\/dl\>/)\r
+ {\r
+ if($dt ne "" && $dd ne "") {\r
+ #$testtt = 0;\r
+ #if($dd =~ m/ for the [a-zA-Z_\" ]+ value( of [a-zA-Z_\"]+)?/) {\r
+ # print $dd . "\r\n";\r
+ $dd =~ s/ for the [a-zA-Z_\" ]+ value( of \<code\>[a-zA-Z_\"]+\<\/code\>)?//g;\r
+ # print "=========================" . "\r\n";\r
+ # print $dd . "\r\n";\r
+ # $testtt = 1;\r
+ #}\r
+ my @arrORdd = split / OR([\s]*\<br\/\>| )|,| or([\s]*\<br\/\>| )/, ($dd);\r
+ my @arrANDdd = split /\bAND\b|,|\band\b/, ($dd);\r
+\r
+ my $edd = "";\r
+\r
+ #if($testtt == 1) {\r
+ # print $#arrORdd . "\r\n";\r
+ # print $#arrANDdd . "\r\n";\r
+ # print "=========================" . "\r\n";\r
+ # foreach(@arrANDdd) {\r
+ # print $_ . "\r\n";\r
+ # }\r
+ #}\r
+\r
+ if($#arrORdd == 0 && $#arrANDdd == 0){\r
+ $edd = trim($dd);\r
+ my $subnodeDT = "";\r
+ if($dt =~ m/\<a[^\>]+\>([^\<]+)\<\/a\>/) {\r
+ $subnodeDT = $1;\r
+ \r
+ my @arrSubName = split /::/, $subnodeDT;\r
+ my @arr2;\r
+\r
+ if($#arrSubName + 1 == 1) {\r
+ } else {\r
+ for(my $i = 0; $i < $#arrSubName - 1; $i++) {\r
+ push(@arr2, $arrSubName[$i]);\r
+ }\r
+ $subnodeDT = join "::", @arr2;\r
+ }\r
+ }\r
+ \r
+ if($edd ne "") {\r
+ $featureexist = 0; \r
+ #print $subnodeDT . "\r\n";\r
+ foreach(@listFeature) {\r
+ if($_->{feature} eq $edd) {\r
+ $featureexist = 1;\r
+ $subnodeexist = 0;\r
+ my $ng = $_;\r
+ my $mem = new member($dt);\r
+ #push(@{$ng->{members}}, $mem);\r
+ #print $#{$ng->{members}} . $dd . $dt . "\r\n";\r
+ \r
+ foreach(@{$ng->{subnodes}}) {\r
+ if($_->{name} eq $subnodeDT) {\r
+ $subnodeexist = 1;\r
+ my $subnode = $_; \r
+ push(@{$subnode->{members}}, $mem);\r
+ #print $_->{name} . "\r\n";\r
+ }\r
+ }\r
+ \r
+ if($subnodeexist == 0) {\r
+ my $subng = new subnode($subnodeDT);\r
+ push(@{$subnode->{members}}, $mem);\r
+ push(@{$ng->{subnodes}}, $subng);\r
+ }\r
+ } \r
+ }\r
+ if($featureexist == 0) {\r
+ my $ng = new node($edd);\r
+ my $subng = new subnode($subnodeDT);\r
+ my $mem = new member($dt);\r
+ push(@{$subng->{members}}, $mem);\r
+ push(@{$ng->{subnodes}}, $subng);\r
+ push(@listFeature, $ng);\r
+ }\r
+ }\r
+ } else {\r
+ $edd = trim($dd);\r
+ $exist = 0;\r
+\r
+ if($dt =~ m/\<a[^\>]+\>([^\<]+)\<\/a\>/) {\r
+ $name = $1; #Tizen::Media::Camera::Construct\r
+ $name =~ m/(.+)::[^:]+/;\r
+ $namespace = $1; #Tizen::Media::Camera\r
+ }\r
+\r
+ foreach(@listOthers) {\r
+ if($_->{namespace} eq $namespace) {\r
+ $exist = 1;\r
+ my $ng = $_;\r
+ my $mem = new othersmember($dt, $edd, $name);\r
+ push(@{$ng->{members}}, $mem);\r
+ }\r
+ }\r
+ if($exist == 0) {\r
+ my $ng = new othersnode($namespace);\r
+ my $mem = new othersmember($dt, $edd, $name);\r
+\r
+ push(@{$ng->{members}}, $mem);\r
+ push(@listOthers, $ng);\r
+ }\r
+ }\r
+ }\r
+\r
+ $dl = 0;\r
+ $dt = $dd = "";\r
+ }\r
+}\r
+close (FILEHDL);\r
+\r
+my $ftHtmls = "";\r
+my $seq = 1;\r
+@listFeature = sort { lc($a->{feature}) cmp lc($b->{feature}) } @listFeature;\r
+\r
+foreach(@listFeature) {\r
+ my $id = zero_fill($seq, 10);\r
+ $seq++;\r
+\r
+ #$ftHtmls .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>" . "\n"\r
+ # . "<span>" . $_->{feature} . "</span></h2>" . "\n"\r
+ # . "<div style=\"display: none;\" id=\"div_$id\">" . "\n"\r
+ # . "<div class=\"memitem\">" . "\n"\r
+ # . "<div class=\"memproto\">" . "\n"\r
+ # . "<span class=\"memname\">" . $_->{feature} . "</span>" . "\n"\r
+ # . "</div>" . "\n"\r
+ # . "<div class=\"memdoc\">" . "\n";\r
+ $ftHtmls .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>" . "\n"\r
+ . "<span>" . $_->{feature} . "</span></h2>" . "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n"\r
+ . "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\" style=\"background-color: #FFFFFF; background-image: none;\">" . "\n"\r
+ . "<span class=\"memname\"></span>" . "\n"\r
+ . "</div>" . "\n";\r
+\r
+ my $featurename = $_->{feature};\r
+ my $cnt = 0;\r
+ \r
+ foreach(@groupdesc) {\r
+ if($_->{name} eq $featurename) {\r
+ my $desc = $_->{desc};\r
+ $desc =~ s/\'|\¡¯/'/g;\r
+ $desc =~ s/\"/"/g;\r
+ $ftHtmls .= "<div class=\"memdoc\">" . "\n";\r
+ $ftHtmls .= "<dl style=\"margin-top:-5px;_margin-top:-10px;\">$desc</dl>" . "\n";\r
+ $cnt++;\r
+ last;\r
+ }\r
+ }\r
+\r
+ if($cnt == 0) {\r
+ $ftHtmls .= "<div class=\"memdoc\" style=\"margin-top:-5px;_margin-top:-10px;\">" . "\n";\r
+ }\r
+\r
+ @{$_->{subnodes}} = sort { lc($a->{name}) cmp lc($b->{name}) } @{$_->{subnodes}};\r
+\r
+ foreach(@{$_->{subnodes}}) {\r
+ my $subng = $_;\r
+ \r
+ $ftHtmls .= "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\">" . "\n"\r
+ . "<span class=\"memname\">" . $subng->{name} . "</span>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "<div class=\"memdoc\">";\r
+ \r
+ @{$_->{members}} = sort { lc($a->{name}) cmp lc($b->{name}) } @{$_->{members}};\r
+ foreach(@{$subng->{members}}) {\r
+ $ftHtmls .= " <dl>" . "\n"\r
+ . " <dt>" . $_->{member} . "</dt>" . "\n"\r
+ . " </dl>" . "\n"; \r
+ }\r
+ \r
+ $ftHtmls .= "</div>"\r
+ . "</div>";\r
+ \r
+ #print $_->{name} . "\r\n";\r
+ }\r
+ \r
+ #foreach(@{$_->{members}}) {\r
+ # if ($cnt == 0) {\r
+ # $ftHtmls .= " <dl style=\"margin-top:-5px;\">" . "\n"\r
+ # . " <dt>" . $_->{member} . "</dt>" . "\n"\r
+ # . " </dl>" . "\n";\r
+ # } else {\r
+ # $ftHtmls .= " <dl>" . "\n"\r
+ # . " <dt>" . $_->{member} . "</dt>" . "\n"\r
+ # . " </dl>" . "\n";\r
+ # }\r
+ # $cnt++;\r
+ #}\r
+ $ftHtmls .= "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+}\r
+\r
+if($#listOthers > -1) {\r
+ my $id = zero_fill($seq, 10);\r
+ $seq++;\r
+\r
+ #$ftHtmls .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>" . "\n"\r
+ # . "<span>" . "Others" . "</span></h2>" . "\n"\r
+ # . "<div style=\"display: none;\" id=\"div_$id\">" . "\n"\r
+ # . "<div class=\"memitem\">" . "\n"\r
+ # . "<div class=\"memproto\">" . "\n"\r
+ # . "<span class=\"memname\">" . "Others" . "</span>" . "\n"\r
+ # . "</div>" . "\n"\r
+ # . "<div class=\"memdoc\">" . "\n";\r
+ $ftHtmls .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>" . "\n"\r
+ . "<span>" . "Others" . "</span></h2>" . "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n"\r
+ . "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\" style=\"background-color: #FFFFFF; background-image: none;\">" . "\n"\r
+ . "<span class=\"memname\"></span>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "<div class=\"memdoc\" style=\"margin-top:-5px;_margin-top:-10px;\">" . "\n";\r
+\r
+ @listOthers = sort { lc($a->{namespace}) cmp lc($b->{namespace}) } @listOthers;\r
+ foreach(@listOthers) {\r
+ $ftHtmls .= "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\">" . "\n"\r
+ . "<span class=\"memname\">" . $_->{namespace} . "</span>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "<div class=\"memdoc\">" . "\n";\r
+\r
+ @{$_->{members}} = sort { lc($a->{name}) cmp lc($b->{name}) } @{$_->{members}};\r
+\r
+ foreach(@{$_->{members}}) {\r
+ $ftHtmls .= " <dl>" . "\n"\r
+ . " <dt>" . $_->{member} . "</dt>" . "\n"\r
+ . " <dd>" . $_->{feature} . "</dd>" . "\n"\r
+ . " </dl>" . "\n";\r
+ }\r
+ $ftHtmls .= "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ }\r
+ \r
+ $ftHtmls .= "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+}\r
+\r
+if (-d $OUTPUTDIR) \r
+{\r
+}\r
+else\r
+{\r
+ mkdir $OUTPUTDIR, 0755 || die "can't create directory";\r
+}\r
+\r
+my $bottomhtml = creathtmlbottom();\r
+\r
+open FILE, ">", $OUTPUTDIR . "/" . "feature.html" or die "$!\n";\r
+print FILE creathtmltop("Required Feature");\r
+print FILE $ftHtmls;\r
+print FILE $bottomhtml;\r
+close FILE;\r
+\r
+\r
+package node;\r
+\r
+sub new {\r
+ my ($class, $feature) = @_;\r
+\r
+ my $self = { feature => $feature, subnodes => [] };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package subnode;\r
+\r
+sub new {\r
+ my ($class, $name) = @_;\r
+\r
+ my $self = { name => $name, members => [] };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+\r
+package member;\r
+\r
+sub new {\r
+ my ($class, $member) = @_;\r
+\r
+ my $self = { member => $member, name => "" };\r
+\r
+ if($member =~ m/\<a[^\>]+\>([^\<]+)\<\/a\>/)\r
+ {\r
+ $self->{name} = $1;\r
+ }\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package othersnode;\r
+\r
+sub new {\r
+ my ($class, $namespace) = @_;\r
+\r
+ my $self = { namespace => $namespace, members => [] };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package othersmember;\r
+\r
+sub new {\r
+ my ($class, $member, $feature, $name) = @_;\r
+\r
+ my $self = { member => $member, feature => $feature, name => $name };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package groupdesc;\r
+\r
+sub new {\r
+ my ($class, $name, $desc) = @_;\r
+\r
+ my $self = {name => $name, desc => $desc };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}
\ No newline at end of file
--- /dev/null
+use strict;\r
+use warnings;\r
+\r
+my $inputfilename = "";\r
+my $outputfilename = "";\r
+\r
+if($#ARGV + 1 == 1) {\r
+ $inputfilename = $ARGV[0];\r
+ $outputfilename = $ARGV[0];\r
+} elsif ($#ARGV + 1 == 2){\r
+ $inputfilename = $ARGV[0];\r
+ $outputfilename = $ARGV[1];\r
+} else {\r
+ #$inputfilename = "compatibility.html";\r
+ $inputfilename = "deprecated.html";\r
+ $outputfilename = "test2.html";\r
+}\r
+\r
+# Input File Exist Check\r
+\r
+if(fileexist($inputfilename) == 0)\r
+{\r
+ print "File not found : " . $inputfilename;\r
+ exit;\r
+}\r
+\r
+my $mode = "C";\r
+my $originalfile = fileload ($inputfilename);\r
+my $top = gettop ($originalfile);\r
+my $jquery = getjquerycontext($top);\r
+my $content = getcontent ($originalfile);\r
+my $bottom = getbottom ($originalfile);\r
+\r
+my $rootnode = new nodegroup;\r
+\r
+contentToObject($content);\r
+\r
+sortnode(\$rootnode);\r
+\r
+my $htmls = createhtml($rootnode, $jquery);\r
+savefile($top, $htmls, $bottom, $outputfilename);\r
+\r
+sub fileexist {\r
+ if ( -f $_[0] ) {\r
+ return 1;\r
+ } else {\r
+ return 0;\r
+ }\r
+}\r
+\r
+sub fileload {\r
+ if(index(uc($_[0]), "DEPRE") > -1) {\r
+ $mode = "D";\r
+ } else {\r
+ $mode = "C";\r
+ }\r
+\r
+ open FILE, $_[0];\r
+ my @lines = <FILE>;\r
+ close FILE;\r
+ join "", @lines;\r
+}\r
+\r
+sub getarray {\r
+ my @tt = ();\r
+ return \@tt;\r
+}\r
+\r
+sub gettop {\r
+ #substr($_[0], 0, index($_[0], "<dl>") - 1);\r
+ #substr($_[0], 0, index($_[0], "<dl "));\r
+ substr($_[0], 0, index($_[0], "<dl"));\r
+}\r
+\r
+sub getcontent {\r
+ #my $first = index($_[0], "<dl ");\r
+ my $first = index($_[0], "<dl");\r
+ substr($_[0], $first, rindex($_[0], "</dl>") - $first + 5);\r
+}\r
+\r
+sub getbottom {\r
+ substr($_[0], rindex($_[0], "</dl>") + 5);\r
+}\r
+\r
+sub getjquerycontext {\r
+ if (index($_[0], "jquery.js") < 0) {\r
+ return 0;\r
+ } else {\r
+ return 1;\r
+ }\r
+}\r
+\r
+sub contentToObject {\r
+ my @arr = getParserDL($_[0]);\r
+\r
+ my $str;\r
+\r
+ foreach $str (@arr) {\r
+ #print "val : " . $str . "\n";\r
+ my @dt = ($str =~ /<dt>(?<dt>.+)<\/dt>/);\r
+ #print "dt : " . $dt[0] . "\n";\r
+ my @method = ($dt[0] =~ /<a[^>]+>(?<dtkey>[^>]+)<\/a>/);\r
+ #print "method : " . $method[0] . "\n";\r
+ my $text = $str;\r
+\r
+ my $node = new node($method[0], $text);\r
+\r
+ my $ng = setnode(\$rootnode, $method[0]);\r
+\r
+ $ng->addnode(\$node);\r
+ } \r
+}\r
+\r
+sub createhtml {\r
+ my $ng = $_[0];\r
+ my $jquery = $_[1];\r
+ my $java = "";\r
+ if($jquery == 1) {\r
+ $java = "<script type=\"text/javascript\">" . "\n"\r
+ . " function divshow(id) {" . "\n"\r
+ . " if(\$(\"#icon_\" + id).html() == \"-\") {" . "\n"\r
+ . " \$(\"#div_\" + id).hide();" . "\n"\r
+ . " \$(\"#icon_\" + id).html(\"+\");" . "\n"\r
+ . " } else {" . "\n"\r
+ . " \$(\"#div_\" + id).show();" . "\n"\r
+ . " \$(\"#icon_\" + id).html(\"-\");" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " function divallshow(istrue) {" . "\n"\r
+ . " if(istrue == true) {" . "\n"\r
+ . " \$(\"div\").each(function() {" . "\n"\r
+ . " if(\$(this).attr(\"id\").substr(0,4) == \"div_\") {" . "\n"\r
+ . " \$(\"#icon_\" + \$(this).attr(\"id\").substr(4)).html(\"-\");" . "\n"\r
+ . " \$(this).show();" . "\n"\r
+ . " }" . "\n"\r
+ . " });" . "\n"\r
+ . " } else {" . "\n"\r
+ . " \$(\"div\").each(function() {" . "\n"\r
+ . " if(\$(this).attr(\"id\").substr(0,4) == \"div_\") {" . "\n"\r
+ . " \$(\"#icon_\" + \$(this).attr(\"id\").substr(4)).html(\"+\");" . "\n"\r
+ . " \$(this).hide();" . "\n"\r
+ . " }" . "\n"\r
+ . " });" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . "</script>" . "\n";\r
+ } else {\r
+ $java = "<script type=\"text/javascript\">" . "\n"\r
+ . "//<![CDATA[" . "\n"\r
+ . " function divshow(id) {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + id);" . "\n"\r
+ . " var ediv = document.getElementById(\"div_\" + id);" . "\n"\r
+ . " if(eicon.innerHTML == \"-\") {" . "\n"\r
+ . " ediv.style.display = \"none\";" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " } else {" . "\n"\r
+ . " ediv.style.display = \"\";" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " function divallshow(istrue) {" . "\n"\r
+ . " var ediv = document.getElementsByTagName(\"div\");" . "\n"\r
+ . " if(istrue == true) {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " ediv[cnt].style.display = \"\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " } else {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " ediv[cnt].style.display = \"none\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . "//]]>" . "\n"\r
+ . "</script>" . "\n";\r
+ }\r
+\r
+ my $html = $java . "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\" style=\"border-bottom: 1px solid #A8B8D9; height: 15px;\">" . "\n"\r
+ . "<div class=\"memname\" style=\"float: right;\">" . "\n"\r
+ . "<a href=\"javascript:divallshow(true)\" class=\"el\">All Expand</a> " . "\n"\r
+ . "<a href=\"javascript:divallshow(false)\" class=\"el\">All Collapse</a> " . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+\r
+ my $seq = 1;\r
+\r
+ createhtmlchild($ng, \$html, \$seq, 0, 1);\r
+ createhtmlothers($ng, \$html);\r
+\r
+# foreach(@list) {\r
+# my $ng = $_;\r
+#\r
+# if($ng->{name} eq "Multiple Group" || $ng->{name} eq "Others") {\r
+# createhtmlchild($ng, \$html, \$seq, 0);\r
+# }\r
+# }\r
+\r
+ return $html;\r
+}\r
+\r
+sub createhtmlothers {\r
+ my $ng = $_[0];\r
+ my $html = $_[1];\r
+\r
+ my $id = "others";\r
+\r
+ if($#{$ng->{nodes}} + 1 > 0) {\r
+ ${$html} .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>Others</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+\r
+ ${$html} .= "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\">" . "\n";\r
+ ${$html} .= "<span class=\"memname\"></span>" . "\n";\r
+ ${$html} .= "</div>" . "\n"\r
+ . "<div class=\"memdoc\">" . "\n";\r
+\r
+ for(@{$ng->{nodes}}) {\r
+ ${$html} .= "<dl>" . "\n";\r
+ ${$html} .= ${$_}->{text} . "\n";\r
+ ${$html} .= "</dl>" . "\n";\r
+ }\r
+\r
+ ${$html} .= "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+ }\r
+\r
+\r
+}\r
+\r
+\r
+sub createhtmlchild {\r
+ my $ng = $_[0];\r
+ my $html = $_[1];\r
+ my $seq = $_[2];\r
+ my $depth = $_[3];\r
+ my $isFirst = $_[4];\r
+\r
+ my $id = zero_fill(${$seq}, 10);\r
+ ${$seq} = ${$seq} + 1;\r
+ my $isDiv1 = 0;\r
+ my $isDiv2 = 0;\r
+ my $isDupTitle = 0;\r
+\r
+ my @multigroup;\r
+\r
+ if($depth >= 2) {\r
+ for(@{$ng->{childnodegroup}}) {\r
+ if($#{$_->{childnodegroup}} + 1 > 0) {\r
+ if($#{$_->{childnodegroup}[0]->{nodes}} + 1 > 0) {\r
+ push(@multigroup, \$_);\r
+ }\r
+ }\r
+ }\r
+\r
+ my @tmparr;\r
+\r
+ for(@{$ng->{childnodegroup}}) {\r
+ my $cnng = $_;\r
+ my $isexist = 0;\r
+\r
+ for(@multigroup) {\r
+ # ¹è¿¿¡¼ ¿ä¼Ò »èÁ¦\r
+ my $cnode = ${$_};\r
+\r
+ if($cnng == $cnode) {\r
+ $isexist = 1;\r
+ #print "°°Àº°Å ÀÖÀ½ $cnng";\r
+ } \r
+ }\r
+\r
+ if($isexist == 0) {\r
+ push(@tmparr, $cnng);\r
+ }\r
+ }\r
+\r
+ #print "A---------------------\n";\r
+ #for(@{$ng->{childnodegroup}}) {\r
+ # print $_ . "\n";\r
+ #}\r
+ #print "B---------------------\n";\r
+\r
+ my $cnt = $#{$ng->{childnodegroup}} + 1;\r
+ for(my $tmpcnt = 0; $tmpcnt < $cnt; $tmpcnt++) {\r
+ pop(@{$ng->{childnodegroup}});\r
+ }\r
+\r
+ #for(@{$ng->{childnodegroup}}) {\r
+ # print $_ . "\n";\r
+ #}\r
+\r
+ #print "C---------------------\n";\r
+ \r
+ push(@{$ng->{childnodegroup}}, @tmparr);\r
+\r
+ for(@multigroup) {\r
+ push(@{$ng->{childnodegroup}}, ${$_});\r
+ }\r
+\r
+ #for(@{$ng->{childnodegroup}}) {\r
+ # print $_ . "\n";\r
+ #}\r
+ #print "D---------------------\n";\r
+ }\r
+\r
+ my $attFirst = "";\r
+ if($isFirst == 0) {\r
+ $attFirst = " style=\"margin-top:-5px;_margin-top:-10px;\" ";\r
+ }\r
+\r
+ if(($depth != 0 && $depth != 1 && $#{$ng->{childnodegroup}} + 1 > 0) || $depth == 2) {\r
+ if ($depth == 2) {\r
+ if(($mode eq "C" && $#{$ng->{childnodegroup}} + 1 > 1) || ($mode eq "D" && $#{$ng->{nodes}} + 1 > 0)) {\r
+ ${$html} .= "<h2" . $attFirst . "><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{fullname}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ $isDiv1 = 1;\r
+ $isDupTitle = 1;\r
+ }\r
+ }\r
+\r
+ if($isDiv1 == 0 && $#{$_->{childnodegroup}} + 1 > 0) {\r
+ if($#{$_->{childnodegroup}[0]->{nodes}} + 1 > 0 || $depth == 2) {\r
+ ${$html} .= "<h2" . $attFirst . "><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{fullname}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ $isDiv1 = 1;\r
+ $isDupTitle = 1;\r
+ }\r
+ }\r
+\r
+ if($isDiv1 == 0 && $#{$_->{childnodegroup}} + 1 == 1) {\r
+ ${$html} .= "<h2" . $attFirst . "><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{fullname}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ $isDiv1 = 1;\r
+ $isDupTitle = 1;\r
+ }\r
+ }\r
+\r
+\r
+ if($depth != 0 && $depth != 1 && ($#{$_->{nodes}} + 1 > 0 || $#{$_->{childnodegroup}} + 1 > 0)) {\r
+ ${$html} .= "<div class=\"memitem\">" . "\n";\r
+\r
+ if($isDupTitle == 0) {\r
+ ${$html} .= "<div class=\"memproto\">" . "\n";\r
+ ${$html} .= "<span class=\"memname\">" . $ng->{fullname} . "</span>" . "\n";\r
+ } else {\r
+ ${$html} .= "<div class=\"memproto\" style=\"background-color: #FFFFFF; background-image: none;\">" . "\n";\r
+ ${$html} .= "<span class=\"memname\"></span>" . "\n";\r
+ }\r
+ ${$html} .= "</div>" . "\n";\r
+\r
+ if($#{$_->{nodes}} + 1 == 0 && $isDupTitle == 1) {\r
+ ${$html} .= "<div class=\"memdoc\" style=\"margin-top:-5px;_margin-top:-10px;\">" . "\n";\r
+ } else {\r
+ ${$html} .= "<div class=\"memdoc\">" . "\n";\r
+ }\r
+ $isDiv2 = 1;\r
+\r
+ if($#{$_->{nodes}} + 1 > 0) {\r
+ if($depth > 0) {\r
+ my $cntNode = 0;\r
+ for(@{$_->{nodes}}) {\r
+ if($isDupTitle == 1 && $cntNode == 0) {\r
+ ${$html} .= "\t<dl style=\"margin-top:-5px;_margin-top:-10px;\">" . "\n";\r
+ } else {\r
+ ${$html} .= "\t<dl>" . "\n";\r
+ }\r
+\r
+ ${$html} .= ${$_}->{text} . "\n";\r
+ ${$html} .= "</dl>" . "\n";\r
+ $cntNode++;\r
+ }\r
+ }\r
+ }\r
+ }\r
+\r
+ my @childng = @{$ng->{childnodegroup}};\r
+ my $siblingCnt = 0;\r
+ for(@childng) {\r
+ if($siblingCnt == 0 && $#{$_->{nodes}} + 1 == 0) {\r
+ createhtmlchild($_, $html, $seq, $depth + 1, 0);\r
+ } else {\r
+ createhtmlchild($_, $html, $seq, $depth + 1, 1);\r
+ }\r
+ $siblingCnt++\r
+ }\r
+\r
+ if($isDiv2 == 1) {\r
+ ${$html} .= "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+ }\r
+\r
+ if($isDiv1 == 1) {\r
+ ${$html} .= "</div>" . "\n";\r
+ }\r
+}\r
+\r
+sub savefile {\r
+ my $top = $_[0];\r
+ my $htmls = $_[1];\r
+ my $bottom = $_[2];\r
+ my $filename = $_[3];\r
+\r
+ open FILE, ">", $filename or die "$!\n";\r
+\r
+ print FILE $top;\r
+ print FILE $htmls;\r
+ print FILE $bottom;\r
+\r
+ close FILE;\r
+}\r
+\r
+sub getParserDL {\r
+ my $startindex = -1;\r
+ my @arr;\r
+ while(1) {\r
+ my $start = index($_[0], "<dt>", $startindex + 1);\r
+ my $end = index($_[0], "</dd>", $startindex + 1);\r
+ if($start == -1) {\r
+ last;\r
+ }\r
+\r
+ push(@arr, substr($_[0], $start, $end - $start + 5));\r
+\r
+ $startindex = $end;\r
+ }\r
+ @arr;\r
+}\r
+\r
+sub zero_fill\r
+{\r
+ my $pad_len = $_[1];\r
+ my $padded = sprintf("%0${pad_len}d", $_[0]);\r
+ return $padded;\r
+}\r
+\r
+sub trim {\r
+ my @result = @_;\r
+\r
+ foreach (@result) {\r
+ s/^\s+//; # ¾ÕÂÊ °ø¹é Áö¿ì±â\r
+ s/\s+$//; # µÚÂÊ °ø¹é Áö¿ì±â\r
+ }\r
+\r
+ return wantarray ? @result : $result[0];\r
+}\r
+\r
+sub addkey {\r
+ my $arr = $_[0];\r
+ push(@$arr, $_[1]);\r
+\r
+ #foreach (@$arr) {\r
+ # print "\nitem - " . $_->{name};\r
+ #}\r
+\r
+ #print "\n--------------------";\r
+}\r
+\r
+sub containskey {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ if($_->{name} eq $keyname) {\r
+ return 1;\r
+ }\r
+ }\r
+\r
+ return 0;\r
+}\r
+\r
+sub setnode {\r
+ #print "sdfs : " . $_[0];\r
+ my $ng = ${$_[0]}; #nodegroup\r
+ my $method = $_[1]; #method\r
+\r
+ my @arr = split /::/, $method;\r
+\r
+ if($#arr + 1 == 1) {\r
+ return $ng;\r
+ } else {\r
+ my $tm = $ng->{childnodegroup};\r
+\r
+ foreach(@{$tm}) {\r
+ if($_->{name} eq $arr[0]) {\r
+ my @arr2;\r
+\r
+ for(my $i = 1; $i < $#arr + 1; $i++) {\r
+ push(@arr2, $arr[$i]);\r
+ }\r
+ return setnode(\$_, join "::", @arr2);\r
+ }\r
+ }\r
+\r
+ my $newng = new nodegroup();\r
+ $newng->{name} = $arr[0];\r
+ push(@{$tm}, $newng);\r
+\r
+ $newng->{parentnodegroup} = $ng;\r
+\r
+ if($ng->{fullname} eq "") {\r
+ $newng->{fullname} = $arr[0];\r
+ } else {\r
+ $newng->{fullname} = $ng->{fullname} . "::" . $arr[0];\r
+ }\r
+\r
+ my @arr2;\r
+ for(my $i = 1; $i < $#arr + 1; $i++) {\r
+ push(@arr2, $arr[$i]);\r
+ }\r
+ return setnode(\$newng, join "::", @arr2);\r
+ }\r
+}\r
+\r
+sub findnode {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ #print $_->{name} . "-" . $keyname . "\n";\r
+ if($_->{name} eq $keyname) {\r
+ return $_;\r
+ }\r
+ }\r
+}\r
+\r
+sub sortnode {\r
+ ${$_[0]}->sortnodes();\r
+ ${$_[0]}->sortchildnodegroup();\r
+\r
+ foreach(@{$_->{childnodegroup}}) {\r
+ sortnode(\$_);\r
+ }\r
+\r
+}\r
+\r
+\r
+\r
+package node;\r
+\r
+sub new {\r
+ my ($class, $method, $text) = @_;\r
+\r
+ my $self = {method => $method, text => $text };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package nodegroup;\r
+\r
+sub new {\r
+ my ($class) = @_;\r
+\r
+ my $self = {name => "", fullname => "", my @parentnodegroup => ()};\r
+\r
+ my @childnodegrouptmp = getarray();\r
+ $self->{childnodegroup} = \@childnodegrouptmp;\r
+ my @nodestmp = getarray();\r
+ $self->{nodes} = \@nodestmp;\r
+\r
+ pop(@{$self->{childnodegroup}});\r
+ pop(@{$self->{nodes}});\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+sub getarray {\r
+ my @tt = ();\r
+ return \@tt;\r
+}\r
+\r
+sub setname {\r
+ my $self = shift;\r
+ $self->{name} = $_[0];\r
+}\r
+\r
+sub addnode {\r
+ my $self = shift;\r
+# print $_[0]->{method} . "\n";\r
+ push(@{$self->{nodes}}, $_[0]);\r
+}\r
+\r
+sub sortnodes {\r
+\r
+ my $self = shift;\r
+\r
+ my $n = $self->{nodes};\r
+\r
+ #foreach(@{$n}) {\r
+ # print ${$_} . "\n";\r
+ #}\r
+ #print "------------------" . "\n";\r
+\r
+ #foreach(@{$n}) {\r
+ # print ${${$_}->{dtdddata}}->{dtkey} . "\n";\r
+ #}\r
+ @{$n} = sort { lc(${$a}->{method}) cmp lc(${$b}->{method}) || lc(${${$a}->{dtdddata}}->{dtkey}) cmp lc(${${$b}->{dtdddata}}->{dtkey}) || lc(${${$a}->{dtdddata}}->{dt}) cmp lc(${${$b}->{dtdddata}}->{dt}) } @{$n};\r
+}\r
+\r
+sub sortchildnodegroup {\r
+ my $self = shift;\r
+\r
+ my $n = $self->{childnodegroup};\r
+\r
+ @{$n} = sort { lc($a->{name}) cmp lc($b->{name}) } @{$n};\r
+}\r
+\r
+\r
+package groupdesc;\r
+\r
+sub new {\r
+ my ($class, $name, $desc) = @_;\r
+\r
+ my $self = {name => $name, desc => $desc };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}
\ No newline at end of file
--- /dev/null
+#bada_Privilege.pl privilege.html ./1/privilege.html\r
+use strict;\r
+use warnings;\r
+\r
+my $inputfilename = "";\r
+my $outputfilename = "";\r
+\r
+if($#ARGV + 1 == 1) {\r
+ $inputfilename = $ARGV[0];\r
+ $outputfilename = $ARGV[0];\r
+} elsif ($#ARGV + 1 == 2){\r
+ $inputfilename = $ARGV[0];\r
+ $outputfilename = $ARGV[1];\r
+} else {\r
+ $inputfilename = "privgroup.html";\r
+ $outputfilename = "test.html";\r
+}\r
+\r
+my $mode = "L";\r
+#my $originalfile = fileload ("privgroup.html");\r
+#my $originalfile = fileload ("deprecated.html");\r
+\r
+# Input File Exist Check\r
+\r
+if(fileexist($inputfilename) == 0)\r
+{\r
+ print "File not found : " . $inputfilename;\r
+ exit;\r
+}\r
+\r
+my $originalfile = fileload ($inputfilename);\r
+my $top = gettop ($originalfile);\r
+my $jquery = getjquerycontext($top);\r
+my $content = getcontent ($originalfile);\r
+my $bottom = getbottom ($originalfile);\r
+\r
+my @groupdesc = ();\r
+\r
+if ($mode eq "G") {\r
+ getgroupdesc();\r
+\r
+ #foreach(@groupdesc) {\r
+ # print $_->{name} . " - " . $_->{desc} . "\n";\r
+ #}\r
+}\r
+\r
+my @list = ();\r
+\r
+contentToObject($content);\r
+\r
+@list = sort { $a->{seq} cmp $b->{seq} || lc($a->{name}) cmp lc($b->{name}) } @list;\r
+\r
+foreach(@list) {\r
+ sortnode(\$_);\r
+}\r
+\r
+my $htmls = createhtml($jquery);\r
+savefile($top, $htmls, $bottom, $outputfilename);\r
+\r
+#foreach(@list) {\r
+# my $ng = $_;\r
+# foreach(@{$ng->{childnodegroup}}) {\r
+# my $subng = $_;\r
+# foreach(@{$subng->{childnodegroup}}) {\r
+# my $ss = $_;\r
+# foreach(@{$ss->{childnodegroup}}) {\r
+# my $sdf = $_;\r
+# print $sdf->{name} . ":";\r
+# }\r
+# }\r
+# }\r
+# print "---------------------------" . "\n";\r
+#}\r
+\r
+sub fileexist {\r
+ if ( -f $_[0] ) {\r
+ return 1;\r
+ } else {\r
+ return 0;\r
+ }\r
+}\r
+\r
+sub fileload {\r
+ #if(index(uc($_[0]), "GROUP") > -1) {\r
+ if($_[0] =~ /privilege.html/) {\r
+ #print "11";\r
+ $mode = "G";\r
+ } else {\r
+ $mode = "L";\r
+ }\r
+\r
+ open FILE, $_[0];\r
+ my @lines = <FILE>;\r
+ close FILE;\r
+ join "", @lines;\r
+}\r
+\r
+sub getgroupdesc {\r
+ open FILE, "privilege_desc.txt";\r
+ my @lines = <FILE>;\r
+ close FILE;\r
+\r
+ my $name = "";\r
+ my $desc = "";\r
+\r
+ foreach(@lines) {\r
+ if(trim($name) eq "") {\r
+ $name = trim($_);\r
+ } elsif(trim($_) eq "") {\r
+ my $gd = new groupdesc($name, $desc);\r
+ push(@groupdesc, $gd);\r
+\r
+ $name = "";\r
+ $desc = "";\r
+ } else {\r
+ if(trim($desc) eq "") {\r
+ $desc = $_;\r
+ } else {\r
+ $desc .= $_ . "<br/>";\r
+ }\r
+ }\r
+ }\r
+}\r
+\r
+sub getarray {\r
+ my @tt = ();\r
+ return \@tt;\r
+}\r
+\r
+sub gettop {\r
+ #substr($_[0], 0, index($_[0], "<dl>") - 1);\r
+ substr($_[0], 0, index($_[0], "<dl"));\r
+}\r
+\r
+sub getcontent {\r
+ my $first = index($_[0], "<dl");\r
+ substr($_[0], $first, rindex($_[0], "</dl>") - $first + 5);\r
+}\r
+\r
+sub getbottom {\r
+ substr($_[0], rindex($_[0], "</dl>") + 5);\r
+}\r
+\r
+sub getjquerycontext {\r
+ if (index($_[0], "jquery.js") < 0) {\r
+ return 0;\r
+ } else {\r
+ return 1;\r
+ }\r
+}\r
+\r
+sub contentToObject {\r
+ my @arr = getParserDL($_[0]);\r
+\r
+ my $str;\r
+\r
+ foreach $str (@arr) {\r
+ my @dt = ($str =~ /<dt>(?<dt>.+)<\/dt>/);\r
+ my @aa2 = ($dt[0] =~ /<a[^>]+>(?<dtkey>[^>]+)<\/a>/);\r
+ my $dtkey = $aa2[0];\r
+ my @aa3 = ($str =~ /<dd>(?<dd>[\s\S]+)<\/dd>/);\r
+ $aa3[0] =~ s/<[^<]+>//g;\r
+ $aa3[0] =~ s/\([^\)]+\)//g;\r
+ my $dd = $aa3[0];\r
+\r
+ my @arrdd = split / OR | \| | or /, ($dd);\r
+ my @arrddand = split / AND | and /, ($dd);\r
+\r
+ #¹è¿ÀÇ Å©±â´Â $# + 1\r
+ if($#arrddand + 1 == 1) {\r
+ #print ($dd);\r
+ my @arrdd = split / OR | \| |,/, ($dd);\r
+ my $eachddsrc;\r
+\r
+ foreach $eachddsrc (@arrdd) {\r
+ my $eachdd = trim($eachddsrc);\r
+\r
+ #print " : " . $eachdd;\r
+ if($eachdd =~ /(.+)/) {\r
+ $eachdd = $1;\r
+ }\r
+ #print " : " . $eachdd . "\r\n";\r
+\r
+ if($eachdd eq "") {\r
+ next;\r
+ }\r
+\r
+ if(containskey(\@list, $eachdd) == 0) {\r
+ my $seq = 4;\r
+ if(lc($eachdd) eq "public") {\r
+ $seq = 1;\r
+ } elsif(lc($eachdd) eq "partner") {\r
+ $seq = 2;\r
+ } elsif(lc($eachdd) eq "platform") {\r
+ $seq = 3;\r
+ }\r
+\r
+ my $ng = new nodegroup($seq);\r
+ $ng->setname($eachdd);\r
+ addkey(\@list, $ng);\r
+ }\r
+\r
+ my $dtdddata = new dtdd($dt[0], $dtkey, $eachdd);\r
+ my $n = new node($dtkey, \$dtdddata);\r
+\r
+ my $findng = findnode(\@list, $eachdd);\r
+ #print "search : " . $findng->{name} . "\n";\r
+ my $ng = setnode(\$findng, $dtkey);\r
+ #print "ng : " . $ng->{name} . "\n";\r
+ #push($ng->{nodes}, $n);\r
+ $ng->addnode(\$n);\r
+ }\r
+ }\r
+\r
+ if($#arrdd + 1 > 1) {\r
+ my $eachdd = "Others";\r
+\r
+ if($dd =~ /(.+)/) {\r
+ $dd = $1;\r
+ }\r
+\r
+ if($dd eq "") {\r
+ next;\r
+ }\r
+\r
+ if(containskey(\@list, $eachdd) == 0) {\r
+ my $ng = new nodegroup(9999);\r
+ $ng->setname($eachdd);\r
+ addkey(\@list, $ng);\r
+ }\r
+\r
+ my $dtdddata = new dtdd($dt[0], $dtkey, $dd);\r
+ my $n = new node($dtkey, \$dtdddata);\r
+\r
+ my $findng = findnode(\@list, $eachdd);\r
+ my $ng = setnode(\$findng, $dtkey);\r
+ $ng->addnode(\$n);\r
+ }\r
+\r
+ if($#arrddand + 1 > 1) {\r
+ my $eachdd = "Others";\r
+\r
+ if($dd =~ /(.+)/) {\r
+ $dd = $1;\r
+ }\r
+\r
+ if($dd eq "") {\r
+ next;\r
+ }\r
+\r
+ if(containskey(\@list, $eachdd) == 0) {\r
+ my $ng = new nodegroup(9999);\r
+ $ng->setname($eachdd);\r
+ addkey(\@list, $ng);\r
+ }\r
+\r
+ my $dtdddata = new dtdd($dt[0], $dtkey, $dd);\r
+ my $n = new node($dtkey, \$dtdddata);\r
+\r
+ my $findng = findnode(\@list, $eachdd);\r
+ my $ng = setnode(\$findng, $dtkey);\r
+ $ng->addnode(\$n);\r
+ }\r
+ } \r
+}\r
+\r
+sub createhtml {\r
+ my $jquery = $_[0];\r
+ my $java = "";\r
+ if($jquery == 1) {\r
+ $java = "<script type=\"text/javascript\">" . "\n"\r
+ . " function divshow(id) {" . "\n"\r
+ . " if(\$(\"#icon_\" + id).html() == \"-\") {" . "\n"\r
+ . " \$(\"#div_\" + id).hide();" . "\n"\r
+ . " \$(\"#icon_\" + id).html(\"+\");" . "\n"\r
+ . " } else {" . "\n"\r
+ . " \$(\"#div_\" + id).show();" . "\n"\r
+ . " \$(\"#icon_\" + id).html(\"-\");" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " function divallshow(istrue) {" . "\n"\r
+ . " if(istrue == true) {" . "\n"\r
+ . " \$(\"div\").each(function() {" . "\n"\r
+ . " if(\$(this).attr(\"id\").substr(0,4) == \"div_\") {" . "\n"\r
+ . " if(\$(\"#icon_\" + \$(this).attr(\"id\").substr(4)).length > 0) {" . "\n"\r
+ . " \$(\"#icon_\" + \$(this).attr(\"id\").substr(4)).html(\"-\");" . "\n"\r
+ . " \$(this).show();" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " });" . "\n"\r
+ . " } else {" . "\n"\r
+ . " \$(\"div\").each(function() {" . "\n"\r
+ . " if(\$(this).attr(\"id\").substr(0,4) == \"div_\") {" . "\n"\r
+ . " if(\$(\"#icon_\" + \$(this).attr(\"id\").substr(4)).length > 0) {" . "\n"\r
+ . " \$(\"#icon_\" + \$(this).attr(\"id\").substr(4)).html(\"+\");" . "\n"\r
+ . " \$(this).hide();" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " });" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . "</script>" . "\n";\r
+ } else {\r
+ $java = "<script type=\"text/javascript\">" . "\n"\r
+ . "//<![CDATA[" . "\n"\r
+ . " function divshow(id) {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + id);" . "\n"\r
+ . " var ediv = document.getElementById(\"div_\" + id);" . "\n"\r
+ . " if(eicon.innerHTML == \"-\") {" . "\n"\r
+ . " ediv.style.display = \"none\";" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " } else {" . "\n"\r
+ . " ediv.style.display = \"\";" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " function divallshow(istrue) {" . "\n"\r
+ . " var ediv = document.getElementsByTagName(\"div\");" . "\n"\r
+ . " if(istrue == true) {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " if(eicon != null) {" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " ediv[cnt].style.display = \"\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " } else {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " if(eicon != null) {" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " ediv[cnt].style.display = \"none\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . "//]]>" . "\n"\r
+ . "</script>" . "\n";\r
+ }\r
+\r
+ my $html = $java . "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\" style=\"border-bottom: 1px solid #A8B8D9; height: 15px;\">" . "\n"\r
+ . "<div class=\"memname\" style=\"float: right;\">" . "\n"\r
+ . "<a href=\"javascript:divallshow(true)\" class=\"el\">All Expand</a> " . "\n"\r
+ . "<a href=\"javascript:divallshow(false)\" class=\"el\">All Collapse</a> " . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+\r
+ my $seq = 1;\r
+\r
+ foreach(@list) {\r
+ my $ng = $_;\r
+\r
+ if($ng->{name} eq "Multiple Group" || $ng->{name} eq "Others") {\r
+ next;\r
+ }\r
+ createhtmlchild($ng, \$html, \$seq, 0, $#list + 1, 1);\r
+ }\r
+\r
+ foreach(@list) {\r
+ my $ng = $_;\r
+\r
+ if($ng->{name} eq "Multiple Group" || $ng->{name} eq "Others") {\r
+ createhtmlchild($ng, \$html, \$seq, 0, $#list + 1, 1);\r
+ }\r
+ }\r
+\r
+ return $html;\r
+}\r
+\r
+sub createhtmlchild {\r
+ my $ng = $_[0];\r
+ my $html = $_[1];\r
+ my $seq = $_[2];\r
+ my $depth = $_[3];\r
+ my $siblingcount = $_[4];\r
+ my $isFirst = $_[5];\r
+\r
+ my $id = zero_fill(${$seq}, 10);\r
+ ${$seq} = ${$seq} + 1;\r
+ my $isDiv1 = 0;\r
+ my $isDiv2 = 0;\r
+ my $isDupTitle = 0;\r
+\r
+ my $h2Title = "";\r
+\r
+ my $attFirst = "";\r
+ if($isFirst == 0) {\r
+ $attFirst = " style=\"margin-top:-5px;_margin-top:-10px;\" ";\r
+ }\r
+\r
+ if($depth == 0) {\r
+ if(($mode eq "L") && ($ng->{name} eq "SYSTEM" || $ng->{name} eq "USER")) {\r
+ $ng->{name} = lc($ng->{name});\r
+ }\r
+\r
+ if($siblingcount == 1) {\r
+ ${$html} .= "<div style=\"\" id=\"div_$id\">" . "\n";\r
+ $isDupTitle = 1;\r
+ } else {\r
+ ${$html} .= "<h2" . $attFirst . "><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{name}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ $isDupTitle = 1;\r
+ $h2Title = $ng->{name};\r
+ }\r
+ $isDiv1 = 1;\r
+ }\r
+\r
+ if($mode eq "L" && $depth == 2) {\r
+ ${$html} .= "<h2" . $attFirst . "><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{fullname}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ $isDiv1 = 1;\r
+ $isDupTitle = 1;\r
+ $h2Title = $ng->{fullname};\r
+ }\r
+\r
+ my @nodes = @{$ng->{nodes}};\r
+ my $isEmptyName = 0;\r
+\r
+ if($depth == 0 || ($mode eq "L" && $depth == 2) || $#nodes + 1 > 0) {\r
+ ${$html} .= "<div class=\"memitem\">" . "\n";\r
+\r
+ if($h2Title eq $ng->{name} || $h2Title eq $ng->{fullname}) {\r
+ ${$html} .= "<div class=\"memproto\" style=\"background-color: #FFFFFF; background-image: none;\">" . "\n";\r
+ $isEmptyName = 1;\r
+ } else {\r
+ ${$html} .= "<div class=\"memproto\" >" . "\n";\r
+ }\r
+ \r
+ \r
+ if($isDupTitle == 0) {\r
+ if($depth == 0) {\r
+ if($h2Title eq $ng->{name}) {\r
+ ${$html} .= "<span class=\"memname\"></span>" . "\n";\r
+ } else\r
+ {\r
+ ${$html} .= "<span class=\"memname\">" . $ng->{name} . "</span>" . "\n";\r
+ }\r
+ } else {\r
+ if($h2Title eq $ng->{fullname}) {\r
+ ${$html} .= "<span class=\"memname\"></span>" . "\n";\r
+ } else\r
+ {\r
+ ${$html} .= "<span class=\"memname\">" . $ng->{fullname} . "</span>" . "\n";\r
+ }\r
+ }\r
+ } else {\r
+ ${$html} .= "<span class=\"memname\"></span>" . "\n";\r
+ }\r
+\r
+ ${$html} .= "</div>" . "\n";\r
+\r
+ if($#{$_->{nodes}} + 1 == 0 && $isEmptyName == 1) {\r
+ ${$html} .= "<div class=\"memdoc\" style=\"margin-top:-5px;_margin-top:-10px;\">" . "\n";\r
+ } else {\r
+ ${$html} .= "<div class=\"memdoc\">" . "\n";\r
+ }\r
+\r
+ $isDiv2 = 1;\r
+\r
+ if($depth == 0 && $mode eq "G") {\r
+ foreach(@groupdesc) {\r
+ #print $_->{name} . "\r\n";\r
+ if($_->{name} eq $ng->{name}) {\r
+ my $desc = $_->{desc};\r
+ $desc =~ s/\'|\¡¯/'/g;\r
+ $desc =~ s/\"/"/g;\r
+ ${$html} .= "<dl style=\"margin-top:-5px;_margin-top:-10px;\">$desc</dl>";\r
+ last;\r
+ }\r
+ }\r
+ }\r
+ }\r
+\r
+ if($#nodes + 1 > 0) {\r
+ if($depth > 0) {\r
+ my $cntNode = 0;\r
+ foreach(@nodes) {\r
+ #${$html} .= "\t<dl>" . "\n"\r
+ # . "\t\t<dt>" . ${${$_}->{dtdddata}}->{dt} . "</dt>" . "\n"\r
+ # . "\t\t<dd>" . ${${$_}->{dtdddata}}->{dd} . "</dd>" . "\n"\r
+ # . "\t</dl>" . "\n"; \r
+\r
+ if($isEmptyName == 1 && $cntNode == 0) {\r
+ ${$html} .= "\t<dl style=\"margin-top:-5px;_margin-top:-10px;\">" . "\n";\r
+ } else {\r
+ ${$html} .= "\t<dl>" . "\n";\r
+ }\r
+ ${$html} .= "\t\t<dt>" . ${${$_}->{dtdddata}}->{dt} . "</dt>" . "\n"\r
+ . "\t</dl>" . "\n"; \r
+ $cntNode++;\r
+ }\r
+ }\r
+ }\r
+\r
+ my @childng = @{$ng->{childnodegroup}};\r
+ my $siblingCnt = 0;\r
+ foreach(@childng) {\r
+ if($siblingCnt == 0 && $#{$_->{nodes}} + 1 == 0) {\r
+ createhtmlchild($_, $html, $seq, $depth + 1, $#childng + 1, 0);\r
+ } else {\r
+ createhtmlchild($_, $html, $seq, $depth + 1, $#childng + 1, 1);\r
+ }\r
+ }\r
+\r
+ if($isDiv2 == 1) {\r
+ ${$html} .= "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+ }\r
+\r
+ if($isDiv1 == 1) {\r
+ ${$html} .= "</div>" . "\n";\r
+ }\r
+}\r
+\r
+sub savefile {\r
+ my $top = $_[0];\r
+ my $htmls = $_[1];\r
+ my $bottom = $_[2];\r
+ my $filename = $_[3];\r
+\r
+ open FILE, ">", $filename or die "$!\n";\r
+\r
+ print FILE $top;\r
+ print FILE $htmls;\r
+ print FILE $bottom;\r
+\r
+ close FILE;\r
+}\r
+\r
+sub getParserDL {\r
+ my $startindex = -1;\r
+ my @arr;\r
+ while(1) {\r
+ my $start = index($_[0], "<dt>", $startindex + 1);\r
+ my $end = index($_[0], "</dd>", $startindex + 1);\r
+ if($start == -1) {\r
+ last;\r
+ }\r
+\r
+ push(@arr, substr($_[0], $start, $end - $start + 5));\r
+\r
+ $startindex = $end;\r
+ }\r
+ @arr;\r
+}\r
+\r
+sub zero_fill\r
+{\r
+ my $pad_len = $_[1];\r
+ my $padded = sprintf("%0${pad_len}d", $_[0]);\r
+ return $padded;\r
+}\r
+\r
+sub trim {\r
+ my @result = @_;\r
+\r
+ foreach (@result) {\r
+ s/^\s+//; # ¾ÕÂÊ °ø¹é Áö¿ì±â\r
+ s/\s+$//; # µÚÂÊ °ø¹é Áö¿ì±â\r
+ }\r
+\r
+ return wantarray ? @result : $result[0];\r
+}\r
+\r
+sub addkey {\r
+ my $arr = $_[0];\r
+ push(@$arr, $_[1]);\r
+\r
+ #foreach (@$arr) {\r
+ # print "\nitem - " . $_->{name};\r
+ #}\r
+\r
+ #print "\n--------------------";\r
+}\r
+\r
+sub containskey {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ if($_->{name} eq $keyname) {\r
+ return 1;\r
+ }\r
+ }\r
+\r
+ return 0;\r
+}\r
+\r
+sub setnode {\r
+ #print "sdfs : " . $_[0];\r
+ my $ng = ${$_[0]}; #nodegroup\r
+ my $method = $_[1]; #method\r
+\r
+ my @arr = split /::/, $method;\r
+\r
+ if($#arr + 1 == 1) {\r
+ return $ng;\r
+ } else {\r
+ my $tm = $ng->{childnodegroup};\r
+ #my @tm = ($ng->{childnodegroup});\r
+ foreach(@{$tm}) {\r
+ if($_->{name} eq $arr[0]) {\r
+ my @arr2;\r
+\r
+ for(my $i = 1; $i < $#arr + 1; $i++) {\r
+ push(@arr2, $arr[$i]);\r
+ }\r
+ return setnode(\$_, join "::", @arr2);\r
+ }\r
+ }\r
+\r
+ my $newng = new nodegroup();\r
+ $newng->{name} = $arr[0];\r
+ push(@{$tm}, $newng);\r
+ #print $#{$tm} . "\n";\r
+ #foreach(@{$tm}) {\r
+ # print ${$tm}[0] . "\n";\r
+ # print "------------\n";\r
+ #}\r
+\r
+ $newng->{parentnodegroup} = $newng;\r
+\r
+ if($ng->{fullname} eq "") {\r
+ $newng->{fullname} = $arr[0];\r
+ } else {\r
+ $newng->{fullname} = $ng->{fullname} . "::" . $arr[0];\r
+ }\r
+\r
+ my @arr2;\r
+ for(my $i = 1; $i < $#arr + 1; $i++) {\r
+ push(@arr2, $arr[$i]);\r
+ }\r
+ return setnode(\$newng, join "::", @arr2);\r
+ }\r
+}\r
+\r
+sub findnode {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ #print $_->{name} . "-" . $keyname . "\n";\r
+ if($_->{name} eq $keyname) {\r
+ return $_;\r
+ }\r
+ }\r
+}\r
+\r
+sub sortnode {\r
+ $_->sortnodes();\r
+ \r
+ if($mode eq "G") {\r
+ $_->sortchildnodegroup();\r
+ } else {\r
+ if($_->{fullname} eq "") {\r
+ $_->sortchildnodegroup();\r
+ } else {\r
+ $_->sortchildnodegroup();\r
+\r
+ my @three = ();\r
+ my @four = ();\r
+ \r
+ foreach($_->{childenodegroup}) {\r
+ my $ng = $_->{nodes};\r
+\r
+ if($#{$ng} + 1 > 0) {\r
+ push(@three, $_);\r
+ } else {\r
+ push(@four, $_);\r
+ }\r
+ }\r
+\r
+ push @three, @four;\r
+\r
+ $_->{childenodegroup} = @three;\r
+ }\r
+ }\r
+\r
+ foreach(@{$_->{childnodegroup}}) {\r
+ sortnode(\$_);\r
+ }\r
+\r
+}\r
+\r
+\r
+package dtdd;\r
+\r
+sub new {\r
+ my ($class, $dt, $dtkey, $dd) = @_;\r
+\r
+ my $self = {dt => $dt, dtkey => $dtkey, dd => $dd };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+#sub say {\r
+# my ($self) = @_;\r
+# return $self->{dt};\r
+#}\r
+\r
+package node;\r
+\r
+sub new {\r
+ my ($class, $method, $dtdddata) = @_;\r
+\r
+ my $self = {method => $method, dtdddata => $dtdddata };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package nodegroup;\r
+\r
+sub new {\r
+ my ($class, $seq) = @_;\r
+\r
+ my $self = {name => "", fullname => "", my @parentnodegroup => (), seq => $seq};\r
+\r
+ my @childnodegrouptmp = getarray();\r
+ $self->{childnodegroup} = \@childnodegrouptmp;\r
+ my @nodestmp = getarray();\r
+ $self->{nodes} = \@nodestmp;\r
+\r
+ pop(@{$self->{childnodegroup}});\r
+ pop(@{$self->{nodes}});\r
+\r
+# $self->{nodes} = []; #new node;\r
+# $self->{childnodegroup} = (); #new nodegroup;\r
+# $self->{fullname} = "";\r
+# $self->{parentnodegroup} = []; #new nodegroup;\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+sub getarray {\r
+ my @tt = ();\r
+ return \@tt;\r
+}\r
+\r
+sub setname {\r
+ my $self = shift;\r
+ $self->{name} = $_[0];\r
+}\r
+\r
+sub addnode {\r
+ my $self = shift;\r
+# print $_[0]->{method} . "\n";\r
+ push(@{$self->{nodes}}, $_[0]);\r
+}\r
+\r
+sub sortnodes {\r
+\r
+ my $self = shift;\r
+\r
+ my $n = $self->{nodes};\r
+\r
+ #foreach(@{$n}) {\r
+ # print ${$_} . "\n";\r
+ #}\r
+ #print "------------------" . "\n";\r
+\r
+ #foreach(@{$n}) {\r
+ # print ${${$_}->{dtdddata}}->{dtkey} . "\n";\r
+ #}\r
+ @{$n} = sort { lc(${$a}->{method}) cmp lc(${$b}->{method}) || lc(${${$a}->{dtdddata}}->{dtkey}) cmp lc(${${$b}->{dtdddata}}->{dtkey}) || lc(${${$a}->{dtdddata}}->{dt}) cmp lc(${${$b}->{dtdddata}}->{dt}) } @{$n};\r
+}\r
+\r
+sub sortchildnodegroup {\r
+ my $self = shift;\r
+\r
+ my $n = $self->{childnodegroup};\r
+\r
+ @{$n} = sort { lc($a->{name}) cmp lc($b->{name}) } @{$n};\r
+}\r
+\r
+\r
+package groupdesc;\r
+\r
+sub new {\r
+ my ($class, $name, $desc) = @_;\r
+\r
+ my $self = {name => $name, desc => $desc };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}
\ No newline at end of file
--- /dev/null
+#!/usr/bin/perl\r
+#------------------------------------------------------------------------------\r
+# TreeGenerate.pl -i toc.xml -o tocOut.xml -r replace.properties\r
+#------------------------------------------------------------------------------\r
+# doxygen javascript tree remodeling tool\r
+#------------------------------------------------------------------------------\r
+use File::Spec;\r
+\r
+#------------------------------------------------------------------------------\r
+# Global Data declaration\r
+#------------------------------------------------------------------------------\r
+$DEBUG_LEVEL = 0;\r
+$CUR_PART = 0;\r
+$HASH_NAMESPACES = {};\r
+$HASH_CLASS = {};\r
+$HASH_ADDEDPARENTS = {};\r
+$XML_FILE = "";\r
+$OUTPUT_JS_FILE = 0;\r
+$OUTPUT_XML_FILE = 0;\r
+$OPENED_BRACETS_LIST = {};\r
+$LAST_LEVEL = 0;\r
+$START_LIB = 0;\r
+$IN_FUNCTION_LIST = 0;\r
+$OPENED_BRACETS = 0;\r
+$LAST_CLASS="";\r
+$first_one=1;\r
+$label = "";\r
+$replace_properties = {};\r
+#------------------------------------------------------------------------------\r
+# Private functions\r
+#------------------------------------------------------------------------------\r
+sub TabIndent\r
+{\r
+ my ($count) = shift;\r
+ my $res = "";\r
+ my $i = 0;\r
+ while ($i < $count)\r
+ {\r
+ $res = "$res\t";\r
+ $i++;\r
+ }\r
+ return $res;\r
+}\r
+sub CountJsOpened\r
+{\r
+ my $result = 0;\r
+ my $line;\r
+ if ($OUTPUT_JS_FILE)\r
+ {\r
+ open (READ_JS_FH, '<', $OUTPUT_JS_FILE) or die $!;\r
+ while ($line = <READ_JS_FH>)\r
+ {\r
+ while ($line =~ m/(.*)\[(.*)/)\r
+ {\r
+ $line = "$1$2";\r
+ $result++;\r
+ }\r
+ }\r
+ close(READ_JS_FH);\r
+ }\r
+ return $result;\r
+}\r
+\r
+sub CountJsClosed\r
+{\r
+ my $result = 0;\r
+ my $line;\r
+ if ($OUTPUT_JS_FILE)\r
+ {\r
+ open (READ_JS_FH, '<', $OUTPUT_JS_FILE) or die $!;\r
+ while ($line = <READ_JS_FH>)\r
+ {\r
+ while ($line =~ m/(.*)\](.*)/)\r
+ {\r
+ $line = "$1$2";\r
+ $result++;\r
+ }\r
+ }\r
+ close(READ_JS_FH);\r
+ }\r
+ return $result;\r
+}\r
+\r
+sub debug\r
+{\r
+ my ($line) = shift;\r
+ if ($DEBUG_LEVEL >= 3)\r
+ {\r
+ print $line;\r
+ print "\n";\r
+ }\r
+}\r
+\r
+sub info\r
+{\r
+ my ($line) = shift;\r
+ if ($DEBUG_LEVEL >= 2)\r
+ {\r
+ print $line;\r
+ print "\n";\r
+ }\r
+}\r
+\r
+sub warning\r
+{\r
+ my ($line) = shift;\r
+ if ($DEBUG_LEVEL >= 1)\r
+ {\r
+ print $line;\r
+ print "\n";\r
+ }\r
+}\r
+\r
+sub error\r
+{\r
+ my ($line) = shift;\r
+ print $line;\r
+ print "\n";\r
+}\r
+\r
+sub get_common_level\r
+{\r
+ my ($lineA) = shift;\r
+ my ($lineB) = shift;\r
+ #PRINT_JS ("A:$lineA B:$lineB\n");\r
+ #lineB contains lineA\r
+ if ($lineB =~ m/$lineA(.*)/)\r
+ {\r
+ if ($1 =~ m/^:/)\r
+ {\r
+ return $lineA;\r
+ }\r
+ }\r
+\r
+ while ($lineA =~ m/(.*)::([^:]+)/)\r
+ {\r
+ $test = $1;\r
+ #PRINT_JS ("Test:$test A:$lineA B:$lineB\n");\r
+ if ($lineB =~ m/$1(.*)/)\r
+ {\r
+ #PRINT_JS("ret:$test 1:$1\n");\r
+ return $test;\r
+ }\r
+ $lineA = $test;\r
+ }\r
+ return "";\r
+}\r
+\r
+sub get_level\r
+{\r
+ my ($level) = 1;\r
+ my ($line) = shift;\r
+ my ($level_line) = $line;\r
+# if ($line =~ m/\s/)\r
+# {\r
+# die ("Invalid input:$line");\r
+# }\r
+ while ($level_line =~ m/(.*)::([^:]+)/)\r
+ {\r
+ $level_line = "$1";\r
+ $level++;\r
+ }\r
+ debug ("get_level($line)=$level\n");\r
+ return $level;\r
+}\r
+sub PARENT\r
+{\r
+ my ($class) = shift;\r
+ if ($class =~ m/(.*)::([^:]*)/)\r
+ {\r
+ return $1;\r
+ }\r
+ return "";\r
+}\r
+my $STARTED_NMSPC = 0;\r
+\r
+sub PRINT_XML\r
+{\r
+ my $line = shift;\r
+ if ($OUTPUT_XML_FILE)\r
+ {\r
+ print OUTPUT_XML_FH $line;\r
+ }\r
+}\r
+\r
+sub PRINT_JS\r
+{\r
+ my $line = shift;\r
+ if ($OUTPUT_JS_FILE)\r
+ {\r
+ print OUTPUT_JS_FH $line;\r
+ }\r
+}\r
+sub Skip\r
+{\r
+ $arg = shift;\r
+ $page = shift;\r
+ if ($arg=~m/Supported Functions/)\r
+ {\r
+ if ($BUFFER)\r
+ {\r
+ PRINT_JS ("$BUFFER [\n");\r
+ $BUFFER = 0;\r
+ }\r
+ PRINT_JS (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ PRINT_XML (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ PRINT_JS ("[ \"$arg\", \"$page\", null ], \n");\r
+ PRINT_XML ("<topic label=\"$arg\" href=\"$page\" />\n");\r
+ return 1;\r
+ }\r
+ if($arg =~ m/^OpenGL\&\#174\;$/) {\r
+ return 0;\r
+ }\r
+ #return ($arg=~m/(Test)|(Classes)|(Functions)|(Enumerations)|(Defines)|(Typedefs)|(libopenal)|(libfreealut)|(Debugging)|(OpenGL)|(Libxml2)/);\r
+ #return ($arg=~m/(Test)|(Classes)|(Functions)|(Enumerations)|(Defines)|(Typedefs)|(libopenal)|(libfreealut)|(Debugging)|(OpenGL)|(Libxml2)/);\r
+ return ($arg=~m/(Test)|(Classes)|(Functions)|(Enumerations)|(Defines)|(Typedefs)|(libopenal)|(libfreealut)|(Debugging)|(OpenGL)/);\r
+}\r
+my $cur_stack_level = 0;\r
+my $stack;\r
+sub Push\r
+{\r
+ $arg=shift;\r
+# PRINT_JS("Push $arg\n");\r
+ $stack[$cur_stack_level] = $arg;\r
+ $cur_stack_level ++;\r
+}\r
+sub Pop\r
+{\r
+ if (!$cur_stack_level)\r
+ {\r
+ return "";\r
+ }\r
+ $cur_stack_level--;\r
+ $ret = $stack[$cur_stack_level];\r
+# PRINT_JS("Pop $ret\n");\r
+ return $ret;\r
+}\r
+sub GetLastClass\r
+{\r
+ if ($cur_stack_level < 1)\r
+ {\r
+ return "";\r
+ }\r
+ return $stack[$cur_stack_level - 1];\r
+}\r
+sub Unstack\r
+{\r
+}\r
+sub unindent\r
+{\r
+ my ($curr_class) = shift;\r
+ my ($cur_lvl) = shift;\r
+ #there we start from a new list with potential common parents\r
+ my $COMMON = get_common_level($LAST_CLASS, $curr_class);\r
+ my $A=get_level($curr_class);\r
+ my $B=get_level($COMMON);\r
+ my ($current);\r
+ while ($COMMON && !($COMMON =~ m/$LAST_CLASS/)) # if the common part _IS_ the last class, then we simply got up one level\r
+ {\r
+ debug ("COMMON:$COMMON LAST_CLASS:$LAST_CLASS");\r
+ $current = Pop();\r
+\r
+ for (keys %HASH_NAMESPACES)\r
+ {\r
+ my $hash_class = $_;\r
+ my $page = $HASH_NAMESPACES{$_};\r
+ if ($hash_class =~ m/$current\:/)\r
+ {\r
+ for ($i = 0; $i < 2 + $cur_stack_level; $i++)\r
+ {\r
+ PRINT_XML ("\t");\r
+ PRINT_JS ("\t");\r
+ }\r
+ PRINT_JS ("[ \"$hash_class\", \"$page\", null \], \n");\r
+ PRINT_XML ("<topic label=\"$hash_class\" href=\"$page\"/>\n");\r
+ delete $HASH_NAMESPACES{$_};\r
+ }\r
+ }\r
+\r
+ debug ("UNINDENTED:$current");\r
+ #if there remains brothers....\r
+ if ($current)\r
+ {\r
+ for (keys %HASH_NAMESPACES)\r
+ {\r
+ my $class = $_;\r
+ my $page = $HASH_NAMESPACES{$_};\r
+ debug("Testing $class AND '$current'\n");\r
+ if ($class =~ m/$current(.*)/)\r
+ {\r
+ if ($1 =~ m/^:/)\r
+ {\r
+ for ($i = 0; $i < 2 + $cur_stack_level; $i++)\r
+ {\r
+ PRINT_JS ("\t");\r
+ }\r
+ $line = "[\"$class\", \"$page\", null \], ";\r
+ PRINT_JS ("$line\n");\r
+ delete $HASH_NAMESPACES{$_};\r
+ }\r
+ }\r
+ }\r
+ }\r
+\r
+ for ($i = 0; $i < 1 + $cur_stack_level; $i++)\r
+ {\r
+ PRINT_JS ("\t");\r
+ PRINT_XML ("\t");\r
+ }\r
+ $cur_lvl++;\r
+\r
+ PRINT_XML ("</topic>\n");\r
+ PRINT_JS ("\]\],\n");\r
+ $LAST_CLASS=GetLastClass();\r
+ }\r
+}\r
+\r
+sub DISPLAY\r
+{\r
+ my ($level) = shift;\r
+ my ($curr_class) = shift;\r
+ my ($line) = shift;\r
+ my ($cur_lvl) = $level;\r
+ my ($indent) = $LAST_LEVEL;\r
+ my $class="";\r
+ my $page="";\r
+ my ($skip) = 0;\r
+ $CUR_PARENT = PARENT($curr_class);\r
+\r
+ if ($line =~ m/\[\s*"([^"]+)"\s*,\s*"([^"]+)"\s*,\s*null\s*\]\s*,/)\r
+ {\r
+ $TYPE=0;\r
+ $class = $1;\r
+ $page = $2;\r
+ if (!($class =~ m/::/))\r
+ {\r
+ $skip = 1;\r
+ debug ("REJECTED:$class\n");\r
+ }\r
+ }\r
+ elsif ($line =~ m/\[\s*"([^"]+)"\s*,\s*"([^"]+)"\s*,\s*\[/)\r
+ {\r
+ $TYPE=1;\r
+ $class = $1;\r
+ $page = $2;\r
+ }\r
+ else\r
+ {\r
+ print "DISPLAY (level:$level curr_class:$curr_class line:$line\n";\r
+ print "line did not match anything, bailing out\n";\r
+ die;\r
+ }\r
+\r
+ if ($cur_lvl == $LAST_LEVEL)\r
+ {\r
+ $CUR_PARENT = PARENT($curr_class);\r
+ $LAST_PARENT = GetLastClass();\r
+ if (!(($CUR_PARENT =~ m/$LAST_PARENT/) && ($LAST_PARENT =~ m/$CUR_PARENT/)))\r
+ {\r
+ unindent($curr_class, $cur_lvl);\r
+ }\r
+ }\r
+ else\r
+ {\r
+ if (($TYPE == 0) && ($LAST_TYPE == 0))\r
+ {\r
+ unindent($curr_class, $cur_lvl);\r
+ }\r
+ if (($HASH_ADDEDPARENTS{$LAST_PARENT}) && $TYPE)\r
+ {\r
+ unindent($curr_class, $cur_lvl);\r
+ }\r
+ }\r
+ #Push ($CUR_PARENT);\r
+ $LAST_LEVEL = $level;\r
+ if (!$skip)\r
+ {\r
+ for ($i = 0; $i < 1 + $cur_stack_level; $i++)\r
+ {\r
+ PRINT_JS ("\t");\r
+ PRINT_XML ("\t");\r
+ }\r
+ }\r
+ if ($first_one)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_JS ("\t\[\"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ Pop();\r
+ }\r
+ else\r
+ {\r
+ if ($class =~ m/:/)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_JS ("$line");\r
+ }\r
+ }\r
+ else\r
+ {\r
+ if (!$skip)\r
+ {\r
+ $line =~ m/\[\s*"([^"]*)"\s*,\s*"([^"]*)"\s*,\s*\[/;\r
+ PRINT_JS ("[ \"$1\", \"$2\", null ],\n");\r
+ }\r
+ }\r
+ }\r
+\r
+ $class=~s/[<>]/_/g;\r
+ if ($first_one)\r
+ {\r
+ $first_one = 0;\r
+ $LAST_CLASS=$class;\r
+ }\r
+ elsif ($TYPE == 0)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_XML ("<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ }\r
+ elsif ($TYPE == 1)\r
+ {\r
+ if ($class =~ m/:/)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_XML ("<topic label=\"$class\" href=\"$page\" >\n");\r
+ }\r
+ }\r
+ else\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_XML ("<topic label=\"$class\" href=\"$page\" />\n");\r
+ }\r
+ }\r
+ $LAST_CLASS=$class;\r
+ }\r
+ $LAST_TYPE=$TYPE;\r
+}\r
+\r
+sub DISPLAY2\r
+{\r
+ my ($level) = shift;\r
+ my ($curr_class) = shift;\r
+ my ($line) = shift;\r
+ my ($cur_lvl) = $level;\r
+ my ($indent) = $LAST_LEVEL;\r
+ my $class="";\r
+ my $page="";\r
+ my ($skip) = 0;\r
+ $CUR_PARENT = PARENT($curr_class);\r
+\r
+ if ($line =~ m/\[\s*"([^"]+)"\s*,\s*"([^"]+)"\s*,\s*null\s*\]\s*,/)\r
+ {\r
+ $TYPE=0;\r
+ $class = $1;\r
+ $page = $2;\r
+ if (!($class =~ m/::/))\r
+ {\r
+ $skip = 1;\r
+ debug ("REJECTED:$class\n");\r
+ }\r
+ }\r
+ elsif ($line =~ m/\[\s*"([^"]+)"\s*,\s*"([^"]+)"\s*,\s*\[/)\r
+ {\r
+ $TYPE=1;\r
+ $class = $1;\r
+ $page = $2;\r
+ }\r
+ else\r
+ {\r
+ print "DISPLAY (level:$level curr_class:$curr_class line:$line\n";\r
+ print "line did not match anything, bailing out\n";\r
+ die;\r
+ }\r
+\r
+ if ($cur_lvl == $LAST_LEVEL)\r
+ {\r
+ $CUR_PARENT = PARENT($curr_class);\r
+ $LAST_PARENT = GetLastClass();\r
+ if (!(($CUR_PARENT =~ m/$LAST_PARENT/) && ($LAST_PARENT =~ m/$CUR_PARENT/)))\r
+ {\r
+ unindent($curr_class, $cur_lvl);\r
+ }\r
+ }\r
+ else\r
+ {\r
+ if (($TYPE == 0) && ($LAST_TYPE == 0))\r
+ {\r
+ unindent($curr_class, $cur_lvl);\r
+ }\r
+ if (($HASH_ADDEDPARENTS{$LAST_PARENT}) && $TYPE)\r
+ {\r
+ unindent($curr_class, $cur_lvl);\r
+ }\r
+ }\r
+ #Push ($CUR_PARENT);\r
+ $LAST_LEVEL = $level;\r
+ if (!$skip)\r
+ {\r
+ for ($i = 0; $i < 1 + $cur_stack_level; $i++)\r
+ {\r
+ PRINT_JS ("\t");\r
+ PRINT_XML ("\t");\r
+ }\r
+ }\r
+ if ($first_one)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_JS ("\t\[\"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ Pop();\r
+ }\r
+ else\r
+ {\r
+ if ($class =~ m/:/)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_JS ("$line");\r
+ }\r
+ }\r
+ else\r
+ {\r
+ if (!$skip)\r
+ {\r
+ $line =~ m/\[\s*"([^"]*)"\s*,\s*"([^"]*)"\s*,\s*\[/;\r
+ PRINT_JS ("[ \"$1\", \"$2\", null ],\n");\r
+ }\r
+ }\r
+ }\r
+\r
+ $class=~s/[<>]/_/g;\r
+ if ($first_one)\r
+ {\r
+ $first_one = 0;\r
+ $LAST_CLASS=$class;\r
+ }\r
+ elsif ($TYPE == 0)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_XML ("<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ }\r
+ elsif ($TYPE == 1)\r
+ {\r
+ if ($class =~ m/:/)\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_XML ("<topic label=\"$class\" href=\"$page\" >\n");\r
+ }\r
+ }\r
+ else\r
+ {\r
+ if (!$skip)\r
+ {\r
+ PRINT_XML ("<topic label=\"$class\" href=\"$page\" />\n");\r
+ }\r
+ }\r
+ $LAST_CLASS=$class;\r
+ }\r
+ $LAST_TYPE=$TYPE;\r
+}\r
+\r
+#\r
+sub display_subclasses\r
+{\r
+ my ($class) = shift;\r
+ my ($class_line) = $class;\r
+ my ($curr_class) = 0;\r
+\r
+ while ($class_line =~ m/([^:]+)::(.+)$/)\r
+ {\r
+ $class_line = "$2";\r
+ $subclass=$1;\r
+ if ($curr_class)\r
+ {\r
+ $curr_class = "$curr_class\:\:$subclass";\r
+ }\r
+ else\r
+ {\r
+ $curr_class = "$1";\r
+ }\r
+ if ($HASH_NAMESPACES{$curr_class})\r
+ {\r
+ my ($level) = get_level ($curr_class);\r
+ if ($level)\r
+ {\r
+ DISPLAY ($level, $curr_class, "\[ \"$curr_class\", \"$HASH_NAMESPACES{$curr_class}\", \[\n");\r
+ Push ($curr_class);\r
+ $OPENED_BRACETS += 2;\r
+ $HASH_ADDEDPARENTS{$curr_class}=1;\r
+ debug ("OPENED_BRACETS:$OPENED_BRACETS");\r
+ }\r
+ else\r
+ {\r
+ DISPLAY ($level, $curr_class, "\[ \"$curr_class\", \"$HASH_NAMESPACES{$curr_class}\", null \],\n");\r
+ debug ("OPENED_BRACETS:$OPENED_BRACETS");\r
+ }\r
+ delete $HASH_NAMESPACES{$curr_class};\r
+ $HASH_ADDEDPARENTS{$curr_class}=1;\r
+ }\r
+ }\r
+}\r
+\r
+sub display_subclasses2\r
+{\r
+ my ($class) = shift;\r
+ my ($class_line) = $class;\r
+ my ($curr_class) = 0;\r
+\r
+ if ($HASH_NAMESPACES{$class})\r
+ {\r
+ my ($level) = get_level ($class);\r
+ if ($level)\r
+ {\r
+ DISPLAY ($level, $class, "\[ \"$class\", \"$HASH_NAMESPACES{$class}\", \[\n");\r
+ Push ($class);\r
+ $OPENED_BRACETS += 2;\r
+ $HASH_ADDEDPARENTS{$class}=1;\r
+ debug ("OPENED_BRACETS:$OPENED_BRACETS");\r
+ }\r
+ else\r
+ {\r
+ DISPLAY ($level, $class, "\[ \"$class\", \"$HASH_NAMESPACES{$class}\", null \],\n");\r
+ debug ("OPENED_BRACETS:$OPENED_BRACETS");\r
+ }\r
+ delete $HASH_NAMESPACES{$class};\r
+ $HASH_ADDEDPARENTS{$class}=1;\r
+ }\r
+}\r
+\r
+sub parse_classline\r
+{\r
+ my ($line) = shift;\r
+ my ($class) = shift;\r
+ my ($level) = get_level($class);\r
+ my ($page) = shift;\r
+ info ("Class:$class Page:$page Level:$level Line:$line");\r
+ if ($level == 0)\r
+ {\r
+ PRINT_JS ("\t\t\[ \"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ else\r
+ {\r
+ #first print the subclasses\r
+ display_subclasses ($class);\r
+ DISPLAY ($level, $class, "\[ \"$class\", \"$page\", null \],\n");\r
+ }\r
+}\r
+\r
+sub parse_classline2\r
+{\r
+ my ($line) = shift;\r
+ my ($class) = shift;\r
+ my ($level) = get_level($class);\r
+ my ($page) = shift;\r
+ info ("Class:$class Page:$page Level:$level Line:$line");\r
+ if ($level == 0)\r
+ {\r
+ PRINT_JS ("\t\t\[ \"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ else\r
+ {\r
+ #first print the subclasses\r
+ display_subclasses2 ($class);\r
+ #DISPLAY2 (1, $class, "\[ \"$class\", \"$page\", null \],\n");\r
+ }\r
+}\r
+\r
+sub print_header\r
+{\r
+ my ( $volume, $directory, $file ) = File::Spec->splitpath( $FILE );\r
+ my $privfile = $FILE, $compfile = $FILE, $deprfile = $FILE, $visfile = $FILE, $pagfile = $FILE, $featurefile = $FILE;\r
+ $privfile =~ s/$file$/privilege.html/;\r
+ $compfile =~ s/$file$/compatibility.html/;\r
+ $deprfile =~ s/$file$/deprecated.html/;\r
+ #$visfile =~ s/$file$/visibility.html/;\r
+ $pagfile =~ s/$file$/pages.html/;\r
+ $featurefile =~ s/$file$/feature.html/;\r
+\r
+ PRINT_JS "var NAVTREE =\n";\r
+ PRINT_JS "[\n";\r
+ PRINT_JS " [ \"" . $label . "\", \"index.html\", [\n";\r
+ if(-f $pagfile)\r
+ {\r
+ PRINT_JS " [ \"Related Pages\", \"pages.html\", [\n";\r
+ if(-f $compfile)\r
+ {\r
+ PRINT_JS " [ \"Compatibility\", \"compatibility.html\", null ],\n";\r
+ }\r
+ if(-f $deprfile)\r
+ {\r
+ PRINT_JS " [ \"Deprecated List\", \"deprecated.html\", null ],\n";\r
+ }\r
+ if(-f $privfile)\r
+ {\r
+ PRINT_JS " [ \"Privilege\", \"privilegeintro.html\", [\n";\r
+ PRINT_JS " [ \"Privilege Level\", \"privlevel.html\", null ]\n"; \r
+ PRINT_JS " [ \"Privilege\", \"privilege.html\", null ],\n";\r
+ PRINT_JS " ]],\n";\r
+ }\r
+ if(-f $featurefile)\r
+ {\r
+ PRINT_JS " [ \"Required Feature\", \"feature.html\", null ],\n";\r
+ }\r
+ # if(-f $visfile)\r
+ # {\r
+ # PRINT_JS " [ \"Visibility\", \"visibility.html\", null ],\n";\r
+ # }\r
+ PRINT_JS " ]],\n";\r
+ }\r
+\r
+ PRINT_XML "<toc label=\"" . $label . "\" topic=\"index.html\">\n";\r
+ if(-f $pagfile)\r
+ {\r
+ PRINT_XML " <topic label=\"Related Pages\" href=\"pages.html\">\n";\r
+ if(-f $compfile)\r
+ {\r
+ PRINT_XML " <topic label=\"Compatibility\" href=\"compatibility.html\">\n";\r
+ PRINT_XML " </topic>\n";\r
+ }\r
+ if(-f $deprfile)\r
+ {\r
+ PRINT_XML " <topic label=\"Deprecated List\" href=\"deprecated.html\">\n";\r
+ PRINT_XML " </topic>\n";\r
+ }\r
+ if(-f $privfile)\r
+ {\r
+ PRINT_XML " <topic label=\"Privilege\" href=\"privilegeintro.html\">\n";\r
+ PRINT_XML " <topic label=\"Privilege Level\" href=\"privlevel.html\">\n";\r
+ PRINT_XML " </topic>\n";\r
+ PRINT_XML " <topic label=\"Privilege\" href=\"privilege.html\">\n"; \r
+ PRINT_XML " </topic>\n";\r
+ PRINT_XML " </topic>\n";\r
+ }\r
+ if(-f $featurefile)\r
+ {\r
+ PRINT_XML " <topic label=\"Required Feature\" href=\"feature.html\">\n";\r
+ PRINT_XML " </topic>\n";\r
+ }\r
+ # if(-f $visfile)\r
+ # {\r
+ # PRINT_XML " <topic label=\"Visibility\" href=\"visibility.html\">\n";\r
+ # PRINT_XML " </topic>\n";\r
+ # }\r
+ PRINT_XML " </topic>\n";\r
+ }\r
+}\r
+$output_array;\r
+sub buffer_line\r
+{\r
+ my $count = 0;\r
+ my $level;\r
+ $line = shift;\r
+ $output_array = ();\r
+ $output_array[$count]=$line;\r
+ if ($line =~ m/<topic\s+label\s*=\s*"([^"]+)"\s+href\s*=\s*"([^"]+)"\s*>/)\r
+ {\r
+ $level = 1; # number of topics to close\r
+ do {\r
+ debug ("count:$count LEVEL:$level LINE:$line");\r
+ $line = <OUTPUT_XML_FH>;\r
+ $count++;\r
+ $output_array[$count]=$line;\r
+ if ($line =~ m/<topic[^\/]+>/)\r
+ {\r
+ $level++;\r
+ }\r
+ elsif ($line =~ m/<\/topic>/)\r
+ {\r
+ $level--;\r
+ }\r
+ } while ($level);\r
+ }\r
+ elsif ($line =~ m/\[\s*"([^"])*"\s*,\s*"([^"])*"\s*,\s*\[/)\r
+ {\r
+ $level = 1; # number of topics to close\r
+ do {\r
+ debug ("count:$count LEVEL:$level LINE:$line");\r
+ $line = <OUTPUT_JS_FH>;\r
+ $count++;\r
+ $output_array[$count]=$line;\r
+ if ($line =~ m/[\s*"[^"]*"\s*,\s*"[^"]*"\s*,\s*\[/)\r
+ {\r
+ $level++;\r
+ }\r
+ elsif ($line =~ m/\]\s*\]\s*,/)\r
+ {\r
+ $level--;\r
+ }\r
+ } while ($level);\r
+ }\r
+ else\r
+ {\r
+ die("bad line:$line");\r
+ }\r
+ $count++;\r
+ $output_array[$count]=0;\r
+}\r
+\r
+sub unbuffer_array\r
+{\r
+ my $new_array;\r
+ my @array=@_;\r
+ my $line;\r
+ my $nb_arrays = 0;\r
+ my $i;\r
+ my $inner_arrays;\r
+\r
+ @inner_arrays = ();\r
+ debug ("Received:'@array'");\r
+ $line = shift(@array);\r
+\r
+ if ($line =~ m/<topic[^\/]+>/)\r
+ {\r
+ print OUTPUT_FINAL_XML_FH $line;\r
+ }\r
+ elsif ($line =~ m/[\s*"[^"]*"\s*,\s*"[^"]*"\s*,\s*\[/)\r
+ {\r
+ print OUTPUT_FINAL_JS_FH $line;\r
+ }\r
+ elsif (!$line)\r
+ {\r
+ return;\r
+ }\r
+ else\r
+ {\r
+ die ("script error LINE:$line");\r
+ }\r
+ {\r
+\r
+ my $last_line;\r
+ $last_line = "";\r
+ while ($line = shift(@array))\r
+ {\r
+# print OUTPUT_FINAL_JS_FH ("LINE_READ:$line");\r
+ if (($line =~ m/<topic[^\/]+>/) || ($line =~ m/\[\s*"[^"]*"\s*,\s*"[^"]*"\s*,\s*\[/))\r
+ {\r
+ debug ("START BUFFERING:$line");\r
+ #buffer a new array\r
+ my $level = 1;\r
+ my $count = 0;\r
+ @new_array = ();\r
+ $new_array[$count]=$line;\r
+ debug ("Buffering new array#$nb_arrays $line");\r
+ do {\r
+ debug ("LEVEL:$level LINE:$line");\r
+ $line = shift(@array);\r
+ $count++;\r
+ $new_array[$count]=$line;\r
+ if ($line =~ m/<topic[^\/]+>/)\r
+ {\r
+ $level++;\r
+ }\r
+ elsif ($line =~ m/<\/topic>/)\r
+ {\r
+ $level--;\r
+ }\r
+ elsif ($line =~ m/\[\s*"[^"]*"\s*,\s*"[^"]*"\s*,\s*\[/)\r
+ {\r
+ $level++;\r
+ }\r
+ elsif ($line =~ m/\]\s*\]\s*,/)\r
+ {\r
+ $level--;\r
+ }\r
+ } while ($level);\r
+ push @inner_arrays, [@new_array];\r
+ $nb_arrays++;\r
+ }\r
+ else\r
+ {\r
+ debug ("PRINTING:$line");\r
+ if ($line =~ m/<\/topic>/)\r
+ {\r
+ $last_line = $line;\r
+ }\r
+ elsif ($line =~ m/\]\s*\]\s*,/)\r
+ {\r
+ $last_line = $line;\r
+ }\r
+ else\r
+ {\r
+ if ($OUTPUT_XML_FILE)\r
+ {\r
+ print OUTPUT_FINAL_XML_FH $line;\r
+ }\r
+ else\r
+ {\r
+ print OUTPUT_FINAL_JS_FH $line;\r
+ }\r
+ }\r
+ }\r
+ }\r
+ {\r
+ my $tmp_copy;\r
+ for $i ( 0 .. $#inner_arrays ) {\r
+ @{$tmp_copy[$i]} = @{$inner_arrays[$i]};\r
+ }\r
+ for $i ( 0 .. $#inner_arrays ) {\r
+ debug ("\t elt $i is [ @{$tmp_copy[$i]} ],\n");\r
+ unbuffer_array (@{$tmp_copy[$i]});\r
+ }\r
+ }\r
+\r
+ if ($OUTPUT_XML_FILE)\r
+ {\r
+ print OUTPUT_FINAL_XML_FH $last_line;\r
+ }\r
+ if ($OUTPUT_JS_FILE)\r
+ {\r
+ print OUTPUT_FINAL_JS_FH $last_line;\r
+ }\r
+ }\r
+}\r
+\r
+sub trim {\r
+ my @result = @_;\r
+\r
+ foreach (@result) {\r
+ s/^\s+//; \r
+ s/\s+$//; \r
+ }\r
+\r
+ return wantarray ? @result : $result[0];\r
+}\r
+\r
+sub labelparse {\r
+ $ret = $1;\r
+\r
+ # replace\r
+ foreach $_ (keys %replace_properties) {\r
+ $ret =~ s/$_/$replace_properties{$_}/g;\r
+ }\r
+\r
+ return $ret;\r
+}\r
+\r
+#------------------------------------------------------------------------------\r
+# arguments parsing\r
+#------------------------------------------------------------------------------\r
+while ($ARG=shift)\r
+{\r
+ debug("arg:$ARG");\r
+ if ($ARG =~ m/^-i/)\r
+ {\r
+ $FILE = shift;\r
+ if ($FILE)\r
+ {\r
+ debug ("INPUT_FILE:$FILE");\r
+ if ($FILE =~ m/([^\.]+\.js)/)\r
+ {\r
+ $INPUT_TYPE="JS";\r
+ }\r
+ else\r
+ {\r
+ $INPUT_TYPE="XML";\r
+ }\r
+ }\r
+ }\r
+ elsif ($ARG =~ m/^-o/)\r
+ {\r
+ $OUTPUT_FILE = shift;\r
+ if ($OUTPUT_FILE =~ m/^(.+[\/\\])?([^\\\.\/]+\.js)/)\r
+ {\r
+ $OUTPUT_JS_FILE = "$1tmp_$2";\r
+ $OUTPUT_FINAL_JS_FILE = "$1$2";\r
+ open (OUTPUT_JS_FH, '>', $OUTPUT_JS_FILE) or die "Could not open $OUTPUT_JS_FILE Error:$!";\r
+ debug ("OUTPUT_JS_FILE:$OUTPUT_JS_FILE");\r
+ }\r
+ elsif ($OUTPUT_FILE =~ m/^(.+[\/\\])?([^\\\.\/]+\.xml)/)\r
+ {\r
+ $OUTPUT_XML_FILE = "$1tmp_$2";\r
+ $OUTPUT_FINAL_XML_FILE = "$1$2";\r
+ open (OUTPUT_XML_FH, '>', $OUTPUT_XML_FILE) or die "Could not open $OUTPUT_XML_FILE Error:$!";\r
+ debug ("OUTPUT_XML_FILE:$OUTPUT_XML_FILE");\r
+ }\r
+ }\r
+ elsif ($ARG =~ m/^-r/)\r
+ {\r
+ $REPLACE_FILE = shift;\r
+ if ( -f $REPLACE_FILE ) {\r
+ } else {\r
+ die ("Erreur d'ouverture de $REPLACE_FILE");\r
+ }\r
+ }\r
+ else\r
+ {\r
+ $FILE = $ARG;\r
+ $OUTPUT_FILE = $FILE;\r
+ debug ("INPUT_FILE:$FILE");\r
+ if ($FILE =~ m/([^\.]+\.js)/)\r
+ {\r
+ $INPUT_TYPE="JS";\r
+ }\r
+ else\r
+ {\r
+ $INPUT_TYPE="XML";\r
+ }\r
+ if ($OUTPUT_FILE =~ m/^(.+[\/\\])?([^\\\.\/]+\.js)/)\r
+ {\r
+ $OUTPUT_JS_FILE = "$1tmp_$2";\r
+ $OUTPUT_FINAL_JS_FILE = "$1$2";\r
+ open (OUTPUT_JS_FH, '>', $OUTPUT_JS_FILE) or die "Could not open $OUTPUT_JS_FILE Error:$!";\r
+ debug ("OUTPUT_JS_FILE:$OUTPUT_JS_FILE");\r
+ }\r
+ elsif ($OUTPUT_FILE =~ m/^(.+[\/\\])?([^\\\.\/]+\.xml)/)\r
+ {\r
+ $OUTPUT_XML_FILE = "$1tmp_$2";\r
+ $OUTPUT_FINAL_XML_FILE = "$1$2";\r
+ open (OUTPUT_XML_FH, '>', $OUTPUT_XML_FILE) or die "Could not open $OUTPUT_XML_FILE Error:$!";\r
+ debug ("OUTPUT_XML_FILE:$OUTPUT_XML_FILE");\r
+ }\r
+ }\r
+}\r
+if (((!$OUTPUT_XML_FILE) && (!$OUTPUT_JS_FILE)) || (!$FILE))\r
+{\r
+ print "usage: \n";\r
+ print " script.pl -i input.js -o navtree.js\n";\r
+ print " script.pl -i toc.xml -o newtoc.xml\n";\r
+ print " Will output navtree.js and newtoc.xml from data in input.js and toc.xml\n";\r
+ print "OR\n";\r
+ print " script.pl toc.xml\n";\r
+ print " script.pl navtree.js\n";\r
+ print " Will read navtree.js or toc.xml and output the modified files to replace them\n";\r
+ die;\r
+}\r
+\r
+#------------------------------------------------------------------------------\r
+# replace properies read\r
+#------------------------------------------------------------------------------\r
+if($REPLACE_FILE) {\r
+ open(FILEHDL,$REPLACE_FILE) || die ("Erreur d'ouverture de $FILE");\r
+ while ($line = <FILEHDL>)\r
+ {\r
+ chomp $line;\r
+ # ignore blanks and lines that start with #\r
+ if (($line ne '') && ($line !~ /^#/)) {\r
+ ($parameterName, $parameterValue) = split(/=/, $line);\r
+ $replace_properties{trim($parameterName)} = trim($parameterValue);\r
+ #print $parameterName . " : " . $parameterValue . " : " . $replace_properties{trim($parameterName)} . "\r\n";\r
+ }\r
+ }\r
+ close(FILEHDL);\r
+}\r
+#------------------------------------------------------------------------------\r
+# toc label search\r
+#------------------------------------------------------------------------------\r
+open(FILEHDL,$FILE) || die ("Erreur d'ouverture de $FILE");\r
+while ($line = <FILEHDL>)\r
+{\r
+ if($line =~ m/\<toc label=\"([^\"]+)\"/)\r
+ {\r
+ $label = $1;\r
+ last;\r
+ }\r
+}\r
+close (FILEHDL);\r
+\r
+#------------------------------------------------------------------------------\r
+# engine itself\r
+#------------------------------------------------------------------------------\r
+print_header();\r
+#First read the namespaces\r
+open(FILEHDL,$FILE) || die ("Erreur d'ouverture de $FILE");\r
+while ($line = <FILEHDL>)\r
+{\r
+ debug ("Reading:$line");\r
+ if (($line =~ m/\s*\[\s*\"Namespace List\"\s*,\s*\"[^\"]+\"\s*,\s*\[\s*/)\r
+ || ($line =~ m/\s*<topic\s+label\s*=\s*"Namespace List"\s+href\s*=\s*"[^"]+"\s*>\s*/))\r
+ {\r
+ info ("Entered the namespaces");\r
+ $CUR_PART = "namespaces";\r
+ }\r
+ elsif (($CUR_PART =~ m/namespaces/) &&\r
+ (($line =~ m/\s*\]\s*\],\s*/) || ($line =~ m/\s*<\/topic>\s*/))\r
+ )\r
+ {\r
+ info ("Left the namespaces");\r
+ $CUR_PART = 0;\r
+ }\r
+ elsif ($CUR_PART =~ m/namespaces/)\r
+ {\r
+ if (($line =~ m/\s*\[\s*\"([^\"]+)\"\s*,\s*\"([^\"]+)\"\s*,\s*null\s*\][\s*,]*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"([^\"]+)"\s*href\s*=\s*"([^"]+)"\s*\/>\s*/))\r
+ {\r
+ my $class = $1;\r
+ my $page = $2;\r
+ $HASH_NAMESPACES{$class}=$page;\r
+ info ("HASH_NAMESPACES['$class'] <= '$page'");\r
+ }\r
+ }\r
+}\r
+close (FILEHDL);\r
+\r
+PRINT_JS ("\t[ \"Namespace List\", \"namespaces.html\", [\n");\r
+PRINT_XML ("\t<topic label=\"Namespace List\" href=\"namespaces.html\">\n");\r
+\r
+my @arrClass;\r
+open(FILEHDL,$FILE) || die ("Erreur d'ouverture de $FILE");\r
+#Then do the actual job\r
+while ($line = <FILEHDL>)\r
+{\r
+ debug ("Reading:$line");\r
+ if (($line =~ m/\s*\[\s*\"Class List\"\s*,\s*\"[^\"]+\"\s*,\s*\[\s*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"Class List"\s*href\s*=\s*"[^"]+"\s*>\s*/))\r
+ {\r
+ info ("Entered the classes");\r
+ $CUR_PART = "classes";\r
+ }\r
+ elsif (($CUR_PART =~ m/classes/) && (($line =~ m/\s*\]\s*\],\s*/)\r
+ || ($line =~ m/\s*<\/topic>\s*/)))\r
+ {\r
+ info ("Left the classes");\r
+ $CUR_PART = 0;\r
+ }\r
+ elsif ($CUR_PART =~ m/classes/)\r
+ {\r
+ if (($line =~ m/\s*\[\s*\"([^\"]+)\"\s*,\s*\"([^\"]+)\"\s*,\s*null\s*\][\s,]*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"([^\"]+)"\s*href\s*=\s*"([^"]+)"\s*\/>\s*/))\r
+ {\r
+ my $class = $1;\r
+ my $page = $2;\r
+\r
+ while($class =~ m/::[^:]+$/ || $class =~ m/^[^:]+$/ )\r
+ {\r
+ if($page =~ m/^structTizen/)\r
+ {\r
+ #structTizen remove\r
+ last;\r
+ }\r
+ else\r
+ {\r
+ if(exists $HASH_NAMESPACES{$class})\r
+ {\r
+ if(exists $HASH_CLASS{$class})\r
+ {\r
+ push @{$HASH_CLASS{$class}}, $line;\r
+ }\r
+ else\r
+ {\r
+ my @arr = $line;\r
+ $HASH_CLASS{$class} = \@arr;\r
+ }\r
+ \r
+ #print $class . " : " . ($#{$HASH_CLASS{$class}} + 1) . "\r\n";\r
+ last;\r
+ }\r
+ $class =~ s/::[^:]+$//;\r
+ }\r
+ }\r
+ }\r
+\r
+ }\r
+}\r
+close (FILEHDL);\r
+\r
+my @arrNamespace;\r
+\r
+foreach $_ (sort keys %HASH_NAMESPACES) {\r
+ push(@arrNamespace, $_);\r
+}\r
+\r
+while($#arrNamespace + 1 > 0)\r
+{\r
+ my $namespace = shift @arrNamespace;\r
+ my $namespacepage = $HASH_NAMESPACES{$namespace};\r
+ #my $reg = $namespace . "::" . "[^:]+\$";\r
+\r
+ if($namespace eq "")\r
+ {\r
+ next;\r
+ }\r
+\r
+ my $isChildExist = 0;\r
+ if($#arrNamespace + 1 > 0 && !($namespace eq "Tizen"))\r
+ {\r
+ my $namespace2 = shift @arrNamespace;\r
+ my $tempna = $namespace . "::";\r
+\r
+ if($namespace2 =~ m/$tempna/)\r
+ {\r
+ $isChildExist = 1;\r
+ }\r
+ unshift @arrNamespace, $namespace2;\r
+ }\r
+\r
+ if(exists $HASH_CLASS{$namespace} || $isChildExist == 1)\r
+ {\r
+ my $class = $namespace;\r
+ my $page = $namespacepage;\r
+\r
+ PRINT_JS ("\t\t\[ \"$class\", \"$page\", \[\n");\r
+ PRINT_XML ("\t\t<topic label=\"$class\" href=\"$page\">\n");\r
+\r
+ foreach(@{$HASH_CLASS{$namespace}})\r
+ {\r
+ my $line = $_;\r
+ if (($line =~ m/\s*\[\s*\"([^\"]+)\"\s*,\s*\"([^\"]+)\"\s*,\s*null\s*\][\s,]*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"([^\"]+)"\s*href\s*=\s*"([^"]+)"\s*\/>\s*/))\r
+ {\r
+ my $class = $1;\r
+ my $page = $2;\r
+\r
+ PRINT_JS ("\t\t\t\[ \"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t\t\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ }\r
+\r
+ while($#arrNamespace + 1 > 0)\r
+ {\r
+ my $namespace2 = shift @arrNamespace;\r
+ my $namespacepage2 = $HASH_NAMESPACES{$namespace2};\r
+\r
+ my $tempna = $namespace . "::";\r
+\r
+ if($namespace2 =~ m/$tempna/)\r
+ {\r
+ if($#{$HASH_CLASS{$namespace2}} + 1 > 0) \r
+ {\r
+ PRINT_JS ("\t\t\t\[ \"$namespace2\", \"$namespacepage2\", \[\n");\r
+ PRINT_XML ("\t\t\t<topic label=\"$namespace2\" href=\"$namespacepage2\">\n");\r
+\r
+ foreach(@{$HASH_CLASS{$namespace2}})\r
+ {\r
+ my $line = $_;\r
+ if (($line =~ m/\s*\[\s*\"([^\"]+)\"\s*,\s*\"([^\"]+)\"\s*,\s*null\s*\][\s,]*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"([^\"]+)"\s*href\s*=\s*"([^"]+)"\s*\/>\s*/))\r
+ {\r
+ my $class = $1;\r
+ my $page = $2;\r
+\r
+ PRINT_JS ("\t\t\t\t\[ \"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t\t\t\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+ }\r
+\r
+ PRINT_JS ("\t\t\t\]\],\n");\r
+ PRINT_XML ("\t\t\t</topic>\n");\r
+ }\r
+ else\r
+ {\r
+ PRINT_JS ("\t\t\t\[ \"$namespace2\", \"$namespacepage2\", null \],\n");\r
+ PRINT_XML ("\t\t\t<topic label=\"$namespace2\" href=\"$namespacepage2\"/>\n");\r
+ }\r
+ }\r
+ else\r
+ {\r
+ unshift @arrNamespace, $namespace2;\r
+ last;\r
+ }\r
+ }\r
+\r
+ PRINT_JS ("\t\t\]\],\n");\r
+ PRINT_XML ("\t\t</topic>\n");\r
+ }\r
+ else\r
+ {\r
+ my $line = "";\r
+ my $class = $namespace;\r
+ my $page = $namespacepage;\r
+ PRINT_JS ("\t\t\[ \"$class\", \"$page\", null \],\n");\r
+ PRINT_XML ("\t\t<topic label=\"$class\" href=\"$page\"/>\n");\r
+ }\r
+}\r
+\r
+PRINT_JS ("\t\]\],\n");\r
+PRINT_XML ("\t</topic>\n");\r
+\r
+open(FILEHDL,$FILE) || die ("Erreur d'ouverture de $FILE");\r
+#Libraries and end functions\r
+$SKIP_LEVEL = -1;\r
+$CUR_LIB_LEVEL = 0;\r
+$Newlib = 0;\r
+@arrLibrary = ();\r
+@arrNewlib = ();\r
+while ($line = <FILEHDL>)\r
+{\r
+ debug ("Reading:$line");\r
+ if (($line =~ m/\s*\[\s*\"Libraries\"\s*,\s*\"[^\"]+\"\s*,\s*\[\s*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"Libraries"\s*href\s*=\s*"[^"]+"\s*>\s*/))\r
+ {\r
+ info ("Entered the libraries");\r
+ $CUR_PART = "libraries";\r
+ PRINT_JS ("\t[ \"Libraries\", \"modules.html\", [\n");\r
+ PRINT_XML("\t<topic label=\"Libraries\" href=\"modules.html\">\n");\r
+ $CUR_LIB_LEVEL = 0;\r
+ }\r
+ elsif (($line =~ m/\s*\[\s*\"Class List\"\s*,\s*\"[^\"]+\"\s*,\s*\[\s*/)\r
+ || ($line =~ m/\s*<topic\s*label\s*=\s*"Class List"\s*href\s*=\s*"[^"]+"\s*>\s*/))\r
+ {\r
+ info ("Left libraries");\r
+ $CUR_PART = 0;\r
+ PRINT_JS (" ]]\n");\r
+ }\r
+ elsif ($CUR_PART =~ m/libraries/)\r
+ {\r
+ if (($line =~ m/\\]\s*\]/)\r
+ || ($line =~ m/\<\/topic>/))\r
+ {\r
+ my $current = Pop();\r
+ $CUR_LIB_LEVEL --;\r
+ debug ("closing1:$current LEVEL:$CUR_LIB_LEVEL SKIP:$SKIP_LEVEL\n");\r
+ if ($SKIP_LEVEL == -1)\r
+ {\r
+ if ($BUFFER)\r
+ {\r
+ PRINT_JS("$BUFFER null ], \n");\r
+ $BUFFER = 0;\r
+ }\r
+ else\r
+ {\r
+ PRINT_JS (" ] ],\n");\r
+ }\r
+ #PRINT_XML (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ #PRINT_XML ("</topic>\n");\r
+ }\r
+ if ($SKIP_LEVEL == $CUR_LIB_LEVEL)\r
+ {\r
+ $SKIP_LEVEL = -1;\r
+ }\r
+ }\r
+ elsif (($line =~ m/\s*<topic\s*label\s*=\s*"([^"]+)"\s*href\s*=\s*"([^"]+)"\s*>/)\r
+ || ($line =~ m/"([^"]+)"\s*,\s*"([^"]+)".*\[/))\r
+ {\r
+ $label = labelparse($1);\r
+ $labelhtml = $2;\r
+\r
+ #if( $1 eq "Standard C++ Library" && $Newlib == 1)\r
+ #{\r
+ #print $1 . " : " . $2 . "\r\n";\r
+ # $CUR_LIB_LEVEL --;\r
+ # PRINT_XML (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ # PRINT_XML ("</topic>\n");\r
+ # $Newlib = 0;\r
+ #}\r
+ if (($SKIP_LEVEL == -1) && (Skip ($label,$2)))\r
+ {\r
+ $SKIP_LEVEL = $CUR_LIB_LEVEL;\r
+ }\r
+ $CUR_LIB_LEVEL ++;\r
+ if ($SKIP_LEVEL == -1)\r
+ {\r
+ if ($BUFFER)\r
+ {\r
+ PRINT_JS ("$BUFFER [\n");\r
+ $BUFFER = 0;\r
+ }\r
+ $BUFFER = TabIndent ($CUR_LIB_LEVEL);\r
+ $BUFFER = "$BUFFER\[ \"$label\", \"$2\",";\r
+ #PRINT_XML (TabIndent ($CUR_LIB_LEVEL));\r
+ #PRINT_XML ("<topic label=\"$label\" href=\"$2\">\n");\r
+ if($label ne "Newlib" && $labelhtml =~ m/_Newlib/) {\r
+ push(@arrNewlib, "\t\t\t<topic label=\"$label\" href=\"$labelhtml\">\n\t\t\t</topic>\n");\r
+ } elsif($label eq "Newlib") {\r
+ push(@arrLibrary, "\t\t<topic label=\"$label\" href=\"$labelhtml\">\n");\r
+ } else {\r
+ push(@arrLibrary, "\t\t<topic label=\"$label\" href=\"$labelhtml\">\n\t\t</topic>\n");\r
+ }\r
+ }\r
+ Push ("$label");\r
+ if( $1 eq "Newlib")\r
+ {\r
+ $line = <FILEHDL>;\r
+ $Newlib = 1;\r
+ #print $1 . " a:b " . $2 . "\r\n";\r
+ }\r
+ }\r
+ elsif (($line =~ m/\s*<topic\s*label\s*=\s*"([^"]+)"\s*href\s*=\s*"([^"]+)"\s*\/>/)\r
+ || ($line =~ m/"([^"]+)"\s*,\s*"([^"]+)".*\]/))\r
+\r
+ {\r
+ $label = labelparse($1);\r
+\r
+ if (($SKIP_LEVEL == -1) && (!Skip ($label,$2)))\r
+ {\r
+ if ($BUFFER)\r
+ {\r
+ PRINT_JS ("$BUFFER [\n");\r
+ $BUFFER = 0;\r
+ }\r
+ PRINT_JS (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ PRINT_JS ("[ \"$label\", \"$2\", null ], \n");\r
+ PRINT_XML (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ PRINT_XML ("<topic label=\"$label\" href=\"$2\"/>\n");\r
+ }\r
+ }\r
+ elsif (($line =~ m/<\/topic\s*>/)\r
+ || ($line =~ m/\]\s*\]/))\r
+ {\r
+ my $current = Pop();\r
+ $CUR_LIB_LEVEL --;\r
+ if ($SKIP_LEVEL == -1)\r
+ {\r
+ PRINT_JS (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ PRINT_XML (TabIndent ($CUR_LIB_LEVEL + 1));\r
+ if ($BUFFER)\r
+ {\r
+ PRINT_JS("$BUFFER null ], \n");\r
+ $BUFFER = 0;\r
+ }\r
+ else\r
+ {\r
+ PRINT_JS ("]],\n");\r
+ }\r
+ PRINT_XML ("</topic>\n");\r
+ }\r
+ if ($SKIP_LEVEL == $CUR_LIB_LEVEL)\r
+ {\r
+ $SKIP_LEVEL = -1;\r
+ }\r
+ }\r
+ }\r
+ elsif ($line =~ m/<\/toc>/)\r
+ {\r
+ #library print\r
+ foreach(@arrLibrary) {\r
+ if($_ =~ m/Libxml2/) {\r
+ PRINT_XML ($_);\r
+ }\r
+ }\r
+ foreach(@arrLibrary) {\r
+ if($_ =~ m/Standard EGLIBC/) {\r
+ PRINT_XML ($_);\r
+ }\r
+ }\r
+ foreach(@arrLibrary) {\r
+ if($_ =~ m/Standard C/) {\r
+ PRINT_XML ($_);\r
+ }\r
+ }\r
+ foreach(@arrLibrary) {\r
+ if($_ =~ m/Standard/) {\r
+ } elsif($_ =~ m/Libxml2/) {\r
+ } elsif($_ =~ m/Newlib/) {\r
+ PRINT_XML ($_);\r
+ foreach(@arrNewlib) {\r
+ PRINT_XML ($_);\r
+ }\r
+ PRINT_XML ("\t\t</topic>\n");\r
+ } else {\r
+ PRINT_XML ($_);\r
+ }\r
+ }\r
+\r
+ if($#arrLibrary + 1 > 0) {\r
+ PRINT_XML ("\t</topic>");\r
+ }\r
+\r
+ if (!($CUR_PART =~ m/functions/))\r
+ {\r
+ PRINT_JS ("];\n");\r
+ PRINT_XML ("\n</toc>\n");\r
+ }\r
+ $CUR_PART = "functions";\r
+ }\r
+ elsif ($line =~ m/\s*function\s*[^\(\s]+\s*\([^\)]+\)\s*/)\r
+ {\r
+ info ("Entered the End function statements");\r
+ if (!($CUR_PART =~ m/functions/))\r
+ {\r
+ close (OUTPUT_JS_FH);\r
+ open (OUTPUT_JS_FH, '>>', $OUTPUT_JS_FILE) or die $!;\r
+ my $closed = CountJsClosed();\r
+ my $opened = CountJsOpened();\r
+ $closed++; #For the last ]; which counts as 1\r
+ while ($closed < $opened)\r
+ {\r
+ PRINT_JS ("]");\r
+ $closed++;\r
+ }\r
+ PRINT_JS ("\n");\r
+ PRINT_JS ("];\n");\r
+ PRINT_XML ("\n</toc>\n");\r
+ }\r
+\r
+ $CUR_PART = "functions";\r
+ PRINT_JS ("$line");\r
+ }\r
+ elsif ($CUR_PART =~ m/functions/)\r
+ {\r
+ PRINT_JS ("$line");\r
+ }\r
+}\r
+close (FILEHDL);\r
+\r
+if ($OUTPUT_JS_FILE)\r
+{\r
+ close (OUTPUT_JS_FH);\r
+ # Second step work in progress\r
+ open (OUTPUT_JS_FH, '<', $OUTPUT_JS_FILE) or die $!;\r
+ open (OUTPUT_FINAL_JS_FH, '>', $OUTPUT_FINAL_JS_FILE) or die $!;\r
+ my ($IN_NAMESPACES) = 0;\r
+ my $nb_arrays = 0;\r
+ while ($line = <OUTPUT_JS_FH>)\r
+ {\r
+ print OUTPUT_FINAL_JS_FH $line;\r
+ }\r
+ close (OUTPUT_FINAL_JS_FH);\r
+ close (OUTPUT_JS_FH);\r
+ unlink($OUTPUT_JS_FILE);\r
+}\r
+\r
+if ($OUTPUT_XML_FILE)\r
+{\r
+ close (OUTPUT_XML_FH);\r
+ # Second step work in progress\r
+ open (OUTPUT_XML_FH, '<', $OUTPUT_XML_FILE) or die $!;\r
+ open (OUTPUT_FINAL_XML_FH, '>', $OUTPUT_FINAL_XML_FILE) or die $!;\r
+ my ($IN_NAMESPACES) = 0;\r
+ my $nb_arrays = 0;\r
+ while ($line = <OUTPUT_XML_FH>)\r
+ {\r
+ print OUTPUT_FINAL_XML_FH $line;\r
+ }\r
+ close (OUTPUT_FINAL_XML_FH);\r
+ close (OUTPUT_XML_FH);\r
+ unlink($OUTPUT_XML_FILE);\r
+} # OUTPUT_XML_FILE\r
+\r
+#------------------------------------------------------------------------------\r
+# index.html check .. for pages.html\r
+#------------------------------------------------------------------------------\r
+my ( $volume, $directory, $file ) = File::Spec->splitpath( $FILE );\r
+my $preDir = $FILE;\r
+$preDir =~ s/$file$//;\r
+\r
+my $pagesFile = $preDir . "pages.html";\r
+\r
+my $CUR_STATE = 0;\r
+my $itemcnt = 0;\r
+\r
+if(-f $pagesFile)\r
+{\r
+ open(FILEHDL,$pagesFile) || die ("Erreur d'ouverture de $pagesFile");\r
+ #Then do the actual job\r
+ while ($line = <FILEHDL>)\r
+ {\r
+ #<div class="contents">\r
+ #<li><a class="el" href="deprecated.html">Deprecated List</a>\r
+ debug ("Reading:$line");\r
+ if ($CUR_STATE == 0 && $line =~ m/\<div class=\"contents\"\>/)\r
+ {\r
+ $CUR_STATE = 1;\r
+ }\r
+ elsif ($CUR_STATE == 1 && $line =~ m/^\<\/div\>$/)\r
+ {\r
+ $CUR_STATE = 0;\r
+ last;\r
+ }\r
+ elsif ($CUR_STATE == 1 && $line =~ m/\<li[^\>]*\>\<a class=\"el\"/)\r
+ {\r
+ $itemcnt++;\r
+ }\r
+ }\r
+ close (FILEHDL);\r
+}\r
+else\r
+{\r
+ $itemcnt = 0;\r
+}\r
+\r
+if($itemcnt > 0)\r
+{\r
+ exit;\r
+}\r
+\r
+if($preDir eq "")\r
+{\r
+ $preDir = "./";\r
+}\r
+\r
+opendir DH, $preDir or die "Couldn't open the current directory : $preDir";\r
+while($_ = readdir(DH))\r
+{\r
+ next if $_ =~ /^\.\.?$/;\r
+ #if ($_ =~ m/^class/)\r
+ if ($_ =~ m/html$/)\r
+ {\r
+ open(FILEHDL, $preDir . $_) || die ("Error d'ouverture de " . $preDir . $_);\r
+ my @line_list = ( );\r
+\r
+ while ($line = <FILEHDL>)\r
+ {\r
+ debug ("Reading:$line");\r
+ if ($line =~ m/\<a href=\"pages.html\"\>/)\r
+ {\r
+ }\r
+ else\r
+ {\r
+ push (@line_list, $line);\r
+ }\r
+ }\r
+ close (FILEHDL);\r
+ \r
+ open (FILEHDL, '>', $preDir . $_) or die $!;\r
+ foreach(@line_list)\r
+ {\r
+ print FILEHDL $_;\r
+ }\r
+ close (FILEHDL);\r
+ }\r
+}\r
+closedir DH;\r
+\r
--- /dev/null
+use strict;\r
+use warnings;\r
+\r
+my $inputfilename = "";\r
+my $outputfilename = "";\r
+\r
+if($#ARGV + 1 == 1) {\r
+ $inputfilename = $ARGV[0];\r
+ $outputfilename = $ARGV[0];\r
+} elsif ($#ARGV + 1 == 2){\r
+ $inputfilename = $ARGV[0];\r
+ $outputfilename = $ARGV[1];\r
+} else {\r
+ $inputfilename = "visibility.html";\r
+ $outputfilename = "test.html";\r
+}\r
+\r
+# Input File Exist Check\r
+if(fileexist($inputfilename) == 0)\r
+{\r
+ print "File not found : " . $inputfilename;\r
+ exit;\r
+}\r
+\r
+my $originalfile = fileload ($inputfilename);\r
+my $top = gettop ($originalfile);\r
+my $content = getcontent ($originalfile);\r
+my $bottom = getbottom ($originalfile);\r
+\r
+my @list = ();\r
+my @printlist = ();\r
+\r
+initList();\r
+contentToObject($content);\r
+\r
+#@list = sort { lc($a->{name}) cmp lc($b->{name}) } @list;\r
+\r
+foreach(@list) {\r
+ sortnode(\$_);\r
+}\r
+\r
+my $htmls = createhtml();\r
+savefile($top, $htmls, $bottom, $outputfilename);\r
+\r
+sub fileexist {\r
+ if ( -f $_[0] ) {\r
+ return 1;\r
+ } else {\r
+ return 0;\r
+ }\r
+}\r
+\r
+sub fileload {\r
+ open FILE, $_[0];\r
+ my @lines = <FILE>;\r
+ close FILE;\r
+ join "", @lines;\r
+}\r
+\r
+sub getarray {\r
+ my @tt = ();\r
+ return \@tt;\r
+}\r
+\r
+sub gettop {\r
+ #substr($_[0], 0, index($_[0], "<dl>") - 1);\r
+ substr($_[0], 0, index($_[0], "<dl"));\r
+}\r
+\r
+sub getcontent {\r
+ my $first = index($_[0], "<dl");\r
+ substr($_[0], $first, rindex($_[0], "</dl>") - $first + 5);\r
+}\r
+\r
+sub getbottom {\r
+ substr($_[0], rindex($_[0], "</dl>") + 5);\r
+}\r
+\r
+sub initList {\r
+ my $ng = new nodegroup(); $ng->setname("public"); addkey(\@list, $ng);\r
+ my $ng2 = new nodegroup(); $ng2->setname("public-extended"); addkey(\@list, $ng2);\r
+ my $ng3 = new nodegroup(); $ng3->setname("partner"); addkey(\@list, $ng3);\r
+ my $ng4 = new nodegroup(); $ng4->setname("partner-operator"); addkey(\@list, $ng4);\r
+ my $ng5 = new nodegroup(); $ng5->setname("partner-manufacturer"); addkey(\@list, $ng5);\r
+ my $ng6 = new nodegroup(); $ng6->setname("partner-extended"); addkey(\@list, $ng6);\r
+ my $ng7 = new nodegroup(); $ng7->setname("private"); addkey(\@list, $ng7);\r
+}\r
+\r
+sub contentToObject {\r
+ my @arr = getParserDL($_[0]);\r
+\r
+ my $str;\r
+\r
+ foreach $str (@arr) {\r
+ my @dt = ($str =~ /<dt>(?<dt>.+)<\/dt>/);\r
+ my @aa2 = ($dt[0] =~ /(?<dtcategory>[^<]+)<a[^>]+>(?<dtkey>[^>]+)<\/a>/);\r
+ my $dtCategory = $aa2[0];\r
+ my $dtkey = $aa2[1];\r
+\r
+ if (trim($dtCategory) eq "File") {\r
+ next;\r
+ } else {\r
+ if (trim($dtCategory) eq "Class") {\r
+ next;\r
+ } else {\r
+ }\r
+ }\r
+\r
+ my @aa3 = ($str =~ /<dd>(?<dd>[\s\S]+)<\/dd>/);\r
+ $aa3[0] =~ s/<[^<]+>//g;\r
+ my $dd = trim($aa3[0]);\r
+\r
+ #print " : " . $eachdd;\r
+ if($dd =~ /(.+)/) {\r
+ $dd = $1;\r
+ }\r
+\r
+ if($dd eq "") {\r
+ next;\r
+ }\r
+\r
+ if(containskey(\@list, $dd) == 0) {\r
+ print "\"" . $dd . "\" not found.";\r
+ exit;\r
+ }\r
+\r
+ my $dtdddata = new dtdd($dt[0], $dtkey, $dd);\r
+ my $n = new node($dtkey, \$dtdddata);\r
+\r
+ my $findng = findnode(\@list, $dd);\r
+ #print "search : " . $findng->{name} . "\n";\r
+ my $ng = setnode(\$findng, $dtkey);\r
+ #print "ng : " . $ng->{name} . "\n";\r
+ #push($ng->{nodes}, $n);\r
+ $ng->addnode(\$n);\r
+ } \r
+}\r
+\r
+sub createhtml {\r
+ my $java = "";\r
+ $java = "<script type=\"text/javascript\">" . "\n"\r
+ . "//<![CDATA[" . "\n"\r
+ . " function divshow(id) {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + id);" . "\n"\r
+ . " var ediv = document.getElementById(\"div_\" + id);" . "\n"\r
+ . " if(eicon.innerHTML == \"-\") {" . "\n"\r
+ . " ediv.style.display = \"none\";" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " } else {" . "\n"\r
+ . " ediv.style.display = \"\";" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " function divallshow(istrue) {" . "\n"\r
+ . " var ediv = document.getElementsByTagName(\"div\");" . "\n"\r
+ . " if(istrue == true) {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " if(eicon != null) {" . "\n"\r
+ . " eicon.innerHTML = \"-\";" . "\n"\r
+ . " ediv[cnt].style.display = \"\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " } else {" . "\n"\r
+ . " for(var cnt = 0; cnt < ediv.length; cnt++) {" . "\n"\r
+ . " if(ediv[cnt].id.substr(0,4) == \"div_\") {" . "\n"\r
+ . " var eicon = document.getElementById(\"icon_\" + ediv[cnt].id.substr(4));" . "\n"\r
+ . " if(eicon != null) {" . "\n"\r
+ . " eicon.innerHTML = \"+\";" . "\n"\r
+ . " ediv[cnt].style.display = \"none\";" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . " }" . "\n"\r
+ . "//]]>" . "\n"\r
+ . "</script>" . "\n";\r
+\r
+ my $html = $java . "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\" style=\"border-bottom: 1px solid #A8B8D9; height: 15px;\">" . "\n"\r
+ . "<div class=\"memname\" style=\"float: right;\">" . "\n"\r
+ . "<a href=\"javascript:divallshow(true)\" class=\"el\">All Expand</a> " . "\n"\r
+ . "<a href=\"javascript:divallshow(false)\" class=\"el\">All Collapse</a> " . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+\r
+ my $seq = 1;\r
+\r
+ # \r
+ foreach(@list) {\r
+ my $ng = $_;\r
+\r
+ my @nodes = @{$ng->{nodes}};\r
+ my @childng = @{$ng->{childnodegroup}};\r
+\r
+ if($#nodes + 1 + $#childng + 1 > 0) {\r
+ push(@printlist, $ng);\r
+ }\r
+ }\r
+\r
+ foreach(@printlist) {\r
+ my $ng = $_;\r
+\r
+ my @nodes = @{$ng->{nodes}};\r
+ my @childng = @{$ng->{childnodegroup}};\r
+\r
+ if($#nodes + 1 + $#childng + 1 > 0) {\r
+ #print $#nodes + 1 + $#childng + 1 . "\r\n";\r
+ createhtmlchild($ng, \$html, \$seq, 0, $#printlist + 1);\r
+ }\r
+ }\r
+\r
+ return $html;\r
+}\r
+\r
+sub createhtmlchild {\r
+ my $ng = $_[0];\r
+ my $html = $_[1];\r
+ my $seq = $_[2];\r
+ my $depth = $_[3];\r
+ my $siblingcount = $_[4];\r
+\r
+ my $id = zero_fill(${$seq}, 10);\r
+ ${$seq} = ${$seq} + 1;\r
+ my $isDiv1 = 0;\r
+ my $isDiv2 = 0;\r
+\r
+ #print $depth . " : " . $ng->{name} ." : " . $ng->{fullname} . " : " . $siblingcount . "\r\n";\r
+ if($depth == 0) {\r
+ if($siblingcount == 1) {\r
+ ${$html} .= "<div style=\"\" id=\"div_$id\">" . "\n";\r
+ } else {\r
+ ${$html} .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{name}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ }\r
+ $isDiv1 = 1;\r
+ }\r
+\r
+ if($depth == 2) {\r
+ ${$html} .= "<h2><a href=\"javascript:divshow('$id')\" id=\"icon_$id\" class=\"el\">+</a>". "\n"\r
+ . "<span>$ng->{fullname}</span></h2>". "\n"\r
+ . "<div style=\"display: none;\" id=\"div_$id\">" . "\n";\r
+ $isDiv1 = 1;\r
+ }\r
+\r
+ my @nodes = @{$ng->{nodes}};\r
+\r
+ if($depth == 0 || $depth == 2 || $#nodes + 1 > 0) {\r
+ ${$html} .= "<div class=\"memitem\">" . "\n"\r
+ . "<div class=\"memproto\">" . "\n";\r
+ if($depth == 0) {\r
+ ${$html} .= "<span class=\"memname\">" . $ng->{name} . "</span>" . "\n";\r
+ } else {\r
+ ${$html} .= "<span class=\"memname\">" . $ng->{fullname} . "</span>" . "\n";\r
+ }\r
+\r
+ ${$html} .= "</div>" . "\n"\r
+ . "<div class=\"memdoc\">" . "\n";\r
+ $isDiv2 = 1;\r
+ }\r
+\r
+ if($#nodes + 1 > 0) {\r
+ if($depth > 0) {\r
+ foreach(@nodes) {\r
+ ${$html} .= "\t<dl>" . "\n"\r
+ . "\t\t<dt>" . ${${$_}->{dtdddata}}->{dt} . "</dt>" . "\n"\r
+ . "\t\t<dd>" . ${${$_}->{dtdddata}}->{dd} . "</dd>" . "\n"\r
+ . "\t</dl>" . "\n"; \r
+ }\r
+ }\r
+ }\r
+\r
+ my @childng = @{$ng->{childnodegroup}};\r
+\r
+ foreach(@childng) {\r
+ createhtmlchild($_, $html, $seq, $depth + 1, $#childng + 1);\r
+ }\r
+\r
+ if($isDiv2 == 1) {\r
+ ${$html} .= "</div>" . "\n"\r
+ . "</div>" . "\n";\r
+ }\r
+\r
+ if($isDiv1 == 1) {\r
+ ${$html} .= "</div>" . "\n";\r
+ }\r
+}\r
+\r
+sub savefile {\r
+ my $top = $_[0];\r
+ my $htmls = $_[1];\r
+ my $bottom = $_[2];\r
+ my $filename = $_[3];\r
+\r
+ open FILE, ">", $filename or die "$!\n";\r
+\r
+ print FILE $top;\r
+ print FILE $htmls;\r
+ print FILE $bottom;\r
+\r
+ close FILE;\r
+}\r
+\r
+sub getParserDL {\r
+ my $startindex = -1;\r
+ my @arr;\r
+ while(1) {\r
+ my $start = index($_[0], "<dt>", $startindex + 1);\r
+ my $end = index($_[0], "</dd>", $startindex + 1);\r
+ if($start == -1) {\r
+ last;\r
+ }\r
+\r
+ push(@arr, substr($_[0], $start, $end - $start + 5));\r
+\r
+ $startindex = $end;\r
+ }\r
+ @arr;\r
+}\r
+\r
+sub zero_fill\r
+{\r
+ my $pad_len = $_[1];\r
+ my $padded = sprintf("%0${pad_len}d", $_[0]);\r
+ return $padded;\r
+}\r
+\r
+sub trim {\r
+ my @result = @_;\r
+\r
+ foreach (@result) {\r
+ s/^\s+//; # \BE\D5\C2\CA \B0\F8\B9\E9 \C1\F6\BF\EC\B1\E2\r
+ s/\s+$//; # \B5\DA\C2\CA \B0\F8\B9\E9 \C1\F6\BF\EC\B1\E2\r
+ }\r
+\r
+ return wantarray ? @result : $result[0];\r
+}\r
+\r
+sub addkey {\r
+ my $arr = $_[0];\r
+ push(@$arr, $_[1]);\r
+\r
+ #foreach (@$arr) {\r
+ # print "\nitem - " . $_->{name};\r
+ #}\r
+\r
+ #print "\n--------------------";\r
+}\r
+\r
+sub containskey {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ if($_->{name} eq $keyname) {\r
+ return 1;\r
+ }\r
+ }\r
+\r
+ return 0;\r
+}\r
+\r
+sub setnode {\r
+ #print "sdfs : " . $_[0];\r
+ my $ng = ${$_[0]}; #nodegroup\r
+ my $method = $_[1]; #method\r
+\r
+ my @arr = split /::/, $method;\r
+\r
+ if($#arr + 1 == 1) {\r
+ return $ng;\r
+ } else {\r
+ my $tm = $ng->{childnodegroup};\r
+ #my @tm = ($ng->{childnodegroup});\r
+ foreach(@{$tm}) {\r
+ if($_->{name} eq $arr[0]) {\r
+ my @arr2;\r
+\r
+ for(my $i = 1; $i < $#arr + 1; $i++) {\r
+ push(@arr2, $arr[$i]);\r
+ }\r
+ return setnode(\$_, join "::", @arr2);\r
+ }\r
+ }\r
+\r
+ my $newng = new nodegroup();\r
+ $newng->{name} = $arr[0];\r
+ push(@{$tm}, $newng);\r
+ #print $#{$tm} . "\n";\r
+ #foreach(@{$tm}) {\r
+ # print ${$tm}[0] . "\n";\r
+ # print "------------\n";\r
+ #}\r
+\r
+ $newng->{parentnodegroup} = $newng;\r
+\r
+ if($ng->{fullname} eq "") {\r
+ $newng->{fullname} = $arr[0];\r
+ } else {\r
+ $newng->{fullname} = $ng->{fullname} . "::" . $arr[0];\r
+ }\r
+\r
+ my @arr2;\r
+ for(my $i = 1; $i < $#arr + 1; $i++) {\r
+ push(@arr2, $arr[$i]);\r
+ }\r
+ return setnode(\$newng, join "::", @arr2);\r
+ }\r
+}\r
+\r
+sub findnode {\r
+ my $arr = $_[0];\r
+ my $keyname = $_[1];\r
+\r
+ foreach (@$arr) {\r
+ #print $_->{name} . "-" . $keyname . "\n";\r
+ if($_->{name} eq $keyname) {\r
+ return $_;\r
+ }\r
+ }\r
+}\r
+\r
+sub sortnode {\r
+ $_->sortnodes();\r
+ \r
+# if($mode eq "G") {\r
+# $_->sortchildnodegroup();\r
+# } else {\r
+ if($_->{fullname} eq "") {\r
+ $_->sortchildnodegroup();\r
+ } else {\r
+ $_->sortchildnodegroup();\r
+\r
+ my @three = ();\r
+ my @four = ();\r
+ \r
+ foreach($_->{childenodegroup}) {\r
+ my $ng = $_->{nodes};\r
+\r
+ if($#{$ng} + 1 > 0) {\r
+ push(@three, $_);\r
+ } else {\r
+ push(@four, $_);\r
+ }\r
+ }\r
+\r
+ push @three, @four;\r
+\r
+ $_->{childenodegroup} = @three;\r
+ }\r
+# }\r
+\r
+ foreach(@{$_->{childnodegroup}}) {\r
+ sortnode(\$_);\r
+ }\r
+\r
+}\r
+\r
+\r
+package dtdd;\r
+\r
+sub new {\r
+ my ($class, $dt, $dtkey, $dd) = @_;\r
+\r
+ my $self = {dt => $dt, dtkey => $dtkey, dd => $dd };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+#sub say {\r
+# my ($self) = @_;\r
+# return $self->{dt};\r
+#}\r
+\r
+package node;\r
+\r
+sub new {\r
+ my ($class, $method, $dtdddata) = @_;\r
+\r
+ my $self = {method => $method, dtdddata => $dtdddata };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+package nodegroup;\r
+\r
+sub new {\r
+ my ($class) = @_;\r
+\r
+ my $self = {name => "", fullname => "", my @parentnodegroup => ()};\r
+\r
+ my @childnodegrouptmp = getarray();\r
+ $self->{childnodegroup} = \@childnodegrouptmp;\r
+ my @nodestmp = getarray();\r
+ $self->{nodes} = \@nodestmp;\r
+\r
+ pop(@{$self->{childnodegroup}});\r
+ pop(@{$self->{nodes}});\r
+\r
+# $self->{nodes} = []; #new node;\r
+# $self->{childnodegroup} = (); #new nodegroup;\r
+# $self->{fullname} = "";\r
+# $self->{parentnodegroup} = []; #new nodegroup;\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
+\r
+sub getarray {\r
+ my @tt = ();\r
+ return \@tt;\r
+}\r
+\r
+sub setname {\r
+ my $self = shift;\r
+ $self->{name} = $_[0];\r
+}\r
+\r
+sub addnode {\r
+ my $self = shift;\r
+# print $_[0]->{method} . "\n";\r
+ push(@{$self->{nodes}}, $_[0]);\r
+}\r
+\r
+sub sortnodes {\r
+\r
+ my $self = shift;\r
+\r
+ my $n = $self->{nodes};\r
+\r
+ #foreach(@{$n}) {\r
+ # print ${$_} . "\n";\r
+ #}\r
+ #print "------------------" . "\n";\r
+\r
+ #foreach(@{$n}) {\r
+ # print ${${$_}->{dtdddata}}->{dtkey} . "\n";\r
+ #}\r
+ @{$n} = sort { lc(${$a}->{method}) cmp lc(${$b}->{method}) || lc(${${$a}->{dtdddata}}->{dtkey}) cmp lc(${${$b}->{dtdddata}}->{dtkey}) || lc(${${$a}->{dtdddata}}->{dt}) cmp lc(${${$b}->{dtdddata}}->{dt}) } @{$n};\r
+}\r
+\r
+sub sortchildnodegroup {\r
+ my $self = shift;\r
+\r
+ my $n = $self->{childnodegroup};\r
+\r
+ @{$n} = sort { lc($a->{name}) cmp lc($b->{name}) } @{$n};\r
+}\r
+\r
+\r
+package groupdesc;\r
+\r
+sub new {\r
+ my ($class, $name, $desc) = @_;\r
+\r
+ my $self = {name => $name, desc => $desc };\r
+\r
+ bless $self, $class;\r
+\r
+ return $self;\r
+}\r
--- /dev/null
+http://tizen.org/privilege/alarm\r
+Allows the application to reserve an alarm and wake up the device at the reserved time.\r
+\r
+http://tizen.org/privilege/application.launch \r
+Allows the application to launch another application or allows the current application?to be launched conditionally.\r
+\r
+http://tizen.org/privilege/application.read \r
+Allows the application to get package information.\r
+\r
+http://tizen.org/privilege/application.kill \r
+Allows the application to terminate another application.\r
+\r
+http://tizen.org/privilege/appmanager.install \r
+Allows the application to install an application package.\r
+\r
+http://tizen.org/privilege/appmanager.launch \r
+Allows the application to launch?another application conditionally.\r
+\r
+http://tizen.org/privilege/appmanager.uninstall \r
+Allows the application to uninstall an application package.\r
+\r
+http://tizen.org/privilege/appsetting \r
+Allows the application to manage application settings.\r
+\r
+http://tizen.org/privilege/appusage \r
+Allows the application to receive notifications about application changes.\r
+\r
+http://tizen.org/privilege/audiomanager.route \r
+Allows the application to get and set the audio input and output routes and receive notifications about route-related events.\r
+\r
+http://tizen.org/privilege/audiomanager.session \r
+Allows the application to handle the audio session policy between applications.\r
+\r
+http://tizen.org/privilege/audiomanager.voipsession \r
+Allows the application to perform audio session management with the VoIP call.\r
+\r
+http://tizen.org/privilege/audiorecorder \r
+Allows the application to manage audio recording.\r
+\r
+http://tizen.org/privilege/bluetooth.admin \r
+Allows the application to change the Bluetooth state, such as activating, deactivating, and setting the device name.\r
+\r
+http://tizen.org/privilege/bluetooth.gap \r
+Allows the application to use the GAP (Generic Access Profile), for example, to discover and pair devices.\r
+\r
+http://tizen.org/privilege/bluetooth.health \r
+Allows the application to use the HDP (Health Device Profile), for example, to send health data.\r
+\r
+http://tizen.org/privilege/bluetooth.opp \r
+Allows the application to use the OPP (Object Push Profile), for example, to send files.\r
+\r
+http://tizen.org/privilege/bluetooth.spp \r
+Allows the application to use the SPP (Serial Port Profile), for example, to send serial data.\r
+\r
+http://tizen.org/privilege/bluetoothmanager \r
+Allows the application to change the Bluetooth state related to privacy and security issues, such as changing the discoverable mode.\r
+\r
+http://tizen.org/privilege/calendar.read \r
+Allows the application to read?schedule and task information.\r
+\r
+http://tizen.org/privilege/calendar.write \r
+Allows the application to create, update, and delete schedule and task information.\r
+\r
+http://tizen.org/privilege/callforward \r
+Allows the application to controls the call forwarding service.\r
+\r
+http://tizen.org/privilege/callhistory.read \r
+Allows the application to read call history.\r
+\r
+http://tizen.org/privilege/callhistory.write \r
+Allows the application to create, update, and delete call history.\r
+\r
+http://tizen.org/privilege/camera \r
+Allows the application to manage the device cameras for previewing and capturing.\r
+\r
+http://tizen.org/privilege/cellbroadcast \r
+Allows the application to manage Cell Broadcast Service.\r
+\r
+http://tizen.org/privilege/certificate.read \r
+Allows the application to read certificates.\r
+\r
+http://tizen.org/privilege/certificate.write \r
+Allows the application to add, update, and delete certificates.\r
+\r
+http://tizen.org/privilege/chatonv \r
+Allows the application to provide the ChatOnV service.\r
+\r
+http://tizen.org/privilege/contact.read \r
+Allows the application to read contacts.\r
+\r
+http://tizen.org/privilege/contact.write \r
+Allows the application to create, update, and delete contacts.\r
+\r
+http://tizen.org/privilege/content.read \r
+Allows the application to read content.\r
+\r
+http://tizen.org/privilege/content.write \r
+Allows the application to create, update, and delete content.\r
+\r
+http://tizen.org/privilege/context.place \r
+Allows the application to retrieve places.\r
+\r
+http://tizen.org/privilege/contextmanager.place Allows the application to add, update, and delete places.\r
+\r
+http://tizen.org/privilege/customnetaccount \r
+Allows the application to use the Internet with a specified bearer.\r
+\r
+http://tizen.org/privilege/dns \r
+Allows the application to provide DNS (Domain Name Service).\r
+\r
+http://tizen.org/privilege/download \r
+Allows the application to manage HTTP downloads.\r
+\r
+http://tizen.org/privilege/http \r
+Allows the application to communicate with the HTTP server.\r
+\r
+http://tizen.org/privilege/ime \r
+Allows the application to provide a way to input characters and symbols into an associated text input UI control.\r
+\r
+http://tizen.org/privilege/inputmanager \r
+Allows the application to generate touch and key events, and capture screens.\r
+\r
+http://tizen.org/privilege/location \r
+Allows the application to use the user location data.\r
+\r
+http://tizen.org/privilege/messaging.email \r
+Allows the application to send email messages.\r
+\r
+http://tizen.org/privilege/messaging.mms \r
+Allows the application to send MMS messages.\r
+\r
+http://tizen.org/privilege/messaging.sms \r
+Allows the application to send and receive SMS messages, and retrieve SMS messages from the SMS message boxes.\r
+\r
+http://tizen.org/privilege/mobilecare \r
+Allows the application to control Samsung MobileCare.\r
+\r
+http://tizen.org/privilege/network.account \r
+Allows the application to manage network accounts.\r
+\r
+http://tizen.org/privilege/network.connection \r
+Allows the application to manage network connections.\r
+\r
+http://tizen.org/privilege/network.statistics.read \r
+Allows the application to read network statistics.\r
+\r
+http://tizen.org/privilege/network.statistics.write \r
+Allows the application to reset network statistics.\r
+\r
+http://tizen.org/privilege/networkmanager \r
+Allows the application to update existing system network accounts.\r
+\r
+http://tizen.org/privilege/nfc.admin \r
+Allows the application to change the NFC state, such as activating or deactivating the NFC feature.\r
+\r
+http://tizen.org/privilege/nfc.cardemulation \r
+Allows the application to control the card emulation.\r
+\r
+http://tizen.org/privilege/nfc.common \r
+Allows the application to manage the common NFC features.\r
+\r
+http://tizen.org/privilege/nfc.p2p \r
+Allows the application to push NFC messages to other devices.\r
+\r
+http://tizen.org/privilege/nfc.tag \r
+Allows the application to read and write tag information.\r
+\r
+http://tizen.org/privilege/notification \r
+Allows the application to notify?the user through various notification mechanisms, such as message and badge.\r
+\r
+http://tizen.org/privilege/notificationmanager \r
+Allows the application to manage notifications.\r
+\r
+http://tizen.org/privilege/packageinfo \r
+Allows the application to get package information.\r
+\r
+http://tizen.org/privilege/packagelicensemanager \r
+Allows the application to manage DRM licenses for application support.\r
+\r
+http://tizen.org/privilege/packagemanager.install \r
+Allows the application to install or uninstall an application package.\r
+\r
+http://tizen.org/privilege/packagesetting \r
+Allows the application to set the package configurations.\r
+\r
+http://tizen.org/privilege/power \r
+Allows the application to keep and control power states.\r
+\r
+http://tizen.org/privilege/push \r
+Allows the application to receive push notifications.\r
+\r
+http://tizen.org/privilege/setting \r
+Allows the application to update or read the user's setting configuration.\r
+\r
+http://tizen.org/privilege/smstrigger \r
+Allows the application to receive SMS messages from a specified port.\r
+\r
+http://tizen.org/privilege/socket \r
+Allows the application to communicate with other devices and servers.\r
+\r
+http://tizen.org/privilege/systeminfo \r
+Allows the application to retrieve system information, such as network, SIM, and call details.\r
+\r
+http://tizen.org/privilege/systemsetting.read \r
+Allows the application to read the user's secure or privacy setting configuration.\r
+\r
+http://tizen.org/privilege/systemsetting.write \r
+Allows the application to change or write the user's secure or privacy setting configuration.\r
+\r
+http://tizen.org/privilege/uimanager \r
+Allows the application to manage the systematic properties of the UI.\r
+\r
+http://tizen.org/privilege/useridentity \r
+Allows the application to access privacy information for user identification purposes.\r
+\r
+http://tizen.org/privilege/vibrator \r
+Allows the application to activate and use the device vibrator feature.\r
+\r
+http://tizen.org/privilege/videorecorder \r
+Allows the application to manage video recording with the camera.\r
+\r
+http://tizen.org/privilege/wappush \r
+Allows the application to manage WAP push messages.\r
+\r
+http://tizen.org/privilege/web.privacy \r
+Allows the application to manage the user data stored by the Web control or browser.\r
+\r
+http://tizen.org/privilege/web.service \r
+Allows the application to display Web content or use the Web content-related API.\r
+\r
+http://tizen.org/privilege/wifi.admin \r
+Allows the application to manage a Wi-Fi device.\r
+\r
+http://tizen.org/privilege/wifi.read \r
+Allows the application to request Wi-Fi information.\r
+\r
+http://tizen.org/privilege/wifi.wifidirect.admin \r
+Allows the application to manage a Wi-Fi Direct\A2\E2 device.\r
+\r
+http://tizen.org/privilege/wifi.wifidirect.read \r
+Allows the application to request Wi-Fi Direct\A2\E2 information.\r
+\r
+http://tizen.org/privilege/drmservice \r
+Allows the application to manage the?DRM (Digital Rights Management) licenses and retrieve DRM content information.\r
+\r
+http://tizen.org/privilege/imemanager \r
+Allows the application to manage input methods installed in the system.\r
+\r
+http://tizen.org/privilege/telephonymanager \r
+Allows the application to configure the cellular network.\r
+\r
+http://tizen.org/privilege/platforminfo \r
+Allows the application to read platform information, such as platform or API version.\r
+\r
+http://tizen.org/privilege/applicensemanager \r
+Allows the application to manage the licenses for supporting application DRM (Digital Rights Management).\r
+\r
+http://tizen.org/privilege/wifimanager \r
+Allows the application to manage the Wi-Fi system settings. \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
+ \r
--- /dev/null
+http://tizen.org/privilege/account.read\r
+Allows the application to read accounts.\r
+\r
+http://tizen.org/privilege/account.write\r
+Allows the application to create, update, and delete accounts.\r
+\r
+http://tizen.org/privilege/alarm\r
+Allows the application to set an alarm and wake the device up at the scheduled time.\r
+\r
+http://tizen.org/privilege/antivirus\r
+Allows the Antivirus application to scan for harmful content.\r
+\r
+http://tizen.org/privilege/application.kill\r
+Allows the application to close another application.\r
+\r
+http://tizen.org/privilege/application.launch\r
+Allows the application to be opened conditionally or to open another application.\r
+\r
+http://tizen.org/privilege/application.read\r
+Allows the application to read application information.\r
+\r
+http://tizen.org/privilege/appmanager.certificate\r
+ Allows the application to get specified application certificates.\r
+\r
+http://tizen.org/privilege/appmanager.kill\r
+Allows the application to close another application.\r
+\r
+http://tizen.org/privilege/appmanager.launch\r
+Allows the application to manage another application opening conditionally.\r
+\r
+http://tizen.org/privilege/appsetting\r
+Allows the application to manage application settings.\r
+\r
+http://tizen.org/privilege/appusage\r
+Allows the application to receive notifications about foreground application changes.\r
+\r
+http://tizen.org/privilege/appwidgetprovider.install\r
+Allows the application to add Dynamic Box to the home screen.\r
+\r
+http://tizen.org/privilege/audiomanager.route\r
+Allows the application to set audio input and output routes and receive notifications about route events.\r
+\r
+http://tizen.org/privilege/audiorecorder\r
+Allows the application to manage audio recording.\r
+\r
+http://tizen.org/privilege/bluetooth.admin\r
+Allows the application to change Bluetooth settings, such as turning Bluetooth on or off, and setting the local device name.\r
+\r
+http://tizen.org/privilege/bluetooth.gap\r
+Allows the application to use the Generic Access Profile (GAP), for example, to scan for and pair devices.\r
+\r
+http://tizen.org/privilege/bluetooth.health\r
+Allows the application to use the Health Device Profile (HDP), for example, to send health data.\r
+\r
+http://tizen.org/privilege/bluetooth.opp\r
+Allows the application to use the Object Push Profile (OPP), for example, to send files.\r
+\r
+http://tizen.org/privilege/bluetooth.spp\r
+Allows the application to use the Serial Port Profile (SPP), for example, to send serial data.\r
+\r
+http://tizen.org/privilege/bluetoothmanager\r
+Allows the application to change Bluetooth system settings related to privacy and security, such as the visible mode.\r
+\r
+http://tizen.org/privilege/bookmark.read\r
+Allows the application to read bookmarks.\r
+\r
+http://tizen.org/privilege/bookmark.write\r
+Allows the application to create, update, and?delete bookmarks.\r
+\r
+http://tizen.org/privilege/calendar.read\r
+Allows the application to read?schedule and task information.\r
+\r
+http://tizen.org/privilege/calendar.write\r
+Allows the application to create, update, and delete schedule and task information.\r
+\r
+http://tizen.org/privilege/callforward\r
+Allows the application to control the call forwarding service.\r
+\r
+http://tizen.org/privilege/callhistory.read\r
+Allows the application to read call logs.\r
+\r
+http://tizen.org/privilege/callhistory.write\r
+Allows the application to create, update, and delete call logs.\r
+\r
+http://tizen.org/privilege/camera\r
+Allows the application to manage device cameras to preview and capture pictures.\r
+\r
+http://tizen.org/privilege/cellbroadcast\r
+Allows the application to manage the Cell Broadcast Service (CBS).\r
+\r
+http://tizen.org/privilege/certificate.read\r
+Allows the application to read certificates.\r
+\r
+http://tizen.org/privilege/certificate.write\r
+Allows the application to add, update, and delete certificates.\r
+\r
+http://tizen.org/privilege/contact.read\r
+Allows the application to read contacts.\r
+\r
+http://tizen.org/privilege/contact.write\r
+Allows the application to add, update, and delete contacts.\r
+\r
+http://tizen.org/privilege/content.read\r
+Allows the application to read content.\r
+\r
+http://tizen.org/privilege/content.write\r
+Allows the application to create, update and delete content.\r
+\r
+http://tizen.org/privilege/customnetaccount\r
+Allows the application to use the Internet with a specified bearer.\r
+\r
+http://tizen.org/privilege/datacontrol.consumer\r
+Allows the application to access specific data exported by other applications.\r
+\r
+http://tizen.org/privilege/datasync\r
+Allows the application to synchronise device data to the server using the OMA DS 1.2 protocol.\r
+\r
+http://tizen.org/privilege/dns\r
+Allows the application to provide the Domain Name Service (DNS).\r
+\r
+http://tizen.org/privilege/download \r
+Allows the application to manage HTTP downloads.\r
+\r
+http://tizen.org/privilege/drmservice \r
+Allows the application to manage Digital Rights Management (DRM) licences and retrieve DRM content information.\r
+\r
+http://tizen.org/privilege/filesystem.read \r
+Allows the application to read file systems.\r
+\r
+http://tizen.org/privilege/filesystem.write\r
+Allows the application to write to file systems.\r
+\r
+http://tizen.org/privilege/fullscreen\r
+Allows the application to use full screen.\r
+\r
+http://tizen.org/privilege/geolocationpermission.read \r
+Allows the application to read geolocation permissions.\r
+\r
+http://tizen.org/privilege/geolocationpermission.write \r
+Allows the application to delete geolocation permissions.\r
+\r
+http://tizen.org/privilege/http \r
+Allows the application to communicate with the HTTP server.\r
+\r
+http://tizen.org/privilege/ime \r
+Allows the application to provide a way to input characters and symbols into an associated input field.\r
+\r
+http://tizen.org/privilege/imemanager \r
+Allows the application to manage the installed input methods.\r
+\r
+http://tizen.org/privilege/inputmanager \r
+Allows the application to generate touch and key events, and capture screens.\r
+\r
+http://tizen.org/privilege/internet \r
+Allows the application to access the Internet.\r
+\r
+http://tizen.org/privilege/location \r
+Allows the application to use the user location data.\r
+\r
+http://tizen.org/privilege/lockmanager \r
+Allows the application to unlock the device.\r
+\r
+http://tizen.org/privilege/log \r
+Allows the application to use the system log (dlog).\r
+\r
+http://tizen.org/privilege/mediacapture \r
+Allows the application to manage video recording and audio recording with camera or audio recorder.\r
+\r
+http://tizen.org/privilege/messaging.email \r
+Allows the application to send email messages.\r
+\r
+http://tizen.org/privilege/messaging.mms \r
+Allows the application to send MMS messages.\r
+\r
+http://tizen.org/privilege/messaging.read \r
+Allows the application to receive?messages, and retrieve messages from the message boxes.\r
+\r
+http://tizen.org/privilege/messaging.send \r
+Allows the application to send SMS, MMS, and email messages.\r
+\r
+http://tizen.org/privilege/messaging.sms \r
+Allows the application to send and receive?SMS messages, and retrieve SMS messages from the SMS message boxes.\r
+\r
+http://tizen.org/privilege/messaging.write \r
+Allows the application to write SMS, MMS, and email messages.\r
+\r
+http://tizen.org/privilege/netstatisticsmanager \r
+Allows the application to reset network statistics.\r
+\r
+http://tizen.org/privilege/network.account \r
+Allows the application to manage network accounts.\r
+\r
+http://tizen.org/privilege/network.connection \r
+Allows the application to manage network connections.\r
+\r
+http://tizen.org/privilege/network.statistics \r
+Allows the application to read network statistics.\r
+\r
+http://tizen.org/privilege/network.statistics.read \r
+Allows the application to read network statistics.\r
+\r
+http://tizen.org/privilege/networkbearerselection\r
+Allows the application to request/release a specific network connection.\r
+\r
+http://tizen.org/privilege/networkmanager \r
+Allows the application to update system network accounts.\r
+\r
+http://tizen.org/privilege/nfc.admin \r
+Allows the application to change NFC settings, such as turning NFC on or off.\r
+\r
+http://tizen.org/privilege/nfc.common \r
+Allows the application to use NFC common features.\r
+\r
+http://tizen.org/privilege/nfc.p2p \r
+Allows the application to push NFC messages to other devices.\r
+\r
+http://tizen.org/privilege/nfc.tag \r
+Allows the application to read and write NFC tag information.\r
+\r
+http://tizen.org/privilege/nfcmanager \r
+Allows the application to change NFC system settings, such as turning on or off reserved push, which sends predefined NDEF messages.\r
+\r
+http://tizen.org/privilege/notification \r
+Allows the application to provide user notifications, such as messages and badges.\r
+\r
+http://tizen.org/privilege/notification.read \r
+Allows the application to get notifications.\r
+\r
+http://tizen.org/privilege/notification.write \r
+Allows the application to update notifications.\r
+\r
+http://tizen.org/privilege/notificationmanager \r
+Allows the application to manage notifications.\r
+\r
+http://tizen.org/privilege/package.info \r
+Allows the application to receive package information.\r
+\r
+http://tizen.org/privilege/packageinfo \r
+Allows the application to receive package information.\r
+\r
+http://tizen.org/privilege/packagemanager.info \r
+Allows the application to receive detailed package information.\r
+\r
+http://tizen.org/privilege/packagemanager.install \r
+Allows the application to install or uninstall application packages.\r
+\r
+http://tizen.org/privilege/packagemanager.setting \r
+Allows the application to set package configurations.\r
+\r
+http://tizen.org/privilege/packagesetting \r
+Allows the application to set package configurations.\r
+\r
+http://tizen.org/privilege/platforminfo \r
+Allows the application to read information such as the platform or API version.\r
+\r
+http://tizen.org/privilege/power \r
+Allows the application to hold and control power states.\r
+\r
+http://tizen.org/privilege/privacymanager.read \r
+Allows the application to read privacy settings.\r
+\r
+http://tizen.org/privilege/privacymanager.write \r
+Allows the application to change privacy settings.\r
+\r
+http://tizen.org/privilege/privilegemanager.read \r
+Allows the application to?read privilege information.\r
+\r
+http://tizen.org/privilege/push \r
+Allows the application to receive push notifications.\r
+\r
+http://tizen.org/privilege/se \r
+Allows the application to access tosecure smart card chip such as UICC/SIM, embedded secure element, or secure SD card.\r
+\r
+http://tizen.org/privilege/secureelement \r
+Allows the application to access tosecure smart card chip such as UICC/SIM, embedded secure element, or secure SD card.\r
+\r
+http://tizen.org/privilege/setting \r
+Allows the application to update or read user settings.\r
+\r
+http://tizen.org/privilege/settingmanager.read\r
+Allows the application to read security or privacy settings.\r
+\r
+http://tizen.org/privilege/settingmanager.write \r
+Allows the application to change security or privacy settings.\r
+\r
+http://tizen.org/privilege/shortcut.install \r
+Allows the application to add and remove shortcuts from the home screen.\r
+\r
+http://tizen.org/privilege/smstrigger \r
+Allows the application to receive SMS messages from a specified port.\r
+\r
+http://tizen.org/privilege/socket \r
+Allows the application to communicate with other devices and servers.\r
+\r
+http://tizen.org/privilege/system \r
+Allows the application to access system information.\r
+\r
+http://tizen.org/privilege/systeminfo \r
+Allows the application to retrieve system information, such as network, SIM, and call details.\r
+\r
+http://tizen.org/privilege/systemmanager \r
+Allows the application to access secure system information.\r
+\r
+http://tizen.org/privilege/systemsetting.read \r
+Allows the application to read security or privacy settings.\r
+\r
+http://tizen.org/privilege/systemsetting.write \r
+Allows the application to change security or privacy settings.\r
+\r
+http://tizen.org/privilege/telephony \r
+Allows the application to retrieve telephony information, such as network, SIM, and call details.\r
+\r
+http://tizen.org/privilege/telephonymanager \r
+Allows the application to configure the mobile networks.\r
+\r
+http://tizen.org/privilege/testautomation \r
+Allows the application to use the test automation feature.\r
+\r
+http://tizen.org/privilege/time \r
+Allows the application to get time and date information.\r
+\r
+http://tizen.org/privilege/tizen \r
+Allows the application to use Tizen Web device API common module.\r
+\r
+http://tizen.org/privilege/uimanager \r
+Allows the application to manage UI properties.\r
+\r
+http://tizen.org/privilege/unlimitedstorage \r
+Allows the application to use attached storage without size limitations for DB or files.\r
+\r
+http://tizen.org/privilege/useridentity \r
+Allows the application to access privacy information for user identification purposes.\r
+\r
+http://tizen.org/privilege/userprofile.read \r
+Allows the application to read?the user profile.\r
+\r
+http://tizen.org/privilege/userprofile.write \r
+Allows the application to manage?the user profile.\r
+\r
+http://tizen.org/privilege/vibrator \r
+Allows the application to turn on and use vibrate.\r
+\r
+http://tizen.org/privilege/videorecorder \r
+Allows the application to manage video recording with the camera.\r
+\r
+http://tizen.org/privilege/wappush \r
+Allows the application to manage WAP push messages.\r
+\r
+http://tizen.org/privilege/web.privacy \r
+Allows the application to manage the user data stored by the Web control or browser.\r
+\r
+http://tizen.org/privilege/web.service \r
+Allows the application to display Web content or use the Web content-related API.\r
+\r
+http://tizen.org/privilege/wifi.admin \r
+Allows the application to manage Wi-Fi on the device, such as turning Wi-Fi on or off, and connecting to AP.\r
+\r
+http://tizen.org/privilege/wifi.read \r
+Allows the application to request Wi-Fi information.\r
+\r
+http://tizen.org/privilege/wifi.wifidirect.admin \r
+Allows the application to manage Wi-Fi Direct on the device.\r
+\r
+http://tizen.org/privilege/wifi.wifidirect.read \r
+Allows the application to request Wi-Fi Direct information.\r
+\r
+http://tizen.org/privilege/wifimanager \r
+Allows the application to manage the Wi-Fi system settings, such as updating AP information.\r
+\r
--- /dev/null
+&reg; = ®
\ No newline at end of file
--- /dev/null
+#!/bin/sh
+
+check_errs()
+{
+ # Function. Parameter 1 is the return code
+ # Para. 2 is text to display on failure.
+ if [ "${1}" -ne "0" ]; then
+ echo "ERROR # ${1} : ${2}"
+ # as a bonus, make our script exit with the right error code.
+ exit ${1}
+ fi
+}
+
+# git clone managed-api
+email=$(git config --get user.email)
+name=`echo $email | awk 'BEGIN {FS="@"}{print $1}'`
+
+rm -rf managed-api
+git clone ssh://$name@slp-info.sec.samsung.net:29418/magnolia/doc/managed-api
+
+echo '****************************************************'
+echo 'Generating Web API Ref plugin file '
+echo '****************************************************'
+
+./managed-api/web/generate.sh jar
+
+echo 'copy Web API Ref to plugin folder '
+
+cp managed-api/web/plugin/org.tizen.web.device.apireference*.jar ../../plugins/
+check_errs $? "fail to zip"
+
--- /dev/null
+<?xml version="1.0" encoding="utf-8"?>
+<extensions>
+ <tocOrder>
+ <toc id="/org.tizen.gettingstarted/index.xml"/>
+ <toc id="/org.tizen.web.appprogramming/index.xml"/>
+ <toc id="/org.tizen.native.appprogramming/index.xml"/>
+ <toc id="/org.tizen.platform.development/index.xml"/>
+ <toc id="/org.tizen.sdk.development/index.xml"/>
+ <toc id="/org.eclipse.development.doc/index.xml"/>
+ </tocOrder>
+</extensions>
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.7"/>
+ <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.tizen.ide.documentation.linker</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
--- /dev/null
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.7
+org.eclipse.jdt.core.compiler.compliance=1.7
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
+org.eclipse.jdt.core.compiler.source=1.7
--- /dev/null
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: Linker
+Bundle-SymbolicName: org.tizen.ide.documentation.linker
+Bundle-Version: 1.0.0.qualifier
+Bundle-Activator: org.tizen.ide.documentation.linker.Activator
+Require-Bundle: org.eclipse.ui,
+ org.eclipse.core.runtime
+Bundle-ActivationPolicy: lazy
+Bundle-RequiredExecutionEnvironment: JavaSE-1.7
+Bundle-Vendor: The Linux Foundation
--- /dev/null
+source.. = src/
+output.. = bin/
+bin.includes = META-INF/,\
+ .
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">\r
+\r
+<html>\r
+<head>\r
+ <script>\r
+var linktable = {\r
+ 'button': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_button.htm',\r
+ 'checkboxes': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_checkbox.htm',\r
+ 'datetimepicker': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_datetimepicker.htm',\r
+ 'footer': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_header_footer.htm',\r
+ 'header': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_header_footer.htm',\r
+ 'list': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_list.htm',\r
+ 'listdivider': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_listdivider.htm',\r
+ 'progressbar': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_progressbar.htm',\r
+ 'searchbar': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_searchbar.htm',\r
+ 'slider': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_slider.htm',\r
+ 'swipe': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_swipe.htm',\r
+ 'tabbar':'/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_tabbar.htm',\r
+ 'fliptoggleswitch': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_toggleswitch.htm',\r
+ 'tokentextarea':'/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_tokentextarea.htm',\r
+ 'searchfilterbar': '/help/topic/org.tizen.web.uiwidget.apireference/html/widgets/widget_searchbar.htm',\r
+ '_end': undefined\r
+};\r
+function link(widget) {\r
+ var url = linktable[widget];\r
+ if (url === undefined) url = errorpage;\r
+ location.href = url;\r
+ console.log(widget + ':' + url);\r
+}\r
+\r
+var parser = document.createElement('a');\r
+parser.href = location.href;\r
+var widget = parser.hash.substring(1);\r
+link(widget);\r
+\r
+ </script>\r
+</head>\r
+</html><html><head></head><body></body></html>
\ No newline at end of file
--- /dev/null
+package org.tizen.ide.documentation.linker;
+
+import org.eclipse.ui.plugin.AbstractUIPlugin;
+import org.osgi.framework.BundleContext;
+
+/**
+ * The activator class controls the plug-in life cycle
+ */
+public class Activator extends AbstractUIPlugin {
+
+ // The plug-in ID
+ public static final String PLUGIN_ID = "org.tizen.ide.documentation.linker"; //$NON-NLS-1$
+
+ // The shared instance
+ private static Activator plugin;
+
+ /**
+ * The constructor
+ */
+ public Activator() {
+ }
+
+ /*
+ * (non-Javadoc)
+ * @see org.eclipse.ui.plugin.AbstractUIPlugin#start(org.osgi.framework.BundleContext)
+ */
+ public void start(BundleContext context) throws Exception {
+ super.start(context);
+ plugin = this;
+ }
+
+ /*
+ * (non-Javadoc)
+ * @see org.eclipse.ui.plugin.AbstractUIPlugin#stop(org.osgi.framework.BundleContext)
+ */
+ public void stop(BundleContext context) throws Exception {
+ plugin = null;
+ super.stop(context);
+ }
+
+ /**
+ * Returns the shared instance
+ *
+ * @return the shared instance
+ */
+ public static Activator getDefault() {
+ return plugin;
+ }
+
+}
projects / sdk / doc / content.git / commitdiff
