|Subject:||Re: [Paparazzi-devel] Contributing to the Paparazzi project - Beginner questions|
|Date:||Thu, 12 Sep 2013 23:13:21 +0200|
Do you mind if I add the highlighting?
Is it a good idea to just have the module documentation in the doxygen docs and then just add a link in the wiki to the respective doxygen page for a module?
Imho it would be great to have both, since the wiki has pictures/figures.
Hm. Since I'm new to paparazzi, I'd like to gain more XP first.- At some point we want to convert subsystems to the modules format as well (and use that in the same way to generate docs for them).Then we could also specify the matching settings files and automatically add them (see issue 23)- For other generic defines/options, it would make sense to rethink the way we specify options. E.g. a generic macro to add a new option with description that can then be parsed by doxygen).
Sure, I could write the generic macro and some parser/doxygen magic to generate the list, but I still have limited experience with the code to sufficently test it afterwards.
For example, to use ppz I had to install python (well, python was already installed), tcl-dev and ocaml-*.
About the paparazzi source code (available through github):
-) Upon installing the paparazzi-software package, I noticed that paparazzi has quite a lot of dependencies of which most look to be redundant.
Less dependencies, imho ease code testing, maintenance and installation.
Are there any plans to reduce the number of dependencies and external libraries?
Could you be a bit more specific? What do you mean by redundant dependencies?In general it would be good to reduce dependencies if you can achieve the same thing with another lib we already have...
Paparazzi uses afaik four 'programming' languages (python, tcl or it's libraries, C, ocaml) or more!?
Additionally I had to install XML parsers for python and ocaml.
Thus I thought that there are redundancies I could help to get rid of...
But: From your answer to my rather provocative question, I get that I should learn more about ppz before.
If I find something I think can be done using another lib that's already in use, I'll write the necessary code and let you know.
Sorry, I did not mean to be rude!
|[Prev in Thread]||Current Thread||[Next in Thread]|