Offseason UI/Internals Refurbish #8

Merged
1withspaghetti merged 62 commits from dev into main 2024-10-02 00:32:52 -05:00
1withspaghetti commented 2024-04-24 13:02:16 -05:00 (Migrated from github.com)

I am going to start off by apologizing for the 73 changed files and 2.7k additions. I definitely should have broken this up into multiple pull requests, but it is too late now. Thank you so much to those of you who even glimpse at everything and leave helpful feedback 🙏

This PR includes many UI changes, especially loading indicators and error messages, as well as a fundamental change to how extra match data is handled internally. I also documented a large amount of the code and plan to do more in the future. Additionally, the README file now includes instructions and screenshots for how to use/manage the scouting app.

These commits are the result of a lot of feedback and plans I wanted to do before our competitions but never got around to completing. I made these changes to avoid repetitive code and make migration to new games easier once the next season starts. The UI changes also make everything more intuitive and user-friendly, as well as provide extra features such as a pick list for scouting leads.

I want this code to look professional and industry-level, or at least close to that. Mentors, I doubt you hear this often, but I WANT your nit-picky comments, your barrage of questions, etc. I need this code to be easily understandable so future students can work on it effectively.

For the purpose of testing, I attached two zip files representing all the data we collected during our two competitions. You can import them on the data page and play around with the new UI.
You can view an online preview on the website by clicking the link sent by the vercel bot in the comments of this PR.
Scouting Data - 8248 - 2024wasam.zip
Scouting Data - 8248 - 2024wasno.zip

Trello card for these tasks: https://trello.com/c/iDm72GPd/118-scouting-app-refurbish-for-next-season

