Added comment about stack variable buffer overflow sighting.

constructors and destructors?

added tree.onOpen() and tree.onClose() event emitters. ex: tree.onOpen = function() { do something when tree is opened };

added emulated event emitter/handler adapter (applies event handling and emitting prototypes to objects)

use chat.colors instead of chat.settings for attribute settings, use array slice(-1 * chat.settings.MAX_HISTORY) to retrieve message history

Version 1.27: Simplified how SlyEdit decides whether to use bbs.msg_number or bbs.smb_curmsg.  SlyEdit now uses bbs.msb_number if it's greater than 0 (rather than checking the Synchronet verison and build date).

Also, for sysops who have Digital Distortion's Message Lister installed, this version of SlyEdit now requires version 1.36 (or newer) of Digital Distortion's Message Lister.

Version 1.26: Updated to use the absolute message number only on Synchronet >= 3.16 from March 12, 2013 onward, since bbs.msg_number is valid only from that date forward.  For previous versions & builds of Synchronet, SlyEdit uses bbs.smb_curmsg, as before (although that can result in some incorrect message headers chosen for author initials in Scan For New Messages To You, resulting in incorrect initials used in message quoting).

Version 1.25: Now using bbs.msg_number (absolute) rather than bbs.smb_curmsg (index) to retrieve a message header for the purpose of getting the author's initials when quoting a message.  bbs.msg_number is always correct when replying to messages in all situations (such as the Read Message prompt, scanning for new messages, and scanning for new messages to you).

If you use Digital Distortion message Lister, this version of SlyEdit requires version 1.34 of Digital Distortion Message Lister, which was updated to provide the correct message number to this verison of SlyEdit.

Mr. Smarty Pants.

Does strlen include NULL terminator?

places other than just viewing a message header - for use in Nightfox's SlyEdit.

shows example usage of MSG_* @-codes.

fixed client splice() method, removed broken db shadow object stuff (may result in fragments of shadow objects being left behind in the case of a splice)

use JSONdb.remove() method instead of writing undefined when deleting a record (removes records completely instead of leaving an empty property behind)