Author Topic: Doxygen Docs  (Read 2387 times)

0 Members and 1 Guest are viewing this topic.

Offline Inquisitor

I just ran Doxygen on the source, it actually came out readable.

I'll work with Thunder (and probably upload to the CVS website as well) to put this on the website(s) but if folks want to run it themselves, I believe it can be downloaded for free at doxygen.org

This creates documentation on the source code including class heirarchies, linked HTML pages in the code (leading you from function to function in the source), etc.

Some developers find this level pof documentation useful.

I'll try and keep this updated, and both an unaltered (released) copy and a copy run on our development tree after major milestones, and on the websites in the future.

It's 45 megs uncompressed HTML, FYI.
No signature.

 

Offline phreak

  • Gun Phreak
  • 211
  • -1
does anyone here have 45 megs of webspace?
Offically approved by Ebola Virus Man :wtf:
phreakscp - gtalk
phreak317#7583 - discord

 

Offline Inquisitor

I think that we have it on the CVS website, I have to dash an email off to them tonight when i get home (unless they are reading :)).

Also, that's Thunder's call for the temp website space as well :)
No signature.

 

Offline penguin

  • Eudyptes codus
  • 28
  • Still alive.
nifty :yes:

A nice thing to do would be to add function header comments so that doxygen can produce more legible output.  I am in favor of the javadoc syntax, since, umm well, I do java development as well.  Standards are nice :nod:

http://www.stack.nl/~dimitri/doxygen/docblocks.html

I guess any new stuff that gets added should adhere to the "officially approved" syntax, and anyone with a few spare cycles :rolleyes: can go back and fix the existing headers.

That should put an end to all the "can someone please explain the source code to me" posts... or at least we have a standard answer: RTFM :D
your source code slave

 

Offline Inquisitor

Yeah, lets add a standards discussion to the agenda for saturday, I tried to get at it last time, but wasn't sure how to frame it.
No signature.

 

Offline Inquisitor

These are uploading now, and will be able to be accessed at:

http://fs2source.warpcore.org/dox/

I'll redo them in the format of the site at a later date (unless someone wants to do that for me) but there they are (or there they will be).

Enjoy!
No signature.

 

Offline EdrickV

  • Valued
  • 29
    • http://members.aol.com/HunterComputers
How big would all the docs be in a zip file? Loading them locally would be a lot quicker then from the web. (Especially since not everyone is likely to be online while editing the source code.)

Last time I tried Doxygen on the FS2 source it crashed.
Ground - "Let me help you out, you're clear to taxi any way you can, to any runway you see."

Mesh Gallery/Downloads:
http://members.aol.com/ArisKalzar/Gallery.html
Turreting 101:
http://members.aol.com/EdrickV/FS2/Turreting.html

http://members.aol.com/HunterComputers

 

Offline Inquisitor

No idea, will look tomorrow.

Maybe pop onto IRC and we can work thru the Doxygen issues?
No signature.

 

Offline EdrickV

  • Valued
  • 29
    • http://members.aol.com/HunterComputers
I'm not really fond of IRC, and my Doxygen issues were probably because I was running it from Cygwin rather then a Linux box. It caused a GPF as I recall. It was a while ago. But you got it to work right so there are Doxygen docs for FS2 now anyways. :)
Ground - "Let me help you out, you're clear to taxi any way you can, to any runway you see."

Mesh Gallery/Downloads:
http://members.aol.com/ArisKalzar/Gallery.html
Turreting 101:
http://members.aol.com/EdrickV/FS2/Turreting.html

http://members.aol.com/HunterComputers

 

Offline Inquisitor

Ah, there IS a windows port of it, might be friendlier to run.

And our IRC server is very newbie friendly ;)
No signature.