Use d3 to make svg widgets of the robot. side view and top down. side view should show whether the wheels are running and the current height of the forklifts. the topdown widget should rotate using the gyroscope and show crate distance using the distance sensors.

testing page is receiving blobObjects instead of text when messaging the server. Turn them into text.

line 63 in testingpage

http://bost.ocks.org/mike/bar/ is a good tutorial

Here's a solution to your SD values that have problems in them -- this uses encode/decodeURIComponent to do the work for you, which should be pretty fast and makes the variables easy to understand.

http://jsfiddle.net/n1117h5p/

Can't be on the internet AND on the robot network at the same time. Embed it!

This task is for Leon (@lleontan) and Jacob (@kcodes7 ?)

Javascript/HTML stuff

• Learn about HTML 5
• jQuery
• Bootstrap 3
• d3.js

Python

• Tornado is an awesome python framework you can use to create a standalone web server: http://www.tornadoweb.org/en/stable/
• Python actually already has a built in web server you can use, I integrated one into wpilib for some experimental stuff: https://github.com/virtuald/pyfrc-html-interface

I've done a number of fixes in testingpage.html. port them over to the other files.
They are.
-fixed/updated import urls for bootstrap,css jquery
-cleaned up code

They should only be visible when the autonomous mode they're associated with is selected.

This is important to make sure we don't mess it up!

UI_MainPage page should have-

1. imports for d3, jquery, and SocketController.js
2. ids for html elements
3. sample text inside the buttons

get the array from keyStore.

This means that when the driver switches the forklift position, the buttons should clearly show the currently targeted position (or none if in manual mode).

Additionally, when the button is clicked, then it should also change. However -- you don't need to do that in the onclick button -- if the robot code is working correctly, then it'll set the targeted position and the UI will show that.

Talk with the robot team to identify what sensors we need to make it happen. At the moment the robot doesn't have limit switches to detect collision with totes. Are the distance sensors accurate enough or do limit switches need to be installed?

Put files in folders. update the paths for stuff in the files so stuff still works.

1. Implement new layout
2. Implement new liftTo buttons
3. Finish top down visual
4. Finish side view visual
5. Fix encoding
6. Implement Camera Feed
7. Move Timer

UI_SettingsPage should be divided into RobotSettings.html,AutonomousSettings.html,VisionSettings.html, and GuiSettings.html

in testingpage make the form message the server when the user presses enter. currently only works when the button is clicked.

In order of importance

1. driver buttons

*enable/disable auto-acquire
*set forklift positions
*drop buttons

2. Settings
*autonomous *vision *forklift *persistence(cookies)
3. visual robot representation
vertical and side view
4. stored settings
5. game clock
6. other
<><>

After build season is finished we need to get the camera feed from the robot and display it on UI_Mainpage

The networktables support needs to be extended to allow selecting a particular autonomous mode. Probably will need subtable listener support to make this work.

Run the robot code once frc1418/2015-robot#27 is merged, and you'll see what you need to do. The 'outline viewer' can help out too.

make a fake networktables that can communicate with the tornado server.

Items in the same group have the same string before |, and should be shown together.

The robot and driverstations need to have the same id's. coordinate with the robot team so we can set the same values.

put the information in your notebook online so we can see it anytime!