|
|
|
 Everyone needs to start working with what they are given, and start appreciating FIRST, not complaining about what they think FIRST is doing wrong. - Marygrace [more] |
 |
|
|||||||
|
||||||||
 |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| Everyone needs to start working with what they are given, and start appreciating FIRST, not complaining about what they think FIRST is doing wrong. - Marygrace [more] |
|
|
|||||||
|
||||||||
|
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Finding Documentation
|
|
#2
05-05-2012, 09:15
|
|||
|
|||
|
Re: Finding Documentation
The best documentation is ALWAYS the source code. Luckily for you, WPILib is open source, and you get said source when you install the software.
Also, if you've ever used doxygen before, you can generate documentation FROM the source code. This documentation is *relatively* complete. You can see an example at http://rbmj.github.com/612-code/doc/html/ of what this looks like.
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
