|
Re: Using A Scripting Language To Script Robot Behaviour
Quote:
Originally Posted by apalrd
1. I was not intending to writing raw XML. ...
2. If you had an autonomous editor, ...
3. On error, ...
|
That all sounds entirely reasonable; but the complications might detract from those benefits of using a scripting language that made you consider using one in the first place.
Regardless, have fun; and learn something.
Good luck on the fields,
Blake
PS: For my money, if I couldn't run any autonomous on a practice field, I would want to see the entire script run and get used to draw the route (and label the other actions) in a GUI; before I put the robot into a match with an untested, freshly-edited script. The graphics API would be substituted for the real robot's API inside the cRIO. Switching between sending the script's outputs to the graphics API or the real robot API(s) would be a mistake-proofed, 1-line change and would be reflected in the state of something you could see (an LED) if you briefly turn on the robot before a match.
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|