V3.1 SP1 (3.0.1) released

.. updated versioning and upgrade ids.

.gitignore

@@ -0,0 +1,8 @@
+Makefile
+
+# old skool
+.svn
+
+# osx noise
+.DS_Store
+profile

INSTALL-LINUX

@@ -0,0 +1,401 @@
+                                 +++++++++++++++++++++++
+                                 LINUX BUILD WALKTHROUGH
+                                 +++++++++++++++++++++++
+
+                                     Mark Liversedge
+                                     John Ehrlinger
+
+                                        May 2011
+                                      Version 1.1
+
+A walkthrough of building GoldenCheetah from scratch on Ubuntu linux. This walkthrough
+should be largely the same for any Linux distro.
+
+CONTENTS
+
+1. BASIC INSTALLATION WITH MANDATORY DEPENDENCIES
+   - QT
+   - git
+
+2. ADDING OPTIONAL DEPENDENCIES WHEN BUILDING VERSION 2
+   - FTDI D2XX
+   - SRMIO
+   - liboauth
+   - QwtPlot3d
+   - libkml
+
+3. ADDING OPTIONAL DEPENDENCIES WHEN BUILDING VERSION 3
+   - checking out the release 3 branch & building with MANDATORY dependencies
+     - flex
+     - bison
+   - libical - Diary window and CalDAV support (google/mobileme calendar integration)
+   - libvlc  - Video playback in training mode
+   - clucene - Indexing/Searching ride files
+
+
+1. BASIC INSTALLATION WITH MANDATORY DEPENDENCIES
+=================================================
+
+Installed Ubuntu 11.04 from CD image amd-64.iso. You will not need to do this if you
+already have a Linux distribution installed. Left this step in to highlight the
+Linux distribution the commands below were executed on.
+
+login and open a terminal to get a shell prompt
+
+Download MANDATORY DEPENDENCIES (browser)
+-----------------------------------------
+Download and install the Qt 4.8 SDK from http://qt-project.org/
+Once that is completed test qmake is ok with: qmake --version (should report 4.7.0 or higher)
+
+Install git with:
+$ sudo apt-get install git
+Said Y to prompt about all git files installed (git-gui et al)
+
+Install FLEX and BISON
+----------------------
+
+You will need flex v2.5.9 or later
+$ sudo apt-get install bison
+$ sudo apt-get install flex
+$ vi gcconfig.pri
+
+Ensure you have the following lines (which are now also in gcconfig.pri.in which has
+been updated to reflect the new dependencies in version 3)
+
+QMAKE_LEX  = flex
+QMAKE_YACC = bison
+win32 {
+  QMAKE_YACC = bison --file-prefix=y -t
+  QMAKE_MOVE = cmd /c move
+  QMAKE_DEL_FILE = rm -f
+}
+
+Build!
+------
+$ make clean
+$ qmake
+$ make
+
+You will now have a release3 binary but with none of the release3 dependencies compiled in.
+Get latest GOLDEN CHEETAH source files
+--------------------------------------
+$ mkdir -p ~/Projects/Live
+$ cd ~/Projects/Live
+$ git clone git://github.com/GoldenCheetah/GoldenCheetah.git
+$ cd GoldenCheetah
+
+Configure MANDATORY DEPENDENCIES
+--------------------------------
+$ cd qwt
+$ cp qwtconfig.pri.in qwtconfig.pri
+$ cd ../src
+$ cp gcconfig.pri.in gcconfig.pri
+$ vi gcconfig.pri
+
+Comment out the D2XX_INCLUDE and SRMIO_INSTALL lines for now (put # in first character of the line
+to comment out), we will install that in a moment, if we need to.
+
+If you are building for your local host you may find that you get better performance if
+compiling with gcc -O3 (tree vectorization can have a significat impact) [or -Ofast]
+
+If so you might like to uncomment:
+
+QMAKE_CXXFLAGS += -O3
+
+Save and exit
+
+$ cd ..
+
+BUILD WITH BASIC CONFIGURATION
+$ qmake -recursive
+$ make
+
+Congratulations you have now build a basic GoldenCheetah and can run this safely. See below for
+optional dependencies you can install to support other features.
+
+ADDING OPTIONAL DEPENDENCIES WHEN BUILDING VERSION 2
+====================================================
+
+D2XX - For Powertap downloads via USB
+-------------------------------------
+
+Download the FTDI drivers from http://www.ftdichip.com/Drivers/D2XX.htm (e.g. I used Linux 
+64-bit drivers from http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.0.4.tar.gz)
+
+Extract into your home directory (I put mine into ~/Projects/ with archive manager which
+created a sub-directory ~/Projects/libftd2xx1.0.4
+
+$ cd src
+$ vi gcconfig.pri
+
+Uncomment the D2XX_INCLUDE entry and make it match (my home is /home/markl)
+D2XX_INCLUDE = /home/markl/libftd2xx1.0.4
+
+Make clean is needed if you have previouslt built, since source files examine #defines before
+including this feature. You can skip it if you know why ;)
+$ make clean
+$ qmake
+$ make
+
+You now have D2XX support, for downloading from a PT via a USB cradle.
+
+SRMIO - For SRM powercontrol V downloads via Serial
+---------------------------------------------------
+
+$ cd ~/Projects
+$ git clone git://github.com/rclasen/srmio srmio
+$ cd srmio
+
+Get automake and tools, if you don't already have them (I didn't after a fresh install)
+$ sudo apt-get install automake
+$ sudo apt-get install libtool
+
+Generate the configure script, run it, build and install srmio
+$ sh genautomake.sh
+$ ./configure
+$ make
+$ sudo make install
+
+Lets go config GC and build with SRMIO
+$ cd ~/Projects/Live/GoldenCheetah/src
+$ vi gcconfig.pri
+
+Uncomment the SRMIO_INSTALL and replace with the target used from srmio install:
+SRMIO_INSTALL = /usr/local/
+
+At the bottom of gcconfig.pri you will see the include directory should reference from
+the base install location (/usr/local) make sure it says:
+
+SRMIO_INCLUDE = $${SRMIO_INSTALL}/include
+SRMIO_LIB = $${SRMIO_INSTALL}/lib/libsrmio.a
+
+Make clean is needed if you have previouslt built, since source files examine #defines before
+including this feature. You can skip it if you know why ;)
+$ make clean
+$ qmake
+$ make
+
+You now have SRM support built in.
+
+OAUTH/CRYPT - For Tweet my ride (twitter) support
+-------------------------------------------------
+
+You should be able to install liboauth and dependencies
+directly with:
+$ sudo apt-get install liboauth-dev
+
+If this does not work then:
+
+    Download the source from: http://sourceforge.net/projects/liboauth/files/liboauth-0.9.4.tar.gz/download and
+    unpack it into ~/Projects/liboauth-0.9.4 using archive manager
+
+    $ cd ~/Projects/liboauth-0.9.4
+
+    You may find that libcurl is not installed (which liboauth depends upon) so download it
+    from http://curl.haxx.se/download/curl-7.21.6.tar.gz and unpack it into ~/Projects/curl-7.21.6
+    using archive manager to drag and drop into your Projects folder
+
+    $ cd ~/Projects/curl-7.21.6
+    $ ./configure
+    $ make
+    $ sudo make install
+
+    You should now have libcurl and friends installed in /usr/local
+
+    You may find that liboauth also requires the openssl libs installed, these are available
+    pre-packaged thankfully so:
+    $ sudo apt-get install libssl-dev
+
+    This will also install zlibg which liboauth also desires.
+
+    $ cd ~/Projects/liboauth-0.9.4
+    $ ./configure
+    $ make
+    $ sudo make install
+
+Now we have liboauth and libcurl in /usr/local and libssl in /usr/lib, so we can go back to
+GoldenCheetah and update the gcconfig.pri to point at the right places:
+
+$ cd ~/Projects/Live/GoldenCheetah/src
+$ vi gcconfig.pri
+
+Make sure the following are set:
+LIBOAUTH_INSTALL = /usr/local
+LIBCRYPTO_INSTALL = -lcrypto
+LIBCURL_INSTALL=-lcurl
+
+Make clean is needed if you have previously built, since source files examine #defines before
+including this feature. You can skip it if you know why ;)
+$ make clean
+$ qmake
+$ make
+
+You can now tweet your rides and amaze your friends, or alternatively tweet your rides but
+omit to mention average power to hide your weaknesses.
+
+LIBQWTPLOT3D - For 3D plot
+--------------------------
+
+Download the tarball from http://qwtplot3d.svn.sourceforge.net/viewvc/qwtplot3d/branches/maintain_0_2_x/qwtplot3d/?view=tar
+and unarchive it into your Projects directory using archive manager. There is no version number it just creates a
+subdirectory called qwtplot3d
+
+You will need to install libgl and extensions, this can be done with;
+$ sudo apt-get install libgl1-mesa-dev
+$ sudo apt-get install libglu-dev
+
+On Ubuntu 12.10 I also ran
+$ sudo apt-get install freeglut3 freeglut3-dev
+
+$ cd ~/Projects/qwtplot3d
+Edit the qwtplot3d.pri and add
+CONFIG += staticlib
+
+You will find that on modern Linuxes you also need to fix include/qwt3d_global.h by adding the line:
+#include <GL/glu.h>
+
+then build
+$ qmake
+$ make
+
+Then to let gc know where the qwtplot3d libs are you need to edit gcconfig.pri;
+$ cd ~/Projects/Live/GoldenCheetah/src
+$ vi gcconfig.pri
+
+And uncomment the following line and set the install directory to where you build
+QWT3D_INSTALL = ~/Projects/qwtplot3d
+
+
+
+LIBKML - For export to Google Earth
+-----------------------------------
+
+You will need Google Earth 5.2 or later and therefore libkml that supports this. Unfortunately at the time of writing
+the officially packaged libkml is too old, so you will need to install from source, which means you will need to have
+subversion installed and expat. You may be able to use the currently packaged libkml with
+
+$ sudo apt-get install libkml-dev
+
+if this does not work you will need to build from source:
+
+    $ sudo apt-get install subversion
+    $ sudo apt-get install expat libexpat1 libexpat1-dev
+
+    Once svn is installed you can grab the libkml source and configure build etc:
+    $ cd ~/Projects
+    $ svn checkout http://libkml.googlecode.com/svn/trunk/ libkml
+    $ cd libkml
+
+    You will need automake and friends (see SRMIO above)
+    $ sh autogen.sh
+    $ ./configure
+    $ make
+    $ make install
+    $ sudo make install
+
+    If you get errors about use of 'long long' then edit:
+    - src/kml/{convenience,dom,engine,regionator,xsd}/Makefile
+    - examples/{engine,gpx,gx,hellonet,helloworld,regionator,xsd}/Makefile
+    - and look for the flag -pedantic and remove it. I got this on Linux 64bit builds ymmv.
+
+Once libkml is installed and built:
+
+$ cd ~/Projects/Live/GoldenCheetah/src
+$ vi gcconfig.pri
+
+Ensure KML_INSTALL=/usr/local
+
+Make clean is needed if you have previously built, since source files examine #defines before
+including this feature. You can skip it if you know why ;)
+$ make clean
+$ qmake
+$ make
+
+You can now export rides to Google Earth kml format.
+
+ADDING OPTIONAL DEPENDENCIES WHEN BUILDING VERSION 3
+====================================================
+
+
+NOTE: When you run version 3 it will refresh ride metrics and CP files -- this only occurs the
+      first time it runs (and will refresh only rides that change after that). I find it is best
+      to import ride files once your build where you want it. i.e. don't import until you have
+      got all your dependencies sorted.
+
+NOTE: To reduce the dependencies on 'dormant' code there are a number of new pieces of source
+      that are included in the release3 tree. Notably; qtsoap from qt-solutions, since they
+      work but are likely to be archived and deprecated. If and when that happens we may well
+      adopt whatever classes Trolltech introduce.
+
+
+LIBICAL - Diary integration with Google or MobileMe calendars
+-------------------------------------------------------------
+
+$ cd ~/Projects/Live/GoldenCheetah/src
+
+$ sudo apt-get install libical-dev
+$ vi gcconfig.pri
+
+ICAL_INSTALL=/usr/include
+ICAL_LIBS=-lical
+
+Since the src.pro wants ICAL installed in a different place we need to hack it, *** this will
+be fixed shortly ***
+
+$ vi src.pro
+
+Comment out the ICAL_LIBS entry:
+
+#ICAL_LIBS = $${ICAL_INSTALL}/lib/libical.a
+
+$ make clean
+$ qmake
+$ make
+
+You should now have diary functions.
+
+NOTE: That upload to MobileMe and Google requires a functioning https lib in QT. Depending
+      upon the version installed this might not be the case and will need to be built and
+      configured -- this is beyond the scope of this walkthough. Sorry.
+
+LIBVLC - Video playback in Realtime (Experimental)
+--------------------------------------------------
+
+You will need libvlc 1.1.9 or higher (1.1.8 is ok but will segv on exit)
+$ sudo apt-get install libvlc-dev
+
+$ vi gcconfig.pri
+
+Comment out VLC_INSTALL and it should read:
+
+VLC_INSTALL = /usr/include/vlc/
+
+$ make clean
+$ qmake
+$ make
+
+CLUCENE - Indexing and Searching ride files (search box)
+--------------------------------------------------------
+
+You will need clucene runtime and core libraries, we developed against 0.9.21b-2 but
+any 0.9 branch should work fine, let us know if you experience any issues. You may find
+that the libclucene0ldbl runtime is already installed, this is fine and typical since
+clucene is a very popular search library.
+
+$ sudo apt-get install libclucene-dev
+$ sudo apt-get install libclucene0ldbl
+
+By default, and this is deliberate, the clucene install places the config headers into
+a platform specific location. For my install I just copy the platform (linux) specific
+header config into the normal /usr/include/CLucene directory with the following:
+
+$ sudo cp /usr/lib/CLucene/clucene-config.h /usr/include/CLucene
+
+Next we need to comment out the two CLUCENE lines in gcconfig.pri and they should read:
+
+CLUCENE_INCLUDE = /usr/include/CLucene
+CLUCENE_LIBS    = -lclucene
+
+$ make clean
+$ qmake
+$ make

INSTALL-MAC

