https://github.com/spikes-2212-programming-guild/spikeslib2

A library extending WPILIB with extra features, for the 2020 season onward
https://github.com/spikes-2212-programming-guild/spikeslib2

first-frc frc robotics-competition wpilib

Last synced: 2 months ago
JSON representation

A library extending WPILIB with extra features, for the 2020 season onward

• Host: GitHub
• URL: https://github.com/spikes-2212-programming-guild/spikeslib2
• Owner: Spikes-2212-Programming-Guild
• License: mit
• Created: 2019-11-23T12:58:26.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2024-05-20T10:57:23.000Z (7 months ago)
• Last Synced: 2024-10-10T03:02:53.154Z (2 months ago)
• Topics: first-frc, frc, robotics-competition, wpilib
• Language: Java
• Homepage: https://www.spikes2212.com/spikeslib
• Size: 1.23 MB
• Stars: 7
• Watchers: 3
• Forks: 2
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        

SpikesLib

SpikesLib is a library that extends WPILib written by the FRC team The

Spikes#2212.


Examples

Examples of how to use the library can be found here.


Packages


- command - extensions for WPILib's Command Based framework

- control - controller wrappers and custom controllers

- dashboard - wrappers for SmartDashboard elements

- path - path following code and pure pursuit algorithm

- util - additional utilities

Installation

After creating a Robot Project, import SpikesLib as an online vendor libray, using this link: 
 


https://spikes2212.com/SpikesLib.json


2024 Season


Spikeslib has been  updated  to support WPILib 2024.

2023 Season


Spikeslib has been  updated  to support WPILib 2023.

2022 Season


Spikeslib has been updated to support WPILib 2022.

2020 Season


For this season, SpikesLib has been moved to this repository due to the extensive changes in WPILib. 


The old version is still available at the [old repository](https://github.com/Spikes-2212-Programming-Guild/SpikesLib).

Development

SpikesLib is developed in a feature branches workflow. 


All feature branches are merged into dev branch after testing, which in turn is merged into

master after it passing complete testing 


Branches should be named according to the following convention - name_package_feature


Help us out!

We accept help from everyone! 


If you want to contribute, simply create a branch and open up a pull request, according to the instructions above.