francisbyrne / hangwithme Goto Github PK

When deployed to Meteor.com, the client doesn't appear to have access to any of the collections it subscribes to, eg. Players.find().fetch() on js console returns just the current player.

May be related to Issue #1.

Appears to only occur in local version. Possibly due to Meteor upgrade 0.3 to 0.4

This isn't really an issue, but more of an idea.

How can you take the sharing space aspect of this, cross it with publishing short status messages, and give people the ability to log in and publish to a server simultaneously?

Thinking about the possibilities of Meteor... Let me know if you have any ideas.

When all players have left the game, the game should be removed from the Collection, along with all the players/letters/guesses. It appears to be done on the client side, but when you refresh the page, the game is back again. May not be propagating to the server, or the server may be overriding. Letters/Players/Guesses works as expected.

Alternatively, you could just disable the name input box instead of hiding it on invitation.

To fix this, the word would have to be decoupled from the game and kept server side. Server masks it before sending down to client.

The new auth model in Meteor means that you need to allow updating Mongo collections, so all the database methods have broken. Must refactor to work with Meteor 0.5.0.

Should really do this.

After completing a game and clicking "Back to Lobby", the players waiting no longer shows, even if there are players waiting.

Currently no way of cancelling an invitation. This is annoying when you invite an idle or d/c'd player.

Hangman image needs to be redrawn for both players (not just declining player) when player declines invitation. Need to think about how to do this. Can probably also implement decline notification for this.

My word was "circumfusion" and the word wrapped down to the next line. It should expand the main window to the width of the word, or you should make it big enough to hold the biggest word.

http://min.us/lbpZNlv2VkFn1Q

Compared to examples on the meteor website, the performance for hangwithme is very choppy once deployed to meteor.com.
Looking at network analytics (via chrome dev console), it appears this may be due to large message sizes (1mb+) going back and forth from client to server.

Need to work out why this is happening and reduce the size.

Previous commit has stopped the letter validation methods working.

No unit tests... bad, very bad.

Whenever an opponent is selected in the lobby, the select box de-focusses and the option appears to be de-selected. However, Multiplayer start button still appears and you can still start the game. UX issue though.

Some xhr's are returning 404s when deployed to meteor.com. Not sure what the impact of this is, or whether it is expected; but might be causing some of the unexpected behaviour on the server.

This appears to happen every time the keepalive is sent because the Players Collection changes and the viewport is dependent on that, so it re-renders.