@@ -0,0 +1,311 @@
+                                 +++++++++++++++++++++++
+                                MAC OSX BUILD WALKTHROUGH
+                                 +++++++++++++++++++++++
+
+                                     Mark Liversedge
+
+                                        Nov 2011
+                                      Version 1.1
+
+A walkthrough of building GoldenCheetah from scratch on Mac OSX. This was performed
+on Mac OSX Lion (10.7) but the instructions are largely the same for all versions of
+Mac OS X.
+
+CONTENTS
+
+1. BASIC INSTALLATION WITH MANDATORY DEPENDENCIES
+   - Xcode
+   - Qt
+
+2. ADDING OPTIONAL DEPENDENCIES
+   - FTDI D2XX
+   - SRMIO
+   - liboauth
+   - QwtPlot3d
+   - libkml
+   - libusb
+   - libical
+   - libclucene
+
+
+1. BASIC INSTALLATION WITH MANDATORY DEPENDENCIES
+=================================================
+
+Depending upon the speed of your internet connection and availability of the
+required software the steps in section 1 will take approximately 1 hour.
+
+1.1 Ensure OS X is up-to-date
+-----------------------------
+
+Make sure you have applied all the latest updates to Mac OS X. This can be
+found from the system menu, apple, about this mac, software update.
+
+This walkthrough was performed on an iMac running 10.7.2 (Lion)
+
+1.2 Install XCode from App Store
+--------------------------------
+
+If you are building on 10.6 or higher you should install Xcode4, for earlier
+releases you will need Xcode 3.1.4. If you have capable hardware you should
+consider upgrading to Lion to get the latest bug fixes and capabilities.
+
+To install Xcode on Lion you need to download it via the App Store. You can
+launch the App Store from launchpad, or it may be already in your dock.
+
+Under the search box type in Xcode and it will return a few optios, generally
+Xcode is the first item and shows a blueprint with a hammer icon. Click on
+this to install it. It should be free. The usual app store process will apply
+as the application is downloaded and installed. The download is about 2GB
+so do bear this in mind if you have limits on your internet bandwidth or cap.
+
+1.3 Run the Xcode installer
+---------------------------
+
+The app store download will have added an Install Xcode icon in the launchpad.
+Go ahead and run it.
+
+Xcode includes all the development tools such as a compiler, debugger and
+SDKs. It also installs the 'git' tool for working with Git repositories.
+
+It will run through a wizard to install, just read and then accept the license
+agreement and let it get on with it. If you don't like the license then quit
+and use the development builds from goldencheetah.stand2surtf.net.
+
+You may find it borks at iTunes helper running, you will
+need to force quit the iTunes helper via Finder, Applications, Utilities,
+Activity Monitor if this happens.
+
+1.4 Get the source code
+-----------------------
+
+We store all the Golden Cheetah source code on github.com, it is a great
+site holding repositories for many open source projects. 
+
+First open up a terminal session, then;
+
+$ cd
+$ mkdir Projects
+$ cd Projects
+$ git clone git://github.com/GoldenCheetah/GoldenCheetah.git
+
+You will now have the GoldenCheetah sources downloaded into a 'GoldenCheetah'
+directory in your home directory, under another folder called 'Projects'.
+
+$ cd GoldenCheetah
+$ ls
+
+You should see a number of directories such as doc, qwt, src etc. If you are
+building the latest development release you may need to check it out. At the
+time of writing the latest development release is release_3.0.0dev, if you
+want to build version 3 then you should perform the next command, otherwise 
+skip to 1.5.
+
+$ checkout release_3.0.0dev
+$ ls
+
+You will now see an updated version of this walkthrough, please jump to using
+that since it may be more up-to-date than this walkthrough (depending upon
+where you got it from of course!).
+
+1.5 Install the QT SDK
+----------------------
+
+GoldenCheetah is developed using the Nokia QT toolkit, it is large and will
+need to be downloaded and installed from their website. Alternatively, you 
+can intall qt via macports (http://www.macports.org) as described in section 
+1.5.1. 
+
+As of today, the latest stable release is 4.7.4, we need 4.7 or higher so
+go ahead and download the offline installer - it has everything you need
+but is about 1.3GB. Please make sure you download the installer for Mac
+OS X 10.6 or later, 64-bit.
+
+The url for QT downloads is: http://qt.nokia.com/downloads and whilst the
+offline installer is only 12mb it will still call back and download the
+required objects as you install, I think it is better to get it all in
+one hit (and you can save it to reinstall on another computer or if you
+want to rebuild/reinstall for any other reason).
+
+Once the QT SDK is downloaded you will have a .dmg (disk image) that you
+need to mount by double clicking on it. You will then get a volume mounted
+and shown on your desktop. Go ahead and double click that to start the install
+process. It is probably called something like 'Qt SDK Installer'.
+
+It will popup with a dialog warning that this is downloaded from the internet
+and are you sure you want to open it? Go ahead and click Open.
+
+A wizard will now guide you through the QT install process. Go ahead and accept
+all the defaults, it will install in your home directory and avoid updating the
+system directories, this means you are less likely to bork your Mac OSX installation.
+
+Read and accept the license agreement and then continue and install.
+
+We need to make sure that a program called qmake is installed in a directory where
+it can be found. So, we need to create a link from what we just installed in the
+user programs folder. For QT SDK1.1 (4.7.4) we need to:
+
+$ sudo ln -s ~/QtSDK/Desktop/Qt/474/gcc/bin/qmake /usr/bin/qmake
+
+1.5.1 Install via Mac Ports
+---------------------------
+
+If you have macports installed, you can install the qt dependices 
+with the following commands: 
+
+$ sudo port install qt4-mac
+$ sudo port install qt4-mac-sqlite3-plugin
+
+1.6 DEPRECATED
+--------------
+
+No longer need this step (install boost)
+
+1.7 Configure and Build GoldenCheetah (with no optional dependencies)
+---------------------------------------------------------------------
+
+First thing we need to do is set the build configuration, this means editing the
+private build profile settings. There is one for qwt (a charting library) and
+there is another for GoldenCheetah itself.
+
+$ cd ~/Projects/GoldenCheetah/qwt
+$ cp qwtconfig.pri.in qwtconfig.pri
+$ cd ../src
+$ cp gcconfig.pri.in gcconfig.pri
+$ vi gcconfig.pri 
+
+In that last step you can use whatever editor you feel most comfortable with.
+
+For now we will comment out some of the dependencies we have not installed
+support for yet:
+
+#SRMIO_INSTALL = /usr/local/srmio
+#D2XX_INCLUDE = /usr/local/include/D2XX
+
+we may need to additionally configure to use the local compression
+libraries (at least I did), by adding the following line:
+
+LIBS += -lz
+
+Lastly, since we are on Lion, we can also uncomment and change the following line:
+
+DEFINES += GC_HAVE_LION
+
+Once the changes have been made we are now ready to build for the first time. You
+may notice a lot of warning messages about the version of O/S not being supported.
+This is because QT does not officially support Lion at this point in time (but it
+does work). You can either ignore the warning messages or (like me) go and edit out
+the warning (once you have seen the message once you don't need reminding every
+time you compile).
+
+To do this, edit the file in question as an administrator:
+
+$ sudo vi ~/QtSDK/Desktop/Qt/474/gcc/include/QtCore/qglobal.h
+
+And comment out line 320 (or thereabouts):
+
+//#    warning "This version of Mac OS X is unsupported"
+
+Once this is done you can kick off the build:
+
+$ cd .. #this should put you in the top level dir containing this file
+$ qmake -recursive
+$ make
+
+If make fails to find a Makefile then qmake is configured, by default, to create
+an xcode project file. You will need to change the qmake command above to tell it
+to create a makefile with the following:
+$ qmake -spec macx-g++ -recursive
+$ make
+
+Once this completes you will have a GoldenCheetah.app in the src directory which
+can be launched:
+
+$ open src/GoldenCheetah.app
+
+And you're up and running.
+
+2. ADDING OPTIONAL DEPENDENCIES
+===============================
+
+   - SRMIO
+   - liboauth
+   - QwtPlot3d
+   - libkml
+   - libusb
+   - libical
+
+Since these optional dependencies are more complex and require more advanced
+technical skills we do not provide a walkthrough for building them all but
+instead provide the configure settings and any special considerations that
+should be taken into account.
+
+2.1 SRMIO - For working with PC 5/6/7
+-------------------------------------
+
+SRMIO (git)
+./configure CFLAGS="-isysroot /Developer/SDKs/MacOSX10.7.sdk -arch x86_64" CPPFLAGS=-I/usr/local/D2XX/ --disable-dependency-tracking
+
+2.2 Liboauth - For Twitter support
+----------------------------------
+
+oauth (0.8.8)
+
+./configure CFLAGS="-isysroot /Developer/SDKs/MacOSX10.7.sdk -arch x86_64 CURL_CFLAGS="-I/Developer/SDKs/MacOSX10.7.sdk/usr/include/curl"  CURL_LIBS="-lcurl" --disable-dependency-tracking
+
+2.3 QwtPlot3d - For 3d plot support
+-----------------------------------
+
+qwtplot3d (maintain_0_2_x)
+
+Add the following to qwtplot3d.pro:
+CONFIG += x86_64 static
+QMAKE_MAC_SDK=/Developer/SDKs/MacOSX10.7.sdk
+
+2.4 libkml - For export to Google Earth
+---------------------------------------
+
+expat (2.0.1)
+./configure CFLAGS="-isysroot /Developer/SDKs/MacOSX10.7.sdk -arch x86_64" --disable-dependency-tracking 
+
+libkml (pulled down from the svn repo)
+
+./configure CFLAGS="-isysroot /Developer/SDKs/MacOSX10.7.sdk -arch x86_64" --disable-dependency-tracking --with-expat-include-dir=/usr/local/include --with-expat-lib-dir=/usr/local/lib --disable-swig CXXFLAGS="-isysroot /Developer/SDKs/MacOSX10.7.sdk -arch x86_64"
+
+note: the added CXXFLAGS helped clear the -Werror flag that stopped compilation.
+
+2.5 libusb - For Garmin USB2 stick support
+------------------------------------------
+
+libusb (0.1.12)
+
+To compile on OSX you need to apply the patch here:
+https://trac.macports.org/browser/trunk/dports/devel/libusb-legacy/files?rev=97840
+
+Then:
+./configure --prefix=/opt/libusb/ CFLAGS="-arch x86_64" CXXFLAGS="-arch x86_64" --disable-dependency-tracking
+then 
+sed -i 'bak' 's|CC -dynamiclib|CC -dynamiclib -arch x86_64|g' libtool
+make
+make install
+
+note: that the sed line updates some commands in libtool.  not sure why the arch clags are not getting passed.  
+
+2.6 libical
+-----------
+
+libical (0.46)
+first run autogen.sh
+then
+./configure CFLAGS="-isysroot /Developer/SDKs/MacOSX10.7.sdk -arch x86_64" --disable-dependency-tracking
+
+2.7 clucene
+-----------
+
+DO NOT USE THE MACPORTS VERSION (0.9.23) IT DOES NOT WORK.
+
+git clone git://clucene.git.sourceforge.net/gitroot/clucene/clucene 
+cmake -G "Unix Makefiles"
+make
+sudo make install
+
+will install clucene into /usr/local/include/clucene and /usr/local/lib

INSTALL-WIN32

@@ -0,0 +1,117 @@
+Please note: This is an old build instruction set for Version 2.x.
+
+Most of it is still fairly valid for version 3.x.
+
+Minimum build requirements are: Qt 4.8 with Qt.4.8.4 recommended.
+
+All other libs are find the best that you can except for libusb which requires 0.1.12.
+
+I have found that the cross compiler at http://mxe.cc/ to be great for building GC and SRMIO.
+
+                                 +++++++++++++++++++++++
+                                 WIN32 BUILD WALKTHROUGH
+                                 +++++++++++++++++++++++
+
+                                       Gareth Coco
+
+                                        May 2011
+
+For my install, I am installing all my files into the directory: d:\coding.
+You can use any directory structure you like, you’ll just have to change paths.
+Just ensure that any folder path you use does not have a space in it.
+
+Download the NSI installer application. I use the Portable Apps version from:
+  http://portableapps.com/apps/development/nsis_portable
+- Install in D:\Coding\NSISPortable\
+
+Download Qt SDK from:
+ http://qt.nokia.com/downloads/sdk-windows-cpp
+ (File I am using is qt-sdk-win-opensource-2010.02.1.exe)
+- Install in D:\Coding\Qt
+
+Download the D2XX drivers:
+ http://www.ftdichip.com/Drivers/D2XX.htm
+ (File I am using is: CDM 202.06.00 WHQL Certified.zip)
+- Install in D:\Coding\D2XX
+
+Download qwt-plot3d from:
+ http://sourceforge.net/projects/qwtplot3d/files/
+ (File I am using is qwtplot3d-0.2.7.zip)
+- Install in D:\Coding\qwtplot3d
+
+Edit D:\coding\qwtplot3d\src\qwt3d_function.cpp
+- Add at top of file: #include <cstdio>
+Edit D:\coding\qwtplot3d\qwtplot3d.pro
+- Comment out: #win32:TEMPLATE    = vclib
+
+Then I start the “Qt Command Prompt” from the Qt SDK folder.
+
+d:
+cd d:\coding\qwtplot3d\
+qmake -win32
+mingw32-make release
+
+Now check out your favourite web sites until the code is built.
+
+Leave the Qt Command Prompt window open as we use it later.
+
+Download GoldenCheetah source
+(Either use GIT – git://github.com/GoldenCheetah/GoldenCheetah.git
+ or download the zip file:
+ http://github.com/GoldenCheetah/GoldenCheetah/zipball/master)
+- Install in D:\Coding\GoldenCheetah
+
+Copy D:\Coding\GoldenCheetah\src\gccconfig.pri.in
+  to D:\Coding\GoldenCheetah\src\gccconfig.pri and edit
+- Set: D2XX_INCLUDE = d:/coding/D2XX
+- Comment out #SRMIO_INSTALL
+- Comment out: CONFIG += debug
+- Uncomment: CONFIG += static
+
+Copy D:\Coding\GoldenCheetah\qwt\qwtconfig.pri.in
+  to D:\Coding\GoldenCheetah\qwt\qwtconfig.pri and edit
+- Set win32 { INSTALLBASE    = D:/Coding/Qt  }
+- In #Qt4 win32 { section
+  – Comment out: #CONFIG           += debug     # release/debug/debug_and_release
+  – Add in:   CONFIG           += release
+
+Using the “Qt Command Prompt” window from before:
+
+cd d:\coding\GoldenCheetah
+qmake -win32 -recursive
+mingw32-make release
+
+Go back to checking your email or favourite web sites while this builds.
+
+When all is finished, you should have a release version in:
+
+D:\Coding\GoldenCheetah\src\release\
+
+Next , move required build files into the d:\coding\GoldenCheetah\src\release directory.
+
+cd d:\coding\GoldenCheetah
+copy /y ..\Qt\qt\bin\mingwm10.dll src\release\
+copy /y ..\Qt\qt\bin\QtCore4.dll src\release\
+copy /y ..\Qt\qt\bin\QtGui4.dll src\release\
+copy /y ..\Qt\qt\bin\QtSql4.dll src\release\
+copy /y ..\Qt\qt\bin\QtXml4.dll src\release\
+copy /y ..\Qt\qt\bin\QtNetwork4.dll src\release\
+copy /y ..\Qt\qt\bin\QtOpenGL4.dll src\release\
+copy /y ..\Qt\qt\bin\QtWebKit4.dll src\release\
+copy /y ..\Qt\qt\bin\QtXmlPatterns4.dll src\release\
+copy /y ..\Qt\qt\bin\phonon4.dll src\release\
+copy /y ..\Qt\qt\bin\libgcc_s_dw2-1.dll src\release\
+copy /y ..\qwtplot3d\lib\qwtplot3d.dll src\release\
+mkdir src\release\sqldrivers
+copy /y ..\Qt\qt\plugins\sqldrivers\qsqlite4.dll src\release\sqldrivers\
+mkdir src\release\imageformats
+copy /y ..\Qt\qt\plugins\imageformats\qjpeg4.dll src\release\imageformats\
+
+To build the self installer:
+
+cd d:\coding\GoldenCheetah\src\win32
+d:\coding\NSISPortable\App\NSIS\makensis.exe GoldenCheetahInstall.nsi
+
+You should find the installer file in the directory you are in.
+
+Install and enjoy.

Makefile

@@ -1,31 +0,0 @@
-# 
-# $Id: Makefile,v 1.11 2006/09/06 23:23:03 srhea Exp $
-#
-# Copyright (c) 2006 Sean C. Rhea (srhea@srhea.net)
-#
-# This program is free software; you can redistribute it and/or modify it
-# under the terms of the GNU General Public License as published by the Free
-# Software Foundation; either version 2 of the License, or (at your option)
-# any later version.
-# 
-# This program is distributed in the hope that it will be useful, but WITHOUT
-# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
-# more details.
-# 
-# You should have received a copy of the GNU General Public License along
-# with this program; if not, write to the Free Software Foundation, Inc., 51
-# Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
-#
-
-SUBDIRS=doc src
-
-all: subdirs 
-.PHONY: all subdirs clean
-
-clean:
-	@for dir in $(SUBDIRS); do $(MAKE) -wC $$dir clean; done
-
-subdirs:
-	@for dir in $(SUBDIRS); do $(MAKE) -wC $$dir; done
-

README

@@ -0,0 +1,9 @@
+Golden Cheetah install and build instructions are documented
+for each platform;
+
+INSTALL-WIN32   For building on Microsoft Windows
+INSTALL-LINUX   For building on Ubuntu Linux
+INSTALL-MAC     For building on Apple OS X
+
+Alternatively official builds are available from http://www.goldencheetah.org
+whilst latest developer builds are available from http://goldencheetah.stand2surf.net

build.pro

@@ -0,0 +1,3 @@
+TEMPLATE = subdirs
+SUBDIRS = qwt src
+CONFIG += ordered

contrib/Clucene-2.3.3.4-NoThreads.patch

@@ -0,0 +1,107 @@
+From 44a403d45ae049e7ade3e9b47a39778dcacf4382 Mon Sep 17 00:00:00 2001
+From: Mark Liversedge <liversedge@gmail.com>
+Date: Thu, 28 Mar 2013 22:03:35 +0000
+Subject: [PATCH] Fixup no threads for GC
+
+---
+ src/core/CLucene/debug/lucenebase.h |    2 +-
+ src/shared/CLucene/LuceneThreads.h  |   21 ++++++++++++++++++---
+ src/shared/CLucene/util/Misc.cpp    |    2 ++
+ src/shared/CLucene/util/Misc.h      |    2 ++
+ 4 files changed, 23 insertions(+), 4 deletions(-)
+
+diff --git a/src/core/CLucene/debug/lucenebase.h b/src/core/CLucene/debug/lucenebase.h
+index c053f11..9732ce6 100644
+--- a/src/core/CLucene/debug/lucenebase.h
++++ b/src/core/CLucene/debug/lucenebase.h
+@@ -6,7 +6,7 @@
+ ------------------------------------------------------------------------------*/
+ #ifndef _lucene_debug_lucenebase_
+ #define _lucene_debug_lucenebase_
+-
++#define _CL_DISABLE_MULTITHREADING
+ #include "CLucene/LuceneThreads.h"
+ 
+ CL_NS_DEF(debug)
+diff --git a/src/shared/CLucene/LuceneThreads.h b/src/shared/CLucene/LuceneThreads.h
+index 97072ee..662ff2f 100644
+--- a/src/shared/CLucene/LuceneThreads.h
++++ b/src/shared/CLucene/LuceneThreads.h
+@@ -13,10 +13,10 @@ class CLuceneThreadIdCompare;
+ 
+ #if defined(_CL_DISABLE_MULTITHREADING)
+ 	#define SCOPED_LOCK_MUTEX(theMutex)
+-	#define DEFINE_MUTEX(x)
++	//#define DEFINE_MUTEX(x)
+ 	#define DEFINE_MUTABLE_MUTEX(x)
+ 	#define DEFINE_CONDITION(x)
+-	#define STATIC_DEFINE_MUTEX(x)
++	//#define STATIC_DEFINE_MUTEX(x)
+ 	#define CONDITION_WAIT(theMutex, theCondition)
+ 	#define CONDITION_NOTIFYALL(theCondition)
+ 	#define _LUCENE_CURRTHREADID 1
+@@ -25,11 +25,26 @@ class CLuceneThreadIdCompare;
+ 	#define _LUCENE_THREAD_FUNC_RETURN(val) return (int)val;
+ 	#define _LUCENE_THREAD_CREATE(func, arg) (*func)(arg)
+ 	#define _LUCENE_THREAD_JOIN(value) //nothing to do...
+-	#define _LUCENE_THREADMUTEX void*
++	//#define _LUCENE_THREADMUTEX void*
+ 
+   #define _LUCENE_ATOMIC_INC(theInteger) (++(*theInteger))
+   #define _LUCENE_ATOMIC_DEC(theInteger) (--(*theInteger))
+   #define _LUCENE_ATOMIC_INT int
++#define _LUCENE_ATOMIC_INT_SET(x,v) x=v
++#define _LUCENE_ATOMIC_INT_GET(x) x
++
++struct CLUCENE_SHARED_EXPORT mutex_thread
++{
++	void lock() {}
++	void unlock() {}
++};
++#define _LUCENE_THREADMUTEX CL_NS(util)::mutex_thread
++
++#define DEFINE_MUTEX(theMutex) _LUCENE_THREADMUTEX theMutex;
++#define STATIC_DEFINE_MUTEX(theMutex) static _LUCENE_THREADMUTEX theMutex;
++
++#define CONDITION_WAIT(theMutex, theCondition)	
++#define CONDITION_NOTIFYALL(theCondition)	
+ #else
+ 	#if defined(_LUCENE_DONTIMPLEMENT_THREADMUTEX)
+ 		//do nothing
+diff --git a/src/shared/CLucene/util/Misc.cpp b/src/shared/CLucene/util/Misc.cpp
+index 240b827..ec9eabd 100644
+--- a/src/shared/CLucene/util/Misc.cpp
++++ b/src/shared/CLucene/util/Misc.cpp
+@@ -466,6 +466,7 @@ bool Misc::listFiles(const char* directory, std::vector<std::string>& files, boo
+ std::string Misc::toString(const bool value){
+   return value ? "true" : "false";
+ }
++#ifndef _CL_DISABLE_MULTITHREADING
+ std::string Misc::toString(_LUCENE_THREADID_TYPE value){
+   static int32_t nextindex = 0;
+   static std::map<_LUCENE_THREADID_TYPE, int32_t> ids;
+@@ -474,6 +475,7 @@ std::string Misc::toString(_LUCENE_THREADID_TYPE value){
+   }
+   return toString(ids[value]);
+ }
++#endif
+ std::string Misc::toString(const int32_t value){
+   char buf[20];
+   TCHAR tbuf[20];
+diff --git a/src/shared/CLucene/util/Misc.h b/src/shared/CLucene/util/Misc.h
+index aea7c42..4196e24 100644
+--- a/src/shared/CLucene/util/Misc.h
++++ b/src/shared/CLucene/util/Misc.h
+@@ -67,7 +67,9 @@ CL_NS_DEF(util)
+ 
+   static std::string toString(const int32_t value);
+   static std::string toString(const int64_t value);
++#ifndef _CL_DISABLE_MULTITHREADING
+   static std::string toString(const _LUCENE_THREADID_TYPE value);
++#endif
+   static std::string toString(const bool value);
+   static std::string toString(const float_t value);
+   static std::string toString(const TCHAR* s, int32_t len=-1);
+-- 
+1.7.8.msysgit.0
+

contrib/INDEX

@@ -0,0 +1,5 @@
+Clucene-2.3.3.4-NoThreads.patch         - To patch Clucene on Windows to remove patching
+Fortius USB Driver Stubs.zip            - Drivers for use with Fortius without Tacx software
+Install_D2XX_drivers.mpkg.zip           - D2XX installer for Windows
+Universal_D2XX0.1.6.dmg                 - D2XX installer for Mac OSX
+libusb-0.1.12.tar.gz                    - Libusb (patched) to work with GoldenCheetah

doc/.gitignore

@@ -0,0 +1,9 @@
+# old skool
+.svn
+
+# osx noise
+.DS_Store
+profile
+
+#html files are auto-generated by the scripts:
+*.html

doc/Makefile

@@ -1,49 +0,0 @@
-
-CONTENT=$(wildcard *.content)
-HTML=$(subst .content,.html,$(CONTENT))
-TARBALLS=$(wildcard gc_*.tgz)
-OTHER=logo.jpg sample.gp sample.png cpint.gp cpint.png \
-	screenshot-summary.png screenshot-plot.png \
-	screenshot-cpint.png screenshot-phist.png
-DISTRIB=GoldenCheetah_2006-12-25_Darwin_powerpc.dmg \
-	GoldenCheetah_2006-09-06_Darwin_powerpc.dmg \
-	GoldenCheetah_2006-09-07_Darwin_powerpc.dmg \
-	GoldenCheetah_2006-09-19_Darwin_powerpc.dmg
-
-all: $(HTML)
-.PHONY: all clean install
-
-clean:
-	rm -f $(HTML)
-
-install:
-	rsync -avz -e ssh $(HTML) $(TARBALLS) $(OTHER) $(DISTRIB) \
-		srhea.net:public_html/goldencheetah/
-
-contact.html: contact.content genpage.pl
-	./genpage.pl "Contact Us" $< > $@
-
-contrib.html: contrib.content genpage.pl
-	./genpage.pl "Contributors" $< > $@
-
-download.html: download.content genpage.pl
-	./genpage.pl "Download" $< > $@
-
-faq.html: faq.content genpage.pl
-	./genpage.pl "Frequently Asked Questions" $< > $@
-
-index.html: index.content genpage.pl
-	./genpage.pl "Introduction" $< > $@
-
-license.html: license.content genpage.pl
-	./genpage.pl "License" $< > $@
-
-screenshots.html: screenshots.content genpage.pl
-	./genpage.pl "Screenshots" $< > $@
-
-search.html: search.content genpage.pl
-	./genpage.pl "Search" $< > $@
-
-users-guide.html: users-guide.content genpage.pl
-	./genpage.pl "User's Guide" $< > $@
-

doc/contrib.content

@@ -1,18 +0,0 @@
-<!-- $Id: contrib.content,v 1.4 2006/09/06 04:07:18 srhea Exp $ -->
-
-Sean Rhea bought a PowerTap Pro on April 20, 2006, and immediately set to
-figuring out how to use it from his Mac Powerbook without using Virtual PC.
-Within a week, he was able to download the raw data.  Shortly thereafter, Russ
-Cox asked what he was up to, and the two worked together to figure out the
-packing format used.  By May 4, they could reproduce the numbers given by the
-PowerTap software except for minor discrepancies in the time values.  David
-Easter then pointed out how the checksum bytes in the download protocol were
-used, and Sean Rhea coded up their combined discoveries into the two
-utilities, <code>ptdl</code> and <code>ptunpk</code>.  
-
-<p>
-Rob Carlsen helped get the serial port version of the PowerTap Pro working
-with the Keyspan USB-to-serial adaptor.  Scott Overfield helped me figure out
-that we should be using the <code>/dev/cu.*</code> devices instead of the
-<code>/dev/tty.*</code> ones.
-

doc/contrib/gnupress.tex

@@ -0,0 +1,18 @@
+@c gnupress.tex -- Common Texinfo macros for GNU Press books.
+@c
+@c Print in 7" x 9.25" format.
+@smallbook
+@advance@voffset by -0.25in
+@special{papersize=7in,9.25in}
+@c
+@c Since we are using @smallbook, we ought to use @smallfonts
+@tex
+\global\let\lisporig=\lisp
+\gdef\lisp{\smallexamplefonts\lisporig}%
+\global\let\exampleorig=\example
+\gdef\example{\smallexamplefonts\exampleorig}%
+\global\let\displayorig=\display
+\gdef\display{\smallexamplefonts\displayorig}%
+\global\let\formatorig=\format
+\gdef\format{\smallexamplefonts\formatorig}%
+@end tex

doc/contrib/palatino.tex

@@ -0,0 +1,161 @@
+@c palatino.tex -- TeXinfo macros to set the default Roman font to Palatino
+@c
+@def@palatinoversion{2003-04-01.00}
+@c
+@c Copyright (C) 2003  Free Software Foundation, Inc.
+@c
+@c This palatino.tex file is free software; you can redistribute it and/or
+@c modify it under the terms of the GNU General Public License as
+@c published by the Free Software Foundation; either version 2, or (at
+@c your option) any later version.
+@c
+@c This palatino.tex file is distributed in the hope that it will be
+@c useful, but WITHOUT ANY WARRANTY; without even the implied warranty
+@c of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+@c General Public License for more details.
+@c
+@c You should have received a copy of the GNU General Public License
+@c along with this texinfo.tex file; see the file COPYING.  If not, write
+@c to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+@c Boston, MA 02111-1307, USA.
+@c
+@c You should use this module, go to your root .texi file and make sure
+@c it reads like this:
+@c     \input texinfo  @c -*-texinfo-*-
+@c     @input palatino
+
+@message{Loading palatino [version @palatinoversion]:}
+
+@c Turn on the normal TeX command characters.
+@catcode`\=0
+\catcode`\%=14
+% Set the font macro #1 to the font named #2#3. #4 is the point size.
+% We save \setfont as \setfontorig, so we can restore it at the end of this
+% section.
+\catcode`\#=6
+\let\setfontorig=\setfont
+\def\setfont#1#2#3#4{\font#1=#2#3 at #4}
+\catcode`\#=\other
+
+% Set Palatino as the default roman font face
+\def\rmfontprefix{ppl}
+
+% Only define roman font attributes here.
+\def\rmshape{r}
+\def\rmbshape{b}
+\def\bfshape{b}
+\def\bxshape{b}
+\def\itshape{ri}
+\def\itbshape{bi}
+\def\slshape{ro}
+\def\slbshape{bo}
+\def\scshape{rc}
+\def\scbshape{bc}
+
+\ifx\bigger\relax
+  % not really supported.
+  \def\mainmagstep{12pt}
+  \setfont\textrm\rmfontprefix\rmshape{\mainmagstep}
+\else
+  \def\mainmagstep{10pt}
+  \setfont\textrm\rmfontprefix\rmshape{\mainmagstep}
+\fi
+% Instead of cmb10, you many want to use cmbx10.
+% cmbx10 is a prettier font on its own, but cmb10
+% looks better when embedded in a line with cmr10.
+\setfont\textbf\rmfontprefix\bfshape{\mainmagstep}
+\setfont\textit\rmfontprefix\itshape{\mainmagstep}
+\setfont\textsl\rmfontprefix\slshape{\mainmagstep}
+\setfont\textsc\rmfontprefix\scshape{\mainmagstep}
+\font\texti=zppler7m at \mainmagstep
+\font\textsy=zppler7y at \mainmagstep
+
+% A few fonts for \defun, etc.
+\setfont\defbf\rmfontprefix\bxshape{10pt} %was 1314
+\def\df{\let\tentt=\deftt \let\tenbf = \defbf \bf}
+
+% Fonts for indices, footnotes, small examples (9pt).
+\setfont\smallrm\rmfontprefix\rmshape{9pt}
+\setfont\smallbf\rmfontprefix\bfshape{9pt}
+\setfont\smallit\rmfontprefix\itshape{9pt}
+\setfont\smallsl\rmfontprefix\slshape{9pt}
+\setfont\smallsc\rmfontprefix\scshape{9pt}
+\font\smalli=zppler7m at 9pt
+\font\smallsy=zppler7y at 9pt
+
+% Fonts for small examples (8pt).
+\setfont\smallerrm\rmfontprefix\rmshape{8pt}
+\setfont\smallerbf\rmfontprefix\bfshape{8pt}
+\setfont\smallerit\rmfontprefix\itshape{8pt}
+\setfont\smallersl\rmfontprefix\slshape{8pt}
+\setfont\smallersc\rmfontprefix\scshape{8pt}
+\font\smalleri=zppler7m at 8pt
+\font\smallersy=zppler7y at 8pt
+
+% Fonts for title page:
+\setfont\titlerm\rmfontprefix\rmbshape{18pt}
+\setfont\titleit\rmfontprefix\itbshape{18pt}
+\setfont\titlesl\rmfontprefix\slbshape{18pt}
+\let\titlebf=\titlerm
+\setfont\titlesc\rmfontprefix\scbshape{18pt}
+\font\titlei=zppler7m at 18pt
+\font\titlesy=zppler7y at 18pt
+\def\authorrm{\secrm}
+\def\authortt{\sectt}
+
+% Chapter (and unnumbered) fonts (17.28pt).
+\setfont\chaprm\rmfontprefix\rmbshape{17.28pt}
+\setfont\chapit\rmfontprefix\itbshape{17.28pt}
+\setfont\chapsl\rmfontprefix\slbshape{17.28pt}
+\let\chapbf=\chaprm
+\setfont\chapsc\rmfontprefix\scbshape{17.28pt}
+\font\chapi=zppler7m at 17.28pt
+\font\chapsy=zppler7y at 17.28pt
+
+% Section fonts (14.4pt).
+\setfont\secrm\rmfontprefix\rmbshape{14.4pt}
+\setfont\secit\rmfontprefix\itbshape{14.4pt}
+\setfont\secsl\rmfontprefix\slbshape{14.4pt}
+\let\secbf\secrm
+\setfont\secsc\rmfontprefix\scbshape{14.4pt}
+\font\seci=zppler7m at 14.4pt
+\font\secsy=zppler7y at 14.4pt
+
+% Subsection fonts (13.15pt).
+\setfont\ssecrm\rmfontprefix\rmbshape{13.15pt}
+\setfont\ssecit\rmfontprefix\itbshape{13.15pt}
+\setfont\ssecsl\rmfontprefix\slbshape{13.15pt}
+\let\ssecbf\ssecrm
+\setfont\ssecsc\rmfontprefix\scbshape{13.15pt}
+\font\sseci=zppler7m at 13.15pt
+\font\ssecsy=zppler7y at 13.15pt
+% The smallcaps and symbol fonts should actually be scaled \magstep1.5,
+% but that is not a standard magnification.
+
+% Fonts for short table of contents.
+\setfont\shortcontrm\rmfontprefix\rmshape{12pt}
+\setfont\shortcontbf\rmfontprefix\bxshape{12pt}
+\setfont\shortcontsl\rmfontprefix\slshape{12pt}
+
+% Set keyfont as well.
+\setfont\keyrm\rmfontprefix\rmshape{8pt}
+\font\keysy=zppler7y at 9pt
+
+\let\setfont=\setfontorig
+\def\setfontorig{\relax}
+
+% Restore the TeXinfo character set.
+\catcode`\\=\active
+@catcode`@%=@other
+
+@c Set initial fonts (again)
+@textfonts
+@rm
+
+@c Local variables:
+@c eval: (add-hook 'write-file-hooks 'time-stamp)
+@c page-delimiter: "^\\\\message"
+@c time-stamp-start: "def\\\\palatinoversion{"
+@c time-stamp-format: "%:y-%02m-%02d.%02H"
+@c time-stamp-end: "}"
+@c End:

doc/download.content

@@ -1,120 +0,0 @@
-<!-- $Id: download.content,v 1.6 2006/08/11 20:21:03 srhea Exp $ -->
-
-Right now Golden Cheetah is available as source code and in binary form for
-Mac OS X on PowerPC processors.
-
-<p>
-<font face="arial,helvetica,sanserif">
-<big><strong>Source Code</strong></big>
-</font>
-
-<p>
-The Golden Cheetah source code is available via 
-<a href="http://subversion.tigris.org/">Subversion</a>.
-Use this command to check out the current version of the repository:
-
-<pre>
-  svn checkout http://goldencheetah.org/svn/trunk goldencheetah
-</pre>
-
-You can also browse the source <a
-href="http://goldencheetah.org/svn/trunk">here</a>.
-
-<p>
-<font face="arial,helvetica,sanserif">
-<big><strong>Binaries</strong></big>
-</font>
-
-<p>
-<center>
-<table width="100%">
-<tr>
-<td width="20%"><i>Date</i></td>
-<td width="30%"><i>File</i></td>
-<td><i>Description</i></td>
-</tr>
-
-<tr>
-<td valign="top">Dec 25, 2006</td>
-<td valign="top"><a href="GoldenCheetah_2006-12-25_Darwin_powerpc.dmg">Mac OS
-X PowerPC</a></td>
-<td valign="top">Adds the Power Histogram, which shows how much time a rider
-spent at each particular power level during a ride.</td>
-</tr>
-
-<tr>
-<td valign="top">Sep 19, 2006</td>
-<td valign="top"><a href="GoldenCheetah_2006-09-19_Darwin_powerpc.dmg">Mac OS
-X PowerPC</a></td>
-<td valign="top">Adds the Critical Power Plot, which shows the highest average
-power you've achieved for every interval length over all your rides and the
-selected ride.  Also shows download progress in minutes of ride data
-downloaded.</td>
-</tr>
-
-<tr>
-<td valign="top">Sep 7, 2006</td>
-<td valign="top"><a href="GoldenCheetah_2006-09-07_Darwin_powerpc.dmg">Mac OS
-X PowerPC</a></td>
-<td valign="top">Adds speed and cadence to the ride plot.  Fixes a bug
-found by George Gilliland where reseting the time during a ride could cause
-the GUI to crash.</td>
-</tr>
-
-<tr>
-<td valign="top">Sep 6, 2006</td>
-<td valign="top"><a href="GoldenCheetah_2006-09-06_Darwin_powerpc.dmg">Mac OS
-X PowerPC</a></td>
-<td valign="top">The first release of the Golden Cheetah GUI.</td>
-</tr>
-
-</table>
-</center>
-
-<p>
-<hr width="50%">
-
-<p>
-<font face="arial,helvetica,sanserif">
-<big><strong>Older Stuff</strong></big>
-</font>
-
-<p>
-These are the older, source-only, command-line distributions.  I've left them
-up for historical purposes only; I don't recommend using them. 
-
-<center>
-<table width="100%">
-<tr>
-<td width="20%"><i>Date</i></td>
-<td width="30%"><i>File</i></td>
-<td><i>Description</i></td>
-</tr>
-
-<tr>
-<td valign="top">Aug 11, 2006</td>
-<td valign="top"><a href="gc_2006-08-11.tgz">gc_2006-08-11.tgz</a></td>
-<td valign="top">ptdl now works with Keyspan USB-to-serial adaptor, after
-debugging help from Rob Carlsen.
-</td>
-</tr>
-
-<tr>
-<td valign="top">May 27, 2006</td>
-<td valign="top"><a href="gc_2006-05-27.tgz">gc_2006-05-27.tgz</a></td>
-<td valign="top">Adds the <code>cpint</code> program for computing critical
-power intervals and the <code>ptpk</code> program for converting from
-PowerTuned data files (see the <a href="users-guide.html">User's
-Guide</a>).</td>
-</tr>
-
-<tr>
-<td valign="top">May 16, 2006</td>
-<td valign="top"><a href="gc_2006-05-16.tgz">gc_2006-05-16.tgz</a></td>
-<td valign="top">The first code release, containing <code>ptdl</code> and
-<code>ptunpk</code>.</td>
-</tr>
-
-</table>
-</center>
-

doc/faq.content

@@ -1,65 +0,0 @@
-<!-- $Id: faq.content,v 1.4 2006/07/05 16:59:56 srhea Exp $ -->
-
-<p>
-<i>I downloaded a .dmg, opened it, dragged and dropped GoldenCheetah into
-Applications, double-clicked on it, and nothing happened.  What gives?</i>
-
-<p>
-Are you running OS X Tiger?  You need to be.  If you are, and you're still
-having this problem, open Terminal (in Applications -&gt; Utilities) and type
-this at the prompt:
-
-<blockquote><pre>
-/Applications/GoldenCheetah.app/Contents/MacOS/GoldenCheetah
-</pre></blockquote>
-
-then press &lt;return&gt; and send an email to the mailing list with
-whatever it prints out.  We'll help you debug it.
-
-<p>
-<i>I've downloaded and unpacked the data.  Now what do I do with it?</i>
-
-<p>
-We highly recommend that you buy and read both Joe Friel's <i>The
-Cyclist's Training Bible</i> and Allen and Coggan's <i>Training and
-Racing with a Power Meter</i>.  The former is the definitive book about all
-aspects of cycling training (although we think he's off his rocker in the
-chapter about diet), and the latter is the definitive book about power-based
-training.
-
-<p>
-Also, if you buy either of these books through the links below, we'll get a
-referral fee in return, helping us to support this web site.  Thanks!
-
-<center>
-<iframe
-src="http://rcm.amazon.com/e/cm?t=goldencheetah-20&o=1&p=8&l=as1&asins=B0006JHZ7Q&fc1=000000&IS2=1&lt1=_blank&lc1=0000ff&bc1=000000&bg1=ffffff&f=ifr"
-style="width:120px;height:240px;" scrolling="no" marginwidth="0"
-marginheight="0" frameborder="0"></iframe>
-
-<iframe
-src="http://rcm.amazon.com/e/cm?t=goldencheetah-20&o=1&p=8&l=as1&asins=1931382794&fc1=000000&IS2=1&lt1=_blank&lc1=0000ff&bc1=000000&bg1=ffffff&f=ifr"
-style="width:120px;height:240px;" scrolling="no" marginwidth="0"
-marginheight="0" frameborder="0"></iframe>
-</center>
-
-<p>
-<i>Does the output of <code>ptunpk</code> exactly match that of the software
-included with the PowerTap?</i>
-
-<p>
-Almost.  If you run it in compatibility mode, using the <code>-c</code>
-option, it matches the PowerTap software's output exactly on everything but
-the time values, at least for the five sample rides we've tried it with.
-The times are a little off, but not by more than 0.1%, so we don't consider it
-a big deal.
-
-<p>
-That said, the PowerTap software does some weird things, like converting from
-kilometers to miles by multiplying by 0.62, but then reporting the miles
-values with five digits after the decimal place.  If you run
-<code>ptunpk</code> without the <code>-c</code> option, it will unpack the
-data in the way we think it should.  The results mostly match up with the
-official ones, and are almost certainly identical within the range of accuracy
-of the device.
-

doc/index.content

@@ -1,26 +0,0 @@
-<!-- $Id: index.content,v 1.1 2006/05/16 14:24:50 srhea Exp $ -->
-
-<p>
-The goal of the Golden Cheetah project is to develop a software package that:
-<ul>
-<li>Downloads ride data from power measurement devices, such as the <a
-href="http://www.cycleops.com/products/powertap.htm">CycleOps PowerTap</a>,
-the <a href="http://www.ergomo.net/Home-_14.html">ergomo</a>, the <a
-href="http://www.polarusa.com/consumer/powerkit/default.asp">Polar
-Electro</a>, and the <a href="http://www.srm.de/usa/index.html">SRM Training
-System</a><p>
-<li>Helps athletes analyze downloaded data with features akin to commercial
-power analysis software, such as <a href="http://cyclingpeaks.com/">Cycling
-Peaks</a><p>
-<li>Works on non-Microsoft Windows-based systems, such as FreeBSD, Linux, and
-Mac OS X<p>
-<li>Is available under an 
-<a href="http://www.opensource.org/docs/definition.php">Open Source</a> 
-license
-</ul>
-
-<p>
-In short, we believe that cyclists should be able to download their power data
-to the computer of their choice, analyze it in whatever way they see fit, and
-share their methods of analysis with others.
-

doc/mockups/LTM Chart Settings.bmml

@@ -0,0 +1,610 @@
+<mockup version="1.0" skin="sketch" fontFace="Balsamiq Sans" measuredW="1997" measuredH="568" mockupW="1935" mockupH="553">
+  <controls>
+    <control controlID="0" controlTypeID="com.balsamiq.mockups::TitleWindow" x="62" y="61" w="355" h="400" measuredW="450" measuredH="400" zOrder="0" locked="false" isInGroup="-1">
+      <controlProperties>
+        <bottomheight>0</bottomheight>
+        <dragger>false</dragger>
+        <text>Chart%20Controls%20%5BLTM%20Chart%5D</text>
+      </controlProperties>
+    </control>
+    <control controlID="1" controlTypeID="com.balsamiq.mockups::TabBar" x="84" y="101" w="312" h="284" measuredW="219" measuredH="100" zOrder="1" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Basic%2C%20Preset%2C%20Custom*</text>
+      </controlProperties>
+    </control>
+    <control controlID="2" controlTypeID="com.balsamiq.mockups::Button" x="321" y="413" w="75" h="27" measuredW="53" measuredH="27" zOrder="2" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Done</text>
+      </controlProperties>
+    </control>
+    <control controlID="3" controlTypeID="com.balsamiq.mockups::List" x="101" y="164" w="-1" h="-1" measuredW="100" measuredH="126" zOrder="3" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Best%0AFormula%0AMetric%0AMeasure</text>
+      </controlProperties>
+    </control>
+    <control controlID="4" controlTypeID="com.balsamiq.mockups::List" x="201" y="164" w="171" h="126" measuredW="100" measuredH="126" zOrder="4" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Power%205s%0A%3D60m%20WPK%20*%20RPE%0AAverage_Power%0AWeight</text>
+      </controlProperties>
+    </control>
+    <control controlID="5" controlTypeID="com.balsamiq.mockups::TextInput" x="100" y="140" w="101" h="-1" measuredW="44" measuredH="27" zOrder="5" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Type</text>
+      </controlProperties>
+    </control>
+    <control controlID="6" controlTypeID="com.balsamiq.mockups::TextInput" x="201" y="140" w="171" h="-1" measuredW="56" measuredH="27" zOrder="6" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Details</text>
+      </controlProperties>
+    </control>
+    <control controlID="7" controlTypeID="com.balsamiq.mockups::Button" x="101" y="298" w="75" h="27" measuredW="46" measuredH="27" zOrder="7" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Edit</text>
+      </controlProperties>
+    </control>
+    <control controlID="8" controlTypeID="com.balsamiq.mockups::Button" x="294" y="298" w="36" h="27" measuredW="31" measuredH="27" zOrder="8" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>+</text>
+      </controlProperties>
+    </control>
+    <control controlID="9" controlTypeID="com.balsamiq.mockups::Button" x="336" y="298" w="36" h="27" measuredW="27" measuredH="27" zOrder="9" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>-</text>
+      </controlProperties>
+    </control>
+    <control controlID="12" controlTypeID="com.balsamiq.mockups::Arrow" x="345" y="15" w="225" h="143" measuredW="150" measuredH="100" zOrder="10" locked="false" isInGroup="-1">
+      <controlProperties>
+        <backgroundAlpha>1</backgroundAlpha>
+        <direction>bottom</direction>
+        <rightArrow>false</rightArrow>
+        <text>Lists%20all%20data%20series%20that%20will%20be%20available%20on%20the%20chart</text>
+      </controlProperties>
+    </control>
+    <control controlID="13" controlTypeID="com.balsamiq.mockups::TitleWindow" x="481" y="55" w="489" h="507" measuredW="450" measuredH="400" zOrder="11" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Edit%20Data%20Series%20%5BMetric/Measure%5D</text>
+      </controlProperties>
+    </control>
+    <control controlID="14" controlTypeID="com.balsamiq.mockups::RadioButton" x="497" y="156" w="136" h="22" measuredW="53" measuredH="22" zOrder="12" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>selected</state>
+        <text>Metric</text>
+      </controlProperties>
+    </control>
+    <control controlID="15" controlTypeID="com.balsamiq.mockups::RadioButton" x="497" y="184" w="136" h="22" measuredW="43" measuredH="22" zOrder="13" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Best</text>
+      </controlProperties>
+    </control>
+    <control controlID="16" controlTypeID="com.balsamiq.mockups::RadioButton" x="497" y="212" w="136" h="22" measuredW="63" measuredH="22" zOrder="14" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Formula</text>
+      </controlProperties>
+    </control>
+    <control controlID="17" controlTypeID="com.balsamiq.mockups::RadioButton" x="497" y="130" w="136" h="22" measuredW="68" measuredH="22" zOrder="15" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>selected</state>
+        <text>Measure</text>
+      </controlProperties>
+    </control>
+    <control controlID="18" controlTypeID="com.balsamiq.mockups::Arrow" x="155" y="242" w="326" h="69" measuredW="150" measuredH="100" zOrder="16" locked="false" isInGroup="-1">
+      <controlProperties>
+        <backgroundAlpha>0.25</backgroundAlpha>
+        <direction>bottom</direction>
+        <leftArrow>false</leftArrow>
+        <rightArrow>true</rightArrow>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="19" controlTypeID="com.balsamiq.mockups::Arrow" x="306" y="242" w="175" h="69" measuredW="150" measuredH="100" zOrder="17" locked="false" isInGroup="-1">
+      <controlProperties>
+        <backgroundAlpha>0.25</backgroundAlpha>
+        <direction>bottom</direction>
+        <leftArrow>false</leftArrow>
+        <rightArrow>false</rightArrow>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="20" controlTypeID="com.balsamiq.mockups::List" x="615" y="126" w="317" h="113" measuredW="100" measuredH="132" zOrder="18" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Peak%201m%20Power%0APeak%201m%20WPK%0APeak%201s%20Power%0APeak%201s%20WPK%0APeak%205s%20Power%0APeak%205s%20WPK</text>
+      </controlProperties>
+    </control>
+    <control controlID="21" controlTypeID="com.balsamiq.mockups::TextInput" x="615" y="102" w="317" h="-1" measuredW="58" measuredH="27" zOrder="19" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Metrics</text>
+      </controlProperties>
+    </control>
+    <control controlID="22" controlTypeID="com.balsamiq.mockups::VerticalScrollBar" x="916" y="126" w="-1" h="113" measuredW="16" measuredH="100" zOrder="20" locked="false" isInGroup="-1"/>
+    <control controlID="24" controlTypeID="com.balsamiq.mockups::Label" x="498" y="101" w="-1" h="-1" measuredW="30" measuredH="21" zOrder="21" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Type</text>
+      </controlProperties>
+    </control>
+    <control controlID="26" controlTypeID="com.balsamiq.mockups::Label" x="497" y="264" w="104" h="-1" measuredW="35" measuredH="21" zOrder="22" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Name</text>
+      </controlProperties>
+    </control>
+    <control controlID="27" controlTypeID="com.balsamiq.mockups::Label" x="497" y="304" w="131" h="-1" measuredW="106" measuredH="21" zOrder="23" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Axis%20Label%20/%20Units</text>
+      </controlProperties>
+    </control>
+    <control controlID="28" controlTypeID="com.balsamiq.mockups::Label" x="497" y="342" w="131" h="-1" measuredW="36" measuredH="21" zOrder="24" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="29" controlTypeID="com.balsamiq.mockups::Label" x="497" y="378" w="131" h="-1" measuredW="44" measuredH="21" zOrder="25" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Symbol</text>
+      </controlProperties>
+    </control>
+    <control controlID="30" controlTypeID="com.balsamiq.mockups::Label" x="499" y="416" w="131" h="-1" measuredW="35" measuredH="21" zOrder="26" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Stack</text>
+      </controlProperties>
+    </control>
+    <control controlID="31" controlTypeID="com.balsamiq.mockups::Label" x="499" y="448" w="131" h="-1" measuredW="32" measuredH="21" zOrder="27" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Color</text>
+      </controlProperties>
+    </control>
+    <control controlID="32" controlTypeID="com.balsamiq.mockups::Label" x="499" y="484" w="111" h="-1" measuredW="55" measuredH="21" zOrder="28" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Fill%20Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="33" controlTypeID="com.balsamiq.mockups::TextInput" x="618" y="261" w="97" h="-1" measuredW="79" measuredH="26" zOrder="29" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="34" controlTypeID="com.balsamiq.mockups::TextInput" x="616" y="301" w="97" h="-1" measuredW="79" measuredH="26" zOrder="30" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="35" controlTypeID="com.balsamiq.mockups::ComboBox" x="618" y="340" w="95" h="-1" measuredW="55" measuredH="24" zOrder="31" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Line</text>
+      </controlProperties>
+    </control>
+    <control controlID="36" controlTypeID="com.balsamiq.mockups::ComboBox" x="618" y="378" w="95" h="-1" measuredW="64" measuredH="24" zOrder="32" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Circle</text>
+      </controlProperties>
+    </control>
+    <control controlID="37" controlTypeID="com.balsamiq.mockups::CheckBox" x="627" y="417" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="33" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="38" controlTypeID="com.balsamiq.mockups::CheckBox" x="627" y="483" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="34" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="39" controlTypeID="com.balsamiq.mockups::ColorPicker" x="620" y="447" w="-1" h="-1" measuredW="26" measuredH="28" zOrder="35" locked="false" isInGroup="-1"/>
+    <control controlID="40" controlTypeID="com.balsamiq.mockups::Label" x="738" y="264" w="104" h="-1" measuredW="52" measuredH="21" zOrder="36" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Highlight</text>
+      </controlProperties>
+    </control>
+    <control controlID="41" controlTypeID="com.balsamiq.mockups::Label" x="736" y="304" w="104" h="-1" measuredW="47" measuredH="21" zOrder="37" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Outliers</text>
+      </controlProperties>
+    </control>
+    <control controlID="42" controlTypeID="com.balsamiq.mockups::Label" x="738" y="342" w="104" h="-1" measuredW="50" measuredH="21" zOrder="38" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Baseline</text>
+      </controlProperties>
+    </control>
+    <control controlID="43" controlTypeID="com.balsamiq.mockups::Label" x="738" y="416" w="104" h="-1" measuredW="84" measuredH="21" zOrder="39" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Smooth%20Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="44" controlTypeID="com.balsamiq.mockups::Label" x="738" y="446" w="104" h="-1" measuredW="63" measuredH="21" zOrder="40" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Trend%20Line</text>
+      </controlProperties>
+    </control>
+    <control controlID="45" controlTypeID="com.balsamiq.mockups::CheckBox" x="842" y="417" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="41" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="46" controlTypeID="com.balsamiq.mockups::CheckBox" x="842" y="448" w="20" h="21" measuredW="20" measuredH="21" zOrder="42" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="47" controlTypeID="com.balsamiq.mockups::NumericStepper" x="837" y="263" w="95" h="-1" measuredW="41" measuredH="24" zOrder="43" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>0</text>
+      </controlProperties>
+    </control>
+    <control controlID="48" controlTypeID="com.balsamiq.mockups::NumericStepper" x="837" y="301" w="95" h="-1" measuredW="41" measuredH="24" zOrder="44" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>0</text>
+      </controlProperties>
+    </control>
+    <control controlID="49" controlTypeID="com.balsamiq.mockups::NumericStepper" x="837" y="341" w="95" h="-1" measuredW="61" measuredH="24" zOrder="45" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>-999</text>
+      </controlProperties>
+    </control>
+    <control controlID="50" controlTypeID="com.balsamiq.mockups::TitleWindow" x="991" y="57" w="489" h="507" measuredW="450" measuredH="400" zOrder="46" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Edit%20Data%20Series%20%5BFormula%5D</text>
+      </controlProperties>
+    </control>
+    <control controlID="51" controlTypeID="com.balsamiq.mockups::RadioButton" x="1007" y="158" w="136" h="22" measuredW="53" measuredH="22" zOrder="47" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>up</state>
+        <text>Metric</text>
+      </controlProperties>
+    </control>
+    <control controlID="52" controlTypeID="com.balsamiq.mockups::RadioButton" x="1007" y="186" w="136" h="22" measuredW="43" measuredH="22" zOrder="48" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Best</text>
+      </controlProperties>
+    </control>
+    <control controlID="53" controlTypeID="com.balsamiq.mockups::RadioButton" x="1007" y="214" w="136" h="22" measuredW="63" measuredH="22" zOrder="49" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>selected</state>
+        <text>Formula</text>
+      </controlProperties>
+    </control>
+    <control controlID="54" controlTypeID="com.balsamiq.mockups::RadioButton" x="1007" y="132" w="136" h="22" measuredW="68" measuredH="22" zOrder="50" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Measure</text>
+      </controlProperties>
+    </control>
+    <control controlID="58" controlTypeID="com.balsamiq.mockups::Label" x="1008" y="103" w="-1" h="-1" measuredW="30" measuredH="21" zOrder="51" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Type</text>
+      </controlProperties>
+    </control>
+    <control controlID="59" controlTypeID="com.balsamiq.mockups::Label" x="1007" y="266" w="104" h="-1" measuredW="35" measuredH="21" zOrder="52" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Name</text>
+      </controlProperties>
+    </control>
+    <control controlID="60" controlTypeID="com.balsamiq.mockups::Label" x="1007" y="306" w="131" h="-1" measuredW="106" measuredH="21" zOrder="53" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Axis%20Label%20/%20Units</text>
+      </controlProperties>
+    </control>
+    <control controlID="61" controlTypeID="com.balsamiq.mockups::Label" x="1007" y="344" w="131" h="-1" measuredW="36" measuredH="21" zOrder="54" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="62" controlTypeID="com.balsamiq.mockups::Label" x="1007" y="380" w="131" h="-1" measuredW="44" measuredH="21" zOrder="55" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Symbol</text>
+      </controlProperties>
+    </control>
+    <control controlID="63" controlTypeID="com.balsamiq.mockups::Label" x="1009" y="418" w="131" h="-1" measuredW="35" measuredH="21" zOrder="56" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Stack</text>
+      </controlProperties>
+    </control>
+    <control controlID="64" controlTypeID="com.balsamiq.mockups::Label" x="1009" y="450" w="131" h="-1" measuredW="32" measuredH="21" zOrder="57" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Color</text>
+      </controlProperties>
+    </control>
+    <control controlID="65" controlTypeID="com.balsamiq.mockups::Label" x="1009" y="486" w="111" h="-1" measuredW="55" measuredH="21" zOrder="58" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Fill%20Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="66" controlTypeID="com.balsamiq.mockups::TextInput" x="1128" y="263" w="97" h="-1" measuredW="79" measuredH="26" zOrder="59" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="67" controlTypeID="com.balsamiq.mockups::TextInput" x="1126" y="303" w="97" h="-1" measuredW="79" measuredH="26" zOrder="60" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="68" controlTypeID="com.balsamiq.mockups::ComboBox" x="1128" y="342" w="95" h="-1" measuredW="55" measuredH="24" zOrder="61" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Line</text>
+      </controlProperties>
+    </control>
+    <control controlID="69" controlTypeID="com.balsamiq.mockups::ComboBox" x="1128" y="380" w="95" h="-1" measuredW="64" measuredH="24" zOrder="62" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Circle</text>
+      </controlProperties>
+    </control>
+    <control controlID="70" controlTypeID="com.balsamiq.mockups::CheckBox" x="1137" y="419" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="63" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="71" controlTypeID="com.balsamiq.mockups::CheckBox" x="1137" y="485" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="64" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="72" controlTypeID="com.balsamiq.mockups::ColorPicker" x="1130" y="449" w="-1" h="-1" measuredW="26" measuredH="28" zOrder="65" locked="false" isInGroup="-1"/>
+    <control controlID="73" controlTypeID="com.balsamiq.mockups::Label" x="1248" y="266" w="104" h="-1" measuredW="52" measuredH="21" zOrder="66" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Highlight</text>
+      </controlProperties>
+    </control>
+    <control controlID="74" controlTypeID="com.balsamiq.mockups::Label" x="1246" y="306" w="104" h="-1" measuredW="47" measuredH="21" zOrder="67" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Outliers</text>
+      </controlProperties>
+    </control>
+    <control controlID="75" controlTypeID="com.balsamiq.mockups::Label" x="1248" y="344" w="104" h="-1" measuredW="50" measuredH="21" zOrder="68" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Baseline</text>
+      </controlProperties>
+    </control>
+    <control controlID="76" controlTypeID="com.balsamiq.mockups::Label" x="1248" y="418" w="104" h="-1" measuredW="84" measuredH="21" zOrder="69" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Smooth%20Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="77" controlTypeID="com.balsamiq.mockups::Label" x="1248" y="448" w="104" h="-1" measuredW="63" measuredH="21" zOrder="70" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Trend%20Line</text>
+      </controlProperties>
+    </control>
+    <control controlID="78" controlTypeID="com.balsamiq.mockups::CheckBox" x="1352" y="419" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="71" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="79" controlTypeID="com.balsamiq.mockups::CheckBox" x="1352" y="450" w="20" h="21" measuredW="20" measuredH="21" zOrder="72" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="80" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1347" y="265" w="95" h="-1" measuredW="41" measuredH="24" zOrder="73" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>0</text>
+      </controlProperties>
+    </control>
+    <control controlID="81" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1347" y="303" w="95" h="-1" measuredW="41" measuredH="24" zOrder="74" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>0</text>
+      </controlProperties>
+    </control>
+    <control controlID="82" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1347" y="343" w="95" h="-1" measuredW="61" measuredH="24" zOrder="75" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>-999</text>
+      </controlProperties>
+    </control>
+    <control controlID="83" controlTypeID="com.balsamiq.mockups::SearchBox" x="1128" y="103" w="315" h="-1" measuredW="120" measuredH="25" zOrder="76" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>%3D%20Formula...</text>
+      </controlProperties>
+    </control>
+    <control controlID="84" controlTypeID="com.balsamiq.mockups::TextArea" x="1135" y="125" w="293" h="124" measuredW="200" measuredH="140" zOrder="77" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="85" controlTypeID="com.balsamiq.mockups::VerticalScrollBar" x="1412" y="126" w="-1" h="123" measuredW="16" measuredH="100" zOrder="78" locked="false" isInGroup="-1"/>
+    <control controlID="87" controlTypeID="com.balsamiq.mockups::Label" x="1147" y="130" w="-1" h="-1" measuredW="35" measuredH="21" zOrder="79" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Fields</text>
+      </controlProperties>
+    </control>
+    <control controlID="88" controlTypeID="com.balsamiq.mockups::Label" x="1308" y="131" w="70" h="-1" measuredW="59" measuredH="21" zOrder="80" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Operators</text>
+      </controlProperties>
+    </control>
+    <control controlID="89" controlTypeID="com.balsamiq.mockups::Button" x="1147" y="151" w="-1" h="-1" measuredW="107" measuredH="27" zOrder="81" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>1s%20Peak%20Power</text>
+      </controlProperties>
+    </control>
+    <control controlID="90" controlTypeID="com.balsamiq.mockups::Button" x="1149" y="183" w="-1" h="-1" measuredW="107" measuredH="27" zOrder="82" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>1s%20Peak%20Power</text>
+      </controlProperties>
+    </control>
+    <control controlID="91" controlTypeID="com.balsamiq.mockups::Button" x="1149" y="215" w="-1" h="-1" measuredW="107" measuredH="27" zOrder="83" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>1s%20Peak%20Power</text>
+      </controlProperties>
+    </control>
+    <control controlID="92" controlTypeID="com.balsamiq.mockups::Button" x="1301" y="152" w="85" h="27" measuredW="49" measuredH="27" zOrder="84" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>AND</text>
+      </controlProperties>
+    </control>
+    <control controlID="93" controlTypeID="com.balsamiq.mockups::Button" x="1303" y="184" w="85" h="27" measuredW="42" measuredH="27" zOrder="85" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>OR</text>
+      </controlProperties>
+    </control>
+    <control controlID="94" controlTypeID="com.balsamiq.mockups::Button" x="1305" y="216" w="85" h="27" measuredW="40" measuredH="27" zOrder="86" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>%3E%3D</text>
+      </controlProperties>
+    </control>
+    <control controlID="95" controlTypeID="com.balsamiq.mockups::VerticalScrollBar" x="1266" y="126" w="-1" h="123" measuredW="16" measuredH="100" zOrder="87" locked="false" isInGroup="-1"/>
+    <control controlID="96" controlTypeID="com.balsamiq.mockups::TitleWindow" x="1508" y="61" w="489" h="507" measuredW="450" measuredH="400" zOrder="88" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Edit%20Data%20Series%20%5BBests%5D</text>
+      </controlProperties>
+    </control>
+    <control controlID="97" controlTypeID="com.balsamiq.mockups::RadioButton" x="1524" y="162" w="136" h="22" measuredW="53" measuredH="22" zOrder="89" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>up</state>
+        <text>Metric</text>
+      </controlProperties>
+    </control>
+    <control controlID="98" controlTypeID="com.balsamiq.mockups::RadioButton" x="1524" y="190" w="136" h="22" measuredW="43" measuredH="22" zOrder="90" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>selected</state>
+        <text>Best</text>
+      </controlProperties>
+    </control>
+    <control controlID="99" controlTypeID="com.balsamiq.mockups::RadioButton" x="1524" y="218" w="136" h="22" measuredW="63" measuredH="22" zOrder="91" locked="false" isInGroup="-1">
+      <controlProperties>
+        <state>up</state>
+        <text>Formula</text>
+      </controlProperties>
+    </control>
+    <control controlID="100" controlTypeID="com.balsamiq.mockups::RadioButton" x="1524" y="136" w="136" h="22" measuredW="68" measuredH="22" zOrder="92" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Measure</text>
+      </controlProperties>
+    </control>
+    <control controlID="101" controlTypeID="com.balsamiq.mockups::Label" x="1525" y="107" w="-1" h="-1" measuredW="30" measuredH="21" zOrder="93" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Type</text>
+      </controlProperties>
+    </control>
+    <control controlID="102" controlTypeID="com.balsamiq.mockups::Label" x="1524" y="270" w="104" h="-1" measuredW="35" measuredH="21" zOrder="94" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Name</text>
+      </controlProperties>
+    </control>
+    <control controlID="103" controlTypeID="com.balsamiq.mockups::Label" x="1524" y="310" w="131" h="-1" measuredW="106" measuredH="21" zOrder="95" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Axis%20Label%20/%20Units</text>
+      </controlProperties>
+    </control>
+    <control controlID="104" controlTypeID="com.balsamiq.mockups::Label" x="1524" y="348" w="131" h="-1" measuredW="36" measuredH="21" zOrder="96" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="105" controlTypeID="com.balsamiq.mockups::Label" x="1524" y="384" w="131" h="-1" measuredW="44" measuredH="21" zOrder="97" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Symbol</text>
+      </controlProperties>
+    </control>
+    <control controlID="106" controlTypeID="com.balsamiq.mockups::Label" x="1526" y="422" w="131" h="-1" measuredW="35" measuredH="21" zOrder="98" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Stack</text>
+      </controlProperties>
+    </control>
+    <control controlID="107" controlTypeID="com.balsamiq.mockups::Label" x="1526" y="454" w="131" h="-1" measuredW="32" measuredH="21" zOrder="99" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Color</text>
+      </controlProperties>
+    </control>
+    <control controlID="108" controlTypeID="com.balsamiq.mockups::Label" x="1526" y="490" w="111" h="-1" measuredW="55" measuredH="21" zOrder="100" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Fill%20Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="109" controlTypeID="com.balsamiq.mockups::TextInput" x="1645" y="267" w="97" h="-1" measuredW="79" measuredH="26" zOrder="101" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="110" controlTypeID="com.balsamiq.mockups::TextInput" x="1643" y="307" w="97" h="-1" measuredW="79" measuredH="26" zOrder="102" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="111" controlTypeID="com.balsamiq.mockups::ComboBox" x="1645" y="346" w="95" h="-1" measuredW="55" measuredH="24" zOrder="103" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Line</text>
+      </controlProperties>
+    </control>
+    <control controlID="112" controlTypeID="com.balsamiq.mockups::ComboBox" x="1645" y="384" w="95" h="-1" measuredW="64" measuredH="24" zOrder="104" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Circle</text>
+      </controlProperties>
+    </control>
+    <control controlID="113" controlTypeID="com.balsamiq.mockups::CheckBox" x="1654" y="423" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="105" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="114" controlTypeID="com.balsamiq.mockups::CheckBox" x="1654" y="489" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="106" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="115" controlTypeID="com.balsamiq.mockups::ColorPicker" x="1647" y="453" w="-1" h="-1" measuredW="26" measuredH="28" zOrder="107" locked="false" isInGroup="-1"/>
+    <control controlID="116" controlTypeID="com.balsamiq.mockups::Label" x="1765" y="270" w="104" h="-1" measuredW="52" measuredH="21" zOrder="108" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Highlight</text>
+      </controlProperties>
+    </control>
+    <control controlID="117" controlTypeID="com.balsamiq.mockups::Label" x="1763" y="310" w="104" h="-1" measuredW="47" measuredH="21" zOrder="109" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Outliers</text>
+      </controlProperties>
+    </control>
+    <control controlID="118" controlTypeID="com.balsamiq.mockups::Label" x="1765" y="348" w="104" h="-1" measuredW="50" measuredH="21" zOrder="110" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Baseline</text>
+      </controlProperties>
+    </control>
+    <control controlID="119" controlTypeID="com.balsamiq.mockups::Label" x="1765" y="422" w="104" h="-1" measuredW="84" measuredH="21" zOrder="111" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Smooth%20Curve</text>
+      </controlProperties>
+    </control>
+    <control controlID="120" controlTypeID="com.balsamiq.mockups::Label" x="1765" y="452" w="104" h="-1" measuredW="63" measuredH="21" zOrder="112" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Trend%20Line</text>
+      </controlProperties>
+    </control>
+    <control controlID="121" controlTypeID="com.balsamiq.mockups::CheckBox" x="1869" y="423" w="-1" h="-1" measuredW="20" measuredH="21" zOrder="113" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="122" controlTypeID="com.balsamiq.mockups::CheckBox" x="1869" y="454" w="20" h="21" measuredW="20" measuredH="21" zOrder="114" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text/>
+      </controlProperties>
+    </control>
+    <control controlID="123" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1864" y="269" w="95" h="-1" measuredW="41" measuredH="24" zOrder="115" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>0</text>
+      </controlProperties>
+    </control>
+    <control controlID="124" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1864" y="307" w="95" h="-1" measuredW="41" measuredH="24" zOrder="116" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>0</text>
+      </controlProperties>
+    </control>
+    <control controlID="125" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1864" y="347" w="95" h="-1" measuredW="61" measuredH="24" zOrder="117" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>-999</text>
+      </controlProperties>
+    </control>
+    <control controlID="126" controlTypeID="com.balsamiq.mockups::NumericStepper" x="1694" y="147" w="95" h="-1" measuredW="41" measuredH="24" zOrder="118" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>5</text>
+      </controlProperties>
+    </control>
+    <control controlID="127" controlTypeID="com.balsamiq.mockups::ComboBox" x="1797" y="145" w="95" h="-1" measuredW="69" measuredH="24" zOrder="119" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Minute</text>
+      </controlProperties>
+    </control>
+    <control controlID="128" controlTypeID="com.balsamiq.mockups::Label" x="1694" y="177" w="95" h="-1" measuredW="30" measuredH="21" zOrder="120" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Peak</text>
+      </controlProperties>
+    </control>
+    <control controlID="129" controlTypeID="com.balsamiq.mockups::ComboBox" x="1797" y="175" w="95" h="-1" measuredW="66" measuredH="24" zOrder="121" locked="false" isInGroup="-1">
+      <controlProperties>
+        <text>Power</text>
+      </controlProperties>
+    </control>
+  </controls>
+</mockup>

doc/screenshots.content

@@ -1,35 +0,0 @@
-<!-- $Id: faq.content,v 1.4 2006/07/05 16:59:56 srhea Exp $ -->
-
-<p>
-<center>
-
-<big><font face="arial,helvetica,sanserif">
-The Ride Summary
-</font></big>
-<p>
-<img src="screenshot-summary.png" alt="Ride Summary Screen" align="center">
-
-<p>
-<big><font face="arial,helvetica,sanserif">
-The Power, Heart Rate, Speed, and Cadence Plot
-</font></big>
-<p>
-<img src="screenshot-plot.png" alt="Power and HR Plot" align="center">
-
-<p>
-<big><font face="arial,helvetica,sanserif">
-The Critical Power Plot
-</font></big>
-<p>
-<img src="screenshot-cpint.png" alt="The Critical Power Plot" align="center">
-
-<p>
-<big><font face="arial,helvetica,sanserif">
-The Power Histogram
-</font></big>
-<p>
-<img src="screenshot-phist.png" alt="The Power Histogram" align="center">
-
-</center>
-
-

doc/user/.gitignore

@@ -0,0 +1,10 @@
+*.aux
+*.cp
+*.cps
+*.fn
+*.ky
+*.log
+*.pg
+*.toc
+*.tp
+*.vr

doc/user/GC3-FAQ.info

@@ -0,0 +1,822 @@
+This is GC3-FAQ.info, produced by makeinfo version 4.13 from
+GC3-FAQ.texinfo.
+
+This manual is for Golden Cheetah, version 3.0.
+
+Copyright (C) 2013 Mark Liversedge
+
+
+File: GC3-FAQ.info,  Node: Top,  Next: Top,  Prev: Top
+
+title
+*****
+
+This manual is for GoldenCheetah, version 3.0.
+
+* Menu:
+
+* MOST COMMON QUESTIONS OF ALL::    Most common questions
+* GENERAL:: General Questions
+* DATA::    Working with Data
+* METRICS:: Working with Metrics
+* UPLOADING AND DOWNLOADING::   Uploading and Downloading Data
+* SEASONS AND EVENTS::  Seasons and Events
+* CHARTS::  Configuring and Using Charts
+* INDEX::   Index
+
+
+File: GC3-FAQ.info,  Node: MOST COMMON QUESTIONS OF ALL,  Next: GENERAL,  Prev: INDEX,  Up: Top
+
+1 MOST COMMON QUESTIONS OF ALL
+******************************
+
+1.1 How do I override / manually enter TSS for a ride?
+======================================================
+
+The details chart on the analysis view allows you to override metrics
+on the metrics tab.  By default the most common metrics are listed,
+including average HR, distance and so on.  From v3.0 the default setup
+will also include TSS as a metric you can override here.
+
+If the metric is not there you will need to configure GoldenCheetah to
+allow it to be shown.  This is simple to do and described in 3.9 below.
+
+1.2 How do I add or remove a chart?
+===================================
+
+To add a new chart to the view you can select from the + menu on the
+right hand side of the scope bar (the scope bar is underneath the
+toolbar and lets you select from Home, Analysis, Train etc).
+
+Depending upon which view you are on the charts available will differ.
+For example realtime plots only appear on the Train view, whilst charts
+that work with individual rides will only appear on the analysis view.
+
+To remove a chart, when you mouse over a chart (in tabbed or tiled
+mode) a small triangle will appear in the top left of the chart. This
+is a menu drop down, if you click on it you will see a `Close' option.
+This is the option to remove (close) the chart.
+
+1.3 Can I enter my weight and track/plot it?
+============================================
+
+Weight can be maintained in 3 ways;
+
+   * Every athlete is setup with a weight value - this is the fallback
+     value should no     other weight measure be available. It can be
+     found under preferences and athlete.
+
+   * The 'Weight' field can be maintained in the details screen. This
+     is found on the     'Workout' tab in the details screen by
+     default. Any entry here will be used for this ride     ONLY.
+
+   * You can download weight from a withings scale. This is performed
+     manually via the     menu option Tools->Get Withings Data. This is
+     then used to update the local measures     database.
+
+When calculating W/KG the Activity value is used if present, if not we
+then fall back to the last Withing measure that was collected, and if
+that is not available we then fall back to the default value for the
+athlete.
+
+The weight from withings and weight from the activity can both be
+plotted separately in the LTM plots.
+
+1.4 How do I plot x sec power best?
+===================================
+
+As of v3.0 it is still not possible to plot custom durations for power
+bests. We are looking to add this in version 3.1, but for now you can
+only plot 1s, 5s, 10s, 15s, 20s, 30s, 1min, 2min, 5min, 10min, 20min,
+30min and 60min bests.
+
+1.5 I can't find Aerolab / Performance Manager?
+===============================================
+
+By default we do not add these charts to the layout. Aerolab can be
+added to the Analysis view via the '+' menu found to the right hand
+side of the GoldenCheetah scope bar.
+
+Similarly, the Performance manager can be added to the Home layout via
+the '+' menu. We may deprecate this chart in the near future since the
+LTM charts can be used to plot a PMC and we expect to implement an
+interactive PMC for planning in v3.1.
+
+1.6 What happened to weekly summary?
+====================================
+
+It has been deprecated since the Diary view allows you to summarise by
+day, week and month and add charts to the view that summarise for the
+selection. As the weekly summary was fixed on specific charts and did
+not handle other selections (e.g. monthly) it has been deprecated in
+view of the diary view.
+
+At present you can treat the Diary view as you would have the weekly
+summary - they offer the same functionality. We expect the diary view
+to extend to planned workouts when we implement planning functionality
+in v3.1.
+
+1.7 Where are all the chart settings?
+=====================================
+
+All chart settings can be found under the drop down menu that appears
+in the top left hand corner of a chart when you mouse over it. They
+will appear as a popup dialog box.
+
+Additionally, when you move the cursor towards the title of a chart in
+a view that is tabbed (not tiled) then a small selection of the most
+important settings for the chart will appear for convenience.
+
+1.8 Where is the preferences / options panel?
+=============================================
+
+On a Mac the configurations page can be found under 'GoldenCheetah ->
+Preferences' on the main menu. Whilst on all other platforms it is
+found via 'Tools -> Options'.
+
+We do this to match the general guidelines for the operating system.
+
+1.9 How do I change the colour of the rides on the calendar/list?
+=================================================================
+
+Activities are coloured according to keywords embedded in their details
+(metadata) you can configure the field that is used and the values that
+are matched and the colours they are shown in from the preferences pane
+via the 'Data Fields' toolbar option then select Notes Processing. The
+keywords and related words are scanned for to determine if the
+associated colour should be used for this ride.
+
+They are processed in the order they are defined with the first match
+being returned. Take care when using values such as 'TT' and 'race'
+since these can also be part of an English word (e.g. ATTEMPT contains
+'TT' and graceful contains 'race'.
+
+
+File: GC3-FAQ.info,  Node: GENERAL,  Next: METRICS,  Prev: MOST COMMON QUESTIONS OF ALL,  Up: Top
+
+2 GENERAL
+*********
+
+2.1 What is GoldenCheetah?
+==========================
+
+GoldenCheetah is primarily a program for cyclists that own a power
+meter. It allows them to record, track and review their performance
+against recorded data. It also allows you to ride your turbo and
+collect data as you ride.
+
+If you do not have a power meter then some of the functionality will
+not be of use to you as a cyclist. But you can still record and track
+progress. We support HR based TRIMP metrics for a HR based PMC for
+example.
+
+2.2 What is a good book or resource on training with power?
+===========================================================
+
+Unquestionably the bible for working with a power meter is Training and
+Racing with a Power Meter by Hunter Allan and Andy Coggan. Make sure
+you look at the 2nd edition since it is revised quite dramatically.
+Whilst it is heavily  biased towards WKO+ as a software package most of
+the functions of note are also available in GoldenCheetah.
+
+2.3 Where can I download the installer for GoldenCheetah ?
+==========================================================
+
+Stable releases are available from `http://www.goldencheetah.org'
+whilst the latest and greatest code build is available from
+`http://goldencheetah.stand2surf.net'. Development builds are for the
+brave, since they may contain bugs. In reality the development builds
+are a changing feast and often contain latest fixes too.
+
+2.4 Where can I get the source code?
+====================================
+
+The GoldenCheetah source code is hosted on github and can be cloned
+using the following url;
+`git://github.com/GoldenCheetah/GoldenCheetah.git'
+
+2.5 I am a triathlete is GoldenCheetah appropriate for me?
+==========================================================
+
+GoldenCheetah is not a multi-sport program. For tracking cycling
+performance it is a good choice. But if you are looking for running and
+swimming metrics and tracking then these features are not available at
+present. It is an excellent choice for analysing cycling aspects of
+triathlon, or working on the trainer.
+
+2.6 Is there a mailing list?
+============================
+
+The mailing list for GoldenCheetah users is maintained via Google
+Groups at
+`http://groups.google.com/forum/?fromgroups=#forum/golden-cheetah-users'
+the first post you make is moderated and may take a while to appear.
+Once your first post is made you can make future posts without
+moderation.
+
+2.7 How do I report a bug or request a new feature?
+===================================================
+
+We use Github issues to record bugs and feature requests. You will need
+to create an account on github and then post a new request or bug at
+`http://www.github.com/GoldenCheetah/GoldenCheetah/issues'
+
+2.8 How can I contribute?
+=========================
+
+Patches are most welcome via the mailing list or a pull request in
+github. Of equal importance is the timely reporting of bugs and help in
+testing fixes. We also desperately need volunteers to translate into
+non-English languages and help with writing documentation including the
+maintenance of this FAQ.
+
+If you want to help, post a note on the golden-cheetah-users mailing
+list.
+
+2.9 Can I donate to the project?
+================================
+
+We are an open source project. Our software is developed by a
+community. We do not have any facility to collect funding or spend it!
+We would rather you spread the word if you think our software is good,
+and maybe help out with documentation, tutorials or translations if you
+can.
+
+
+File: GC3-FAQ.info,  Node: METRICS,  Next: DATA,  Prev: GENERAL,  Up: Top
+
+3 METRICS
+*********
+
+3.1 What is the difference between xPower, NP and Daniels EqP?
+==============================================================
+
+They all serve the same purpose - to express the variable power you
+have generated over a given period of time as a single value. This is
+so you can quantify the intensity of the ride and therefore the
+training stress of the ride.
+
+In practice, NP and xPower are largely the same, whilst Daniels EqP
+place much higher emphasise on upper intensity work. For more info on
+xPower see Dr Skiba's paper on BikeScore
+`http://www.physfarm.com/bikescore.pdf'
+
+3.2 What is the difference between CP and FTP?
+==============================================
+
+CP is a shorthand for CP60 in GoldenCheetah, and is computed using the
+Scherer/Monod protocol using 3 and 20 minutes. Functional Threshold
+Power (FTP) is an actual measure of the power an athlete sustains for
+60 minutes.
+
+Since it is very difficult for an athlete to maintain the desired
+intensity FTP 'reality' tends to result in a number that is much lower
+than CP 'theory'. Often users will consider the two as the same.
+
+In GC we compute TSS and BikeScore using your 'CP' value. If you set it
+to your FTP value TSS will be accurate, BikeScore is likely to be
+lower. And if you set it to your CP value BikeScore will be accurate,
+but TSS will be overstated.
+
+3.3 Why does my CP chart show higher watts for a longer duration?
+=================================================================
+
+A higher power average for a longer time is possible if an effort has
+been "book ended".  If, for example, you did a massive 30 second
+effort, followed by freewheeling for 29:30 then another massive 30
+second effort, then your best average for a continuous 30 minutes would
+in fact be lower that your best average for a continuous 30minutes and
+30 seconds.  (Thanks for Jon Hill from the Golden Cheetah Users mailing
+list for this example).
+
+3.4 Can I set a different CP/FTP for different reasons e.g. CP/FTP on a trainer?
+================================================================================
+
+We allow you to override the CP value for a specific ride by setting
+the "CP" field to the value you wish to use for the ride in question.
+We do not have a concept of 'separate' Cps for different purposes - you
+will need to specify the CP when the data is imported into GC. But this
+allows you to make manual adjustments.
+
+We provide this functionality at user request - we do not endorse the
+concept of multiple CP values. But we do recognise the ongoing debate
+regarding physiological stress from working on a trainer vs on the road.
+
+3.5 How do I seed the CTL for my PMC?
+=====================================
+
+You can seed the starting CTL (we call it LTS, for long term stress)
+when you define a season. That way it is re-usable in a number of
+places. To do this you edit the season (date range) in the Home View
+and can set the Starting LTS.
+
+3.6 Why is elevation different in GoldenCheetah to my other training software / website?
+========================================================================================
+
+Different programs will use different hysteresis values to smooth the
+small changes in altitude. In GC we use a hysteresis value of 3m.
+
+If this is of great concern you can adjust the hysteresis value in
+preferences under the general tab.
+
+3.7 Why is a metric e.g. TSS or average power different in GoldenCheetah to Garmin Connect?
+===========================================================================================
+
+The algorithms for calculating TSS, AP etc are static. They are
+implemented exactly the same way in GoldenCheetah, Garmin Connect,
+TrainingPeaks etc. The algorithms are extremely simple and not prone to
+difficulty in implementation.
+
+However, how each application treats pauses and stops or loss of data
+accounts for most differences. In GoldenCheetah we always calculate
+AP,TSS etc including stop time. Other applications choose to ignore or
+smooth segments of short duration.
+
+In addition, if there are anomalies in your data, with large gaps or
+even time going backwards, this will drastically affect GoldenCheetah's
+calculations.
+
+We NEVER attempt to interpret data anomalies - if the results are not
+as you would expect you will need to correct the data. We do not
+'silently' fix the data for you. There is no secret sauce in
+GoldenCheetah, we are open and transparent with your data.
+
+3.8 How do I set the metrics shown for intervals in the various summaries?
+==========================================================================
+
+In the GoldenCheetah preference pane under the Metrics tab you can
+choose the metrics that will be shown in the ride summary charts and
+the metrics that will be shown in the interval summary in the analysis
+sidebar.
+
+3.9 How do I add a metric to the details screen (so I can override it) ?
+========================================================================
+
+If the metric you want (e.g. TSS) is not shown then you will need to
+add it via the GoldenCheetah preferences pane. On Mac this is from the
+menu option GoldenCheetah->Preferences whilst on Windows and Linux it
+is under Tools->Options.
+
+You will need to select 'Data Fields' option from preferences toolbar
+and then the 'fields' tab. You will see a list of fields that are
+associated with a particular screen tab. If you scroll down you should
+find entries for the 'Metrics' screen tab, you can insert a new entry
+here with the '+' button. You should make sure the new entry is called
+exactly the same thing as the metric in question.
+
+For 'TSS' this is relatively straight forward. For others, e.g.
+'Average Heart Rate' you must make sure that the name includes spaces
+etc. Once your metric has been added to the configuration you should
+save that and return to the details screen where you can now maintain
+it.
+
+If you are creating a manual entry then there is no 'details' tab in
+the dialog. Once you have created the entry (and again in this case TSS
+can be entered in the dialog) you should go to the details tab to
+maintain any other specific fields. The manual entry dialog is designed
+to be simple and accept only the most common of entries.
+
+3.10 Can you calculate gradient, virtual power or other derived series from the ride data?
+==========================================================================================
+
+Not in 3.0. We may introduce derived data series in the future.
+
+3.11 Can I export metrics or access the metric database GC uses?
+================================================================
+
+The metrics are stored within a Sqlite 3 Database called 'metricDBv3'
+that can be found in the athlete directory. You can use any Sqlite 3
+tools to query and work with the db.
+
+Alternatively you can export the db in its entirety using the
+Activity->Export Metrics as CSV to export to a format you can use in a
+spreadsheet program.
+
+
+File: GC3-FAQ.info,  Node: DATA,  Next: UPLOADING AND DOWNLOADING,  Prev: METRICS,  Up: Top
+
+4 DATA
+******
+
+4.1 How do I split, merge or join files?
+========================================
+
+You can split a file by time using the activity->split ride menu item
+(or toolbar button).
+
+To join two rides together (making one longer ride from two rides) you
+can copy rows in the activity editor and paste special in the ride
+editor (right click) and then select append mode.
+
+If you wish to merge rides, that is much harder and would need to be
+performed outside of GC or by cutting and pasting columns in the
+activity editor.
+
+4.2 How can I find 'spikes' or specific values in activity data?
+================================================================
+
+The activity editor has a function to find data on its toolbar. You can
+specify a range or upper or lower limit and find values less than,
+greater than or between a range of values.
+
+Additionally, the editor will scan the file looking for anomalies -
+where the data appears to be out of normal ranges. These are shown with
+a wiggly red line in the editor and can also be listed by clicking on
+the anomalies icon on the editor toolbar.
+
+If the anomalies icon is not enabled on the toolbar then there are no
+anomalies in the currently selected ride.
+
+4.3 How can I fix 'spikes' or 'anomalies' in activity data?
+===========================================================
+
+You can either manually edit the values in the activity editor (there
+is full undo and redo in the editor). Or you can use the fix tools that
+are listed under the tool menu option (fix power spikes, fix gaps in
+recording, fix gps errors, fix torque.
+
+Each of the fix tools opens a dialog that displays texts to explain
+what the fix tool does.
+
+4.4 How can I add/remove a field to edit on the details screen?
+===============================================================
+
+The fields (metadata) that is editable can be configured in the
+preferences pane under the data fields tab. Where no screen is
+specified (its left blank) it will not be made available.
+
+GoldenCheetah ships with a number of fields defined in the config but
+with no screen set.  If you wish to use them simply set the screen tab
+to the tab you would like it to be shown on. To remove a field set the
+field tab to blank.
+
+4.5 What are 'special fields' ?
+===============================
+
+There are a number of fields that when maintained in the details screen
+will be used elsewhere in the code to calculate metrics or for other
+purposes.
+
+Some examples include;
+
+Weight - used in W/KG calculations, Sport and Workout code are     used
+when exporting to other file formats, Identifier is used to assign a
+UUID to the     activity when it is uploaded to online services and so
+on.
+
+There is a full list of special fields and their meaning in the Golden
+Cheetah user guide appendices.
+
+4.6 How do I find/add/sort/delete/edit intervals ?
+==================================================
+
+The context menu (on the right hand side of the splitter handle) for
+the interval sidebar in Analysis view contains a number of options for
+working with intervals.
+
+Additionally, you can click and drag on the performance (aka ride) plot
+to visually define an interval.
+
+4.7 How can I export to a specific file format?
+===============================================
+
+Activity->Export allows you to export the activity to csv, fitlog, gc
+(xml), json, Training Peaks PWX or Garmin TCX format.
+
+4.8 Can I use GC to convert data from one format to another on the command line?
+================================================================================
+
+No. It is something we may add in v3.1
+
+4.9 Can I delete an athlete and all his/her data?
+=================================================
+
+No. It must be done manually by removing the athlete directory via the
+operating system. Please ensure you do this when GoldenCheetah is not
+running.
+
+
+File: GC3-FAQ.info,  Node: UPLOADING AND DOWNLOADING,  Next: SEASONS AND EVENTS,  Prev: DATA,  Up: Top
+
+5 UPLOADING AND DOWNLOADING
+***************************
+
+5.1 Why does upload to TrainingPeaks keep failing?
+==================================================
+
+The Sport field in TrainingPeaks must have very specific values,
+although this is not documented in the XML Schema. We recommend using a
+sport of "Bike" if you plan on uploading rides to training peaks.
+
+5.2 Why does download from TrainingPeaks say I need a premium account?
+======================================================================
+
+Training Peaks only allow paid up members to get access to their data.
+If you are using a free service they do not let you retrieve your data.
+
+5.3 Why is data uploaded to Strava all wrong?
+=============================================
+
+In general Strava will only use GPS data. If your ride does not contain
+GPS data then Strava is not likely to play nice. In addition many of
+the other data series will be ignored. This is related to Strava data
+processing in V2.0 of their API.
+
+We always upload as TCX since the JSON flavour of their API appears to
+have less functionality.
+
+5.4 What settings do I need to get GoldenCheetah to upload to my Google Calendar?
+=================================================================================
+
+The upload to Google Calendar uses their CalDAV API, and as such needs
+to specify a collection. This means when entering the details in the
+passwords pane of preferences you should use the following for the
+caldav url:
+
+`https://www.google.com/calendar/dav/xxxx@gmail.com/events/'
+
+Where xxxx is your username. The username will need to be repeated in
+the username field and obviously set the password too.
+
+5.5 When setting up my Withings wifi scales where do I get the userid and key ?
+===============================================================================
+
+You will need to login to your Withings account
+(`http://my.withings.com') and click on the `share' button at the top
+of the dashboard. From there you will get a popup box with lots of
+options.
+
+If you click on `share on my website' you will be greeted with a number
+of code snippets you can embed in a web page. If you look closely in
+the top right hand corner there will be a box containing the user id
+and public key. These are the two values you need to enter into the
+options dialog.
+
+You will now be able to retrieve withings data via the tools menu.
+
+
+File: GC3-FAQ.info,  Node: SEASONS AND EVENTS,  Next: CHARTS,  Prev: UPLOADING AND DOWNLOADING,  Up: Top
+
+6 SEASONS AND EVENTS
+********************
+
+6.1 Why are there different types of seasons?
+=============================================
+
+This is to help with planning functions. As of v3 there is no real
+distinction made.  Adhoc seasons are expected to be used solely as date
+ranges and have no associated plan.  Whilst other season types may
+contain plans. This is only relevant for planning functions that are
+not available yet.
+
+6.2 What is event used for?
+===========================
+
+It is only used to annotate a LTM chart - so you can show an 'event'
+that happened at a particular date. There are no rules about what
+constitutes and event. It could be a race, a training camp or just a
+day that was particularly meaningful e.g. illness, crash.
+
+6.3 How do create/edit/delete seasons and events?
+=================================================
+
+Seasons and Events are created and edited in the sidebar for the Home
+view. Seasons are listed under date ranges, whilst events are listed
+under the events sidebar item. In both cases they can be created and
+deleted from the sidebar item's drop down menu.
+
+Please note that in v3.0 events can only be created when a user season
+is selected, since events are associated with a particular season. This
+constraint will be removed in v3.1.
+
+
+File: GC3-FAQ.info,  Node: CHARTS,  Next: INDEX,  Prev: SEASONS AND EVENTS,  Up: Top
+
+7 CHARTS
+********
+
+7.1 I want to plot month -1,-2 and -3 how do I do that?
+=======================================================
+
+Assuming the chart allows you to specify a date range you can select
+'This' 'month' and select prior '3' to specify a month 3 years prior,
+similarly 'This' 'month' and prior '2' is a month 2 months ago, whilst
+'This' 'month' and prior '1' is last month.
+
+'This' 'month' prior and 0 is just this month.
+
+7.2 How does the mean max chart calculate CP when showing power?
+================================================================
+
+The CP algorithm searches your best power for two durations; for
+anaerobic efforts it looks between 15s and 1min, for aerobic it looks
+for best efforts between 10mins and an hour.
+
+Once it has found these two best values it will curve fit the two to
+enable the 60min value to be extracted. Bear in mind this is a
+theoretical number and as described above is applicable to the
+BikeScore algorithm. The value for FTP that the TSS algorithm requires
+is simply the highest value for 60mins for the time period, assuming
+you have performed a 60minute test recently.
+
+7.3 How should I use Aerolab?
+=============================
+
+The following is a brief piece of advice from Robert Chung, from a
+discussion on the Golden Cheetah Users mailing list:
+
+Ideally, you'll want calm conditions (both in terms of wind and
+traffic) but here's a     quickie test you can do just to get a handle
+on what to do. Try to find a loop without     stop signs, or an
+out-and-back with maybe a little dip or something in the middle. Make
+ sure you won't get hit by a car and have good sight lines. I just go
+around my block a     few times. Do a loop in the drops, then another
+loop faster, then a loop slower; then     repeat with your hands on the
+hoods.
+
+Weigh yourself and the bike and ballpark the air density.
+
+See whether you can come close to modeling the "true" elevation profile
+by sliding the     CdA slider around. Even with this informal test, as
+long as the wind isn't blowing too     hard, you ought to be able to
+see a difference between the loops where you were in the     drops and
+the loops where you on the hoods, and to spot little bumps and dips in
+the road.
+
+There is also an overview of Virtual Elevation to measure aerodynamics
+in this YouTube video from the power seminar at Interbike 2011 given by
+Jim Meyer the founder of Quarq:
+
+`http://www.youtube.com/watch?v=b8tJnFE_BFg&feature=youtu.be&t=27m58s'
+
+Finally, Robert Chung's original paper is included in the docs section
+of the GoldenCheetah repository, you can it up here (click on 'View
+Raw' to download):
+
+`https://github.com/GoldenCheetah/GoldenCheetah/blob/master/doc/contrib/ChungVE.pdf'
+
+7.4 My map doesn't show?
+========================
+
+This is most likely because you have a proxy that requires
+authentication or session details. We do not have sophisticated support
+for internet proxy servers. We will re-use the operating system
+settings where they are configured.
+
+7.5 What is the treemap plot used for?
+======================================
+
+Typically it is used to visualise where you spend your time or where
+you get best results.  It is not particularly useful if you do not
+maintain details for each ride e.g. workout code, sport et al.
+
+7.6 Can I change the colors in plot x ?
+=======================================
+
+With the exception of the Long Term Metric plots the colours on the
+charts are configured in the GoldenCheetah preferences pane.
+
+We want to use the same colours to plot each data series across the
+charts, so you can change them globally.
+
+The only colours you cannot change are the colours assigned to
+intervals when plotting them on scatterplot or PfPv. These colours are
+assigned according to their sequence.
+
+7.7 How do you zoom in on a chart?
+==================================
+
+You can zoom in on the distribution, scatterplot and PfPv charts by
+selecting the zoom area with the left click of the mouse.
+
+On the performance (ride) plot you can zoom with the span slider at the
+bottom of the chart (if you select the full plot in the chart settings).
+
+There are no other zoom options for the other charts.
+
+7.8 I zoomed in but can't zoom out?
+===================================
+
+Right click will zoom back out to the previous zoom level (in the case
+of zooming multiple times).  If you select another activity the chart
+will return to fully zoomed out.
+
+7.9 GoldenCheetah is saying there is no data for a chart, but I'm sure there is?
+================================================================================
+
+You should check in the editor if the data series is present. if the
+activity is a manual activity entry it will contain no data.
+
+
+File: GC3-FAQ.info,  Node: INDEX,  Next: MOST COMMON QUESTIONS OF ALL,  Prev: CHARTS,  Up: Top
+
+Index
+*****
+
+[index]
+* Menu:
+
+* add:                                   MOST COMMON QUESTIONS OF ALL.
+                                                              (line  20)
+* adhoc:                                 SEASONS AND EVENTS.  (line   9)
+* Aerolab <1>:                           CHARTS.              (line  33)
+* Aerolab:                               MOST COMMON QUESTIONS OF ALL.
+                                                              (line  69)
+* algorithm:                             CHARTS.              (line  19)
+* anomalies:                             DATA.                (line  23)
+* AP:                                    METRICS.             (line  80)
+* best:                                  MOST COMMON QUESTIONS OF ALL.
+                                                              (line  61)
+* bug:                                   GENERAL.             (line  66)
+* Chung:                                 CHARTS.              (line  33)
+* clone:                                 GENERAL.             (line  40)
+* colour <1>:                            CHARTS.              (line  84)
+* colour:                                MOST COMMON QUESTIONS OF ALL.
+                                                              (line 115)
+* contribute:                            GENERAL.             (line  73)
+* CP <1>:                                CHARTS.              (line  19)
+* CP:                                    METRICS.             (line  22)
+* CSV:                                   DATA.                (line  88)
+* CTL:                                   METRICS.             (line  63)
+* cycle:                                 SEASONS AND EVENTS.  (line   9)
+* Daniels:                               METRICS.             (line   9)
+* donate:                                GENERAL.             (line  85)
+* download <1>:                          UPLOADING AND DOWNLOADING.
+                                                              (line  16)
+* download:                              GENERAL.             (line  31)
+* elevation:                             METRICS.             (line  71)
+* EqP:                                   METRICS.             (line   9)
+* event:                                 SEASONS AND EVENTS.  (line  18)
+* feature:                               GENERAL.             (line  66)
+* FITLOG:                                DATA.                (line  88)
+* FTP:                                   METRICS.             (line  22)
+* Garmin Connect:                        METRICS.             (line  80)
+* github:                                GENERAL.             (line  40)
+* Google:                                UPLOADING AND DOWNLOADING.
+                                                              (line  33)
+* install:                               GENERAL.             (line  31)
+* join:                                  DATA.                (line   9)
+* JSON:                                  DATA.                (line  88)
+* LTS:                                   METRICS.             (line  63)
+* mail:                                  GENERAL.             (line  56)
+* map:                                   CHARTS.              (line  69)
+* merge:                                 DATA.                (line   9)
+* month:                                 CHARTS.              (line   9)
+* NP:                                    METRICS.             (line   9)
+* options:                               MOST COMMON QUESTIONS OF ALL.
+                                                              (line 106)
+* override:                              METRICS.             (line 110)
+* PMC <1>:                               METRICS.             (line  63)
+* PMC:                                   MOST COMMON QUESTIONS OF ALL.
+                                                              (line  69)
+* preferences:                           MOST COMMON QUESTIONS OF ALL.
+                                                              (line 106)
+* prior:                                 CHARTS.              (line   9)
+* PWX:                                   DATA.                (line  88)
+* remove:                                MOST COMMON QUESTIONS OF ALL.
+                                                              (line  20)
+* report:                                GENERAL.             (line  66)
+* season:                                SEASONS AND EVENTS.  (line   9)
+* settings:                              MOST COMMON QUESTIONS OF ALL.
+                                                              (line  95)
+* source:                                GENERAL.             (line  40)
+* spikes:                                DATA.                (line  23)
+* split:                                 DATA.                (line   9)
+* Strava:                                UPLOADING AND DOWNLOADING.
+                                                              (line  22)
+* TCX:                                   DATA.                (line  88)
+* trainer:                               METRICS.             (line  50)
+* TrainingPeaks:                         UPLOADING AND DOWNLOADING.
+                                                              (line   9)
+* treemap:                               CHARTS.              (line  77)
+* triathlete:                            GENERAL.             (line  47)
+* TSS <1>:                               METRICS.             (line  80)
+* TSS:                                   MOST COMMON QUESTIONS OF ALL.
+                                                              (line   9)
+* unzoom:                                CHARTS.              (line 108)
+* upload:                                UPLOADING AND DOWNLOADING.
+                                                              (line   9)
+* VE:                                    CHARTS.              (line  33)
+* weekly summary:                        MOST COMMON QUESTIONS OF ALL.
+                                                              (line  81)
+* weight:                                MOST COMMON QUESTIONS OF ALL.
+                                                              (line  36)
+* Withings:                              UPLOADING AND DOWNLOADING.
+                                                              (line  46)
+* xPower:                                METRICS.             (line   9)
+* zoom:                                  CHARTS.              (line  97)
+
+
+
+Tag Table:
+Node: Top164
+Node: MOST COMMON QUESTIONS OF ALL609
+Node: GENERAL6062
+Node: METRICS9684
+Node: DATA16676
+Node: UPLOADING AND DOWNLOADING20606
+Node: SEASONS AND EVENTS23090
+Node: CHARTS24487
+Node: INDEX29288
+
+End Tag Table

doc/user/GC3-FAQ.texinfo

@@ -0,0 +1,778 @@
+\input texinfo   @c -*-texinfo-*-
+@ifnotinfo
+@input palatino
+@end ifnotinfo
+@c %**start of header
+@setfilename FAQ.texinfo
+@settitle Golden Cheetah FAQ
+@c %**end of header
+@paragraphindent 0
+
+@copying
+This manual is for Golden Cheetah, version 3.0.
+
+Copyright @copyright{} 2013 Mark Liversedge
+@end copying
+
+@titlepage
+@title Golden Cheetah FAQ
+@c @subtitle subtitle-if-any
+@c @subtitle second-subtitle
+@author Mark Liversedge
+
+@c  The following two commands
+@c  start the copyright page.
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+
+@end titlepage
+
+@c So the toc is printed at the start.
+@contents
+
+@ifnottex
+@node Top,Top,Top,
+@top title
+
+This manual is for GoldenCheetah, version 3.0.
+@end ifnottex
+
+@menu
+* MOST COMMON QUESTIONS OF ALL::    Most common questions
+* GENERAL:: General Questions
+* DATA::    Working with Data
+* METRICS:: Working with Metrics
+* UPLOADING AND DOWNLOADING::   Uploading and Downloading Data
+* SEASONS AND EVENTS::  Seasons and Events
+* CHARTS::  Configuring and Using Charts
+* INDEX::   Index
+@end menu
+
+@node MOST COMMON QUESTIONS OF ALL,GENERAL,INDEX,Top
+@chapter MOST COMMON QUESTIONS OF ALL
+
+
+@section How do I override / manually enter TSS for a ride?
+@cindex TSS
+
+The details chart on the analysis view allows you to override metrics on the metrics tab. 
+By default the most common metrics are listed, including average HR, distance and so on.
+From v3.0 the default setup will also include TSS as a metric you can override here.
+
+If the metric is not there you will need to configure GoldenCheetah to allow it to be shown.
+This is simple to do and described in 3.9 below.
+
+@section How do I add or remove a chart?
+@cindex add
+@cindex remove
+
+To add a new chart to the view you can select from the + menu on the right hand side of 
+the scope bar (the scope bar is underneath the toolbar and lets you select from Home,
+Analysis, Train etc).
+
+Depending upon which view you are on the charts available will differ. For example realtime
+plots only appear on the Train view, whilst charts that work with individual rides will only
+appear on the analysis view.
+
+To remove a chart, when you mouse over a chart (in tabbed or tiled mode) a small triangle
+will appear in the top left of the chart. This is a menu drop down, if you click on it
+you will see a `Close' option. This is the option to remove (close) the chart.
+
+@section Can I enter my weight and track/plot it?
+@cindex weight
+
+Weight can be maintained in 3 ways;
+
+@itemize @bullet
+
+@item Every athlete is setup with a weight value -- this is the fallback value should no
+    other weight measure be available. It can be found under preferences and athlete.
+
+@item The 'Weight' field can be maintained in the details screen. This is found on the 
+    'Workout' tab in the details screen by default. Any entry here will be used for this ride
+    ONLY.
+
+@item You can download weight from a withings scale. This is performed manually via the
+    menu option Tools->Get Withings Data. This is then used to update the local measures
+    database.
+@end itemize
+
+When calculating W/KG the Activity value is used if present, if not we then fall back to
+the last Withing measure that was collected, and if that is not available we then fall
+back to the default value for the athlete.
+
+The weight from withings and weight from the activity can both be plotted separately in
+the LTM plots.
+
+
+
+@section How do I plot x sec power best?
+@cindex best
+
+As of v3.0 it is still not possible to plot custom durations for power bests. We are
+looking to add this in version 3.1, but for now you can only plot 1s, 5s, 10s, 15s, 20s,
+30s, 1min, 2min, 5min, 10min, 20min, 30min and 60min bests.
+
+
+
+@section I can't find Aerolab / Performance Manager?
+@cindex Aerolab
+@cindex PMC
+
+By default we do not add these charts to the layout. Aerolab can be added to the Analysis
+view via the '+' menu found to the right hand side of the GoldenCheetah scope bar.
+
+Similarly, the Performance manager can be added to the Home layout via the '+' menu. We
+may deprecate this chart in the near future since the LTM charts can be used to plot a PMC
+and we expect to implement an interactive PMC for planning in v3.1.
+
+
+
+@section What happened to weekly summary?
+@cindex weekly summary
+
+It has been deprecated since the Diary view allows you to summarise by day, week and month
+and add charts to the view that summarise for the selection. As the weekly summary was fixed
+on specific charts and did not handle other selections (e.g. monthly) it has been deprecated
+in view of the diary view.
+
+At present you can treat the Diary view as you would have the weekly summary -- they offer
+the same functionality. We expect the diary view to extend to planned workouts when we
+implement planning functionality in v3.1.
+
+
+
+@section Where are all the chart settings?
+@cindex settings
+
+All chart settings can be found under the drop down menu that appears in the top left hand
+corner of a chart when you mouse over it. They will appear as a popup dialog box.
+
+Additionally, when you move the cursor towards the title of a chart in a view that is tabbed
+(not tiled) then a small selection of the most important settings for the chart will appear
+for convenience.
+
+@section Where is the preferences / options panel?
+@cindex preferences
+@cindex options
+
+On a Mac the configurations page can be found under 'GoldenCheetah -> Preferences' on the
+main menu. Whilst on all other platforms it is found via 'Tools -> Options'.
+
+We do this to match the general guidelines for the operating system.
+
+@section How do I change the colour of the rides on the calendar/list?
+@cindex colour
+
+Activities are coloured according to keywords embedded in their details (metadata) you can
+configure the field that is used and the values that are matched and the colours they are
+shown in from the preferences pane via the 'Data Fields' toolbar option then select Notes
+Processing. The keywords and related words are scanned for to determine if the associated
+colour should be used for this ride.
+
+They are processed in the order they are defined with the first match being returned. Take
+care when using values such as 'TT' and 'race' since these can also be part of an English
+word (e.g. ATTEMPT contains 'TT' and graceful contains 'race'.
+
+
+
+@node GENERAL,METRICS,MOST COMMON QUESTIONS OF ALL,Top
+@chapter GENERAL
+
+
+@section What is GoldenCheetah?
+
+GoldenCheetah is primarily a program for cyclists that own a power meter. It allows them to
+record, track and review their performance against recorded data. It also allows you to ride
+your turbo and collect data as you ride.
+
+If you do not have a power meter then some of the functionality will not be of use to you
+as a cyclist. But you can still record and track progress. We support HR based TRIMP metrics
+for a HR based PMC for example.
+
+
+
+@section What is a good book or resource on training with power?
+
+Unquestionably the bible for working with a power meter is Training and Racing with a Power
+Meter by Hunter Allan and Andy Coggan. Make sure you look at the 2nd edition since it is
+revised quite dramatically. Whilst it is heavily  biased towards WKO+ as a software package
+most of the functions of note are also available in GoldenCheetah.
+
+
+
+@section Where can I download the installer for GoldenCheetah ?
+@cindex download
+@cindex install
+
+Stable releases are available from @url{http://www.goldencheetah.org} whilst the latest and greatest
+code build is available from @url{http://goldencheetah.stand2surf.net}. Development builds are for the
+brave, since they may contain bugs. In reality the development builds are a changing feast
+and often contain latest fixes too.
+
+
+
+@section Where can I get the source code?
+@cindex source
+@cindex github
+@cindex clone
+
+The GoldenCheetah source code is hosted on github and can be cloned using the following url;
+@code{git://github.com/GoldenCheetah/GoldenCheetah.git}
+
+
+
+@section I am a triathlete is GoldenCheetah appropriate for me?
+@cindex triathlete
+
+GoldenCheetah is not a multi-sport program. For tracking cycling performance it is a good
+choice. But if you are looking for running and swimming metrics and tracking then these
+features are not available at present. It is an excellent choice for analysing cycling
+aspects of triathlon, or working on the trainer.
+
+
+
+@section Is there a mailing list?
+@cindex mail
+
+The mailing list for GoldenCheetah users is maintained via Google Groups at
+@url{http://groups.google.com/forum/?fromgroups=#forum/golden-cheetah-users} the first post you
+make is moderated and may take a while to appear. Once your first post is made you can
+make future posts without moderation.
+
+
+
+@section How do I report a bug or request a new feature?
+@cindex feature
+@cindex bug
+@cindex report
+
+We use Github issues to record bugs and feature requests. You will need to create an
+account on github and then post a new request or bug at 
+@url{http://www.github.com/GoldenCheetah/GoldenCheetah/issues}
+
+
+
+@section How can I contribute?
+@cindex contribute
+
+Patches are most welcome via the mailing list or a pull request in github. Of equal
+importance is the timely reporting of bugs and help in testing fixes. We also desperately
+need volunteers to translate into non-English languages and help with writing documentation
+including the maintenance of this FAQ.
+
+If you want to help, post a note on the golden-cheetah-users mailing list.
+
+
+
+@section Can I donate to the project?
+@cindex donate
+
+We are an open source project. Our software is developed by a community. We do not have
+any facility to collect funding or spend it! We would rather you spread the word if you
+think our software is good, and maybe help out with documentation, tutorials or
+translations if you can.
+
+
+
+@node METRICS,DATA,GENERAL,Top
+@chapter METRICS
+
+
+@section What is the difference between xPower, NP and Daniels EqP?
+@cindex xPower
+@cindex NP
+@cindex Daniels
+@cindex EqP
+
+They all serve the same purpose -- to express the variable power you have generated over
+a given period of time as a single value. This is so you can quantify the intensity of
+the ride and therefore the training stress of the ride.
+
+In practice, NP and xPower are largely the same, whilst Daniels EqP place much higher
+emphasise on upper intensity work. For more info on xPower see Dr Skiba's paper on BikeScore
+@url{http://www.physfarm.com/bikescore.pdf}
+
+
+
+@section What is the difference between CP and FTP?
+@cindex CP
+@cindex FTP
+
+CP is a shorthand for CP60 in GoldenCheetah, and is computed using the Scherer/Monod
+protocol using 3 and 20 minutes. Functional Threshold Power (FTP) is an actual measure of
+the power an athlete sustains for 60 minutes.
+
+Since it is very difficult for an athlete to maintain the desired intensity FTP 'reality'
+tends to result in a number that is much lower than CP 'theory'. Often users will
+consider the two as the same.
+
+In GC we compute TSS and BikeScore using your 'CP' value. If you set it to your FTP value
+TSS will be accurate, BikeScore is likely to be lower. And if you set it to your CP value
+BikeScore will be accurate, but TSS will be overstated.
+
+
+
+@section Why does my CP chart show higher watts for a longer duration?
+@cindex CP
+
+A higher power average for a longer time is possible if an effort has been "book ended".
+If, for example, you did a massive 30 second effort, followed by freewheeling for 29:30
+then another massive 30 second effort, then your best average for a continuous 30 minutes
+would in fact be lower that your best average for a continuous 30minutes and 30 seconds.
+(Thanks for Jon Hill from the Golden Cheetah Users mailing list for this example).
+
+
+
+@section Can I set a different CP/FTP for different reasons e.g. CP/FTP on a trainer?
+@cindex CP
+@cindex FTP
+@cindex trainer
+
+We allow you to override the CP value for a specific ride by setting the "CP" field to
+the value you wish to use for the ride in question. We do not have a concept of 'separate'
+Cps for different purposes -- you will need to specify the CP when the data is imported
+into GC. But this allows you to make manual adjustments.
+
+We provide this functionality at user request -- we do not endorse the concept of multiple
+CP values. But we do recognise the ongoing debate regarding physiological stress from
+working on a trainer vs on the road.
+
+
+@section How do I seed the CTL for my PMC?
+@cindex PMC
+@cindex CTL
+@cindex LTS
+
+You can seed the starting CTL (we call it LTS, for long term stress) when you define a
+season. That way it is re-usable in a number of places. To do this you edit the season
+(date range) in the Home View and can set the Starting LTS.
+
+@section Why is elevation different in GoldenCheetah to my other training software / website?
+@cindex elevation
+
+Different programs will use different hysteresis values to smooth the small changes in
+altitude. In GC we use a hysteresis value of 3m.
+
+If this is of great concern you can adjust the hysteresis value in preferences under the
+general tab.
+
+
+
+@section Why is a metric e.g. TSS or average power different in GoldenCheetah to Garmin Connect?
+@cindex TSS
+@cindex AP
+@cindex Garmin Connect
+
+The algorithms for calculating TSS, AP etc are static. They are implemented exactly the
+same way in GoldenCheetah, Garmin Connect, TrainingPeaks etc. The algorithms are extremely
+simple and not prone to difficulty in implementation.
+
+However, how each application treats pauses and stops or loss of data accounts for most
+differences. In GoldenCheetah we always calculate AP,TSS etc including stop time. Other
+applications choose to ignore or smooth segments of short duration.
+
+In addition, if there are anomalies in your data, with large gaps or even time going
+backwards, this will drastically affect GoldenCheetah's calculations.
+
+We NEVER attempt to interpret data anomalies -- if the results are not as you would expect
+you will need to correct the data. We do not 'silently' fix the data for you. There is no
+secret sauce in GoldenCheetah, we are open and transparent with your data.
+
+
+
+@section How do I set the metrics shown for intervals in the various summaries?
+
+In the GoldenCheetah preference pane under the Metrics tab you can choose the metrics
+that will be shown in the ride summary charts and the metrics that will be shown in the
+interval summary in the analysis sidebar.
+
+
+
+@section How do I add a metric to the details screen (so I can override it) ?
+@cindex override
+
+If the metric you want (e.g. TSS) is not shown then you will need to add it via the
+GoldenCheetah preferences pane. On Mac this is from the menu option
+GoldenCheetah->Preferences whilst on Windows and Linux it is under Tools->Options.
+
+You will need to select 'Data Fields' option from preferences toolbar and then the
+'fields' tab. You will see a list of fields that are associated with a particular screen
+tab. If you scroll down you should find entries for the 'Metrics' screen tab, you can
+insert a new entry here with the '+' button. You should make sure the new entry is
+called exactly the same thing as the metric in question.
+
+For 'TSS' this is relatively straight forward. For others, e.g. 'Average Heart Rate' you
+must make sure that the name includes spaces etc. Once your metric has been added to the
+configuration you should save that and return to the details screen where you can now
+maintain it.
+
+If you are creating a manual entry then there is no 'details' tab in the dialog. Once
+you have created the entry (and again in this case TSS can be entered in the dialog)
+you should go to the details tab to maintain any other specific fields. The manual entry
+dialog is designed to be simple and accept only the most common of entries.
+
+
+
+@section Can you calculate gradient, virtual power or other derived series from the ride data?
+
+Not in 3.0. We may introduce derived data series in the future.
+
+
+
+@section Can I export metrics or access the metric database GC uses?
+
+The metrics are stored within a Sqlite 3 Database called 'metricDBv3' that can be found
+in the athlete directory. You can use any Sqlite 3 tools to query and work with the db.
+
+Alternatively you can export the db in its entirety using the Activity->Export Metrics
+as CSV to export to a format you can use in a spreadsheet program. 
+
+
+
+@node DATA,UPLOADING AND DOWNLOADING,METRICS,Top
+@chapter DATA
+
+
+
+@section How do I split, merge or join files?
+@cindex split
+@cindex merge
+@cindex join
+
+You can split a file by time using the activity->split ride menu item (or toolbar button).
+
+To join two rides together (making one longer ride from two rides) you can copy rows
+in the activity editor and paste special in the ride editor (right click) and then select
+append mode.
+
+If you wish to merge rides, that is much harder and would need to be performed outside
+of GC or by cutting and pasting columns in the activity editor.
+
+
+
+@section How can I find 'spikes' or specific values in activity data?
+@cindex spikes
+@cindex anomalies
+
+The activity editor has a function to find data on its toolbar. You can specify a range
+or upper or lower limit and find values less than, greater than or between a range of values.
+
+Additionally, the editor will scan the file looking for anomalies -- where the data
+appears to be out of normal ranges. These are shown with a wiggly red line in the editor
+and can also be listed by clicking on the anomalies icon on the editor toolbar.
+
+If the anomalies icon is not enabled on the toolbar then there are no anomalies in the
+currently selected ride.
+
+
+
+@section How can I fix 'spikes' or 'anomalies' in activity data?
+@cindex spikes
+@cindex anomalies
+
+You can either manually edit the values in the activity editor (there is full undo and
+redo in the editor). Or you can use the fix tools that are listed under the tool menu
+option (fix power spikes, fix gaps in recording, fix gps errors, fix torque.
+
+Each of the fix tools opens a dialog that displays texts to explain what the fix tool does.
+
+
+
+@section How can I add/remove a field to edit on the details screen?
+
+The fields (metadata) that is editable can be configured in the preferences pane under
+the data fields tab. Where no screen is specified (its left blank) it will not be made
+available.
+
+GoldenCheetah ships with a number of fields defined in the config but with no screen set.
+If you wish to use them simply set the screen tab to the tab you would like it to be
+shown on. To remove a field set the field tab to blank.
+
+
+
+@section What are 'special fields' ?
+
+There are a number of fields that when maintained in the details screen will be used
+elsewhere in the code to calculate metrics or for other purposes.
+
+Some examples include;
+
+    Weight - used in W/KG calculations, Sport and Workout code are
+    used  when exporting to other file formats, Identifier is used to assign a UUID to the
+    activity when it is uploaded to online services and so on.
+
+There is a full list of special fields and their meaning in the Golden Cheetah user
+guide appendices.
+
+
+
+@section How do I find/add/sort/delete/edit intervals ?
+
+The context menu (on the right hand side of the splitter handle) for the interval
+sidebar in Analysis view contains a number of options for working with intervals.
+
+Additionally, you can click and drag on the performance (aka ride) plot to visually
+define an interval.
+
+
+
+@section How can I export to a specific file format?
+@cindex PWX
+@cindex JSON
+@cindex TCX
+@cindex CSV
+@cindex FITLOG
+
+Activity->Export allows you to export the activity to csv, fitlog, gc (xml), json,
+Training Peaks PWX or Garmin TCX format.
+
+
+
+@section Can I use GC to convert data from one format to another on the command line?
+
+No. It is something we may add in v3.1
+
+
+
+@section Can I delete an athlete and all his/her data?
+
+No. It must be done manually by removing the athlete directory via the operating
+system. Please ensure you do this when GoldenCheetah is not running.
+
+
+
+@node UPLOADING AND DOWNLOADING,SEASONS AND EVENTS,DATA,Top
+@chapter UPLOADING AND DOWNLOADING
+
+
+
+@section Why does upload to TrainingPeaks keep failing?
+@cindex TrainingPeaks
+@cindex upload
+
+The Sport field in TrainingPeaks must have very specific values, although this is not
+documented in the XML Schema. We recommend using a sport of "Bike" if you plan on
+uploading rides to training peaks.
+
+
+
+@section Why does download from TrainingPeaks say I need a premium account?
+@cindex TrainingPeaks
+@cindex download
+
+Training Peaks only allow paid up members to get access to their data. If you are
+using a free service they do not let you retrieve your data.
+
+
+
+@section Why is data uploaded to Strava all wrong?
+@cindex Strava
+
+In general Strava will only use GPS data. If your ride does not contain GPS data then
+Strava is not likely to play nice. In addition many of the other data series will be
+ignored. This is related to Strava data processing in V2.0 of their API.
+
+We always upload as TCX since the JSON flavour of their API appears to have less
+functionality.
+
+
+
+@section What settings do I need to get GoldenCheetah to upload to my Google Calendar?
+@cindex Google
+
+The upload to Google Calendar uses their CalDAV API, and as such needs to specify a
+collection. This means when entering the details in the passwords pane of preferences
+you should use the following for the caldav url:
+    
+    @url{https://www.google.com/calendar/dav/xxxx@@gmail.com/events/}
+
+Where xxxx is your username. The username will need to be repeated in the username
+field and obviously set the password too.
+
+
+@section When setting up my Withings wifi scales where do I get the userid and key ?
+@cindex Withings
+
+You will need to login to your Withings account (@url{http://my.withings.com}) and
+click on the `share' button at the top of the dashboard. From there you will get a
+popup box with lots of options.
+
+If you click on `share on my website' you will be greeted with a number of code
+snippets you can embed in a web page. If you look closely in the top right hand
+corner there will be a box containing the user id and public key. These are the
+two values you need to enter into the options dialog.
+
+You will now be able to retrieve withings data via the tools menu.
+
+@node SEASONS AND EVENTS,CHARTS,UPLOADING AND DOWNLOADING,Top
+@chapter SEASONS AND EVENTS
+
+
+
+@section Why are there different types of seasons?
+@cindex season
+@cindex adhoc
+@cindex cycle
+
+This is to help with planning functions. As of v3 there is no real distinction made.
+Adhoc seasons are expected to be used solely as date ranges and have no associated plan.
+Whilst other season types may contain plans. This is only relevant for planning
+functions that are not available yet.
+
+
+
+@section What is event used for?
+@cindex event
+
+It is only used to annotate a LTM chart -- so you can show an 'event' that happened at
+a particular date. There are no rules about what constitutes and event. It could be a
+race, a training camp or just a day that was particularly meaningful e.g. illness, crash.
+
+
+@section How do create/edit/delete seasons and events?
+@cindex event
+@cindex season
+
+Seasons and Events are created and edited in the sidebar for the Home view. Seasons are
+listed under date ranges, whilst events are listed under the events sidebar item. In
+both cases they can be created and deleted from the sidebar item's drop down menu.
+
+Please note that in v3.0 events can only be created when a user season is selected, since
+events are associated with a particular season. This constraint will be removed in v3.1.
+
+@node CHARTS,INDEX,SEASONS AND EVENTS,Top
+@chapter CHARTS
+
+
+
+@section I want to plot month -1,-2 and -3 how do I do that?
+@cindex month
+@cindex prior
+
+Assuming the chart allows you to specify a date range you can select 'This' 'month'
+and select prior '3' to specify a month 3 years prior, similarly 'This' 'month' and
+prior '2' is a month 2 months ago, whilst 'This' 'month' and prior '1' is last month.
+
+'This' 'month' prior and 0 is just this month.
+
+
+
+@section How does the mean max chart calculate CP when showing power?
+@cindex CP
+@cindex algorithm
+
+The CP algorithm searches your best power for two durations; for anaerobic efforts it 
+looks between 15s and 1min, for aerobic it looks for best efforts between 10mins and
+an hour.
+
+Once it has found these two best values it will curve fit the two to enable the
+60min value to be extracted. Bear in mind this is a theoretical number and as described
+above is applicable to the BikeScore algorithm. The value for FTP that the TSS algorithm
+requires is simply the highest value for 60mins for the time period, assuming you have
+performed a 60minute test recently.
+
+
+
+@section How should I use Aerolab?
+@cindex Aerolab
+@cindex Chung
+@cindex VE
+
+The following is a brief piece of advice from Robert Chung, from a discussion on the
+Golden Cheetah Users mailing list:
+
+    Ideally, you'll want calm conditions (both in terms of wind and traffic) but here's a
+    quickie test you can do just to get a handle on what to do. Try to find a loop without
+    stop signs, or an out-and-back with maybe a little dip or something in the middle. Make
+    sure you won't get hit by a car and have good sight lines. I just go around my block a
+    few times. Do a loop in the drops, then another loop faster, then a loop slower; then
+    repeat with your hands on the hoods.
+
+    Weigh yourself and the bike and ballpark the air density. 
+
+    See whether you can come close to modeling the "true" elevation profile by sliding the
+    CdA slider around. Even with this informal test, as long as the wind isn't blowing too
+    hard, you ought to be able to see a difference between the loops where you were in the
+    drops and the loops where you on the hoods, and to spot little bumps and dips in the road. 
+
+There is also an overview of Virtual Elevation to measure aerodynamics in this
+YouTube video from the power seminar at Interbike 2011 given by Jim Meyer the founder
+of Quarq:
+
+    @url{http://www.youtube.com/watch?v=b8tJnFE_BFg&feature=youtu.be&t=27m58s}
+
+Finally, Robert Chung's original paper is included in the docs section of the GoldenCheetah
+repository, you can it up here (click on 'View Raw' to download):
+
+    @url{https://github.com/GoldenCheetah/GoldenCheetah/blob/master/doc/contrib/ChungVE.pdf}
+
+
+
+@section My map doesn't show?
+@cindex map
+
+This is most likely because you have a proxy that requires authentication or session
+details. We do not have sophisticated support for internet proxy servers. We will
+re-use the operating system settings where they are configured.
+
+
+
+@section What is the treemap plot used for?
+@cindex treemap
+
+Typically it is used to visualise where you spend your time or where you get best
+results.  It is not particularly useful if you do not maintain details for each ride
+e.g. workout code, sport et al.
+
+
+
+@section Can I change the colors in plot x ?
+@cindex colour
+
+With the exception of the Long Term Metric plots the colours on the charts are
+configured in the GoldenCheetah preferences pane.
+
+We want to use the same colours to plot each data series across the charts, so you
+can change them globally.
+
+The only colours you cannot change are the colours assigned to intervals when plotting
+them on scatterplot or PfPv. These colours are assigned according to their sequence.
+
+
+
+@section How do you zoom in on a chart?
+@cindex zoom
+
+You can zoom in on the distribution, scatterplot and PfPv charts by selecting the zoom
+area with the left click of the mouse.
+
+On the performance (ride) plot you can zoom with the span slider at the bottom of the
+chart (if you select the full plot in the chart settings).
+
+There are no other zoom options for the other charts.
+
+
+
+@section I zoomed in but can't zoom out?
+@cindex zoom
+@cindex unzoom
+
+Right click will zoom back out to the previous zoom level (in the case of zooming
+multiple times).  If you select another activity the chart will return to fully
+zoomed out.
+
+
+
+@section GoldenCheetah is saying there is no data for a chart, but I'm sure there is?
+
+You should check in the editor if the data series is present. if the activity is a
+manual activity entry it will contain no data.
+
+@node INDEX,MOST COMMON QUESTIONS OF ALL,CHARTS,Top
+@unnumbered Index
+
+@printindex cp
+
+@bye

doc/user/GC3-Manual.texinfo

@@ -0,0 +1,898 @@
+\input texinfo   @c -*-texinfo-*-
+@ifnotinfo
+@input palatino
+@end ifnotinfo
+@c %**start of header
+@setfilename GC3-Manual.texinfo
+@settitle Golden Cheetah User Manual
+@c %**end of header
+@paragraphindent 0
+ 
+@copying
+This manual is for Golden Cheetah, version 3.0.
+ 
+Copyright @copyright{} 2013 Mark Liversedge
+@end copying
+ 
+@titlepage
+@image{"image/0-icon",140pt,140pt}
+@vskip 20pt
+@title Golden Cheetah User Manual
+@c @subtitle subtitle-if-any
+@c @subtitle second-subtitle
+@author Mark Liversedge
+ 
+@c  The following two commands
+@c  start the copyright page.
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+ 
+@end titlepage
+ 
+@c So the toc is printed at the start.
+@contents
+ 
+@c ********************************************************************************
+@c Welcome chapter
+@c ********************************************************************************
+@chapter WELCOME TO GOLDENCHEETAH
+@node WELCOME
+
+@vskip 6pt 
+@center @strong{GoldenCheetah is an open source program for cyclists.}
+@vskip 12pt
+ 
+In fact, it is primarily a program for cyclists with a power meter. It provides functions
+to download, import, edit, upload and analyse rides containing power data.
+ 
+It can be used to analyse bike rides that do not contain power, perhaps containing speed,
+cadence or GPS data. It can be used to analyse other kinds of workouts, perhaps run or
+swim activities. It can be used purely as a log or journal for any activity.
+ 
+@vskip 12pt 
+@center @strong{GoldenCheetah is primarily an open source program for cyclists that own a power meter.}
+@vskip 12pt
+ 
+In addition to the post-workout analysis it can also be used as a desktop application to
+record and monitor workouts on a cycle trainer. It captures telemetry from ANT+ sensors
+and can also work directly with Bike trainers that provide the right kind of interface.
+ 
+In this manual we will be explaining how to use and configure the functions within GoldenCheetah.
+We will be describing it from the perspective of a bike rider. In all cases we will be describing
+how the functions within GoldenCheetah work, and how to configure them.
+ 
+This is not a manual on how to train with power. We would urge you to read other books for that
+kind of information and would recommend `Racing and Training with a Power Meter' by
+Dr Andrew Coggan and Hunter Allan.
+ 
+@section About this latest version, V3.0
+
+This manual has been written as a companion to the latest release of GoldenCheetah, v3.0.
+Released in Spring 2013, it represented an overhaul of the code and was a major update.
+ 
+If you are new to GoldenCheetah then all the functions it provides will be new to you, but
+for existing users, version 3.0 had introduced;
+ 
+@heading 500+ bug fixes and minor enhancements
+ 
+It fixed 46 serious issues and over 400 bugs in over 1,500 different
+commits. GoldenCheetah is now over 120,000 lines of code.  In addition
+to addressing stability issues it also addressed a number of performance
+related issues.  Whilst the new metric functionality and database means that
+a modern PC is recommended, the code is still efficient enough to run on
+a netbook.
+ 
+@heading Redesigned UI and UX
+ 
+One of the most immediate changes you will notice with v3.0 are the
+major changes to the user experience and user interface. From the
+initial help screens for new users through to the redesigned preferences
+pane for advanced users, it is more complete and more professional.
+ 
+There are 4 views available with specific and detailed sidebars for
+performance tracking (home), short term tracking (diary) as well as
+the well known analysis and training views from earlier releases.
+ 
+It now allows you to view charts tabbed and tiled, you can resize and
+move charts around and customise them using roll-over controls. The
+activity list is fully configurable and can be configured to show any
+number of columns.
+ 
+@heading Support for the latest bike computers
+ 
+It supports direct download features for the Cyclops Joule and Joule GPS
+as well as the latest SRM Powercontrol 6 and 7. We also added support for
+the O-sync Macro and Macro X.
+ 
+@heading Support for more telemetry
+ 
+Alongside the support for the latest bike computers it also added the ability to
+track and plot new data series, including; Headwind, LR Balance, Temperature and
+Slope.
+ 
+@heading Export and Batch Export as well as lots of new file formats
+ 
+It will now export and batch export your data to a wide variety of file
+formats include TCX, PWX, JSON and XML as well as FITLOG and GPX.
+ 
+It also supports reading files from SportTracks, GPX, Tacx CAF and the
+SLF/SMF file formats. We have also added legacy WKO+ file format support
+(CP 1.0 and 1.1) as well as import of Wattbike TXT exports.
+ 
+@heading Support for a wide selection of internet services
+ 
+It can upload and download data from; Withings, Zeo, Strava, TrainingPeaks,
+Training Stage Buch, RideWithGPS as well as Internet based calendars (calDAV)
+such as Google Calendar.
+ 
+@heading Realtime training significantly enhanced
+ 
+Support has been added for native ANT+ removing the need for quarqd. Video Playback
+is built in using VLC/QTKit. It now has a  media library to organise and reference
+any video content you may have from Tacx Ergvideos through Sufferfest.
+ 
+It supports Virtual Power for popular devices from KK, LeMond and many other
+trainers.  We have added support for the amazing new Wahoo Fitness Kickr trainer
+as well as the old Tacx Fortius.
+ 
+It also introduces new ways to ride on the trainer including;
+Streetview, SpinScan (on Computrainer) and an enhanced Workout Plot that plots
+telemetry against the workout as you ride.
+ 
+It also includes Computrainer calibration, a workout wizard and download
+from ErgDB as well as Multi-device Support allowing you to ride with with
+your ANT+ powermeter on your Computrainer, Kickr or Fortius.
+ 
+@heading Advanced search and data filtering
+ 
+It introduces free text search across all activities and a data filter (using the same search box)
+to filter activities with specific properties. Some examples of using the filter might be
+finding all rides with a TSS > 300 or perhaps those with an IF >0.9 and a duration of > 1hr.
+ 
+The search and filter functions can be applied to the charts -- which means that
+you can plot a PMC only where sport is "Bike" or perhaps power distribution but only
+where the workout code is FTPTEST.
+ 
+@heading Lots of new charts
+ 
+It provides a new HR to Power analysis chart as well as a more utilitarian 2d scatter
+plot. It will also use Bing as map provider for the Map chart.
+ 
+The histogram and CP curve plots will now plot data for a date range rather than for
+a specific ride and it will also now plot a mean max curve for HR, Power, Speed, Cadence,
+xPower, VAM and NP.
+ 
+@heading New metrics, including TrainingPeaks' TSS and NP
+ 
+The TrainingPeaks metrics have been added to both the analysis functions as well as the
+training functions (e.g. track TSS as you ride the trainer).
+ 
+There are now over 100 different metrics and measures you can work with including things
+like; Pace, Maximums, Gradient, VAM, wpk, time in HR Zones and many, many more.
+ 
+@section Open Source
+ 
+GoldenCheetah is an open source program. This means the source code is freely available to
+download and compile. You can add new features and fix bugs. All we ask is that you then
+share your work back to the main project.
+ 
+This is how GoldenCheetah has developed since it was first created in 2006. Over 50 different
+people have contributed new features and fixes in the 7 years since then.
+ 
+@heading Mailing list
+ 
+As you would expect there is an active community of users and developers, you can join the
+discussion and contribute. The main GoldenCheetah website is @url{www.goldencheetah.org}
+and the main mailing list is hosted on Google Groups and is called golden-cheetah-users.
+ 
+@heading Reporting bugs and requesting new features
+ 
+The code is hosted in a repository at GitHub. Github is an internet service hosting open
+source and commercial code repositories for thousands of projects. In addition to hosting
+projects GitHub also provides an issue tracker.
+ 
+The issue tracker URL is: @url{github.com/GoldenCheetah/GoldenCheetah/issues}.
+ 
+We use the GitHub issue tracker to manage all bug reports and feature requests. If you are
+looking for a new feature or have experienced a problem using the software then you should
+consider raising it on the issue tracker.
+ 
+As a non-developer one of the most valuable contributions you can make to the project is to
+provide accurate and informative bug reports. This makes it easier for the developers to fix
+the code and in turn makes the software better for everyone.
+
+@section Bit of Past and Present
+ 
+In early 2006 a Cat 1 racer called Sean Rhea bought a Powertap. Back then power meters were not
+very common. They certainly weren't very open. The software options were very limited. But
+Sean was a bit of a geek.
+ 
+He set about reverse engineering the protocol the Powertap used to communicate with the PC and
+he developed a couple of command line utilities in the C programming language; `ptdl' and `ptunpk'.
+These utilities downloaded data from a Powertap via its serial interface saving to `raw' files
+on disk, and then read that raw file and formatted the output for inputting into GNU plot.
+ 
+But it soon became clear that using the command line was not at all user friendly. A GUI was
+going to be required. And so, in late 2006 Sean set about writing a GUI version using the
+QT framework and moving to the C++ language (because he needed to learn QT for his new job).
+ 
+This early version had the main charts you see today, indeed a lot of that early code is still
+present. It could plot the ride, histograms and the CP curve that it is famous for.
+ 
+From 2007 with Sean leading many new people became involved and new features
+were introduced; support for SRM using the libsrm project written by Rainer Clasen. Support for
+Linux, Windows, Metrics, File Formats, Power Zones and a large number of new charts including
+a Performance Manager written by Eric Murray. Google Map written by Greg Lonnon.
+ 
+During this time the project moved from a `hack' project to a fully fledged open source development
+project and saw Jamie Kimberley, Robert Carlsen and Justin Knotzke assist Sean in managing development
+with the introduction of a bugs database and more formalised releases for Linux, Mac and Windows.
+ 
+In Summer 2009 a lot of the current developers joined the project, notably Damien Grauser who added
+much needed support for interval analysis and Mark Liversedge who contributed WKO+ file support and
+the 3d plot. Over the next 12 months v2.0 was developed introducing the training View (with Justin Knotzke)
+as well as the editor and tools, metadata and long term plotting charts.
+ 
+At the tail end of 2010 Sean handed leadership of the project to Mark. Sean was no longer racing and most
+develpoment was now being delivered by others anyway. So in January 2011 Mark merged a number of features
+that were being developed in private into the main repository and thus V3 development began.
+ 
+In Spring 2013, after 3 years of development version 3 was released, along with this user guide.
+ 
+Version 3 is a landmark release and provides a platform for future development - the modular views and
+configurable layouts means it will be very easy to introduce new functionality and concepts without
+needing to adjust the underlying code. In short, v3 provides a future platform.
+
+@section Future Plans
+ 
+Version 3.1 is already being planned and the high priority features include;
+
+@itemize @bullet 
+@item Planning functions centred around the concept of an interactive performance manager chart
+where you set target events and physical adaptations or performance targets with a progression of
+daily stress and long term stress.
+ 
+@item Interval Analysis and Comparison across separate rides, to compare efforts and track and rank
+performance in intervals or `segments' of rides and routes.
+ 
+@item Season by Season progression to compare and rank performance development in cycles and seasons
+across the long term charts, but also the critical power and distribution charts.
+ 
+@item Separation of the training view into a separate program `OpenTrainer' to enable more advanced
+graphical displays including video with overlay and animations.
+@end itemize
+ 
+Version 3.1, hopefully, will not take so long to come to fruition and is currently targetted for Spring
+2014.
+ 
+@c ********************************************************************************
+@c Quick start guide
+@c ********************************************************************************
+@chapter QUICK START GUIDE
+@node QUICK
+
+For those of you that are new to GoldenCheetah this section gets you up and running
+with the software and using its basic features. For those of you with experience of
+GoldenCheetah from previous releases, you might like to skip this chapter.
+ 
+@section Downloading and Installing
+There are four ways to get GoldenCheetah onto your PC and available for use:
+@itemize @bullet
+
+@item @strong{Download a Stable release build} - We maintain a stable release binary for download and installation
+on the GoldenCheetah website, at @url{www.goldencheetah.org/download}.
+
+@item @strong{Download a Development build}  - We also provide regular build updated of the
+very latest code on the GoldenCheetah development build website, at @url{www.stand2surf.net}.
+
+@item @strong{Build from Source} - Since we provide the source code for the program
+you can get the source from GitHub and build your own.  But unless you plan on
+contributing to the project this is probably a pointless exercise. You
+could just use the pre-built binaries described above.
+
+@item @strong{Apt-get install} - If you are running a Linux distro you can get the GoldenCheetah
+binary and dependencies installed via apt-get. It is worth noting that at the time of writing
+the V3 build has not yet been packaged.
+
+@end itemize
+
+Once you have the binary installed you can go ahead and run it, it doesn't need any
+configuration before you start.
+ 
+@section Running for the first time
+
+When you run GoldenCheetah for the very first time it will prompt you with the Athlete 
+selection dialog box. In GoldenCheetah we allow you to create as many athletes as you
+like. This may sound like it is only useful for coaches, but in fact you may want to
+set up a scratch athlete to play and learn.
+
+Either way in this first run you will not have an athlete created, and will see a blank
+dialog, asking you to select or create an athlete to work with:
+
+@vskip 12pt
+@center @image{"image/1-noathlete",140pt}
+@center @emph{Figure 1: Initial Dialog}
+@vskip 6pt
+
+At this point you should go ahead and click `New...'. This will open another dialog
+window to create a new athlete and set some basic data. 
+
+@vskip 12pt
+@center @image{"image/1-newathlete",140pt}
+@center @emph{Figure 2: New Athlete Dialog}
+@vskip 6pt
+
+Whilst it is possible to configure these values in preferences or within an individual activity
+you should go ahead and set up as much of the data as accurately as possible. These values
+are used as defaults in many metric calculations. 
+
+If you click on the blank athlete icon on the right it is possible to set an image for the athlete
+too. This isn't used anywhere at present, but that may change in the future.
+
+The LTHR value is the HR at which the onset of blood lactate accumulates, whilst the CP value is
+the maximum theoretical watts you can hold for an hour. It is very similar to your FTP (if that
+is a term you understand).
+
+Once you're happy with the settings click save and you will then be able to select your new athlete
+in that initial dialog (except of course there is now an athlete listed). Go ahead and open that
+athlete and you wil be greeted with GoldenCheetah, but a splash page.
+
+@vskip 12pt
+@center @image{"image/1-blankstate",280pt}
+@center @emph{Figure 3: Analysis view splash screen}
+@vskip 6pt
+
+This page is shown because there is no data associated with this athlete. We need to go ahead and
+download some data from your bike computer or import some data from disk or USB.
+
+@section Downloading a ride from device
+
+If you use a Powertap, SRM, Joule, Joule GPS or Macro-X device you will be able to download from
+it directly. Please make sure the device is conected and plugged in correctly. For example, if you
+are downloading from a Powertap please make sure the computer is firmly connected and displays
+`HOST' on its screen.
+
+@vskip 12pt
+@center @image{"image/1-download",210pt}
+@center @emph{Figure 4: Download Dialog}
+@vskip 6pt
+
+To start the download go ahead and click the download from device button. This will open up the 
+download dialog. Select the right kind of device and serial port before clicking on the `Download'
+button. If no serial port is listed, or the port is not correct you can click on the `Rescan' 
+button to look again for your device. This is sometimes required if you click on `Download' before
+the device is connected.
+
+Any ride files will then be downloaded and imported into GoldenCheetah and the splash screen will
+disappear to reveal the Analysis view of GoldenCheetah. Congratulations - you can now start using
+GoldenCheetah to analyse and track your performance.
+ 
+@section Importing data from file 
+
+To import files into GoldenCheetah you have a couple of options. You can drag and drop them from 
+a file explorer or from the desktop into the main GoldenCheetah window, or you can select them via 
+the import files button on the splash screen.  Once you have done either the import activity 
+wizard will appear to process the selected files.
+
+@vskip 12pt
+@center @image{"image/1-import",280pt}
+@center @emph{Figure 5: Import Activity Wizard}
+@vskip 6pt
+
+You will notice that the files are opened first to ensure you have the required permissions to 
+read them before being validated. Once validated the dialog will prompt you to edit any of the dates 
+(some file formats do not include date information). Once you have set the dates (if needed) you can 
+click on save to complete the import and save the files to disk.
+ 
+The splash screen will now disapper and reveal the main GoldenCheetah analysis view and you can
+now start analysing and tracking your performance.
+
+@c ********************************************************************************
+@c Basic Navigation
+@c ********************************************************************************
+@chapter GETTING AROUND GOLDENCHEETAH
+@node NAVIGATION
+ 
+@vskip 12pt
+@center @image{"image/2-mainwindow",280pt}
+@center @emph{Figure 6: Main window elements}
+@vskip 6pt
+
+Regardless of whether you are training with your bike trainer, reviewing recent activities in the diary
+or tracking long term performance in the home view, the GoldenCheetah layout is always the same.
+
+Looking at the figure above you will see the following components;
+@itemize @bullet
+
+@item @strong{Menu Bar} - this contains all the menu options for GoldenCheetah. The screenshot shown is
+from the Mac OSX version, but the menu bar is similar in modern Linux distributions. On Windows the menu
+bar will be seen within the main window rather than at the top of the screen.
+
+@item @strong{Tool Bar} - the toolbar contains buttons to get quick access to functions that also available
+within the menu bar. We place them in the toolbar because they are used very commonly, and it is handy to be
+able to get at them quickly and easily.
+
+In V3 the toolbar is biased towards functions used during analysis, but this may change as we get more feedback
+from users about what they use most commonly in the other views.
+
+@item @strong{Scope Bar} - the scope bar is used to select the view. Each view offers different functionality as
+their names suggest. Additionally there is a `+' menu to the right of the scope bar for adding charts to the view
+selected.
+
+@item @strong{Side Bar} - the side bar contains selections and lists that are most appropriate for what the user
+is currently doing. It changes as different views are selected in the scope bar.
+
+@item @strong{Main View} - selected via the scope bar the main view shows the charts and windows relevant to the
+view in question. Analysis View contains analysis functions and so on. Note that the view can be shown in a tabbed
+style or a scrolling set of tiles.
+
+@end itemize
+
+The only time the main window looks different to that shown above is when running for the first time or when no
+data is available. In this case a `splash' screen is shown to assist new users in importing data or setting up
+devices etc.
+@page
+@section The Menu Bar
+
+The GoldenCheetah menu bar is no different to any other application. The only slight confusion is the location of the
+preferences pane across platform. On Windows and Linux the preferences pane can be found as Tools->Options whilst
+on a Mac it is found as GoldenCheetah->Preferences.
+
+@strong{NOTE:} Each menu is now explained in the section below, but depending upon the options installed when
+the program was built you may not see all the menu options listed. If you installed a stable build from the 
+GoldenCheetah website it will have all available options compiled in @emph{this is not the case for Development builds}.
+
+@heading The @emph{Athlete} menu
+
+The Athlete menu is largely about opening and closing new windows. Since in GoldenCheetah we open a new window to
+work with a specific athlete (you cannot switch athlete in the main window, you need to open another window). As a
+result this menu is rather trivial:
+
+@itemize @bullet
+
+@item @strong{New...} - Opens the new athlete dialog we saw in the quick start guide and then proceeds to open a
+@item @strong{Open...} - Opens the choose athlete dialog in order that you select an athlete to open in a new window.
+@item @strong{Close} - Closes the current athlete window.
+@end itemize
+
+@strong{NOTE:} When you restart GoldenCheetah it will always open the athlete you last opened, so if you open up an
+athlete and close to go back to a previous window the last Athlete that was opened will be displayed, rather than the
+last one you closed. You can specify which athlete to open on the command line e.g. @code{$ ./GoldenCheetah "Mark Liversedge"}.
+
+@heading The @emph{Activity} menu
+
+In GoldenCheetah we refer to a ride file or any file that contains data related to an exercise you have completed as an `Activity'
+this is because simply referring to it as a `ride' wouldn't be valid if, for example, it was a run!
+
+Additionally, a prescribed activity plan (e.g. 2x20 mins at L4) we refer to as a `workout'. This may be confusing to users
+that come to us from TrainingPeaks WKO+ where a workout refers to a past activity. We refer to future activities as planned
+activities and past activities as just activities. 
+
+So, this menu contains functions for working with activities -- past exercises that have been recorded and imported into GoldenCheetah.
+
+@itemize @bullet
+@item @strong{Download from device...} - Also available from the tool bar this function opens the dialog to download data 
+directly from a device. We support SRM Powercontrol, Powertap LYC, Joule and Macro-X devices.
+@item @strong{Import from file...} - This option will open a file selecton box to select one @emph{or more} files to import. Once 
+selected the files will be processed by the import wizard.  You can also import files by just dragging and dropping them 
+on the analysis view.
+
+@strong{NOTE:} If you try and drag and drop on the training view we will try and import videos and workouts (not activities).
+@item @strong{Manual activity entry...} - This will open up a dialog box to create a manual entry. There is also a button on
+the toolbar that does this. A manual activity gives you the opportunity to estimate time, distance, stress and other metrics
+for an activity that wasn't record (for example on a gym bike). @xref{Importing Exporting Downloading and Creating Data, Manual activity}.
+@item @strong{Export...} - Will open a dialog box to export the currently selected activity. You can select the directory
+to export to and the file format to write the export as. This is particularly useful if you want to send your data to a 
+coach who requires data in a format his software understands.
+
+For example; PWX files can be read by WKO+ and Garmin TCX files can be read by almost all sports software. 
+
+@strong{NOTE:} Whilst we offer FITLOG format for SportsTracks we would not recommend it, since the fidelity of the 
+file format is very suspect. 
+@item @strong{Batch export...} - This opens the batch export dialog, it provides the ability to select the output
+directory and format to export to as well as select the activities you wish to export. Since this functions is
+typically used to export data for import into another program there is a select all option too.
+@item @strong{Export Metrics as CSV...} - Although the metric database is a sqlite file it can be useful to export
+all the metrics as a comma separated variable format to work with in a spreadsheet. This function will export all
+columns and rows to a CSV file of your choice.
+@item @strong{Upload to TrainingPeaks} - This will upload the currently selected ride to TrainingPeaks.com. There are
+no options since the account and password need to be defined in the preferences pane before you start.
+@item @strong{Download from TrainingPeaks...} - This will open the download dialog for TrainingPeaks.com. It allows
+you to select the specific activities you want to download and will match the available activities to any existing
+activities by examining their date and time.
+@item @strong{Upload to Strava...} - This opens the upload to strava dialog to allow you to select which data
+series you want included.
+@item @strong{Download from Strava...} - Download from Strava requires a Strava activity ID. Once you provide this
+the activity will be downloaded and imported into your activity library. Note that there is no option to select
+activities from a list since Strava do not support this (data lock-in).
+@item @strong{Upload to RideWithGPS...} - This will upload the currently selected ride to RideWithGPS.com. There
+are no options required.
+@item @strong{Upload to Trainingstagebuch...} - This will upload the currently selected ride to TrainingStageBuch.com.
+The user id and password need to be configured in the preferences pane in order for this to work.
+@item @strong{Save activity} - We do not automatically save changes to activities, if you want to update the
+activity you must save it. The metrics for the activity will only be updated when it is saved.
+@item @strong{Delete activity...} - Permanently deletes the ride from the ride library. There is no undo so use
+with caution. It will prompt to confirm you really mean it.
+@item @strong{Split activity...} - Will open the split activity wizard, this wizard will allow you to find
+breaks in an activity and split it into separate activities. This is of particular use when you forget to
+stop recording and end up with multiple activites downloaded as a single activity.
+@end itemize
+
+@heading The @emph{Tools} menu
+
+The Tools menu contains a selection of `handy' utilities, its a bit of a catch all for functions that are
+either related to manipulating activities or don't really fit in anywhere else.
+
+@itemize @bullet
+@item @strong{Options...} - Only on Linux and Windows this opens the preferences pane. Note that the preferences
+pane is an application in its own right and will remain open even when you have closed the main windows. You can
+also have multiple preferences panes open at once @strong{we recommend you do not do this}.
+@item @strong{Critical Power Estimator...} - Opens a dialog to estimate your CP based upon a short and long
+power best or result from a specific test. We recommend using 3 minutes and 20 minutes since that aligns
+with the algorithm used (Monod/Scherer).
+@item @strong{Air Density (Rho) Estimator...} - Opens a tool for estimating Air Density based upon temperature
+and air pressure. This is useful when working with Aerolab.
+@item @strong{Get Withings Data...} - Downloads all measures for you Withings weight scale, but the user id
+and public key need to be configured in the passwords section of the preferences pane.
+@item @strong{Get Zeo Data...} - Downloads sleep data for your Zeo sleep monitor. You will need to have
+configured the user id and pasword in the preferences pane.
+@item @strong{Create a new workout...} - Opens the workout wizard for creating a training view workout. This
+will create a `.erg' or `.crs' workout.
+@item @strong{Download workouts from ErgDB...} - Opens a dialog to select and download training view workouts
+from the internet ErgDB website.
+@item @strong{Import workouts or videos...} - Opens a file dialog to select and import a workout or video into
+the training view library.
+@item @strong{Scan disk for videos and workouts...} - Opens a dialog to scan directoris for workouts and
+videos and import into the training view library.
+@item @strong{Upload Activity to Calendar} - Will create a calendar entry to any CalDAV based calendar service.
+You will need to configure the URL, user and password in the preferences pane before using this.
+@item @strong{Refresh Calendar} - Will read any entries from your CalDAV internet calendar to display on the 
+calendar view.
+@item @strong{Find intervals...} - Opens a dialog to find intervals in the current activity. This menu option
+is here since it has always been on the tools menu. It should really be moved to the @emph{Activity} menu.
+@item @strong{Adjust Torque Values...} - An editor tool for adjusting the torque data series. This is useful
+when using a Powertap without calibrating.
+@item @strong{Fix GPS Errors...} - An editor tool for extrapolating and adjusting GPS values, this is useful
+when your GPS device lost its satellite connection or after importing from other software and the data
+contains invalide values.
+@item @strong{Fix Gaps In Recording...} - GoldenCheetah expects all data series samples to have timestamps
+separated by a consistent recording interval (e.g. every 1 second). This tool dialog allows you to
+extrapolate values where there are gaps in recording. In future releases we may remove the need for the 
+data series to have regular timestamps.
+@item @strong{Fix HR Spikes...} - Find and smooth out spikes in HR, usually caused by loss of conection or
+iterference from overhead power lines.
+@item @strong{Fix Power Spikes...} - Find and smooth out spikes in Power, usually caused by reed switch
+being double triggered or recording interference.
+@end itemize
+
+@heading The @emph{View} menu
+
+The View menu provides a menu access to the view configuration, showing and hiding UI elements as well as
+switching fullscreen and adding charts to the layout.
+
+@itemize @bullet
+@item @strong{Toggle Full Screen} - As the name suggests toggles between normal and full screen. On
+Linux and Mac this is also available from the F11 key (and you can use the ESC key to leave full
+screen mode too). On Mac Lion we use the standard toolbar button for switching between normal and
+full screen mode.
+@item @strong{Show Left Sidebar} - Toggles the display of the sidebar.The button on the toolbar also
+does the same. You can also drag and close the sidebar by hand.
+@item @strong{Show Toolbar} -  Toggles showing or hiding the tool bar.
+@item @strong{Tabbed View} - Toggles tabbed or tiled mode for the current view.
+@item @strong{Analysis} - Switch to the Analysis view.
+@item @strong{Home} - Switch to the Home view.
+@item @strong{Train} - Switch to the Training view.
+@item @strong{Diary} - Switch to the Diary view.
+@item @strong{Add Chart} - Opens a submenu to select a chart to add. When selected an add chart dialog
+will be open showing the chart and allowing you to adjust the chart settings before it is added to the
+current view.
+@item @strong{Reset Layout} - Will reset the current view layout to the application default. This is
+useful if you spoil your setup, or want to fall back to the current application default. Note that the
+application default will change and improve over time.
+@end itemize
+
+@heading The @emph{Window} menu
+
+Simply lists the current windows you have open and allows you to select the window to raise and make 
+the current window focus.
+@page
+@section The Toolbar and Scope bar
+
+@vskip 12pt
+@center @image{"image/2-toolbar",350pt}
+@center @emph{Figure 7: Tool Bar and Scope Bar}
+@vskip 6pt
+
+Working from left to right in the toolbar, there are a number of buttons to download and import
+activities that are mostly relevant to the analysis view;
+and lastly a search box;
+@itemize @bullet
+@item @strong{Download Activity} - Will open a dialog to download an activity from a supported
+device (including Powertap Cervo, SRM Powercontrol, O-Synce Macro, Saris Joule).
+@item @strong{Compose Manual Activity} - Will open a dialog to manually enter an activity, for
+example when you worked out at a gym and could not record the data.
+@item @strong{Find Intervals} - Will open a dialog to find peak and best intervals in an activity.
+@item @strong{Split Activity} - Will open a dialog to split an activity into separate activities.
+This is useful when you have an activity that spans mutiple days.
+@item @strong{Delete Activity} - Deletes the currently selected activity. Will prompt the user to
+confirm before doing so.
+@end itemize
+
+Then to the right of the toolbar there are a trio of buttons to control the way the 
+main window is laid out;
+@itemize @bullet
+@item @strong{Show/Hide Sidebar} - Will toggle the visibility of the sidebar, if it is hidden it
+will how it. If it is shown it will hide it.
+@item @strong{Tabbed Mode} - Switch the main view into tabbed mode. See Views and the Sidebar below.
+@item @strong{Tiled Mode} - Switch the main view into tiled mode. See Views and the Siidebat below.
+@end itemize
+
+Lastly to the right of the toolbar there is a search/filter box;
+@itemize @bullet
+@item @strong{Mac OSX only Search box} - On a Mac the search box is limited to text search only, this
+may change as it means one cannot use it to filter the activity list with a data filter.
+@item @strong{Windows/Linux Search/Filter box} - On Windows and Linux the search box can be toggled
+between a search box and filter box by clicking on the search or filter icon inside the box (and to
+the left hand side). See searching and filtering below for more details.
+@end itemize
+
+Beneath the toolbar is the scope bar, this is a selector to choose from one
+of four views in main view -- essentially its a selector for choosing what
+you want to do with GoldenCheetah, it offers four views;
+
+@itemize @bullet
+@item @strong{Home} - The home view is for long term tracking and allows you to work with charts that 
+plot and analyse metrics. It is intended to be used to reviewing progress and identify what is and is
+not working (or perhaps historically, what has worked and what hasn't).
+
+In this view the scope is @emph{generally} limited to the date range or season selected in the associated
+sidebar -- the currently selected ride is not relevant in this view.
+
+@item @strong{Diary} - The diary view is for tracking recent rides - looking at the data in terms of the 
+last day, week or month. As planning functions arrive in v3.1 this view will become more funcitonally
+rich, but for now it is more or less a configurable version of the old @emph{Weekly Chart}.
+
+In this view the scope is limited to the day, week or month of the currently selected activity. As you
+select different activities the date range changes to reflect this.
+
+To select the summarisation level (day, week or month) the summary sidebar contains a drop down selector.
+See Figure 8 below.
+
+@vskip 12pt
+@center @image{"image/2-dayweekmonth",70pt}
+@center @emph{Figure 8: Summary level selector}
+@vskip 6pt
+
+@item @strong{Analysis} - The analysis view is where you review and analyse individual activities. 
+As well as using the numerous analysis charts you can also edit and adjust the telemetry data within
+the activities and add your own narratives and texts.  The narrative fields are configurable to 
+your tastes, see `Metadata' in chapter 4.
+
+In this view the scope is limited to the currently selected activity in the sidebar.
+@end itemize
+
+To the right of the scope bar is a `+' menu button;
+@itemize @bullet
+@item @strong{Add Chart (`+') Menu} - The charts on each view can be configured and added or deleted.
+The `+' menu to the right of the scope bar lists all the charts that are available for the currently
+selected view, see Figure 9 below. Selecting a chart from this menu will open the add chart dialog, which is described 
+below in the secion @emph{Adding and adjusting charts}.
+
+@vskip 12pt
+@center @image{"image/2-chartmenu",180pt}
+@center @emph{Figure 9: The `+' Add Chart Menu}
+@vskip 6pt
+@strong{NOTE:} Only the windows that are relevant for the current view will be listed. You cannot, for example, add a long term
+metric chart to the analysis view, or a performance chart (all plot) to the diary view.
+@end itemize
+ 
+@section Views & Sidebar
+@vskip 12pt
+@noindent @image{"image/2-sideactivity",70pt}
+@noindent @image{"image/2-sideinterval",70pt}
+@noindent @image{"image/2-sidediary",70pt}
+@noindent @image{"image/2-sidehome",70pt}
+@noindent @image{"image/2-sidesummary",70pt}
+@noindent @image{"image/2-sidetrain",70pt}
+@center @emph{Figure 10: Sidebars}
+@vskip 6pt
+scopebar, sidebar, tab/tiled, add chart menu
+ 
+@section Searching and Filtering
+free text search and basics of data filtering
+ 
+@section Adding and adjusting charts
+the dialog, title, settings, finding them again
+ 
+@section Going fullscreen
+key sequences, hiding and showing the toolbar
+screensaver?
+ 
+@section The Metric database
+why, what, where, refreshing, exporting
+ 
+ 
+@c ********************************************************************************
+@c Working with Data
+@c ********************************************************************************
+ 
+@chapter IMPORTING EXPORTING DOWNLOADING AND CREATING DATA
+@node Importing Exporting Downloading and Creating Data
+ 
+@section Download from device
+download dialog, basics for each device (plugging in etc)
+ 
+@section Import from file
+selecting a file, the import wizard
+ 
+@section Manual activity
+the manual activity dialog and refer to details screen for more "indepth" (need a better word) stuff
+ 
+@section Exporting data
+   i A single ride
+  ii Multiple rides
+ 
+@section Uploading and Downloading from the Cloud
+   i TrainingPeaks
+  ii Strava
+ iii TrainingStage Buch
+  iv RideWithGPS
+ 
+ 
+@c ********************************************************************************
+@c ANALYSIS
+@c ********************************************************************************
+ 
+@chapter THE ANALYSIS VIEW
+@node ANALYSIS
+ 
+@section About Activities and Intervals
+ 
+@section Sidebar actions and context menus
+      o activities
+      o intervals
+ 
+@section Editing and adjusting data
+     o using the editor
+       i basics
+      ii anomalies
+     iii find
+     o advanced editor functions
+       i the `fix' tools
+      ii copying, cutting and pasting
+ 
+@c ********************************************************************************
+@c ANALYSIS CHARTS
+@c ********************************************************************************
+@chapter ANALYSIS VIEW CHARTS
+@node ANALYSIS CHARTS
+       i Activity Summary
+      ii Details
+     iii Summary and Details
+      iv Editor
+       v Performance
+      vi Critical Mean Maximals
+     vii Histogram
+    viii Pedal Force vs Velocity
+      ix Heartrate vs Power
+       x Google Map
+      xi Bing Map
+     xii 2d Plot
+    xiii 3d Plot
+     xiv Aerolab Chung Analysis
+ 
+@c ********************************************************************************
+@c HOME
+@c ********************************************************************************
+@chapter THE HOME VIEW
+@node HOME
+ 
+@section About Date Ranges, Seasons and Events
+ 
+@c ********************************************************************************
+@c HOME CHARTS
+@c ********************************************************************************
+@chapter PERFORMANCE TRACKING CHARTS
+@node HOME CHARTS
+       i Long Term Metrics
+         - indepth howto incl. setting up a PMC++
+      ii Performance Manager
+     iii Collection TreeMap
+      iv Critical Mean Maximal
+       v Distribution
+ 
+@c ********************************************************************************
+@c DIARY
+@c ********************************************************************************
+@chapter THE DIARY VIEW
+@node DIARY
+ 
+@section Purpose
+ 
+@section Summarising for Day / Week / Month
+ 
+@section Longer term purpose (planning)
+ 
+@c ********************************************************************************
+@c TRAIN
+@c ********************************************************************************
+@chapter THE TRAIN VIEW
+@node TRAIN
+ 
+@section About Devices, Workouts and Video
+ 
+@section Sidebar actions and context menus
+      o devices
+      o workouts
+      o media
+ 
+@section Working with the Workout Library
+   - Creating a new Workout
+   - Getting Workouts from ErgDB
+  
+@section Setting up and starting a workout
+    - Using CT handlebar controller
+    - controlling workout from mouse + keyboard
+ 
+@c ********************************************************************************
+@c TRAIN CHARTS
+@c ********************************************************************************
+@chapter TRAINING VIEW CHARTS
+@node TRAIN CHARTS
+        i Telemetry
+       ii Workout
+      iii Realtime
+       iv Pedal Stroke
+        v Map
+       vi StreetView
+      vii Video Player
+ 
+ 
+@c ********************************************************************************
+@c Configuration
+@c ********************************************************************************
+@chapter CONFIGURING
+@node CONFIG
+ 
+Intro and explain opening the Preferences Pane
+ 
+@section General
+ 
+@section Athlete
+     i About
+    ii Power Zones
+   iii HR Zones
+ 
+@section Passwords
+    i General
+   ii Withings
+  iii Zeo
+   iv Google Calendar (calDAV)
+ 
+@section Appearance
+ 
+@section Data Fields
+   i Fields
+  ii Notes Keywords
+ iii Processing
+ 
+@section Metrics
+  
+@section Train Devices
+   i Using Multiple Devices
+  ii Adding a device
+ 
+@c ********************************************************************************
+@c Appendices
+@c ********************************************************************************
+@unnumbered A - Supported Devices, Formats & Services
+@unnumbered B - Metrics Reference
+@unnumbered B - Data Filtering Reference
+@unnumbered C - Glossary & Resources
+@unnumbered D - OS Specifics (Directories, Drivers and Permissions)
+ 
+@unnumbered Index
+@printindex cp
+ 
+@bye

doc/user/GC3-Release.info

@@ -0,0 +1,323 @@
+This is GC3-Release.info, produced by makeinfo version 4.13 from GC3-Release.texinfo.
+
+
+File: GC3-Release.info,  Node: Top,  Next: Top,  Prev: Top
+
+title
+*****
+
+These release notes are for GoldenCheetah, version 3.0.
+
+* Menu:
+
+* WHATS NEW::  What's new in V3.0
+* CONTRIBUTORS::  List of Contributors to V3.0
+
+
+File: GC3-Release.info,  Node: WHATS NEW,  Next: CONTRIBUTORS,  Prev: CONTRIBUTORS,  Up: Top
+
+1 Whats New
+***********
+
+1.1 500+ bug fixes and minor enhancements
+=========================================
+
+Over the last 3 years the performance and stability of GoldenCheetah
+has been improved considerably. One of the major criticisms of the
+software was it crashing.
+
+We have fixed 46 serious issues and over 400 bugs in over 1,500
+different commits. GoldenCheetah is now over 120,000 lines of code
+compared to 61,000 of the previous v2.1 release. It is used by 1000s of
+users around the world, from Santiago to Singapore and Auckland to
+Aberdeen.
+
+In addition to addressing stability issues we have also looked closely
+at performance. Whilst the new metric functionality and database means
+that a modern PC is recommended, the code is still efficient enough to
+run on a netbook.
+
+We have introduced pre-computed metrics alongside a cache of ride bests
+across all the main data series to ensure that analysis of long term
+data is as quick and responsive as possible. We also introduced our own
+file format using JSON as an open file format, with a custom parser. We
+can now read a 1hr ride 20x faster using our native format than using
+an equivalent and very popular XML format.
+
+In short, we've squashed the big bugs and made it run much faster.
+
+1.2 Redesigned UI and UX
+========================
+
+One of the most immediate changes you will notice with v3.0 are the
+major changes to the user experience and user interface. From the
+initial help screens for new users through to the redesigned preferences
+pane for advanced users, it provides a  more complete user experience
+with a slicker and more professional user interface.
+
+We wanted an elegant and clean user interface that was intuitive to use
+and revealed complexity when it was required. We think we've come
+pretty close.
+
+There are 4 views available with specific and detailed sidebars for
+peformancee tracking (home), short term tracking (diary) as well as the
+well known analysis and training views from earlier releases.
+
+We now allow you to view charts tabbed and tiled, you can resize and
+move charts around and customise them using roll-over controls. The
+activity list is fully configurable and can be configured to show any
+number of columns. We have overhauled and introduced friendly wizards
+for adding devices and athletes through to manual activity entry.
+
+The UI is largely native on a Mac and the same UI and UX has been
+replicated on Linux and Windows. We also support full screen including
+Lion fullscreen support on a Mac.
+
+We have been through many, many iterations to get to this UX and it has
+been widely tested and critiqued by a large community of GC users.
+
+We think this is the best looking and most intuitive version of
+GoldenCheetah ever released.
+
+1.3 Support for the latest bike computers
+=========================================
+
+We have added direct download support for the Cyclops Joule and Joule
+GPS as well as the latest SRM Powercontrol 6 and 7. We also added
+support for the O-sync Macro and Macro X.
+
+In addition to this we also fixed a few issues related to importing from
+newer Garmin devices since the file format changed.
+
+1.4 Support for more telemetry
+==============================
+
+Alongside the support for the latest bike computers we also added the
+ability to track and plot new data series, including; Headwind, LR
+Balance, Temperature and Slope.
+
+1.5 Export and Batch Export as well as lots of new file formats
+===============================================================
+
+We will now export and batch export your data to a wide variety of file
+formats. We believe it is your data and it should not be locked into any
+sotfware. We support open formats such as TCX, PWX, JSON and XML as well
+as FITLOG and GPX.
+
+We have also added support for reading files from SportTracks, GPX, Tacx
+CAF and the SLF/SMF file formats. We have also added legacy WKO+ file
+format support (CP 1.0 and 1.1) as well as import of Wattbike TXT
+exports.
+
+1.6 Support for a wide selection of Cloud services
+==================================================
+
+We can now upload and download data from cloud services offered by;
+Withings, Zeo, Strava, TrainingPeaks, Training Stage Buch, RideWithGPS
+as well as Internet based calendars (calDAV) such as Google Calendar.
+
+1.7 Improvements to Aerolab
+===========================
+
+There is now an autosolver for CdA and Crr Estimation in Aerolab that
+removes a lot of the guesswork from curve fitting in Virtual Elevation
+as well as a handy Air Density (Rho) estimator.
+
+1.8 Realtime training significantly enhanced
+============================================
+
+We now support Native ANT+ removing the need for quarqd. Video Playback
+is built in using VLC/QTKit. We manage a media library to make sure you
+can re-use any content you may have from Tacx Ergvideos through
+Sufferfest.
+
+We support Virtual Power for popular devices from KK, LeMond and many
+other trainers.  We have added support for the amazing new Wahoo
+Fitness Kickr trainer as well as the old Tacx Fortius.
+
+In the train view we have added lots of new ways to ride on the trainer
+including; Streetview, SpinScan (on Computrainer) and an enhanced
+Workout Plot that plots telemetry against the workout as you ride.
+
+Finally we've added Computrainer calibration, a workout wizard and
+download from ErgDB as well as Multi-device Support allowing you to
+ride with with your ANT+ powermeter on your Computrainer, Kickr or
+Fortius.
+
+1.9 Advanced search and data filtering
+======================================
+
+We now offer the ability to use free text search across all activities,
+enabling lightning quick searches for past activities.  We use a well
+proven and fast search and indexing tool called CLucene to provide
+search as you type functionality.
+
+Additionally we have introduced a data filter (using the same search
+box) to allow you to filter activities for specific properties, for
+example for all rides with a TSS > 300 or perhaps those with an IF >0.9
+and a duration of > 1hr.
+
+Both the search and filter functions can be applied to the charts -
+which means that you can plot a PMC only where sport is "Bike" or
+perhaps power distribution but only where the workout code is FTPTEST.
+
+We are still discovering how powerful these tools are when applied to
+long term performance tracking.
+
+1.10 Lots of new charts
+=======================
+
+It wouldn't be a new release of GoldenCheeth if we didn't introduce
+some new charts for detailed forensic data analysis.
+
+We've added a new HR to Power analysis as well as a more utilitarian 2d
+scatter plot. We've added Bing as map provider for the Map chart.
+
+But the single most asked for feature, and one that has been on the GC
+wish list since it was first released is the ability to plot a
+distribution for a date range.  We can now do that - allowing you to
+plot power distribution for a season or month or any number of
+sophisticated date ranges (we also added lots of advance ways to
+express date ranges).
+
+In addition to plotting distribution charts for ride data you can also
+now plot distribution charts for activity metrics. So, for example, you
+can plot a distribution of ride intensity factors to see intensity mix
+for a season or date range. Additionally, you can choose to plot that
+as say ride time, i.e. how much time have I spent over the last season
+at different intensities. Or perhaps you would like to plot TSS that has
+been accumulated over the season by intensity of ride. You can do that
+in version 3.
+
+Lastly, we have also extended the CP curve to plot more than just
+power. It will now plot a mean max curve for HR, Power, Speed, Cadence,
+xPower, NP et al. And we even added VAM too, for you mountain goats.
+
+1.11 New metrics, including TrainingPeaks' TSS and NP
+=====================================================
+
+Yes, we've been granted permission by our friends at TrainingPeaks to
+use their cylcing metrics in the latest version of GoldenCheetah. We
+know that it is one of the most popular additions.
+
+Not only have we added them as metrics to plot and track, we've also
+added them to the realtime training so you can target an intensity of
+stress for a workout and monitor and adjust the intensity of the
+workout as you ride.
+
+We have also added a whole host of new metrics, there are now over 100
+different metrics and measures you can work with including things like;
+Pace, Maximums, Gradient, VAM, wpk, time in HR Zones and many, many
+more.
+
+1.12 Build and Platform support
+===============================
+
+For the technical amongst you we have removed mandatory Boost
+Dependency, which means you can build GC with nothing more than QT4.8
+installed (we will support QT5 in v3.1).  We now support OpenBSD and
+have moved to using version 6.1 of the QWT library.
+
+On a related note, you can see all the versions used, contributors
+involved and build settigs as we have improved the about box to give
+much more useful information to developers.
+
+1.13 We wrote some documentation!
+=================================
+
+Shock. We now have an FAQ covering over 50 of the most commonly asked
+questions about GoldenCheetah. And a full user manual to compliment the
+existing wiki for user generated content.
+
+One of the other criticisms we often heard about GoldenCheetah was how
+hard it was to use, and how you needed to be a cycling nerd to
+understand it. We feel that the new UI and User Experience coupled with
+much better documentation and help mean this should make this version
+of GoldenCheetah the easiest to use yet.
+
+
+File: GC3-Release.info,  Node: CONTRIBUTORS,  Next: WHATS NEW,  Prev: WHATS NEW,  Up: Top
+
+2 Contributors
+**************
+
+2.1 Credits and Contributors
+============================
+
+Literally thousands of people regularly download, install, develop,
+critique and discuss GoldenCheetah and its features and functions.
+
+Back in 2006 a stupendously gifted guy (and Cat 1 racer) called Sean
+Rhea bought a Powertap. Frustrated with the software that was available
+he set about writing some utilities to plot the data. But first he had
+to reverse engineer the protocol to talk to it.  Back then, and to a
+lesser degree now, these sports and cycling products are closed. You buy
+their product and you're stuck with their software. Sean did something
+amazing - he open sourced his code. By doing that he changed power
+analysis completely.
+
+Here in 2013 with ANT+, BTLE, Wahoo, TrainerRoad, PerfPro and of course
+GoldenCheetah things look very different. The cycling world has gone
+open. Sean can take some of the credit for that.
+
+We stand on his shoulders.
+
+Here in 2013 by far and away the biggest contributors to this project
+are Damien Grauser and Mark Liversedge.  Between the two of them they
+have committed almost 90% of all code to GoldenCheetah in the last 3
+years. Often working on stuff for others they are the reason this
+release is written for you the cyclist .. and not us the developers.
+
+Of equal importance is Gareth Coco our devops guru. With unfathomable
+patience he has built countless release candidates and development
+builds for the last 3 years. He has worked with an ever changing and
+hideous array of wacky dependencies across Windows, Mac and Linux. He
+is pretty much the only reason you can download and install our
+software. Big, big thanks to Gareth.
+
+Thats not to say that there aren't many other significant contributions
+too; Ale Martinez has masterminded and developed multi-language support
+in V3. Translations have been undertaken by Ale himself, but also by
+Til Schmiedeberg, Keisuke Yamaguchi, Marco Piccirilli, Sergei
+Chekhovskii and Rafael Oliveira Ribeiro. And a huge thanks to Satoru
+Kurashiki who has worked tirelessly to get a Debian (and hence Ubuntu)
+package created for GoldenCheetah since v2.1.
+
+A large number of developers have contributed small and large bits of
+code, and many clever coaches and athletes have donated their ideas and
+best practices. I must shout out to Dr Andrea Morelli the professional
+coach, for his encouragement and insight over the last 3 years and Greg
+Steele for some of the most interesting and inspriring thoughts.
+
+Here are all the contributors, all of them have made this version of
+GoldenCheetah the best yet;
+
+Alejandro Martinez, Andrew Bryson, Andy Froncioni, Austin Roach, Berend
+De Schouwer, Bruno Assis, Chris Cleeland, Claus Assmann, Dag Gruneau,
+Damien Grauser, Darren Hague, Dean Junk, Eric Brandt, Eric Murray,
+Frank Zschockelt, Gareth Coco, Greg Lonnon, Ilja Booij, Jaime Jofre,
+Jamie Kimberley, Jim Ley, John Ehrlinger, Josef Gebel, Julian
+Baumgartner, Julian Simioni, Justin Knotzke, Keisuke Yamaguchi, Ken
+Sallot, Luke NRG, Magnus Gille, Marc Boudreau, Mark Liversedge, Mark
+Rages, Mitsukuni Sato, Ned Harding, Patrick McNerthney, Rainer Clasen,
+Robb Romans, Robert Carlsen, Roberto Massa, Ron Alford, Sean Rhea,
+Steven Gribble, Thomas Weichmann, Walter Burki.
+
+Finally a big shout out to three amazing people; Jamie Kimberley who
+has been the glue that held the GoldenCheetah community together,
+Robert Carlsen who has always been the cool guy in the glasses that
+does the cool stuff. And last but not least, my friend Justin Knotzke
+who demands and gets the best from all of us.
+
+Jamie, Robert and Justin have stepped away from regular involvement in
+GoldenCheetah, but their contributions have set the standard and will
+not be forgotten. Cheers Guys.
+
+
+
+Tag Table:
+Node: Top0
+Node: WHATS NEW310
+Node: CONTRIBUTORS9906
+
+End Tag Table

doc/user/GC3-Release.texinfo

@@ -0,0 +1,287 @@
+\input texinfo   @c -*-texinfo-*-
+@ifnotinfo
+@input palatino
+@end ifnotinfo
+@c %**start of header
+@setfilename Release Notes.texinfo
+@settitle Golden Cheetah v3.0 Release Notes
+@c %**end of header
+@paragraphindent 0
+
+@titlepage
+@title Golden Cheetah v3.0 Release Notes
+@c @subtitle subtitle-if-any
+@c @subtitle second-subtitle
+@author Mark Liversedge
+
+@end titlepage
+
+@c So the toc is printed at the start.
+@contents
+
+@ifnottex
+@node Top,Top,Top,
+@top title
+
+These release notes are for GoldenCheetah, version 3.0.
+@end ifnottex
+
+@menu
+* WHATS NEW::  What's new in V3.0
+* CONTRIBUTORS::  List of Contributors to V3.0
+@end menu
+
+@node WHATS NEW,CONTRIBUTORS,CONTRIBUTORS,Top
+@chapter Whats New
+
+@section 500+ bug fixes and minor enhancements
+
+Over the last 3 years the performance and stability of GoldenCheetah
+has been improved considerably. One of the major criticisms of the 
+software was it crashing.
+
+We have fixed 46 serious issues and over 400 bugs in over 1,500 different
+commits. GoldenCheetah is now over 120,000 lines of code compared to 
+61,000 of the previous v2.1 release. It is used by 1000s of users around 
+the world, from Santiago to Singapore and Auckland to Aberdeen.
+
+In addition to addressing stability issues we have also looked closely at
+performance. Whilst the new metric functionality and database means that
+a modern PC is recommended, the code is still efficient enough to run on
+a netbook.
+
+We have introduced pre-computed metrics alongside a cache of ride bests across
+all the main data series to ensure that analysis of long term data is
+as quick and responsive as possible. We also introduced our own file format
+using JSON as an open file format, with a custom parser. We can now read
+a 1hr ride 20x faster using our native format than using an equivalent
+and very popular XML format.
+
+In short, we've squashed the big bugs and made it run much faster.
+
+@section Redesigned UI and UX
+
+One of the most immediate changes you will notice with v3.0 are the 
+major changes to the user experience and user interface. From the
+initial help screens for new users through to the redesigned preferences
+pane for advanced users, it provides a  more complete user experience
+with a slicker and more professional user interface.
+
+We wanted an elegant and clean user interface that was intuitive to
+use and revealed complexity when it was required. We think we've
+come pretty close.
+
+There are 4 views available with specific and detailed sidebars for
+peformancee tracking (home), short term tracking (diary) as well as
+the well known analysis and training views from earlier releases.
+
+We now allow you to view charts tabbed and tiled, you can resize and
+move charts around and customise them using roll-over controls. The
+activity list is fully configurable and can be configured to show any
+number of columns. We have overhauled and introduced friendly wizards
+for adding devices and athletes through to manual activity entry.
+
+The UI is largely native on a Mac and the same UI and UX has been
+replicated on Linux and Windows. We also support full screen including
+Lion fullscreen support on a Mac.
+
+We have been through many, many iterations to get to this UX and it has
+been widely tested and critiqued by a large community of GC users.
+
+We think this is the best looking and most intuitive version of GoldenCheetah
+ever released.
+
+@section Support for the latest bike computers
+
+We have added direct download support for the Cyclops Joule and Joule GPS
+as well as the latest SRM Powercontrol 6 and 7. We also added support for
+the O-sync Macro and Macro X.
+
+In addition to this we also fixed a few issues related to importing from
+newer Garmin devices since the file format changed.
+
+@section Support for more telemetry
+
+Alongside the support for the latest bike computers we also added the ability to
+track and plot new data series, including; Headwind, LR Balance, Temperature and
+Slope.
+
+@section Export and Batch Export as well as lots of new file formats
+
+We will now export and batch export your data to a wide variety of file 
+formats. We believe it is your data and it should not be locked into any
+sotfware. We support open formats such as TCX, PWX, JSON and XML as well
+as FITLOG and GPX.
+
+We have also added support for reading files from SportTracks, GPX, Tacx
+CAF and the SLF/SMF file formats. We have also added legacy WKO+ file 
+format support (CP 1.0 and 1.1) as well as import of Wattbike TXT exports.
+
+@section Support for a wide selection of Cloud services
+
+We can now upload and download data from cloud services offered by; Withings,
+Zeo, Strava, TrainingPeaks, Training Stage Buch, RideWithGPS as well
+as Internet based calendars (calDAV) such as Google Calendar.
+
+@section Improvements to Aerolab
+
+There is now an autosolver for CdA and Crr Estimation in Aerolab that
+removes a lot of the guesswork from curve fitting in Virtual Elevation
+as well as a handy Air Density (Rho) estimator.
+
+@section Realtime training significantly enhanced
+
+We now support Native ANT+ removing the need for quarqd. Video Playback
+is built in using VLC/QTKit. We manage a media library to make sure you
+can re-use any content you may have from Tacx Ergvideos through Sufferfest.
+
+We support Virtual Power for popular devices from KK, LeMond and many other
+trainers.  We have added support for the amazing new Wahoo Fitness Kickr trainer
+as well as the old Tacx Fortius.
+
+In the train view we have added lots of new ways to ride on the trainer including;
+Streetview, SpinScan (on Computrainer) and an enhanced Workout Plot that plots
+telemetry against the workout as you ride.
+
+Finally we've added Computrainer calibration, a workout wizard and download 
+from ErgDB as well as Multi-device Support allowing you to ride with with
+your ANT+ powermeter on your Computrainer, Kickr or Fortius.
+
+@section Advanced search and data filtering
+
+We now offer the ability to use free text search across all activities, enabling
+lightning quick searches for past activities.  We use a well proven and fast
+search and indexing tool called CLucene to provide search as you type functionality.
+
+Additionally we have introduced a data filter (using the same search box) to allow
+you to filter activities for specific properties, for example for all rides with a
+TSS > 300 or perhaps those with an IF >0.9 and a duration of > 1hr.
+
+Both the search and filter functions can be applied to the charts -- which means that
+you can plot a PMC only where sport is "Bike" or perhaps power distribution but only
+where the workout code is FTPTEST.
+
+We are still discovering how powerful these tools are when applied to long term
+performance tracking.
+
+@section Lots of new charts
+
+It wouldn't be a new release of GoldenCheeth if we didn't introduce some new 
+charts for detailed forensic data analysis.
+
+We've added a new HR to Power analysis as well as a more utilitarian 2d scatter
+plot. We've added Bing as map provider for the Map chart.
+
+But the single most asked for feature, and one that has been on the GC wish list
+since it was first released is the ability to plot a distribution for a date range.
+We can now do that -- allowing you to plot power distribution for a season or month
+or any number of sophisticated date ranges (we also added lots of advance ways to
+express date ranges).
+
+In addition to plotting distribution charts for ride data you can also now plot
+distribution charts for activity metrics. So, for example, you can plot a distribution
+of ride intensity factors to see intensity mix for a season or date range. Additionally,
+you can choose to plot that as say ride time, i.e. how much time have I spent over the
+last season at different intensities. Or perhaps you would like to plot TSS that has
+been accumulated over the season by intensity of ride. You can do that in version 3.
+
+Lastly, we have also extended the CP curve to plot more than just power. It will
+now plot a mean max curve for HR, Power, Speed, Cadence, xPower, NP et al. And we
+even added VAM too, for you mountain goats.
+
+@section New metrics, including TrainingPeaks' TSS and NP
+
+Yes, we've been granted permission by our friends at TrainingPeaks to use their
+cylcing metrics in the latest version of GoldenCheetah. We know that it is one of
+the most popular additions.
+
+Not only have we added them as metrics to plot and track, we've also added them to
+the realtime training so you can target an intensity of stress for a workout and
+monitor and adjust the intensity of the workout as you ride.
+
+We have also added a whole host of new metrics, there are now over 100 different
+metrics and measures you can work with including things like; Pace, Maximums,
+Gradient, VAM, wpk, time in HR Zones and many, many more.
+
+@section Build and Platform support
+
+For the technical amongst you we have removed mandatory Boost Dependency, which means
+you can build GC with nothing more than QT4.8 installed (we will support QT5 in v3.1).  
+We now support OpenBSD and have moved to using version 6.1 of the QWT library.
+
+On a related note, you can see all the versions used, contributors involved and build
+settigs as we have improved the about box to give much more useful information to
+developers.
+
+@section We wrote some documentation!
+
+Shock. We now have an FAQ covering over 50 of the most commonly asked questions about
+GoldenCheetah. And a full user manual to compliment the existing wiki for user generated
+content.
+
+One of the other criticisms we often heard about GoldenCheetah was how hard it was to
+use, and how you needed to be a cycling nerd to understand it. We feel that the new UI
+and User Experience coupled with much better documentation and help mean this should
+make this version of GoldenCheetah the easiest to use yet.
+
+
+@node CONTRIBUTORS,WHATS NEW,WHATS NEW,Top
+@chapter Contributors
+
+@section Credits and Contributors
+
+Literally thousands of people regularly download, install, develop, critique and discuss
+GoldenCheetah and its features and functions.
+
+Back in 2006 a stupendously gifted guy (and Cat 1 racer) called Sean Rhea bought a 
+Powertap. Frustrated with the software that was available he set about writing some
+utilities to plot the data. But first he had to reverse engineer the protocol to talk to it. 
+Back then, and to a lesser degree now, these sports and cycling products are closed. You buy 
+their product and you're stuck with their software. Sean did something amazing -- he open 
+sourced his code. By doing that he changed power analysis completely. 
+
+Here in 2013 with ANT+, BTLE, Wahoo, TrainerRoad, PerfPro and of course GoldenCheetah things 
+look very different. The cycling world has gone open. Sean can take some of the credit for that. 
+
+We stand on his shoulders.
+
+Here in 2013 by far and away the biggest contributors to this project are Damien Grauser and 
+Mark Liversedge.  Between the two of them they have committed almost 90% of all code to 
+GoldenCheetah in the last 3 years. Often working on stuff for others they are the reason this 
+release is written for you the cyclist .. and not us the developers.
+
+Of equal importance is Gareth Coco our devops guru. With unfathomable patience he has built
+countless release candidates and development builds for the last 3 years. He has worked with an
+ever changing and hideous array of wacky dependencies across Windows, Mac and Linux. He is pretty
+much the only reason you can download and install our software. Big, big thanks to Gareth.
+
+Thats not to say that there aren't many other significant contributions too; Ale Martinez
+has masterminded and developed multi-language support in V3. Translations have been undertaken
+by Ale himself, but also by Til Schmiedeberg, Keisuke Yamaguchi, Marco Piccirilli, Sergei Chekhovskii
+and Rafael Oliveira Ribeiro. And a huge thanks to Satoru Kurashiki who has worked tirelessly
+to get a Debian (and hence Ubuntu) package created for GoldenCheetah since v2.1.
+
+A large number of developers have contributed small and large bits of code, and many clever
+coaches and athletes have donated their ideas and best practices. I must shout out to
+Dr Andrea Morelli the professional coach, for his encouragement and insight over the last
+3 years and Greg Steele for some of the most interesting and inspriring thoughts.
+
+Here are all the contributors, all of them have made this version of GoldenCheetah the best yet;
+
+Alejandro Martinez, Andrew Bryson, Andy Froncioni, Austin Roach, Berend De Schouwer, Bruno Assis,
+Chris Cleeland, Claus Assmann, Dag Gruneau, Damien Grauser, Darren Hague, Dean Junk, Eric Brandt,
+Eric Murray, Frank Zschockelt, Gareth Coco, Greg Lonnon, Ilja Booij, Jaime Jofre, Jamie Kimberley,
+Jim Ley, John Ehrlinger, Josef Gebel, Julian Baumgartner, Julian Simioni, Justin Knotzke, Keisuke Yamaguchi,
+Ken Sallot, Luke NRG, Magnus Gille, Marc Boudreau, Mark Liversedge, Mark Rages, Mitsukuni Sato,
+Ned Harding, Patrick McNerthney, Rainer Clasen, Robb Romans, Robert Carlsen, Roberto Massa, Ron Alford,
+Sean Rhea, Steven Gribble, Thomas Weichmann, Walter Burki.
+
+Finally a big shout out to three amazing people; Jamie Kimberley who has been the glue
+that held the GoldenCheetah community together, Robert Carlsen who has always been the
+cool guy in the glasses that does the cool stuff. And last but not least, my friend Justin
+Knotzke who demands and gets the best from all of us.
+
+Jamie, Robert and Justin have stepped away from regular involvement in GoldenCheetah, but their
+contributions have set the standard and will not be forgotten. Cheers Guys.
+
+@bye

doc/user/Makefile

@@ -0,0 +1,32 @@
+# 
+# Generate documentation files from the source .texinfo
+#
+
+all: FAQ RELEASE MANUAL
+	rm -f *.aux *.cp *.cps *.fn *.ky *.log *.pg *.toc *.tp *.vr
+
+clean:
+	rm -f GC3-Manual.pdf GC3-FAQ.pdf GC3-FAQ.html \
+    GC3-FAQ.info GC3-Release.pdf GC3-Release.html GC3-Release.info 
+	rm -f *.aux *.cp *.cps *.fn *.ky *.log *.pg *.toc *.tp *.vr
+
+MANUAL: GC3-Manual.pdf 
+FAQ: GC3-FAQ.pdf GC3-FAQ.info
+RELEASE: GC3-Release.pdf GC3-Release.info
+
+## The basic commands, good on Linux/Mac
+## need mingw on Windows
+TEXI2PDF    = texi2pdf
+TEXI2HTML   = texi2html
+MAKEINFO    = makeinfo
+
+.SUFFIXES: .pdf .texinfo .info .html
+
+.texinfo.info:
+	${MAKEINFO} $< -o $@ >/dev/null 2>&1
+
+.texinfo.pdf:
+	${TEXI2PDF} -I ../contrib $< -o $@  >/dev/null 2>&1
+
+.texinfo.html:
+	${TEXI2HTML} $< -o $@ >/dev/null 2>&1

doc/user/image/README

@@ -0,0 +1,10 @@
+We only have images for the Manual since they are so large and
+consume lots of disk space etc.
+
+Each image must be a PDF file, and to make it easier to manage
+and find images we name them;
+
+section-keyword.pdf
+
+e.g.
+0-icon.pdf       - the gc icon image on the first page (section 0)

doc/web/Makefile

@@ -0,0 +1,85 @@
+
+CONTENT=$(wildcard *.content)
+HTML=$(subst .content,.html,$(CONTENT))
+TARBALLS=$(wildcard gc_*.tgz)
+OTHER= 3d.png choose-a-cyclist.png cpint.gp cpint.png critical-power-plot.png critical-power.png \
+       cyclist-info.png editor.png gui-preview.png histogram-analysis.png logo.jpg logo.png \
+       main-window.png map.png metrics-power.png metrics-timedist.png metrics-tiz.png pf-pv-plot.png \
+       pm.png power.zones realtime.png ride-plot.png ride-plot2.png ride-summary.png sample.gp \
+       sample.png weekly-summary.png google-earth.png aerolab.png
+
+BIN=    GoldenCheetah_3.0.0_Mac_32bit.dmg \
+        GoldenCheetah_3.0.0_Mac_64bit.dmg \
+        GoldenCheetah_3.0.0_Windows_Installer.exe
+
+all: $(HTML)
+.PHONY: all clean install
+
+clean:
+	rm -f $(HTML)
+
+install:
+	rsync -avz -e ssh $(HTML) $(TARBALLS) $(OTHER) \
+		goldencheetah.org:/home/srhea/wwwroot/goldencheetah.org/
+
+install-bin:
+	rsync -avz -e ssh $(BIN) \
+		goldencheetah.org:/home/srhea/wwwroot/goldencheetah.org/
+
+bug-tracker.html: bug-tracker.content genpage.pl
+	./genpage.pl "Bug Tracker" $< > $@
+
+command-line.html: command-line.content genpage.pl
+	./genpage.pl "Legacy Command-Line Tools" $< > $@
+
+contact.html: contact.content genpage.pl
+	./genpage.pl "Contact Us" $< > $@
+
+contrib.html: contrib.content genpage.pl
+	./genpage.pl "Contributors" $< > $@
+
+developers-guide.html: developers-guide.content genpage.pl
+	./genpage.pl "Developer's Guide" $< > $@
+
+older-releases.html: older-releases.content genpage.pl
+	./genpage.pl "Older Releases" $< > $@
+
+download.html: download.content genpage.pl
+	./genpage.pl "Download" $< > $@
+
+release-notes.html: release-notes.content genpage.pl
+	./genpage.pl "Release Notes" $< > $@
+
+release-notes_2.1.0.html: release-notes_2.1.0.content genpage.pl
+	./genpage.pl "Release Notes 2.1.0" $< > $@
+
+faq.html: faq.content genpage.pl
+	./genpage.pl "Frequently Asked Questions" $< > $@
+
+index.html: index.content genpage.pl
+	./genpage.pl "Introduction" $< > $@
+
+license.html: license.content genpage.pl
+	./genpage.pl "License" $< > $@
+
+mailing-list.html: mailing-list.content genpage.pl
+	./genpage.pl "Mailing Lists" $< > $@
+
+screenshots.html: screenshots.content genpage.pl
+	./genpage.pl "Screenshots" $< > $@
+
+search.html: search.content genpage.pl
+	./genpage.pl "Search" $< > $@
+
+users-guide.html: users-guide.content genpage.pl
+	./genpage.pl "User's Guide" $< > $@
+
+wiki.html: wiki.content genpage.pl
+	./genpage.pl "Wiki" $< > $@
+
+wishlist.html: wishlist.content genpage.pl
+	./genpage.pl "Wish List" $< > $@
+
+zones.html: zones.content genpage.pl
+	./genpage.pl "Power Zones File Guide" $< > $@
+

doc/web/bug-tracker.content

@@ -0,0 +1,4 @@
+<p>We have an issue tracker set up at
+<a href="https://github.com/GoldenCheetah/GoldenCheetah/issues">GitHub</a>.</p>
+<p>Here is a <a href="https://github.com/blog/411-github-issue-tracker">
+link to short video</a> about the Issue tracker.</p>

doc/web/command-line.content

@@ -1,16 +1,5 @@
 <!-- $Id: users-guide.content,v 1.5 2006/05/27 16:32:46 srhea Exp $ -->
 
-<big><font face="arial,helvetica,sanserif">
-Using the GUI
-</font></big>
-
-<p>
-Using the graphical version of Golden Cheetah should be pretty
-self-explanatory.  Download the disk image from the <a
-href="download.html">download page</a>, drag the Golden Cheetah application
-into your Applications folder, open your Applications folder, and then double
-click on Golden Cheetah.
-
 <p>
 <big><font face="arial,helvetica,sanserif">
 Using the Command Line Utilities
@@ -22,20 +11,22 @@ several command line utilities:
 <code>ptdl</code>, which downloads ride data from a PowerTap Pro version 2.21
 cycling computer, <code>ptunpk</code>, which unpacks the raw bytes downloaded
 by <code>ptdl</code> and outputs more human-friendly ride information, and
-<code>cpint</code>, which computes your critical power (see below).  All three
-are written in simple C code but have only been tested on Mac OS X so far.
-We've also written several Perl scripts to help you graph and summarize the
-data.
+<code>cpint</code>, which computes your critical power (see below).  We've
+also written several Perl scripts to help you graph and summarize the data.
+
+<p>
+NOTE: We no longer support the use of the command-line tools.  Please use the
+graphical version of GoldenCheetah instead.  This documentation is here for
+the benefit of the brave alone.
 
 <p>
 <big><font face="arial,helvetica,sanserif">
 Extracting the Data
 </font></big>
 <p>
-To use <code>ptdl</code>, you'll first need to install 
-<a href="http://www.ftdichip.com/Drivers/VCP.htm">the drivers</a> for the
-FTDI chip the PowerTap Pro USB Downloader uses.  Once these are installed, you
-should be able to just run <code>ptdl</code> without arguments:  
+First, make sure you have the FTDI drivers installed, as described in the <a
+href="users-guide.html">User's Guide</a>.  You can then run <code>ptdl</code>
+without arguments:  
 
 <pre>
 $ ./ptdl 

doc/web/contrib.content

@@ -0,0 +1,61 @@
+<!-- $Id: contrib.content,v 1.4 2006/09/06 04:07:18 srhea Exp $ -->
+
+<p>Sean Rhea bought a PowerTap Pro on April 20, 2006 and immediately set
+to figuring out how to use it from his Mac without using Virtual PC.
+With help from Russ Cox and David Easter, he wrote two command-line
+programs for downloading data from a PowerTap and interpreting that
+data.  Sean released these two tools, <code>ptdl</code> and
+<code>ptunpk</code>, on May 4, 2006.</p>
+
+<p>Later that year, Sean needed to learn QT for his real job, and he set
+about writing a graphical version of his software for practice.  He
+released the first graphical version on September 6, 2006, changing the
+name to GoldenCheetah in reference to an old legend from his days as a
+runner.</p>
+
+<p>Since then, a large community has contributed additional code and
+other support, including:</p>
+
+<table width="80%">
+<tr>
+<td valign="top" width="33%">
+<ul>
+<li>Robert Carlsen</li>
+<li>Rainer Clasen</li>
+<li>Chris Cleeland</li>
+<li>J.T. Conklin</li>
+<li>Dan Connelly</li>
+<li>Damien Grauser</li>
+<li>Steve Gribble</li>
+<li>Dag Gruneau</li>
+<li>Ned Harding</li>
+</ul>
+</td>
+<td valign="top" width="33%">
+<ul>
+<li>Aldy Hernandez</li>
+<li>Jamie Kimberley</li>
+<li>Justin Knotzke</li>
+<li>Andrew Kruse</li>
+<li>Mark Liversedge</li>
+<li>Greg Lonnon</li>
+<li>Tom Montgomery</li>
+<li>Eric Murray</li>
+<li>Scott Overfield</li>
+</ul>
+</td>
+<td valign="top">
+<ul>
+<li>Mark Rages</li>
+<li>Robb Romans</li>
+<li>Mitsukuni Sato</li>
+<li>Berend de Schouwer</li>
+<li>Julian Simioni</li>
+<li>Greg Steele</li>
+<li>Tom Weichmann</li>
+<li>Keisuke Yamaguchi</li>
+</ul>
+</td>
+</tr>
+</table>
+

doc/web/contributors.txt

@@ -0,0 +1,44 @@
+Alejandro Martinez
+Andrew Bryson
+Andy Froncioni
+Austin Roach
+Berend De Schouwer
+Bruno Assis
+Chris Cleeland
+Claus Assmann
+Dag Gruneau
+Damien Grauser
+Darren Hague
+Eric Brandt
+Eric Murray
+Frank Zschockelt
+Gareth Coco
+Greg Lonnon
+Ilja Booij
+Jamie Kimberley
+Jim Ley
+John Ehrlinger
+Josef Gebel
+Julian Baumgartner
+Julian Simioni
+Justin Knotzke
+Keisuke Yamaguchi
+Ken Sallot
+Luke NRG
+Magnus Gille
+Marc Boudreau
+Mark Liversedge
+Mark Rages
+Mitsukuni Sato
+Ned Harding
+Patrick McNerthney
+Rainer Clasen
+Robb Romans
+Robert Carlsen
+Roberto Massa
+Ron Alford
+Sean Rhea
+Steven Gribble
+Thomas Weichmann
+Tom Weichmann
+Walter Bürki

doc/web/developers-guide.content

@@ -0,0 +1,562 @@
+<!-- $Id: users-guide.content,v 1.5 2006/05/27 16:32:46 srhea Exp $ -->
+
+<p>This guide will teach you how to download the GoldenCheetah source code,
+build it, modify it, and submit your changes to be included in the next
+release.  If you're just looking to use GoldenCheetah, please check out the
+<a href="users-guide.html">Users Guide</a> or the
+<a href="download.html">Download Page</a>.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Installing dependencies
+</font></big>
+
+<p>GC requires a number of libraries.  On Mac OS X, you can get most of these
+through <a href="http://www.macports.org/">Mac Ports</a>.  On Linux and other
+Unixes, you can use whatever package manager your distribution provides.  (We
+list the package names for MacPorts and Ubuntu below.)  On Windows, you'll
+probably need to download and install everything by hand.  You might also want
+to read <a href="old-mailing-list-archives/2009-September/002502.html">this
+mailing list message</a> or check the
+ <a href="https://github.com/GoldenCheetah/GoldenCheetah">INSTALL</a> documents
+on GitHub.</p>
+
+<p>You'll need the following:</p>
+<table align="center" width="500">
+<tr>
+  <td>Package</td>
+  <td>Version</td>
+  <td>MacPorts</td>
+  <td>Ubuntu</td>
+</tr>
+<tr>
+  <td><a href="http://qt.nokia.com/downloads">Qt</a></td>
+  <td>4.8.0 or later</td>
+  <td>qt4-mac</td>
+  <td>libqt4-dev</td>
+</tr>
+<tr>
+  <td><a href="http://git-scm.com/download">git</a></td>
+  <td>any</td>
+  <td>git-core</td>
+  <td>git</td>
+</tr>
+</table>
+
+<p>If you're going to download directly from a PowerTap, you might need to
+install the <a href="http://www.ftdichip.com/Drivers/D2XX.htm">FTDI USB
+driver</a>.  If you're going to download directly from an SRM, you need to
+download and install <a href="git://github.com/rclasen/srmio.git">libsrmio</a>.
+Neither of these libraries is required if you just want to import data you've
+already downloaded with another program.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Checking out the code
+</font></big>
+
+<p>Once you've downloaded and installed the above dependencies, you need to
+check out the GC source code.  GC uses <em>git</em> for version control.  To
+checkout the code, execute this command:</p>
+
+<blockquote>
+<pre>
+git clone git://github.com/GoldenCheetah/GoldenCheetah.git
+</pre>
+</blockquote>
+
+<p>That should create a new directory, <code>GoldenCheetah</code>, in your
+current working directory.  In the rest of this document, we'll reference
+paths relative to that directory.  You can find the source code in
+<code>GoldenCheetah/src</code>, for instance.  Likewise, this
+document is in <code>GoldenCheetah/doc/developers-guide.content</code>.<p>
+
+<big><font face="arial,helvetica,sanserif">
+Building an executable
+</font></big>
+
+<p>To build GC, we currently use <em>qmake</em>, which comes with the Qt
+libraries referenced above.  All local configuration is stored in the file
+<code>gcconfig.pri</code>, which you create by copying
+<code>gcconfig.pri.in</code>, both in the <code>GoldenCheetah/src</code>
+directory. Additionally, GoldenCheetah uses a patched version of <a
+href="http://sourceforge.net/projects/qwt/">Qwt</a> which is located in the
+<code>GoldenCheetah/qwt</code> directory. You'll need to copy the
+configuration file <code>qwtconfig.pri.in</code> to <code>qwtconfig.pri</code>
+and edit that file if needed. The steps you'll take are as follows:</p>
+
+<blockquote>
+In the top level GoldenCheetah directory
+<pre>
+cp src/gcconfig.pri.in src/gcconfig.pri
+cp qwt/qwtconfig.pri.in qwt/qwtconfig.pri
+vi src/gcconfig.pri # Follow the directions at the top of the file.
+vi qwt/qwtconfig.pri # This may not need to be edited to successfully build.
+qmake build.pro # called qmake-mac in MacPorts
+make
+</pre>
+</blockquote>
+
+<p>We're aware that a lot of people would rather use a configure-like script
+for the build process.  We would too, but none of us know
+<a href="http://www.gnu.org/software/autoconf/">autoconf</a> well
+enough to integrate it with Qt on Mac, Linux, and Windows.  If you can help
+us out with that, please post a message on the
+<a href="https://groups.google.com/forum/?fromgroups&hl=en#!forum/golden-cheetah-users">GoldenCheetah User's
+Google Group</a>.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Making changes
+</font></big>
+
+<p>Now that you've got GC up and running, you can add whatever features you want.
+We generally frown on dogmatic coding conventions, and we're big fans of the
+"rough consensus and running code" philosophy.  That said, please do your best
+to adhere to the following style guidelines:</p>
+
+<ul>
+<li>Use spaces instead of tabs.
+
+<li>Do not end lines with whitespace.  End every file with a newline.
+Otherwise git becomes angry.  This command will 
+highlight any whitespace problems in commit <em>abcd0123</em> in red:
+
+<blockquote>
+<pre>
+git show --color abcd0123
+</pre>
+</blockquote>
+
+<li>Avoid "using namespace ..." in header files.
+
+<li>Don't declare global variables in header files.  If you must use a global
+variable, declare it <code>static</code> within a .cpp file.
+
+<li>Only call C++'s operator <code>new</code> within the constructors and
+<code>reset</code> functions of <code>std::auto_ptr</code> etc. 
+or when passing a parent pointer to a Qt class (so that the parent
+deletes the child).  Never call <code>delete</code> explicitly.
+
+<li>Do not use <code>malloc</code> or <code>free</code> unless forced to by an
+external C library.
+
+<li>Allocate large buffers on the heap, not on the stack.
+
+<li>When the Qt or C++ standard library has an appropriate function, use it.
+
+<li>Only use external libraries with GPL-compatible licenses.
+
+<li>Avoid C-style casts.  Learn and use C++'s <code>static_cast</code>,
+<code>reinterpret_cast</code>, etc.
+</ul>
+
+<p>Not all of the GoldenCheetah code follows these guidelines today, but we're
+working on it.  You can help out by adhering to them in new code.</p>
+
+<hr width="20%"/>
+
+<p>At some point, you'll probably decide that a change you've made is worth
+sharing with others.  You'll use <em>git</em> again to share your changes, and
+the following sections will show you how.  A warning: git is pretty hard to
+learn, but it's worth it.  Once you get used to it, you'll be surprised you
+ever put up with another revision control system.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Committing changes to git
+</font></big>
+
+<p> An example will make this section more concrete.  Since my SRM doesn't
+record altitude, let's say that I get annoyed that the Ride Summary always
+shows "Elevation Gain (feet): 0.0", so I change the code not to show any ride
+metric whose value is zero.  <em>git-diff</em> shows exactly what I've
+changed:</p>
+
+<blockquote>
+<pre>
+$ cd GoldenCheetah/src
+$ git diff
+diff --git a/src/RideItem.cpp b/src/RideItem.cpp
+index 6971b9b..c368725 100644
+--- a/src/RideItem.cpp
++++ b/src/RideItem.cpp
+@@ -362,6 +362,8 @@ RideItem::htmlSummary()
+                 assert(displayName.length() &gt; 0);
+                 const RideMetric *m = metrics.value(name);
+                 assert(m);
++                if (m-&gt;value(false) == 0.0)
++                    continue;
+                 if (m-&gt;units(metricUnits) == "seconds") {
+                     QString s("&lt;tr&gt;&lt;td&gt;%1:&lt;/td&gt;&lt;td "
+                               "align=\"right\"&gt;%2&lt;/td&gt;&lt;/tr&gt;");
+</pre>
+</blockquote>
+
+<p>In order to share this change, I need to use <em>git-commit</em>:</p>
+
+<blockquote>
+<pre>
+$ git commit RideItem.cpp
+</pre>
+</blockquote>
+
+<p>git will open up an editor for me to type a commit message.  It's important
+to take the time to write good commit messages, as they form a history of who
+has changed which lines of code and for what purpose.  The first line of every
+commit message should be a short description of 50 characters or less.  The
+second line should be blank.  Subsequent lines should be less than 80
+characters long and should describe the change in detail. If your commit
+addresses an existing bug or feature please add a tag to the body of your
+commit message. Allowable tags are "fixes" which is used to close an
+issue and "refs" to reference an issue. For example, adding the text
+"fixes #2" will close issue #2.  Once I write the file and exit the
+editor, <em>git-log</em> will show the result:</p>
+
+<blockquote>
+<pre>
+$ git log -p -1
+commit 30303ef2d11f4bead0860b969b4b74814053b76b
+Author: Sean Rhea &lt;sean.c.rhea@gmail.com&gt;
+Date:   Wed Sep 2 21:04:33 2009 -0400
+
+    don't include zero metrics in ride summary
+
+    When a device doesn't have altitude, there's no reason to show it.  Likewise
+    with heart rate if the user wasn't wearing a heart rate monitor during a ride.
+    Maybe in the future this behavior could be enabled on a per-metric basis.
+
+diff --git a/src/RideItem.cpp b/src/RideItem.cpp
+index 6971b9b..c368725 100644
+--- a/src/RideItem.cpp
++++ b/src/RideItem.cpp
+@@ -362,6 +362,8 @@ RideItem::htmlSummary()
+                 assert(displayName.length() &gt; 0);
+                 const RideMetric *m = metrics.value(name);
+                 assert(m);
++                if (m-&gt;value(false) == 0.0)
++                    continue;
+                 if (m-&gt;units(metricUnits) == "seconds") {
+                     QString s("&lt;tr&gt;&lt;td&gt;%1:&lt;/td&gt;&lt;td "
+                               "align=\"right\"&gt;%2&lt;/td&gt;&lt;/tr&gt;");
+</pre>
+</blockquote>
+
+<p>Note that had I changed more than one file, I would have just listed them
+all when I ran <em>git-commit</em>.  For example,</p>
+
+<blockquote>
+<pre>
+$ git commit file1.cpp file2.cpp
+</pre>
+</blockquote>
+
+<p>I can also commit everything I've changed all at once via</p>
+<blockquote>
+<pre>
+$ git commit . # note the 'dot'
+</pre>
+</blockquote>
+
+<big><font face="arial,helvetica,sanserif">
+Managing commits
+</font></big>
+
+<p>git works best if you commit early and often.  For example, I usually
+commit a few times as I'm writing a new feature.  Once I get my code to
+compile, I commit it again.  Then if I fix any bugs that turn up during
+runtime, I commit the bug fixes.  Then maybe I go back and clean up the new
+code, now that I understand the problem better, and I commit those changes,
+too.</p>
+
+<p>The reasoning behind all of these commits is that commits are like save
+points in a video game.  If at any point I decide I'm messing things up,
+I can just go back to the previous commit.  <em>git-diff</em> shows me my
+uncommitted changes.  Let's say that I've decided I should also change the
+text in the Ride Summary to reflect the fact that I'm only showing non-zero
+metrics now.  Here's my change:</p>
+
+<blockquote>
+<pre>
+$ git diff
+diff --git a/src/RideItem.cpp b/src/RideItem.cpp
+index c368725..2ff9c49 100644
+--- a/src/RideItem.cpp
++++ b/src/RideItem.cpp
+@@ -159,13 +159,13 @@ static const char *metricsXml =
+     "            precision=\"1\"/&gt;\n"
+     "  &lt;/metric_group&gt;\n"
+     "  &lt;metric_group name=\"Averages\"&gt;\n"
+-    "    &lt;metric name=\"average_speed\" display_name=\"Speed\"\n"
++    "    &lt;metric name=\"average_speed\" display_name=\"(Non-zero) Speed\"\n"
+     "            precision=\"1\"/&gt;\n"
+-    "    &lt;metric name=\"average_power\" display_name=\"Power\"\n"
++    "    &lt;metric name=\"average_power\" display_name=\"(Non-zero) Power\"\n"
+     "            precision=\"0\"/&gt;\n"
+-    "    &lt;metric name=\"average_hr\" display_name=\"Heart rate\"\n"
++    "    &lt;metric name=\"average_hr\" display_name=\"(Non-zero) Heart rate\"\n"
+     "            precision=\"0\"/&gt;\n"
+-    "    &lt;metric name=\"average_cad\" display_name=\"Cadence\"\n"
++    "    &lt;metric name=\"average_cad\" display_name=\"(Non-zero) Cadence\"\n"
+     "            precision=\"0\"/&gt;\n"
+     "  &lt;/metric_group&gt;\n"
+     "  &lt;metric_group name=\"BikeScore&#8482;\" note=\"BikeScore is a trademark
+</pre>
+</blockquote>
+
+<p>But now I decide I don't like that change--I'd rather do it another way.
+No problem.  <em>git-checkout</em> will restore the previous version committed:</p>
+
+<blockquote>
+<pre>
+$ git checkout src/RideItem.cpp
+</pre>
+</blockquote>
+
+<p>If I want to restore the entire directory to the state of the last commit,
+I checkout the whole directory:</p>
+
+<blockquote>
+<pre>
+$ git checkout . # note the 'dot'
+</pre>
+</blockquote>
+
+<p>Alternatively, if I had already committed this change, I can use
+<em>git-reset</em> to throw away my latest commit like this:</p>
+
+<blockquote>
+<pre>
+$ git reset --hard HEAD^
+</pre>
+</blockquote>
+
+<p>Be careful with that one, though--it's irreversible.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Combining commits
+</font></big>
+
+<p>Coming back to our example, let's say I instead decide to change the ride
+summary a little differently and commit it:</p>
+
+<blockquote>
+<pre>
+$ git log -p -1
+commit 225f3093a206cbcc296ed1c8a25996ce1968bda6
+Author: Sean Rhea <sean.c.rhea@gmail.com>
+Date:   Sat Sep 5 16:21:33 2009 -0400
+
+    include "non-zero" in metric group titles
+
+diff --git a/src/RideItem.cpp b/src/RideItem.cpp
+index c368725..449e19e 100644
+--- a/src/RideItem.cpp
++++ b/src/RideItem.cpp
+@@ -146,7 +146,7 @@ double RideItem::timeInZone(int zone)
+
+ static const char *metricsXml =
+     "&lt;metrics&gt;\n"
+-    "  &lt;metric_group name=\"Totals\"&gt;\n"
++    "  &lt;metric_group name=\"Non-zero Totals\"&gt;\n"
+     "    &lt;metric name=\"workout_time\" display_name=\"Workout time\"\n"
+     "            precision=\"0\"/&gt;\n"
+     "    &lt;metric name=\"time_riding\" display_name=\"Time riding\"\n"
+@@ -158,7 +158,7 @@ static const char *metricsXml =
+     "    &lt;metric name=\"elevation_gain\" display_name=\"Elevation Gain\"\n"
+     "            precision=\"1\"/&gt;\n"
+     "  &lt;/metric_group&gt;\n"
+-    "  &lt;metric_group name=\"Averages\"&gt;\n"
++    "  &lt;metric_group name=\"Non-zero Averages\"&gt;\n"
+     "    &lt;metric name=\"average_speed\" display_name=\"Speed\"\n"
+     "            precision=\"1\"/&gt;\n"
+     "    &lt;metric name=\"average_power\" display_name=\"Power\"\n"
+</pre>
+</blockquote>
+
+<p>Now I have two commits, which I can see with <em>git-log</em>:</p>
+
+<blockquote>
+<pre>
+$ git log origin/master..devel-guide
+commit 225f3093a206cbcc296ed1c8a25996ce1968bda6
+Author: Sean Rhea &lt;sean.c.rhea@gmail.com&gt;
+Date:   Sat Sep 5 16:21:33 2009 -0400
+
+    include "non-zero" in metric group titles
+
+commit df657cd3f0dcb8484a468c2efb04da77ee0472e0
+Author: Sean Rhea &lt;sean.c.rhea@gmail.com&gt;
+Date:   Wed Sep 2 13:42:33 2009 -0400
+
+    don't include zero metrics in ride summary
+
+    When a device doesn't have altitude, there's no reason to show it.  Likewise
+    with heart rate if the user wasn't wearing a heart rate monitor during a ride.
+    Maybe in the future this behavior could be enabled on a per-metric basis.
+</pre>
+</blockquote>
+
+<p>If I'm happy with my changes, I can share them with the world just
+like they are using <em>git-format-patch</em>.  In this case, however, these
+two changes should really be combined into one: the second change was
+something I should have done along with the first, I just didn't think of it
+at the time.  I can use <em>git-rebase -i</em> to combine them:</p>
+
+<blockquote>
+<pre>
+$ git rebase -i origin/master
+</pre>
+</blockquote>
+
+<p>That will bring up an editor window with a list of my changes, like
+this:</p>
+
+<blockquote>
+<pre>
+pick df657cd don't include zero metrics in ride summary
+pick 225f309 include "non-zero" in metric group titles
+
+# Rebase df33fe2..920643f onto df33fe2
+#
+# Commands:
+#  p, pick = use commit
+#  e, edit = use commit, but stop for amending
+#  s, squash = use commit, but meld into previous commit
+#
+# If you remove a line here THAT COMMIT WILL BE LOST.
+# However, if you remove everything, the rebase will be aborted.
+#
+</pre>
+</blockquote>
+
+<p>The directions are pretty self explanatory.  You can reorder commits by
+reordering their lines in this file.  You can drop a commit by removing it
+from the file entirely.  You can also change the first word on a line from
+"pick" to "squash", and git will combine that commit with the one that comes
+before it.  That's what I want to do here.  I change line 2 of this file so
+that the first two lines are:</p>
+
+<blockquote>
+<pre>
+pick df657cd don't include zero metrics in ride summary
+squash 225f309 include "non-zero" in metric group titles
+</pre>
+</blockquote>
+
+<p>Then I write the file and quit the editor.  Git does a little work
+saying:</p>
+
+<blockquote>
+<pre>
+Rebasing (1/2)
+</pre>
+</blockquote>
+
+<p>And then it brings up another editor window that shows both of my commit
+messages.  I edit the two message to combine them into one, write the file,
+and exit the editor.  git says:</p>
+
+<blockquote>
+<pre>
+Successfully rebased and updated refs/heads/master.
+</pre>
+</blockquote>
+
+<p>And I can see the result with <code>git log -p</code>.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Submitting a patch
+</font></big>
+
+<p>Okay, <em>now</em> I'm ready to share my change.  I'll use
+<em>git-format-patch</em>:
+
+<blockquote>
+<pre>
+$ git format-patch HEAD^
+0001-don-t-include-zero-metrics-in-ride-summary.patch
+</pre>
+</blockquote>
+
+<p>In the <code>GoldenCheetah/src</code> directory I'll now find a <em>patch
+file</em>, <code>0001-don-t-include-zero-metrics-in-ride-summary.patch</code>,
+that other people can use to include my change in their own local git
+repositories.</p>
+
+<p>If you have a patch you'd like to share with others, we recommend that you
+ <a href="https://help.github.com/articles/fork-a-repo">fork</a> the main GIT
+repository and submit a
+ <a href="https://help.github.com/articles/creating-a-pull-request">pull request</a>
+ with your patch. Alternatively you can join the
+ <a href="https://groups.google.com/forum/?fromgroups#!forum/golden-cheetah-developers">
+Golden Cheetah Developer's Group</a> and post a patch there.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Applying patches
+</font></big>
+
+<p>Let's say I email the patch above to the mailing list, and it sounds like a
+useful feature to you.  To test it yourself, you can download the patch file
+to your <code>GoldenCheetah/src</code> directory and apply it to your
+repository using <em>git-am</em>:</p>
+
+<blockquote>
+<pre>
+$ git am 0001-don-t-include-zero-metrics-in-ride-summary.patch
+Applying: don't include zero metrics in ride summary
+</pre>
+</blockquote>
+
+<p>If you now type, "git log", you'll see that "don't include zero metrics in
+ride summary" has been added to your repository.</p>
+
+<p>If enough people like a patch, and it doesn't introduce any new bugs, one
+of the GoldenCheetah maintainers will probably commit it to the official GC
+repository on github.</p>
+
+<big><font face="arial,helvetica,sanserif">
+Staying up to date
+</font></big>
+
+<p>In order to keep your local repository up to date with
+the official one, you use <em>git-fetch</em> followed by
+<em>git-rebase</em>:</p>
+
+<blockquote>
+<pre>
+$ git fetch origin
+$ git rebase origin/master
+First, rewinding head to replay your work on top of it...
+Fast-forwarded master to origin/master.
+</pre>
+</blockquote>
+
+<p>Note that, unlike above, we didn't supply a "-i" option to
+<em>git-rebase</em> this time.</p>
+
+<p><em>git-fetch</em> downloads a copy of all the patches at github to
+your local repository, but it doesn't apply them.  <em>git-rebase</em> undoes
+the changes that are unique to your local repository, applies any new patches
+from <code>origin/master</code>, and then re-applies your patches.</p>
+
+<p>If you have uncommitted changes, the rebase will fail:</p>
+
+<blockquote>
+<pre>
+$ git rebase origin/master
+src/RideItem.cpp: needs update
+cannot rebase: you have unstaged changes
+</pre>
+</blockquote>
+
+<p>Commit your changes with <em>git-commit</em> and then re-run the
+<em>git-rebase</em>.  It will work this time.</p>
+
+<p>For developers who are used to subversion, this need to commit changes
+before rebasing is the most annoying aspect of git.  All I can say is that you
+won't mind it much after time.  Because you can use "git rebase -i" to
+combine, reorder, and even drop commits, a commit in git is much lighter
+weight than one in subversion.  As I said above, commit early and often.</p>
+
+<p>If the changes from github conflict with yours, you'll have to merge.
+<em>git-rebase</em> will exit with an error and a list of directions on how to
+fix things.  Read them carefully.</p>
+
+

doc/web/download.content

@@ -0,0 +1,82 @@
+<!-- $Id: download.content,v 1.6 2009/01/09 20:45:03 rcarlsen Exp $ -->
+
+<p>
+Golden Cheetah is available in binary form for
+Linux x86, Mac OS X (universal binary), and Windows.
+It is also available as source code.
+</p>
+
+<p>
+Golden Cheetah downloads data from all versions of the PowerTap
+computer including the new Joule. Previously you needed to have the
+FTDI USB Drivers installed if you were using the PowerTap USB cradle
+(as opposed to the older, serial cable). This should not be necessary.
+If you are having problems then you can manually install the
+ <a href="http://www.ftdichip.com/Drivers/D2XX.htm">FTDI USB driver</a>.
+</p>
+
+<p>
+On Linux and Mac OS X, Golden Cheetah also downloads from the SRM PCV.  On Mac
+OS X, you'll need to install <a href="http://osx-pl2303.sourceforge.net/">the
+open source PL2303 driver</a> to download from an SRM. Please see the
+<a href="https://github.com/GoldenCheetah/GoldenCheetah/wiki/Installing-the-d2xx-drivers-on-mac-os">WIKI</a> article
+ - <a href="https://github.com/GoldenCheetah/GoldenCheetah/wiki/Pcv-on-mac-os-x">
+PCV on Mac OS X</a> for further information.
+</p>
+
+<p>
+<font face="arial,helvetica,sanserif">
+<big><strong>Download Release 3.0</strong></big>
+</font>
+</p>
+
+<ul>
+<li><a href="GoldenCheetah_3.0.0_Windows_Installer.exe">Windows 32-bit (runs on 64bit as well)</a>
+<li><a href="GoldenCheetah_3.0.0_Mac_32bit.dmg">Mac OS X Intel 32bit (10.6+)</a><br>
+<li><a href="GoldenCheetah_3.0.0_Mac_64bit.dmg">Mac OS X Intel 64bit (10.6+)</a><br>
+</ul>
+</p>
+
+<p>
+Installation is simple. Download the file for your operationg system.<br>
+On Mac, open the DMG and drag and drop where you would like to install.<br>
+For Windows, run the Installer and follow the prompts.<br>
+</p>
+<p>
+There is a <a href="https://github.com/GoldenCheetah/GoldenCheetah/blob/master/doc/user/GC3-Manual.pdf?raw=true">Manual</a>
+and a <a href="https://github.com/GoldenCheetah/GoldenCheetah/blob/master/doc/user/GC3-FAQ.pdf?raw=true">FAQ</a> that
+you can use to help you use the program.
+</p>
+<p>
+There is the older Version 2.1.0  <a href="/users-guide.html">User's Guide</a> on how to install
+and use Golden Cheetah that can assist also.
+</p>
+<p>
+You can also <a href="release-notes.html">view the release notes</a> for 3.0
+or <a href="older-releases.html">download older releases</a> of Golden Cheetah.
+</p>
+
+<p>
+<font face="arial,helvetica,sanserif">
+<big><strong>Development Releases</strong></big>
+</font>
+</p>
+
+<p>Gareth Coco has also made
+<a href="http://goldencheetah.stand2surf.net/">regular development builds</a>
+available.  These binaries are based on the latest source code, so they may have
+more features and less (but sometime more) bugs than the stable release above.
+</p>
+
+<p>
+<font face="arial,helvetica,sanserif">
+<big><strong>Source Code</strong></big>
+</font>
+</p>
+
+<p>
+The Golden Cheetah source code is available via git.  See the
+<a href="developers-guide.html">Developer's Guide</a> for more information.
+You can also <a href="http://github.com/GoldenCheetah/GoldenCheetah/tree/master/">browse
+the source on github</a>.
+</p>

doc/web/faq.content

@@ -0,0 +1,32 @@
+<!-- $Id: faq.content,v 1.4 2006/07/05 16:59:56 srhea Exp $ -->
+
+<p>
+<b><i>GoldenCheetah doesn't find my PowerTap on Ubuntu Linux.</i></b>
+<p>
+If you're using the USB cradle (as opposed to the older, serial one), 
+the FTDI driver sometimes conflicts with the braille terminal in the
+default Ubuntu installation.  Try unplugging the PT cradle from the
+computer and uninstalling <code>brltty</code>:
+<blockquote>
+<code>sudo apt-get remove brltty</code>
+</blockquote>
+Then plug the device back in and it should work.
+
+<p>
+<b><i>I downloaded a .dmg, opened it, dragged and dropped GoldenCheetah into
+Applications, double-clicked on it, and nothing happened.  What
+gives?</i></b>
+
+<p>
+Are you running OS X Tiger (10.4) or later?  You need to be.
+If you are, and you're still
+having this problem, open Terminal (in Applications -&gt; Utilities) and type
+this at the prompt:
+
+<blockquote><pre>
+/Applications/GoldenCheetah.app/Contents/MacOS/GoldenCheetah
+</pre></blockquote>
+
+then press &lt;return&gt; and send an email to the mailing list with
+whatever it prints out.  We'll help you debug it.
+

doc/web/genpage.pl

@@ -16,7 +16,7 @@ open (FILE, "$content_file") or die "Could not open $content_file";
 print<<EOF;
 <!-- 
 
-  Copyright (c) 2006 Sean C. Rhea (srhea\@srhea.net)
+  Copyright (c) 2006-2008 Sean C. Rhea (srhea\@srhea.net)
   All rights reserved.                                             
 
   This file was automatically generated by genpage.pl.  To change it,
@@ -26,16 +26,25 @@ print<<EOF;
 
 <html>
 <head>
-<title>Golden Cheetah: PowerTap Software for Mac OS X</title>
- <meta name="keywords" content="powertap mac cycling performance">
+<title>Golden Cheetah: Cycling Performance Software for Linux, Mac OS X, and Windows</title>
+ <meta name="keywords" content="powertap srm linux mac cycling performance">
+<style type='text/css'>
+li {
+    margin: .5em 0
+}
+body {
+    color: #000000;
+    background: #ffffff;
+}
+:link {
+      color: #5e431b;
+}
+:visited {
+      color: #996e2d;
+}
+</style>
 </head>
 
-<body    text="#000000" 
-         link="#5e431b" 
-        vlink="#996e2d" 
-        alink="#000000" 
-      bgcolor="#ffffff">
-
 <table width="95%" border="0" width="100%" cellspacing="10">
 <tr>
 
@@ -45,32 +54,18 @@ print<<EOF;
 <img src="logo.jpg" width="175" height="175" alt="Picture of Cheetah">
 
 <p>  <b><a href="index.html">Introduction</a></b>
-<br> <b><a href="screenshots.html">Screenshots</a>
-<br> <b><a href="users-guide.html">User's Guide</a>
-<br> <b><a href="faq.html">FAQ</a>
-<br> <b><a href="license.html">License</a></b>
 <br> <b><a href="download.html">Download</a></b>
+<br> <b><a href="screenshots.html">Screenshots</a>
+<br> <b><a href="wiki.html">Wiki</a>
+<br> <b><a href="users-guide.html">User's Guide</a>
+<br> <b><a href="developers-guide.html">Developer's Guide</a>
+<br> <b><a href="faq.html">FAQ</a>
+<br> <b><a href="wishlist.html">Wish List</a>
+<br> <b><a href="license.html">License</a></b>
 <br> <b><a href="contrib.html">Contributors</a></b>
 <br> <b><a href="search.html">Search</a></b>
-<br> <b><a href="cgi-bin/mailman/listinfo/golden-cheetah-users">Mailing List</a></b>
-
-<p>
-<script type="text/javascript"><!--
-google_ad_client = "pub-2993461533095312";
-google_ad_width = 120;
-google_ad_height = 240;
-google_ad_format = "120x240_as";
-google_ad_type = "text";
-google_ad_channel ="";
-google_color_border = "FFFFFF";
-google_color_bg = "FFFFFF";
-google_color_link = "5E431B";
-google_color_url = "996E2D";
-google_color_text = "000000";
-//--></script>
-<script type="text/javascript"
-  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-  </script>
+<br> <b><a href="mailing-list.html">Mailing List</a></b>
+<br> <b><a href="bug-tracker.html">Bug Tracker</a></b>
 
 </center>
 </td>
@@ -87,7 +82,7 @@ google_color_text = "000000";
 Cheetah</font></b></big></big></big>
 <br>
 <big><font face="arial,helvetica,sanserif">
-PowerTap Software for Mac OS X
+Cycling Performance Software for Linux, Mac OS X, and Windows
 </font></big>
 <p>
 </td></tr>
@@ -114,9 +109,9 @@ while (<FILE>) {
 }
 close (FILE);
 
-if (defined $last_mod) {
-    print "<p><hr><em>Last modified $last_mod.</em>\n";
-}
+#if (defined $last_mod) {
+#    print "<p><hr><em>Last modified $last_mod.</em>\n";
+#}
 
 print<<EOF;
 

doc/web/index.content

@@ -0,0 +1,46 @@
+<!-- $Id: index.content,v 1.1 2006/05/16 14:24:50 srhea Exp $ -->
+
+<p>
+<center>
+<em>To all those volunteers who selflessly give their time and without whom
+amateur sport would not exist.</em>
+<br>
+-- Graeme Obree, in the dedication of <em>Flying Scotsman</em>
+</center>
+
+<p>
+GoldenCheetah is a software package that:
+
+<ul>
+<li>Downloads ride data directly from the CycleOps PowerTap and the SRM
+PowerControl V. Support for SRM PowerControl VI and VII is planned for the
+future.<p>
+
+<li>Imports ride data downloaded with other programs, including TrainingPeaks
+WKO+ and the manufacturers' software for the Ergomo, Garmin, Polar, PowerTap,
+and SRM devices.<p>
+
+<li>Provides a rich set of analysis tools, including a critical power graph,
+BikeScore calculation, histogram analysis, a best interval finder, and a pedal
+force versus pedal velocity chart, to name just a few.<p>
+
+<li>Is available for Linux, Mac OS X, and Windows.<p>
+
+<li>Is released under an Open Source license.
+</ul>
+
+<p>
+We believe that cyclists should be able to download their power data
+to the computer of their choice, analyze it in whatever way they see fit, and
+share their methods of analysis with others.
+
+<hr width="20%"/>
+
+<small>
+<p>
+* WKO+ and TrainingPeaks are trademarks of Peaksware, LLC.
+<br/>
+** BikeScore is a trademark of Dr. Philip Friere Skiba, PhysFarm Training
+Systems LLC.
+</p>
+</small>

doc/web/mailing-list.content

@@ -0,0 +1,17 @@
+
+<p>
+There are two mailing lists for the Golden Cheetah project:
+
+<p><a href="http://groups.google.com/group/golden-cheetah-users">Golden
+Cheetah Users</a> is a list for submitting bug reports, feature requests, and
+constructive criticism.  It's a good place to search if you have a question
+that someone might have already answered.  It's also where we discuss new
+features, plans, etc.  On busy days there may be as many as 20 emails sent to
+Golden Cheetah Users.
+
+<p><a href="http://groups.google.com/group/golden-cheetah-announce">Golden
+Cheetah Announce</a> is a lower volume, moderated list where we post
+announcements of new releases, important bug fixes, etc.  If you don't want to
+get a lot of email, but you do want to know when we put out a new release,
+this is the list for you.  It receives one or two emails per month.
+

doc/web/make-release.sh

@@ -1,5 +1,6 @@
 #!/bin/sh
 # $Id: mkdmg.sh,v 1.2 2006/09/06 23:23:03 srhea Exp $
+export PATH=/usr/local/Trolltech/Qt-4.1.1-static/bin:$PATH
 VERS=`date +'%Y-%m-%d'`
 OS=`uname -s`
 CPU=`uname -p`
@@ -7,22 +8,24 @@ SUFFIX="$VERS"_"$OS"_"$CPU"
 rm -rf tmp
 mkdir tmp
 cd tmp
-svn checkout svn+ssh://goldencheetah.org/home/srhea/svnroot/goldencheetah/trunk goldencheetah
+svn checkout svn+ssh://goldencheetah.org/home/srhea/svnroot/goldencheetah/trunk/src goldencheetah
 cd goldencheetah
+qmake
 make
-mv src/gui/GoldenCheetah.app ..
-make clean
-rm doc/gc_*.tgz
-rm doc/GoldenCheetah_*.dmg
+mv gui/GoldenCheetah.app ..
+#make clean
+#rm doc/gc_*.tgz
+#rm doc/GoldenCheetah_*.dmg
+#rm doc/GoldenCheetah_*.tgz
 cd ..
-strip GoldenCheetah.app/Contents/MacOS/GoldenCheetah
-find . -name .svn | xargs rm -rf
-tar czvf src.tgz goldencheetah
 rm -rf goldencheetah
-SIZE=`du -csk * | grep total | awk '{printf "%.0fm", $1/1024+5}'`
+strip GoldenCheetah.app/Contents/MacOS/GoldenCheetah
+#find . -name .svn | xargs rm -rf
+#tar czvf src.tgz goldencheetah
+SIZE=`du -csk GoldenCheetah.app | grep total | awk '{printf "%.0fm", $1/1024+5}'`
 hdiutil create -size $SIZE -fs HFS+ -volname "Golden Cheetah $VERS" tmp.dmg
 hdiutil attach tmp.dmg
-cp -R GoldenCheetah.app src.tgz /Volumes/Golden\ Cheetah\ $VERS/
+cp -R GoldenCheetah.app /Volumes/Golden\ Cheetah\ $VERS/
 hdiutil detach /Volumes/Golden\ Cheetah\ $VERS/
 hdiutil convert tmp.dmg -format UDZO -o GoldenCheetah_$SUFFIX.dmg
 hdiutil internet-enable -yes GoldenCheetah_$SUFFIX.dmg