Quote:
|
I personally prefer a mechanism based package structure for this reason. Something like this:
|
We create new packages for commands for each of the subsystems so they aren't all stuck in the base commands package. Makes it much easier to find what you want.
Code:
blah.blah.blah.blah.drivetrain.commands
My biggest complaint about RobotBuilder when we first used it was that it declared all of our motors and sensors in the RobotMap class instead of in their respective subsystems. Does it still do this?