![]() |
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
This is something I've been waiting for. Looking forward to the conference.
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
The conference is live now, for those of you who can't make it, I'm keeping some quick notes here
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Has anyone else had the meeting program lock up their machine?
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Thanks for sharing your notes.
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
Overall, I think they're taking the right approach with the whole project, and can't wait to test it out. |
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
I'm looking forward to the recording. The notes in the Google doc were also helpful. |
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
For those that weren't at the online webinar, they said we should sign up on this website for announcements instead of emails:
https://usfirst.collab.net/sf/projec...ty_developers/ And it looks like the first announcement is up! https://usfirst.collab.net/sf/frs/do..._documentation |
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
Quote:
|
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API
I'm pretty impressed with what's up so far. It seems the spec covers all the data that I could feasibly want (and more!).
There's really only two feature requests I can think of (which I'll put up on the tracker at some point): - It would be nice to have a single endpoint to get all of an event's matches, with score data when available. Currently, it seems like I'd have to do a request to get the event schedule and then do a second request for the results and overlay the two. It shouldn't be too bad to have an endpoint just like the results one, but returns all matches and nulls out the scores for the unplayed ones. - Push notifications would be awesome. But I understand those aren't a high priority at the beginning. Just keep them in mind for later while designing the system |
| All times are GMT -5. The time now is 08:30. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi