-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web interface overhaul #10
Comments
[ ] Should use websockets |
Do I dare ask, which version of Angular? |
1.x? |
I think the web interface could be its own repo, and I think angular would be overkill. I think a basic web interface is all we need (Jquery and angular aren't really comparable: one is a set of utilities the other is an entire MVW framework) |
Yeah, no need for anything fancy. Some REST APIs, flask-socketio, and a simple enough design will probably suffice |
In terms of my side of things, I cannot stand working with angular 1.x. As soon as you go off the beaten track, and not trust in the magic they give you, everything gets messy quickly. I've had much happier times with react, although that doesn't play well with jquery either (but I'm ok with that) |
I'm happy with rest apis, will need to look into flask-socketio though. |
I can do Flask-SocketIO, if you do the frontend part of SocketIO |
sounds good |
Closing this as there is now a dedicated repo for web. |
We'll be overhauling the web interface.
[ ] Should use better storage method of game state
[ ] Should use AngularJS instead of jQuery
The text was updated successfully, but these errors were encountered: