You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many subsystem are not properly handling their respective systems. They also suffer from random sysouts and obfuscation which only serve to make the code more difficult to read, understand and use. Subsystems should act as interfaces to the components we want to control and avoid automating process for the user to control. These automated process should be contained within commands when possible.
Vision
Exctract extranous behavior into commands and remove obfuscation by making subsystem classes handle less but provide more options to their respective systems .
Guidelines
Subsystems should NOT do any of the following
directly access controller inputs
manipulate input values for purposes other than conversions
mechanisms using relative positions
contain override methods designed to forcible take control, other than for the purpose of disabling
Subsystems should CONTAIN the following
methods converting motor rotations to easy to use values (relative rotations, degrees)
The problem
Many subsystem are not properly handling their respective systems. They also suffer from random sysouts and obfuscation which only serve to make the code more difficult to read, understand and use. Subsystems should act as interfaces to the components we want to control and avoid automating process for the user to control. These automated process should be contained within commands when possible.
Vision
Exctract extranous behavior into commands and remove obfuscation by making subsystem classes handle less but provide more options to their respective systems .
Guidelines
Subsystems should NOT do any of the following
Subsystems should CONTAIN the following
Tasks
The text was updated successfully, but these errors were encountered: