problem with putting documentation into .php files is that swish needs
to be told to index them explicitly via the swish.conf file.

integer.

camera, as well as its width, height, and fps. Tack these params onto
the robotrack URL:

	&camwidth=640&camheight=480&fps=2&camera=1

where camera is 0, 1, or 2 ... Dave can figure out which one he needs.
The allowed camera sizes are:

  640x480, 640x360, 480x360, 384x288, 352x288, 352x240, 320x240, 240x180

as defined by the axis HTTP API.

A little blinken lichten tweakin:

	* mote/sgtools/moteleds.C: If an update hasn't been sent for 1.5
	seconds, send one so the other side still knows we're alive.

	* www/BlinkenLichten.class, www/BlinkenLichten.java: Add the blue
	throbbing rectangle of liveness and cross out the lights if the
	connection seems to be down.  Need this stuff, otherwise it's hard
	to tell the difference between the lights not changing and network
	latency.

	* www/showstuff.php3: Widen the size of the blinky light applet.

Ready for local people to play with.

The current implementation is that we munge the mysql DB on ops directly,
underneath jabberd. We add/del users from the authreg table, and set up
buddy lists in the roster-items and roster-groups tables. modgroups will
invoke the modjabberbuddies whenever a user is added or removed from a
group, although currently I am building buddy lists for just the top level
projects.

The "My IM" link in the collaboration menu will tell the user their
jabber ID on the Emulab chat server (jabber.emulab.net) and also give
them their plain text password to plug into their chat client.

I also installed a java applet (Jeti) that is a simple chat client that
I found off the jabberware page. Like all applets, it exhibits a degree
of flakiness, but I really do not expect too many people to use it.

into a single new script call modgroups. Usage:

	modgroups [-a pid:gid:trust[,pid:gid:trust]...]
                  [-m pid:gid:trust[,pid:gid:trust]...]
                  [-r pid:gid[,pid:gid]...] user

So, -a to add groups, -r to remove groups, and -m to modify the trust
value for a member of a group.

The reason for doing this is that previously, we had no idea in the
backend what group changes actually happened; we just knew what the
current groups are. This make it hard to add and remove users from
mailing lists, chat server buddy lists, etc. This is cleaner ...

Major interface change; the default mode in the map is that click
on a node now *adds* to a highlight (used to be shift-click), and that
click over the floor area deselects everything.

Add a "Distances between highlighted node" menu item, that uses the
x,y,z coords of nodes to determine the distance between them. Okay
so there might be a small constant in there, say 14 feet, that just
happens to be the distance between floors in MEB.

"new" and explain why.  Temporarily make the papers menu item say "new"
(for about two weeks, I think).

Add SMP support caveat.

Also print name of moused over node on the mode line.