Skip to content

Debugging and Testing

Jump to bottom Edit New page
James Errington edited this page Jun 22, 2017 · 1 revision

Debug

Adding a debug query (?debug) to the call to rg2 will download the uncompressed .js files rather than rg2-x-y-z.min.js. This originally made debugging easier on live sites, but the maps now sort that out. It is retained to avoid having to build everything after every change in the local test environment. Yes, I know Webpack would do that, and one day it will get closer to the top of the list of things to do.

The debug setting is also activated if you are using an rg2-override-config.php file.

example: http://www.happyherts.routegadget.co.uk/rg2?debug

Touch interface

After testing a number of possible touch interface solutions it turned out that a simple home-grown solution worked best. Therefore the touch interface does not include any libraries. This might change when jquery-ui adds support for touch, which is meant to happen somewhen.

Testing

See the RG2 Protractor test set-up

Add a custom footer

User Guide

  1. RG2 page layout
  2. Events tab
  3. Courses tab
  4. Results tab
  5. Draw tab
  6. Replay control panel
  7. Display options
  8. Useful things to know

Manager Guide

  1. Installing RG2
  2. Using the RG2 Manager
  3. Map File Guidance
  4. Adding Splitsbrowser Integration
  5. Georeferencing Maps
  6. Setting up Relays
  7. Language Configuration
  8. Events with no Results or Split Times
  9. Security and Caching
  10. Adding a new routegadget.co.uk site
  11. Timed out road crossings and adjusted splits
Clone this wiki locally