Quote:
Originally Posted by linuxboy
Wow, that framework looks extremely useful. Just checking that is something that any team can use within liscensing and FRC rules correct?
|
Yes, any team can use it, within the rules. I just checked, and <R67> from last year states "For the purposes of the FRC, generally available software modules obtained from open sources (e.g. professional publications, commonly used FRC community-accessible web resources, industry source code repositories, etc.) that are not specifically affiliated with individual FRC teams shall be considered COTS items, and may be used." Since it was published on Googlecode, which isn't affiliated with any team, and it was posted here, it's safe to use.
Quote:
Originally Posted by linuxboy
Also noobish question how would I go about linking in that library to another project or would I just open framework as a project(as I believe it is so, I don't have windriver yet though but the unix hidden files indicate so) and edit the Autonomous.cpp and Robot.cpp and their respective.h files and upload that?
Thanks, I know that was a bit convoluted
Oliver
|
It's not a noobish question at all. The way the framework is designed, you download the .zip and open it as a project. We should probably write this in a readme or similar, but you actually don't need to edit Robot.* at all.
The only files you need to change are:
- Autonomous.cpp
- Autonomous.h
- Defines.h
- Includes.h
- Tasks.h
- TaskTemplate.cpp
- TaskTemplate.h
The template file is the bare-bones implementation of a Framework task. Most, if not all, of the places you might need to change are marked with this comment:
You know, I'm going to go make a sample Task that does something really simple, just to give an example.
EDIT: Alright, I attached a sample task. This logs the x, y, and z axes of the first joystick, as well as demonstrates proxy::add, proxy::get, and proxy::set