Difference between revisions of "Useful links"

From OTBWiki
Jump to: navigation, search
(Created page with "Here is a list of links that will help you in your OTB-Developpement. == Community == * Orfeo ToolBox web site [http://www.orfeo-toolbox.org] * The OTB blog [http://blog.orfeo-t…")
 
m (Manuel.grizonnet <1movedto2>)
 
(3 intermediate revisions by one other user not shown)
Line 12: Line 12:
 
* The doxygen that gathers the library documentation [http://www.orfeo-toolbox.org/doxygen]
 
* The doxygen that gathers the library documentation [http://www.orfeo-toolbox.org/doxygen]
 
* Documentation
 
* Documentation
** The Sotware Guide to have a quiet complete description of the functionnality of the OTB []
+
** The Software Guide to have a quiet complete description of the functionality of the OTB
 
*** HTML [http://www.orfeo-toolbox.org/SoftwareGuide]
 
*** HTML [http://www.orfeo-toolbox.org/SoftwareGuide]
 
*** pdf [http://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf]
 
*** pdf [http://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf]
** The Cookbook that will show you how to use our application and Monteverdi  
+
** The Cookbook that will show you how to use our applications and Monteverdi  
 
*** HTML [http://www.orfeo-toolbox.org/CookBook/]
 
*** HTML [http://www.orfeo-toolbox.org/CookBook/]
 
*** pdf [http://www.orfeo-toolbox.org/packages/OTBCookBook.pdf]
 
*** pdf [http://www.orfeo-toolbox.org/packages/OTBCookBook.pdf]
 
* Available packages (sources and exe)
 
* Available packages (sources and exe)
 
** of the last release [http://www.orfeo-toolbox.org/packages]
 
** of the last release [http://www.orfeo-toolbox.org/packages]
** of the current sources http://www.orfeo-toolbox.org/packages/nightly
+
** of the current sources [http://www.orfeo-toolbox.org/packages/nightly]
 
* Bug tracker [http://bugs.orfeo-toolbox.org/my_view_page.php]
 
* Bug tracker [http://bugs.orfeo-toolbox.org/my_view_page.php]
  
Line 27: Line 27:
 
** of the last release doxygen [http://www.orfeo-toolbox.org/doxygen/classes.html]
 
** of the last release doxygen [http://www.orfeo-toolbox.org/doxygen/classes.html]
 
** of the current doxygen [http://www.orfeo-toolbox.org/doxygen-current/classes.html]
 
** of the current doxygen [http://www.orfeo-toolbox.org/doxygen-current/classes.html]
 +
* HG sources [http://hg.orfeo-toolbox.org]
 +
** OTB [http://hg.orfeo-toolbox.org/OTB]
 +
** Monteverdi [http://hg.orfeo-toolbox.org/Monteverdi]
 +
** OTB-Wrapping [http://hg.orfeo-toolbox.org/OTB-Wrapping]
 +
** OTB-Data [http://hg.orfeo-toolbox.org/OTB-Data]
 
* Dashboard, where every nighlty tests results are gathered [http://dash.orfeo-toolbox.org]
 
* Dashboard, where every nighlty tests results are gathered [http://dash.orfeo-toolbox.org]
 
** OTB [dash.orfeo-toolbox.org/index.php?project=OTB]
 
** OTB [dash.orfeo-toolbox.org/index.php?project=OTB]
 
** Monteverdi [http://dash.orfeo-toolbox.org/index.php?project=Monteverdi]
 
** Monteverdi [http://dash.orfeo-toolbox.org/index.php?project=Monteverdi]
 
** OTB-Wrapping [http://dash.orfeo-toolbox.org/index.php?project=OTB-Wrapping]
 
** OTB-Wrapping [http://dash.orfeo-toolbox.org/index.php?project=OTB-Wrapping]
* Coverage. Coverage computation are launched every days. The result can be see in the section "Coverage" of the Dashboard (at the end of the projet page).
+
* Coverage. Coverage computation are launched every days. The result can be see in the section "Coverage" of the Dashboard (at the end of the project page).
 
If you click on the percentage you will see a new page that shows the coverage percentage of each file of the project (see as example [http://dash.orfeo-toolbox.org/viewCoverage.php?buildid=74436]).
 
If you click on the percentage you will see a new page that shows the coverage percentage of each file of the project (see as example [http://dash.orfeo-toolbox.org/viewCoverage.php?buildid=74436]).
* Formatting. Each night, KWStyle check our source code formatting according to some specified rules displays the result at [http://orfeo-toolbox.org/style].
+
* Style. Each night, KWStyle checks our source code style and format according to some specified rules displays the result here [http://orfeo-toolbox.org/style].
The rules are the following one :
+
The rules are the following one:
 
** LEN: Line Length = 120 max chars
 
** LEN: Line Length = 120 max chars
 
** IVR: ivars should match regular expression: m_[A-Z]
 
** IVR: ivars should match regular expression: m_[A-Z]

Latest revision as of 11:19, 22 August 2013

Here is a list of links that will help you in your OTB-Developpement.

Community

  • Orfeo ToolBox web site [1]
  • The OTB blog [2]
  • The wiki [3]
  • Mailing list

Users

  • The doxygen that gathers the library documentation [6]
  • Documentation
    • The Software Guide to have a quiet complete description of the functionality of the OTB
    • The Cookbook that will show you how to use our applications and Monteverdi
  • Available packages (sources and exe)
    • of the last release [11]
    • of the current sources [12]
  • Bug tracker [13]

Developers

  • Classes documentation:
    • of the last release doxygen [14]
    • of the current doxygen [15]
  • HG sources [16]
  • Dashboard, where every nighlty tests results are gathered [21]
    • OTB [dash.orfeo-toolbox.org/index.php?project=OTB]
    • Monteverdi [22]
    • OTB-Wrapping [23]
  • Coverage. Coverage computation are launched every days. The result can be see in the section "Coverage" of the Dashboard (at the end of the project page).

If you click on the percentage you will see a new page that shows the coverage percentage of each file of the project (see as example [24]).

  • Style. Each night, KWStyle checks our source code style and format according to some specified rules displays the result here [25].

The rules are the following one:

    • LEN: Line Length = 120 max chars
    • IVR: ivars should match regular expression: m_[A-Z]
    • IVA ivars should be aligned with previous ivars
    • SEM: Semicolons = 0 max spaces
    • DCL: Declaration order should match Public/Protected/Private
    • EOF: The file should have only one new line
    • TAB: The file should not have any tabs
    • ESP: Spaces at the end of line = 3 max spaces
    • HRD: The header should respect the template
    • DEF: #ifndef/#define should match __[NameOfClass]_[Extension]
    • TDR: Typedefs should match regular expression: [A-Z]
    • TDA: Typedefs should be aligned
    • NMC: The name of the class should match otb[NameOfClass]
    • WCM: The comments are misspelled
    • MCM: The class should have previously define comments starting with \class (allowing empty line)
    • EML: Empty lines = 2 max lines
    • TPL: Template should match the regex: [TNV]
    • OPS: Number of spaces for the operators shoud be: before=1, after=1