Skip to content

v0.0.3-alpha

Pre-release
Pre-release

Choose a tag to compare

View all tags
@nfoert nfoert released this 10 Dec 20:17
· 488 commits to main since this release
v0.0.3-alpha
adf3933
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release implements a menu which gives users quick access to settings and other pages, makes Open Scouting work if there's poor or no internet connection, handles the process of uploading reports that were submitted offline, and keeps reports backed up locally.

image

In this release:

  • Collapsible menu for settings and application state
    • Show a clock
    • Indicate offline/offline status
    • Basic notification system
    • Buttons to link to useful places (home, issues, releases, ect.)
    • Dark mode toggle
    • Credits and attributions section
    • Developer settings section allowing the user to clear the service worker cache
    • Toggle for manually going offline
  • Add a roadmap to describe when changes should be implemented
  • Offline support
    • Pages and other static data are automatically cached by a service worker
    • Reading from the cache is cache first - First it's attempted to be fetched from the cache before falling back to the network
      • This is able to be toggled to the opposite in a developer setting inside the menu, useful for when testing changes quickly and preventing needing to clear the cache every time a file gets a new change
      • Manually going offline causes the service worker to only look for items in the cache and doesn't try to use the network, useful for when there's very poor connection and it's not worth the potential for the site to freeze while a request is timing out
    • The user can't view data when they're offline
  • Characters needed encoded in the URL parameters
  • Events weren't getting created properly in get_data()
  • Data objects now have a UUID
  • Any scouting reports are now automatically backed up to the client. Then, the user can check to ensure that these backed up reports have indeed been uploaded to the server
    • The user can also clear these local reports from inside the submenu
  • While the user is offline, any submitted scouting reports are saved locally
    • The next time the user goes online, the user is reminded that they have reports which can be uploaded. The user can upload these from inside the menu
  • README improvements

Issues closed:

  • #24 - Implement a collapsible menu
  • #14 - Add a dark mode toggle
  • #4 - Attribute The Blue Alliance
  • #17 - Offline use of the application
Assets 2
Loading