Unununium and ELC have lots of good code that needs to be merged into the
main tree.  This should probably be our first priority.

Animation memory is not being cleaned up.  But screw that.  The animation
system needs a total rewrite.  Unununium has some ideas...

The movement buffer in the client should give MOVE-type moves a higher
position in the movement queue.  Again, screw this.  Movement needs a rewrite.
It can probably be coded right alongside animation.

Fix Macintosh path-related bugs.  Or: See if Macintosh support is feasible.

Offer a limit on the length of the the personal server log.  Ditto the text
chat log.

Add hierarchy to the avatar menu, possibly using subdirectories to group them
and the ability to move an av from one local to another.

The SMVS array is not being cleaned up.

TOOBIG should also report the server's limits.  Possibly a LIMITS command
should be added to the protocol.  I think Vile already has the code for this,
so we should just check with him.

Include protocol info so that the server can give lots of info about itself.
This should probably be worked into the previous TODO.

When a server has too many connections (from the same host or in general)
then the user is disconnected with no message.  They should get some
information.  The server sends TOOMANYCONNECTIONS or ROOMFULL.  This means
expanding on the protocol some, so backward compatibility might be at stake.

Offer a server option to limit movement to the screen boundaries.

Add a back button to return to the previous room.

Rearrange everything. ;^)

Add a separate server frontend program that can remotely administrate servers.
It'll connect to the server over the network using some special *secure*
protocol.  It'll also connect to the client for things like connect-to-room.
The client connection doesn't need to go outside localhost, though.

Run the personal server as a separate process, linked to the client via the
server frontend.

Give servers the capability to save their own configuration.  This avoids
having to put ftp-type stuff into the server frontend.

Write a utility to generate technical documentation from comments found inside
OpenVerse library files.  Think javadoc.  This can be called automatically by
cvs to update both the website and the technical documentation portion of the
end-user package.  It should be able to produce text, html, and ohlp formats.
Maybe we can squeeze some xml in there too. ;^)  Dunno what language to write
it in, though...

Generalize lib/common/file.tcl enough to support adding a server frontend.
Also fix it to work with the server.  Have it autosense the default domain.

Continue updating the library file headers.

Make the following plugins: aved, passed, setup, help, servgui, history, email,
textchat, personal.
