source: orbit/iOS/Orbit/Orbit/CorePlotHeaders/mainpage.h @ e5b8e57

Last change on this file since e5b8e57 was a9059a5, checked in by Steve Castellotti <sc@…>, 10 years ago


  • updated to permit custom setting of Throttle, Yaw, and Pitch


  • Minor tweak to Configuration location


  • Property mode set to 100644
File size: 2.0 KB
1/*! @mainpage Core Plot
2 *
3 *  @section intro Introduction
4 *
5 *  Core Plot is a plotting framework for Mac OS X and iOS. It provides 2D visualization of data,
6 *  and is tightly integrated with Apple technologies like Core Animation, Core Data, and Cocoa Bindings.
7 *
8 *  @section start Getting Started
9 *
10 *  See the project wiki at
11 * for information on how to use Core Plot
12 *  in your own application.
13 *
14 *  @section contribute Contributing to Core Plot
15 *
16 *  Core Plot is an open source project. The project home page is on Google Code.
17 *  See for instructions on how to download the source code.
18 *
19 *  @subsection coding Coding Standards
20 *  Everyone has a their own preferred coding style, and no one way can be considered right. Nonetheless, in a
21 *  project like Core Plot, with many developers contributing, it is worthwhile defining a set of basic coding
22 *  standards to prevent a mishmash of different styles which can become frustrating when
23 *  navigating the code base. See the file <code>"Coding Style.mdown"</code> found in the <code>documentation</code> directory
24 *  of the project source for specific guidelines.
25 *
26 *  @subsection documentation Documentation Policy
27 *  See for instructions on how to
28 *  document your code so that your comments will appear in these documentation pages.
29 *
30 *  @subsection testing Testing Policy
31 *  Because Core Plot is intended to be used in scientific, financial, and other domains where correctness is paramount,
32 *  unit testing is integrated into the framework. Good test coverage protects developers from introducing accidental
33 *  regressions and frees them to experiment and refactor without fear of breaking things. See
34 * for instructions on how to build unit tests
35 *  for any new code you add to the project.
36 */
Note: See TracBrowser for help on using the repository browser.