|
Last change
on this file since 22 was
10,
checked in by wcaarls, 12 years ago
|
|
Imported saliency_detection at revision 1000
|
|
File size:
590 bytes
|
| Line | |
|---|
| 1 | /** |
|---|
| 2 | \mainpage |
|---|
| 3 | \htmlinclude manifest.html |
|---|
| 4 | |
|---|
| 5 | \b saliencymaps is ... |
|---|
| 6 | |
|---|
| 7 | <!-- |
|---|
| 8 | Provide an overview of your package. |
|---|
| 9 | --> |
|---|
| 10 | |
|---|
| 11 | |
|---|
| 12 | \section codeapi Code API |
|---|
| 13 | |
|---|
| 14 | <!-- |
|---|
| 15 | Provide links to specific auto-generated API documentation within your |
|---|
| 16 | package that is of particular interest to a reader. Doxygen will |
|---|
| 17 | document pretty much every part of your code, so do your best here to |
|---|
| 18 | point the reader to the actual API. |
|---|
| 19 | |
|---|
| 20 | If your codebase is fairly large or has different sets of APIs, you |
|---|
| 21 | should use the doxygen 'group' tag to keep these APIs together. For |
|---|
| 22 | example, the roscpp documentation has 'libros' group. |
|---|
| 23 | --> |
|---|
| 24 | |
|---|
| 25 | |
|---|
| 26 | */ |
|---|
Note: See
TracBrowser
for help on using the repository browser.
