first content on matrixpilot.com

[Robert Dickenson]

please take a look at:

http://matrixpilot.com/doxygen_trunk/files.html

[William Premerlani]

Robert,

Wow, very nice.

How much of that was somehow generated automatically by something that you wrote?

Best regards,

Bill

On Wed, May 6, 2015 at 7:39 PM, Robert Dickenson <robert.d...@gmail.com> wrote:

please take a look at:

http://matrixpilot.com/doxygen_trunk/files.html

--
You received this message because you are subscribed to the Google Groups "uavdevboard-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uavdevboard-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Phillip Kocmoud]

Hi Rob,

Can you give a little tutorial on how to use this.

Phil

[Robert Dickenson]

The doxygen configuration is 'Doxyfile' in the project root. I'm currently using doxywizard on windows however the command line versions should work with it too. It'd be nice to somehow get it setup to automatically regenerate the live web content on every repository commit..

Unfortunately on my first few passes with it, i noted quite a lot of 'extraneous' include spaghetti, as well as the few remaining upwards dependencies from the lowest level libraries to the application layer - so i've made changes in a number of modules to address these 'issues'. So the graphics look half neat now.

All project should still build okay (have been doing much compiling), and i'm going to perform silsim tests later today, however i'm also going to need to setup a udb board and do some verification on hardware, since some of the changes may well break startup/initialisation.

If anybody is keen to perform some tests on clean checkouts of trunk and/or branch MatrixPilot_helicalTurns, problem reports will be most welcome.

[Robert Dickenson]

so far pretty much the entire site is generated, with just a few initial test entries of doxygen markup within the source modules.

[Leonardo Garberoglio]

Wowwwwww!

The graphical dependecy is awesome!!! It help a lot! I don't know all files and the purpose of each one, so study code to porting to STM32 is a litle tricky becouse I have to look at so many files. With this graphical representation I will have the list of files to look at on just one graph.

It's very useful for me. Call graph and caller graph!!!! what a wonderfull tool!!!!!!!! my printer will be busy this days....

BTW, I would like to write code compatible with this doxygen, what do I have to do? Another thing that will be very usefull is tha hedear comment of each function. I mean, the description that we write before each function:
/**
* @brief This function handles USART6 global interrupt.
*/
void USART6_IRQHandler(void)
{

[Mark Whitehorn]

http://en.wikipedia.org/wiki/Doxygen

It's just sad we can't use javadoc :)

Mark Whitehorn
kd0...@gmail.com

[Robert Dickenson]

if it's better, then why can't we use it, is it for java only?

[Robert Dickenson]

Hi Leo,

I recommend you copy the 'Doxyfile' from trunk, modify to suit your own source tree (shouldn't take much, just add libSTM to the list) and generate your own local doxygen web output!

Since you branch came off beta, you may notice (especially the include tree) it's not so 'clean' - this is because i may quite a few changes in trunk to improve the structure. However please note that i am still in the process of testing these changes.

Cheers, Robert.

[Mark Whitehorn]

:) I meant it's too bad we're not using Java

[Robert Dickenson]

ah-ha, i take it you're having a good time with java. most recently i've been playing with python, and still undecided whether or not i like it (-;