Bug #71
Add Robot Information Pages
| Status: | New | Start date: | 02/19/2012 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | Tim Buckley | % Done: | 30% |
||
| Category: | Data | ||||
| Target version: | 2.0 | ||||
| Resolution: |
Description
- No data about the design of the robot
- No pictures of the robot
- The database backend hated them
While we had useful data about some Logomotion game statistic like minibot times and which targets the robot could place the game elements on, it was essentially limited to scouting information. However, this data is really only useful during the competition and doesn't help build any sort of useful historical information about robots, such as information about the design and other technical information that would be helpful to teams down the line.
The new proposal is to rewrite them from scratch and focus specifically on the design of the robot. In particular, we want to collect pictures of the robots (via the new content APIs), as well as each of the subsystems of the robot (such as arms, shooters, drive systems) and allow teams to describe them.
Currently we're in the process of creating an interface that will:- Allow users to easily input information about the robot structure (e.g. it has a Shooter which contains a Lifter and a Launcher, etc)
- Upload pictures and videos of each component (e.g. CAD schematics, demonstration videos)
- Associate the components graphically according to the structure hierarchy
Ideally the interface should initially show a picture of the robot. It would then show outlines over each of the direct child components of the main robot (e.g. Drive, Shooter) similar to face tagging in Facebook and other social sites. When a component's region is selected, it should zoom to show a picture specifically of the component, or highlight the component (and its children) on the main robot picture. Additionally, it should show any defined descriptions, statistics, or comments that have been associated with the component. The interface should also allow these regions to be defined and modified easily by users.
There's an in-progress demo implementation that can be found at source:src/main/webapp/robot/robottest.html and can be tried on the test site here. It's being implemented with an HTML5 canvas but should also have image export capabilities for a possible mobile app or fallback for older/mobile browsers.