nbonfire / hitztourney Goto Github PK

an Undo button should delete the last submitted matchup result. This would be useful in situations where there was a mistake made, or a result was accidentally submitted multiple times.

use flask, jinja, and ajax/server-sent-events instead of cherrypy, mako, and websockets

The Stats page needs a header row, so that titles like "Lifetime" and "Record" don't need to be called out in every row.

I think this would be the column titles for the current way it is layed out:

Rank, Name, Current Season Rating, Lifetime Rating, Lifetime Record

Currently, the "Choose Players" section lists each player's current season HitzSkill rating, then their lifetime rating in parentheses. Since the matchup algorithm uses the lifetime rating, it would be more simple to just list the lifetime rating, and not the current season rating. The current season rating is not very important, and can still be viewed in each player's "User Stats" page. This would also clean up the list of players in the "Choose Players" section, so that it only lists each player's name and their lifetime rating.

Currently, the JSON output is sorted alphabetically. Ideally, it should be sorted as the fields are listed in the script. This order is the same as the order the stats appear in the save file

It would be great to have hitzSaveRead output CSV. This can either be an option, replace, or add to the existing JSON output.

Do not print the first line, which lists the columns. It currently looks like this:

id,date,istournament,playerid,name,assists,games_played,games_played_actual,goals,hits,one-timer_goals,one-timer_shots,passes,shots,unknown01,unknown02,unknown03,wins,wins_actual

A user's "Game History" currently only shows the results from the current season. It would be good to either show all games played, by default, or have an option for this.

currently "next match" shows the match being played, not the match after. We should probably show this, next and the one after that.

Based on work done for #15 this will be an issue. Sometimes we don't want to erase someone's info so a third party will use their name.

Maybe its not a problem to delete old handles anymore since we track users in the database.
Maybe we shoudl just make newbs use blank names?
@johnz1 What do you think?

Need to create sub-templates to make everything consistent (header, etc)

I know the colors were set when you copied the code, but could you change the winners to be green, losers to be red, and both teams blue or white if the winner hasnt been determined?

1.) use opl to host the save file on a server
2.) Monitor the file
3.) Read the file and interpret it (see https://gist.github.com/nickdanger3d/c4f96de496f2cfc4365d )
4.) Detect changes from the last read
5.) use changes to figure out who played a game, and add that game to our database.

Could the winning percentage be displayed as an actual percentage, or decimal value? Currently, it is displayed as a value without the decimal. e.g. If someone is 5-5, it will say "500", not "50%" or ".500"

The columns in the table on the Stats page should be something like this:

Rank, Name, Lifetime Rating, Current Season Rating, Lifetime Record, Current Season Record

Currently the date column gives the date, month, year, hour, minute, and second. Remove the hour, minute, and second, and just output "year-month-day".

It currently looks like this: 2016-08-10 23:25:22.146248
Change it to look like this: 2016-08-10

(see email from 10/23/15)

Currently, the Game History (in the User stats page) isn't sorted, and displays each game by when it was entered into the system. The game history should be sorted by the date that the games were played.

mysql or sqlite, probably sqlite to keep it more portable

Next to the match number, you can remove the "on the _ TV" text. Just "Samsung" or "Sony" is fine, and is less cluttered.

The name of the event is "2013 HITZ 4/20 Classic", not "HITZ 4/20 Classic 2013".

Not a big deal...

We need to build-in some kind of tiebreaker logic (probably should be performance vs each other. If still tied after that, raise a flag maybe

ideally tweakable.

For some numbers of players, there are back to back byes. We need to reorder the schedule so that doesn't happen.