aaron235 / messageworks Goto Github PK

It goes behind the button; the input needs to be less wide.

Big and scary.

Possibly in the same area that the "disconnected from server" message apperars. This should be done with JSON and Websockets, not JavaScript.

This might require a dynamically sized send box, and some modification in websocks.js.

http://stackoverflow.com/questions/6014702/how-do-i-detect-shiftenter-and-generate-a-new-line-in-textarea/6015906#6015906

Desperately needs fix.

some simple js.

Proposed solution: Redirect to an error page that suggests you to either create a new room, or join the room that already exists that you just created.

Possibly add a direct file writer for log flies, and have the server accept flags for level of verbosity.

Possibly an embedded chat thingy or a link to the about page or to start a new chat.

Because it's really dumb to not have that

Already fixed, filing an issue on it for consistency

Preferably written in inline POD.

Right now, error page titles [which should be identical to the

tag contents in the error page file] are hard-coded in a perl switch statement. They should be parsed from the HTML, to ease the error-adding process and prevent title/h2 mismatches.

Need a separate database containing a document for each room with values for name, privacy, and open date (or more things), and this database can look up the other rooms by collection name, which will contain a document for each message, housed by nothing.

The best solution is probably to avoid writing any whispers to the database ever because of the private nature of them

Self-explanatory.

Typing @[randID] for a valid randID should create a whisper.

• Clicking a user name in the users list or messages should add the "@RandiD" to the start of the input field
• @@ should auto-replace to the randID of the last person who sent you a whisper.

Whisper @NAMEs should be specially formatted [if valid].

Send it like

Bug455

Rug788
Martin
Hug700

or something better. That way user @Formatting and stuff can be done in JS without any additional server queries.

Dragging a file onto the chat window should show an "Add" cursor. The file should be fast-checked a) for file size [shouldn't be bigger than 2mb or so] and b) to be sure it's an image. If both tests pass, the image gets converted to base64 encoding and inserted into the chat as a single message. Otherwise, display an error in the infobar for ~5sec and fade it out.

How to do:

• JS accepts image file, tests, converts to base64
• Perl recognizes data:image/png;base64,asdjfla;ksdjflaksdj links and properly formats them

Put the arrow message history navigation and formatting of the user list in this

so it can be tabbed to and stuff and also have an active state and whatever i dunno

Call MongoDB to get the last 128 message lines, and then ws send them to the new user's controller, as JSON, in order.

Might require an 'm.messageworks.com' subdomain, but this needs to be done.

like in every other chat ever except irc and probably some other stuff

Make the background color of the message div the same hue as the user's color, with only 10% saturation. (Or possibly the same hue and saturation with white text instead of black?)

The offending line: app->log->debug( "Users->new: created new user with randString $self->{randString}" );

Fix plz