aidanbdh / quantum-entanglement Goto Github PK

• Make sure travis is running all tests correctly.

• Add in code coverage test for travis.

• Reset toggled if disconnect.

• Reset toggled if connection refused.

• Add socket event on disconnect.

• Add cursor removal.

• Add disconnect notification.

• Change host if host disconnects.

• Add chat notifications.

• Add shortcut to open chat dialogue.

• Add output file with a log of chat messges.

• Add tests for server.

• Add tests for connect.

• Integrate travisCI

• -i --incognito flags for no notification on connect or cursor color.

• -w --watch flags for no editing abilities or cursor.

• -o --options flags enable only following options for server connect. (-o -w allows only the watch flag to be used)

• -p --private flags require password.

• -t --test flags for tests.

Corresponds to issue 5 of quantum-entanglement-website aidanbdh/quantum-entanglement-website#5

• Add prompts for asking if registered user.

• If user, prompt for name and get info from website db and use that name and color.

• Research Atom repository info.

• Add prompts and notifications for repository connection.

• If different, give the branch and repo name and a link to git clone.

• Save number of connections.

• Increment and decrement number on connect or disconnect.

• If no connections, delete room data.

Corresponds to issue 6 of quantum-entanglement-website aidanbdh/quantum-entanglement-website#6

• Research getting Github login through Atom.

• Repopulate colors array after it is empty.

• Get root file.

• Match all files on connect.

• Add path to event and change files based on path

  • Only update on open?

• Add socket event for moving the cursor.

• Create data structure for cursors.

• Create new cursor when a user connects.

• Display cursor.

• Make cursor different colors for different users.

• Add name option for connection.

• Add notification for user connecting.

Data Structure:

[ { color: 'hex', name: 'string', object: 'Atom Cursor' } ]

On Connect:

Save array of cursors and create Atom Cursor object and assign to object property.

On Disconnect:

Delete cursor.

On Change:

Reassign cursor position based on new location.

If no changes by self for 2s:

Show other names above cursor.

• Delete server files.

• Publish major.

• Create localhost node server with socket.io.

• Create a socket.io connection and send events across the connection.

• Receive events and update text.

• Change alerts to better fit Atom's base theme styling.

• Research Heroku servers and see how to handle different file connections.
  • Add command to command palette to connect to or host a server.
  • Add view element for inputting connection unique name.
  • If connection exists, connect to it by url/uniquename else create new server.
• Before connection, compare Files. If different, offer to change to match or refuse connection.

• Research Atom plugins and decide how best to implement connection, login, updates and settings. https://github.com/aidanbdh/atom-plugin-testing

• Research Socket.io. https://github.com/aidanbdh/socket.io-testing

• Register Plugin. https://atom.io/packages/quantum

• Make plugin downloadable. https://atom.io/packages/quantum