|
Re: What have you developed or are in process of developing?
Last night, I got a prototype working of a set of buildscripts as part of my team's code framework that lets us download our code to either the roboRIO or the cRIO, both with Java 5 features (or 8 on the roboRIO), from the exact same project.
Essentially I ripped out all of the internals from the WPILibJ 2014 SDK, added in Retrotranslator, built a new version of the preverifier executable, modified the build process for faster building, and then put everything into our shared buildscript. The current complete build process for this goes:
When our framework changes: Build CCRE Core Jar file, Build pre-Igneous library packages, Compile Igneous code (Java 1.5), Unpack pre-Igneous libraries, Retrotranslate libraries (except for stub StringBuilder class), Preverify libraries (with upgraded preverifier), Build post-Igneous library packages.
When our code changes: Compile Robot Code (Java 1.5), Retrotranslate Robot Code, Unpack post-Igneous libraries without StringBuilder stub, Preverify libraries (with upgraded preverifier), Package application Jar, Romize Robot Code Suite, Download and Erase Robot Logfiles, Possibly upgrade Squawk release, Deploy Robot Code Suite, Reboot Robot via OTA, open cRIO console.
I'm still getting it to work even if you don't have the roboRIO plugins installed, and once we have that, our entire software team can switch over to Eclipse for code development and the only thing that they'll need to do to target the roboRIO once the build season starts is to install the roboRIO SDK plugins and press a different download button.
I'm also working on upgrading the Poultry Inspector application (named as such because our team is "The Flaming Chickens"), which is a dashboard replacement that uses our team's pub/sub networking protocol (named Cluck, for similar reasons as before.)
I've been upgrading it to have a cleaner interface (SuperCanvas) designed to work well with a touchscreen, and I'm working on extending it to have more options for interaction.
Other goals for the near future: write Eclipse plugins for our code framework, add built-in Mechanum support, add a virtual patch panel system to reconfigure I/O at runtime, add a more robust configuration toolkit, build a unified automatic deployment system, and other miscellaneous features.
__________________
Software manager alumnus. Developer of the CCRE, a powerful robot code framework based on dataflow and composibility.
Refer to as she/her/hers. Years of FRC: 2012, 2013, 2014, 2015, 2016. FLL for a few years beforehand.
Team 1540: The Flaming Chickens | Portland, Oregon | Twitter | Facebook
Last edited by Cel Skeggs : 04-10-2014 at 13:31.
Reason: Minimized length of long post.
|