wiktor-obrebski / client.io Goto Github PK

Emits events with empty body should be possible. Now we got alert message.

In most cases user will just want create json object as argument. It should be done easier than writing all json code. Think about it, project and create something awesome!

Things to check: can we use more than one argument in from socket.io emit?

Standard, very basic event mechanism for our objects. on and emit, per current object.

Test server should also react to '*' events in some way. Probably echo it back.

We need two inputs, one for event name, second for event body - that can be string, number, array or any other js object. Eval function should be used.

When hit enter on event name input, or press "emit" button event should be emitted by provided 'socket' object (standard socket.io socket).

In first version it should be as simple as possible. No css, any special structures.

ATTENTION: we use git flow branching system. check this links:
https://github.com/nvie/gitflow
http://vimeo.com/16018419
edited: it's not necessery

On modal to server connect we need list of last connected servers to easy pick best server without remembering full address.

My advice is to use typeahead control. JQuery ui?

Use "local storage"!

Socket.io 1.0 is here! Is not longer in beta stage.
We MUST give support for this version or all this shit hasnt any sense.

After first site fetch user should see modal window where he can write server address to connect. On this address user must have proper node.js + socket.io app running.
Next user click 'connect' to connect to server ;)

Our app will fetch socket.io-client.js file from this address (it already done in connect.js file).

BIg list that aggregate all events - received and emitted. Should show event name and args. Should override socket methods and base own functionality on it.

Emits history list, working similar like in POSTMAN. When user click emit from list it auto-complete event-id and event-body for him.