[interfacekit] Re: Documentation

>>From what I've gathered, the documentation issue has largely been one 
>addressed on the OBOS list. If I understand how things went, the 
concern for 
>having documentation in the headers when using doxygen was mentioned. 
>However, because this is no longer necessary with doxygen, it looked 
to me 
>like the consensus was to go with doxygen. Erik=3F

Sorry DW to respond to a question to Erik, but Erik and I have been 
investigating this for a while now. Doxygen works perfectly, and is 
pretty easy and nice to use, but we had some disagreements with doxygen 
about the output. We would like to generate something "BeBook-like", 
and doxygen (as most other doc tools) generate a somewhat 
"unstructured" output. We've been looking into a way to fix this for a 
short while, but either you end up writing some duplicate documentation 
(both in a general intro part, and with the docs per member), or you 
end up developing your own wrapper tool around doxygen, and both don't 
look to enticing to me.

Ideas, anyone =3F :)

Regards,

Ithamar.

(Yes, I'm still lurking here)

Other related posts: