-
Notifications
You must be signed in to change notification settings - Fork 129
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
Modernized, added package.json for easy npm install #55
base: master
Are you sure you want to change the base?
Conversation
* Library modularization inspired heavily by pjriot (http://bitbucket.org/pjriot/nodeim) * Remove dev server * Remove daemon library (not working) * Nix middleware scripts * Nix express.js usage
…compress * Client partially rewritten to support socket.io * Fix some typos in the server code that would cause it to crash on sess purge * Add xxtea library for client-side encryption of localStorage data * Convert theme.html to templates.js to simplify IM loading procedure * Uglifyjs crashes on xxtea library; temporarily disable until another solution is found * Remove google-compliler and build dir (for now)
* Localization file added (necessary for error/state message and date formats) * Message templates broken down further into containers and individual messages * Chat & friends list storage saving/restoration works
…chat store * Convert pngs to base64-encoded files and embed them in the default theme.css * Use autogrow.js library in place of home-grown textarea autogrow; new library is more reliable * Fix chat storage such that it restores and saves from/to the proper key
… reconnect * Sending messages between users now works * Setting status now works (status message not working yet) * Reconnecting setup * Temporarily disabled "not connected" tooltip
…talls, update uid() usage, update jade's new lack of ':' support
Conflicts: server/app.js server/dev/app.js server/dev/views/chat.jade
Has this been tested? |
The server component runs, and it merges in some things other forks have been working on. I haven't tested the actual clientside functionality (having trouble with figuring out how to use it, frankly) since I merged in the socket.io branch. Can you advise on getting the client installed on a testing page? I can update this pull request as I make progress. |
I'm interested but it seems like a big change. Could you tell me more about it? Is it still relevant? |
No description provided.