I am going to start off by apologizing for the 73 changed files and 2.7k additions. I definitely should have broken this up into multiple pull requests, but it is too late now. Thank you so much to those of you who even glimpse at everything and leave helpful feedback 🙏 This PR includes many UI changes, especially loading indicators and error messages, as well as a fundamental change to how extra match data is handled internally. I also documented a large amount of the code and plan to do more in the future. Additionally, the README file now includes instructions and screenshots for how to use/manage the scouting app. These commits are the result of a lot of feedback and plans I wanted to do before our competitions but never got around to completing. I made these changes to avoid repetitive code and make migration to new games easier once the next season starts. The UI changes also make everything more intuitive and user-friendly, as well as provide extra features such as a pick list for scouting leads. I want this code to look professional and industry-level, or at least close to that. Mentors, I doubt you hear this often, but I WANT your nit-picky comments, your barrage of questions, etc. I need this code to be easily understandable so future students can work on it effectively. For the purpose of testing, I attached two zip files representing all the data we collected during our two competitions. You can import them on the data page and play around with the new UI. You can view an online preview on the website by clicking the link sent by the vercel bot in the comments of this PR. [Scouting Data - 8248 - 2024wasam.zip](https://github.com/ChainLynxRobotics/ScoutingPWA/files/15098508/Scouting.Data.-.8248.-.2024wasam.zip) [Scouting Data - 8248 - 2024wasno.zip](https://github.com/ChainLynxRobotics/ScoutingPWA/files/15098511/Scouting.Data.-.8248.-.2024wasno.zip) Trello card for these tasks: https://trello.com/c/iDm72GPd/118-scouting-app-refurbish-for-next-season
vercel[bot] commented 2024-04-24 13:02:23 -05:00 (Migrated from github.com)

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
scouting-pwa ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 2, 2024 5:23am
[vc]: #EJAOEiverHVvpBz6j0KlS0tCweup9GKIh0Xoo/ZVAqU=:eyJpc01vbm9yZXBvIjp0cnVlLCJ0eXBlIjoiZ2l0aHViIiwicHJvamVjdHMiOlt7Im5hbWUiOiJzY291dGluZy1wd2EiLCJpbnNwZWN0b3JVcmwiOiJodHRwczovL3ZlcmNlbC5jb20vY2hhaW5seW54cy1wcm9qZWN0cy9zY291dGluZy1wd2EvNFZQdVM1ZDV0dGRQNzVTbXlwdkJ3ckNLS0t5RSIsInByZXZpZXdVcmwiOiJzY291dGluZy1wd2EtZ2l0LWRldi1jaGFpbmx5bnhzLXByb2plY3RzLnZlcmNlbC5hcHAiLCJuZXh0Q29tbWl0U3RhdHVzIjoiREVQTE9ZRUQiLCJyb290RGlyZWN0b3J5IjpudWxsLCJsaXZlRmVlZGJhY2siOnsicmVzb2x2ZWQiOjAsInVucmVzb2x2ZWQiOjAsInRvdGFsIjowLCJsaW5rIjoic2NvdXRpbmctcHdhLWdpdC1kZXYtY2hhaW5seW54cy1wcm9qZWN0cy52ZXJjZWwuYXBwIn19XX0= **The latest updates on your projects**. Learn more about [Vercel for Git ↗︎](https://vercel.link/github-learn-more) | Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **scouting-pwa** | ✅ Ready ([Inspect](https://vercel.com/chainlynxs-projects/scouting-pwa/4VPuS5d5ttdP75SmypvBwrCKKKyE)) | [Visit Preview](https://vercel.live/open-feedback/scouting-pwa-git-dev-chainlynxs-projects.vercel.app?via=pr-comment-visit-preview-link&passThrough=1) | 💬 [**Add feedback**](https://vercel.live/open-feedback/scouting-pwa-git-dev-chainlynxs-projects.vercel.app?via=pr-comment-feedback-link) | Oct 2, 2024 5:23am |
pixelmonaskarion commented 2024-08-29 16:33:23 -05:00 (Migrated from github.com)

Tyler awesome work this app works really well! I was able to get it as a pwa on my iphone while offline. I only had a major problem with the qr code scanner, but I also have some other feedback as well. I think it would be good for you to look over all my comments before we merge your commits. Also sorry for taking 4 months to review your changes.

Never change existing field ids in protobufs. This causes old data to be parsed incorrectly.
I can't get the qr code scanner to work. :(
IMG_D34037120DF6-1
I found some weird selections issues when tapping on data entries in the data page list.
I can create matches with blank ids which seems unintended based on code in Success and error toasts on data page
it may be cool for crossed out picklist items to go to the bottom automatically.
There's a lot of UI at the bottom of the picklist that should definitely be at the top because the list gets really long
'fully' and other places in the README are not underlined but are in <u> tags (I don't think those work in markdown)
CLAW is an awesome name 😄

Tyler awesome work this app works really well! I was able to get it as a pwa on my iphone while offline. I only had a major problem with the qr code scanner, but I also have some other feedback as well. I think it would be good for you to look over all my comments before we merge your commits. Also sorry for taking 4 months to review your changes. Never change existing field ids in protobufs. This causes old data to be parsed incorrectly. I can't get the qr code scanner to work. :( ![IMG_D34037120DF6-1](https://github.com/user-attachments/assets/76dec1dd-29c0-45ee-af93-aa8ad23bcc18) I found some weird selections issues when tapping on data entries in the data page list. I can create matches with blank ids which seems unintended based on code in [Success and error toasts on data page](https://github.com/ChainLynxRobotics/ScoutingPWA/pull/8/commits/a51ebd5a8890fdb8002ad5ca09a027f89963da7d) it may be cool for crossed out picklist items to go to the bottom automatically. There's a lot of UI at the bottom of the picklist that should definitely be at the top because the list gets really long 'fully' and other places in the README are not underlined but are in \<u\> tags (I don't think those work in markdown) CLAW is an awesome name 😄
1withspaghetti commented 2024-09-19 23:15:49 -05:00 (Migrated from github.com)

All issues should be addressed except for the "weird selection issues" on the data page. I wasn't able to recreate any of these, so I don't know how to resolve them.

All issues should be addressed except for the "weird selection issues" on the data page. I wasn't able to recreate any of these, so I don't know how to resolve them.
1withspaghetti commented 2024-10-02 00:31:41 -05:00 (Migrated from github.com)

Force pushing this because I don't want to force somebody to go through even a fraction of the pain it took for me to write this. Just message me on slack or make an issue if there are any problems you see rn.

Force pushing this because I don't want to force somebody to go through even a fraction of the pain it took for me to write this. Just message me on slack or make an issue if there are any problems you see rn.
Sign in to join this conversation.
No description provided.