frc1418 / victiscout Goto Github PK

This would be a test of your JavaScript skills. It seems a little pointless to be writing

<button class="decrease">-</button>

and

<button class="increase">+</button>

around every <input> with type="number" when we could just be generating them automatically for any such input (exempting those with the class large, like the input for team and match numbers) and inserting them appropriately into the DOM. This is not as hard as it may sound.

Defense crossings, goals, and basically anything with a "+" or "-" button can be negative.

Without the bash for windows you can't just install npm with apt-get or cURL. Maybe included into the readme a link to download npm

Probably some off-by-one error.

For the love of god, please. We need to finally update my lazy code from last summer.

I'm thinking of something like the one we use for VictiBot. It could be quite similar, but with black text. We use the font ADAM.CG PRO, same as on the website, FYI.

I suggest fitting auto on one line, widening the screen, and making notes much larger.

If you can do it, also allow editing of matches.

Perhaps include the date and username. The problem we were running into during competition was that people weren't deleting their data.json and it was being duplicated the next day. With some new vs improvements (conflict-removal) this issue should be mitigated, but it would at least be nice to not have to rename files when putting them on the pendrive.

When using "export" the file doesn't say where or that it saved at all.

When looking, it doesn't show up on my desktop, my home folder, or my documents.

OS: Ubuntu Linux 16.04 LTS.

Should be in one big array, not a bunch of objects squished together improperly.

It's not easily readable, and could result in someone selecting the wrong item.

After #49 has been completed, take a nice clean screenshot to replace the current one.

Ran command npm run-script package-win, got error

Fatal error: Unable to parse version string
 undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] package-win: electron-packager . --platform=win32 --arch=all --out ~/Desktop/Scout --overwrite --ignore=\.gitignore
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] package-win script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Owen Salter\AppData\Roaming\npm-cache\_logs\2017-12-01T23_30_27_652Z-debug.log

As a suggestion, perhaps create a folder in the default home directory of the user called something like scouting-data. This way, you know that you are saving to a valid location. Also, have the ability for the user to change the saved directory for the json output file so that it is convenient for the user, as well toggle whether or not the user gets notified of the data being saved to the json file along with it's directory location.

This isn't a terrific idea in the long term, but it would make a lot of things simpler. Plus, it's not like we're storing high-resolution images. One could scout every team for an entire competition and still not have more than 200-some kilobytes of data.

It just says Side. This is something we should track.

It's not really practical to maintain our own system for viewing and manipulating data. If there's a third party library for managing data, we should use that instead.

For those maniacs who want to scout multiple teams at once.

We can only put numbers into the Match input. We should be able to check a box or something to mark it as practice or playoff.

No idea why this happens.

They made sense last year for Stronghold, but not anymore really.

It seems there's a better way.

When we use electron-packager to build packages for macOS, the directories it outputs into dist/ are not owned by the proper user and require admin permissions to delete in Finder. Very weird.

Or move "reset" away from submit.

We shouldn't be keeping all files in root.

One idea for simplifying our current layout would be to move all the app icons into images/logo/ or something like that.

During competitions, we choose who will scout each robot based on that robot's position on the field relative to the bleachers. For example, "Furthest blue," "Middle Red," or "Closest blue."

This allows us to not have to worry about who's going to scout whom before every individual game. However, it can still become a headache as people leave the stands and new ones join. In the past, we've tried to counter this by handing out physical tokens (laminated notecards) designating each position, such that a scouter has to give their token to another person before leaving and nobody will ever forget which position they are to be scouting. These tokens, however, are easy to break, drop, and lose, and occasionally a distraction while scouting. I don't think we should abandon the idea yet, but we should experiment with a better way to handle scouting positions.

My proposal is to add an option to the VictiScout dashboard which would allow scouters to select which field position they're scouting. When selected, their position would be displayed in a prominent position such that other scouters can easily see it.

Since each person is scouting only one position on the field, it will seldom change.

For far blue, middle red, etc.

We should try changing all the JS code to TypeScript.

Every year we have to modify the scouting interface for the new game. This is quite an easy task, all you have to do is look at all the methods of scoring there are and change the elements in index.html accordingly. Right now, you can see from our main screenshot that we have inputs relating to high and low boiler scores and climbs. The methods of scoring in this game are different, so you'll need to follow the current code and replace those inputs. You won't need to touch things like the notes input or anything on the top bar. You may wish to incorporate images into the application if there are lots of ways to score. We did this in 2016 when there were nine types of defense for robots to cross.

You'll only need to know basic HTML for this, and you'll probably be able to comprehend it better if you know some CSS or even JavaScript.

As always, ask if you have any questions.

Here are some sample images of past years' interfaces:
2016:

2017 (Current):

Take a look at package.json, specifically the package* scripts. See if you can figure out how to make electron-packager use a custom icon when building the app. Just use logo.png, of course.

I was wondering if there is any way to attach the file to Firebase.

We should know if the robot can assist other robots in climbing. We should be able to track whether it can lift two robots at the same time, also.

It doesn't have to be an aggressive warning, but it should at least make it clear that nothing has gone wrong, there just aren't any submissions yet.

Even at fully maximized, the scroll bars appear.

OS: Ubuntu Linux, 14.04 LTS.

We're not allowed to host WiFi networks at competitions. One method some teams have used to circumvent this and avoid the time-suck involved in collecting data via USB drive (as we do currently) is to communicate via Bluetooth instead. I'd like to find some way we can replicate this (or use some other wireless transfer method).

In case you need it, I wrote a broken server for VictiScout last preseason. You can find that repository here. However, I think we'd be better off integrating the server capabilities of VictiScout directly into the app itself, such that anyone with their MacBook could click some buttons and become the host.

This is an advanced task, but it shouldn't be too difficult. Here are some resources which may help you start:

• https://github.com/song940/node-bluetooth
• https://github.com/sandeepmistry/noble

Alternatively, it might be a neat idea to handle some backend things in a lower-level language and drop JS to the extent that we can while still using (or at least being able to edit the GUI in HTML/CSS). Maybe Go?