I think I've absolutely solved out the problem on my own problem. To be able to print my thesis like a book with even and odd pages, I had to leave blank pages at the every single files of my thesis. But while converting to PDF, there used to appear moreblank ones. Mine has to do with the page numeration. If on your blank page, number style checked as 'odd and even pages differen', then the word automatically creates more or odd or even blank page. So uncheck it, to be able to get rid off more blankpage.

• Doxygen Config File
• Doxygen Main Page

Doxygen Tutorial Doxygen Tutorial(C/CWhen Ireturned to programming a few years ago, I noticed that open sourcedevelopers were tending to fall into two main groups: those that useDoxygen to generate development documentation, and those thatdocumented very little. So I started to look at Doxygen but was quicklyput off by two major flaws. The Doxygen documentation, both theofficial reference documentation and various howtos and tutorials,missed something for the beginner. They tended to merely explain thecommands and concepts, but did not give a proper lead in for a newuser. Secondly the examples that I looked at appeared as simple listsoffile, class, member, variable names and a few natty diagrams.

To methey conveyed nothing of the intent of the program or any explanationof its internal workings.This is basically a failure of some open source developers, not ofDoxygen. Some speak of 'self-documenting code', however there is reallyno such thing. Meaningful choices of names for entities goes a long waytowards helping make the code readable, but it stops short ofdescribing the purpose of entities, the way blocks of code work, andthe reasons for decisions that were made (most important to thereader). Here I intend to show how I use Doxygen, displaying the extent of itscapabilities, and to do it in away that demonstrates what I believe to be good documentation practice.I only use C and C, but you should be able to follow this even if youuse other languages.As well as command line Doxygen, I consider DoxyWizardto be quite important for providing an intuitive and easy to use GUIinterface. Although the configuration file and command line usage ofDoxygen is well documented, a new user needs to have a basic overallappreciation of what Doxygen is doing before it makes any sense. Installation Refer toany of the existing tutorials and howtos to find out how to installDoxygen and DoxyWizard.

Most distributions provide both of these. GettingStarted Find asimple program consisting of perhaps a source and header file and noDoxygen markup.

The one I used from my collection to develop thistutorial is called '. Open DoxyWizard. The first tab allowsyou to enter the working directory, so fill this in first.

Irlanda: 1854-1900. Cuentos - Opiniones - Poemas; Textos digitales completos. Poemas de Oscar Wilde. Versos e poesias de Oscar Wilde no. Poemas oscar wilde pdf download.

Then clickon the Wizard button. Give a meaningful name and version number (whichwill appear as headings in the final document) and setthe two directories; the first to point to your source code directoryand for the second just make it the same as the working directory (orcreate a new 'docs' directory). Doxygen will place subdirectories tohold the documentation: 'html' for the html files etc.In the Mode tab, choose to document all entities and to include crossreferenced source code. Choose the optimization for your language. Inthe Output tab, if you choose to use the dot tool you will get somereally natting looking dependency graphs. You must have the GraphVizpackage installed for this.Now go back to the first tab and save the configuration. Doxygen offersthe file Doxyfile, which I prefer to use as I always know immediatelywhat it is when I see it.

Now click the Start button. Doxygen will runand create the documentation output. Point a browser to the file in thehtml subdirectory and you will see what Doxygen does without any efforton the developer's part to control it. The author probably understandwhat itall means but no-one else will.The first thing you see on opening index.html is the 'Main Page' tabshowingyour project name and version and nothing else.

Doxygen Config File

There should also be aFiles tab. This shows links to thegenerated documentation for the files and to the source code. There maybe some additional files that Doxygen picked up from the sourcedirectory and that you don't want included. You would need toexplicitely exclude these using the DoxyWizard expert tool. There areother tabs that will appear to allow guidance around the documentation.What Doxygen can do to an undocumented program is to identify thevarious entities in your program and present them in a digestiblemanner. However to produce realdocumentation, the developer must provide comments in the code, andappropriate markup to allow Doxygen to pull out these comments andplace them with the associated entities to guide the reader into anunderstanding of the code.

Doxygen Main Page

If you have already placed good qualitycomments in your code you are 90% of the way there, otherwise there isa bit of work to be done.Providingan Introduction The firstthing a new reader wants to see when viewing documentation is a briefand comprehensive summary of the program's purpose, the authors, datesand various other valuable information. To do this, open your main fileand add a comment at the very top with this information (you havealready done this anyway as part of your commenting of the code -right?). Now to make Doxygen use it on the main tab enter thefollowing markup constructs:. /. or //!

At thebeginning of the comment. If youuse the C comment convention then you can use the second form, buteither areacceptable. If you are using a Doxygen-smart editor such as Kate, thenthe colour ofthe text should change. @mainpageimmediately following. You can add a string after this as a title inplace of the project name that was entered in DoxyWizard. Thisinstructs Doxygen to put the comment on the main tab. @version if youprefer to have it here rather than in the Doxyfile.

@author whoever. @date whenever. @note Placedanywhere this will add a note keyword in bold if desired.Afterthese put a description of the program's purpose.

To make sure thedescription does not get attached to the directive just before it, usethe directive @detail or leavea blank line. Now run Doxygen againand observe the changes. You are now on the way to having some qualitydocumentation.IncludingComments Asmentionedabove, adding an extra. to the /. or a!

To the // comment delimiterwill cause Doxygen to associate the comment with the next definedentity. These comments can be placed before and in the middle of ablock of code such as a function.If you look at a page generated by Doxygen for a simple source file,you will see at the top a list of includes and a dependency graphgenerated from these. Underneath that will be a list of the functionsthat Doxygen found in the file. Detailed documentation for eachfunction appearsfollowing that list.The first step to improving this is to add a brief comment to eachfunction in the list. Just above the function add a comment, andimmediately following the /.

or //! Delimiter,add the directive:@brief Description of thefunctionWhen Doxygen is run, this description will appear underneath thecorresponding function in the function list, and also in the detaileddocumentation for the function.Now underneath the @brief directive, leave a blank line and add adetailed description of what the function does.