Re-doing the Dashboard code

[benbaptist]

I'd love to just completely start fresh with the dashboard. It's awful. I wrote a hacky little web server, the HTML/JS/CSS3 (client-sided) part of it all sucks, it's just awful. awful awful awful awful awful awfulaful awuflawufla.

Anyways, I've thought about moving to Flask, and to that extent, Flask-SocketIO. This means it'll be an extra dependency, but it would be super worth it. It's incredibly easy to work with, lightweight, and would be able to have a nice websocket connection WITHOUT a separate port (it'll run on the actual web server port). Any ideas or thoughts on this?

[suresttexas00]

I say use that dependency! LOL whatever makes the rest of it work better and is easier to use..

[JasonBristol]

Flask would be good! Looks like you are using bootstrap for the front-end. Is there a particular vision you have for the dashboard? Right now it looks like a remote server management console; in that case bootstrap might still be something we could leverage for the quick and dirty cross browser and mobile support, just would need to pretty it up some.

[Sasszem]

Flak looks like good, because it's lite 'n simple. It's perfect for local-hosted webpages.

[benbaptist]

It already uses bootstrap.

[JasonBristol]

Visualizations might add some flair to the dashboard as well, personally I think a visualized metric of player statistics would have benefit. I have around 20-30 players that play at all hours and being able to have a quick dashboard view to track player frequency, logons, etc would make scheduling random events easier. I think something like d3.js would come in handy there