Distinctive features thread.

Check (and post if yo want) comments.

Features:
Generality:
I intend to implement configurability, so it can be used as either a chat room, an instant messenger system, or a support system.

Technical: A small script in the page checks to see if the client needs to be loaded. If there are any messages/chat invites/support invites for them, the client is loaded automagically. They can also click a link to start the client themselves.

Variable key: The key (what identifies the user) could be a cookie(temporary), an IP address, or anything really. It will be generic so we can choose and configure this. This also helps with generality and allows us to use existing login systems (hopefully).

Configurability/Extensability: Because everything will (hopefully) be well designed and documented with a lot of configuration options it will be easy to improve, extend, and repair. For instance you could add in your own window for parts lookup, a script to define words, get rid of color,

Other options: Permanence/durations on rooms. And log output. - This lets the same client that handles chat function as a message board, with some modifications.


The generic object oriented design will help make creation of a compatible client (not really porting) possible.

http://code.google.com/p/xml2json-xslt/ We might be able to do everything in XML and just let it turn to json on it's own. Does it matter? Not yet.
http://gggeek.altervista.org/sw/article_20061113.html
Due to the generic design and extensibility, adding new languages will be simpler. (Notice, I never say easy... I say ease... but never easy, sometimes easier).

Notes for self: Japanese Characters 1. 2. 3. 5. 4. 6.

Google just whent down. But... only for a few seconds. It displayed a "Google is experiencing technical difficulties that may prevent chats from being sent." Interesting... display that chat is down conveniently... could even be in the chat link... when available, it's a link, when not, it's blue.