a lone stray " .

from idle and swapped (but leave in active for now, until we move some
people out).

Sorry, but emulab-ops and testbed are hardwired strings.

appealing to me. :-)

some software versions.  Shrink the emulab cluster picture so it's
not so dominant and therefore inconsistent with the broad story.
*** NOT TESTED ***

The big one.

New look;
most of the changes are in menu.php3.

A lot of the changes in other files are s/<TD>/<TH>/
for table headers.

Also closed some tags, tweaked some table styles, etc..

No actual functionality should have changed.

Will be installing soon...

Also moved the picture to make the text look better.

if its "spin", it was Jay,
if its boring, tedious detail, it was Mike

instead of https. Present doc links as http all the time.  Required
lot of little changes.

proper headers. Split out some of the mail into testbed-logs,
testbed-ops, and testbed-approval. Added a library for including from
our perl scripts. Contains a couple of mail helper functions, but will
hopefully contain more as time goes by.

Fixed a bug in the web interface that was causing breakage for people
with multiple accounts. Mac and Jay have noticed this, when logging
out and trying to join or create a project under a new or different
name.

mention. Suffice to say there are more words.

you pick up the changes in format from the default-defs.php3.

Anyway, I wasted over an hour trying to figure out why I couldn't get the
documents in right hand frame to go through the non-secure server. Turns
out that http://www.emulab.net and https://www.emulab.net are techically
different servers, and browsers have a "security" feature to prevent
"hijacked frames" whatever the hell that is. If the link to be placed in
the target frame is on a different server, it will open a new window
instead. So, by starting a http://www.emulab.net/welcome.html in the right
side, and then trying to put https://www.emulab.net/newproject.php3 in it,
a new window pops up.

Sigh. So, until I figure out a suitable work around, the Welcome frame
documentation is all going through the secure server (slowly of course).

ends up reposting the login, which creates a new hash value in the DB.
But the other frame has also reloaded, and has sent the original hash
value, but that no longer matches whats in the DB, and so the lefthand
frame thinks you are logged in, but the righthand frame thinks your
are not. Hmm, I bet this could be a famous saying; "The lefthand frame
doesn't know what the righthand frame is doing." It could be my 15
minutes in the spotlight.

option list, use a plain list instead. Simplify the DB queries now
that I'm a joining fool, and put in a proper confirmation step for
ending an experiment. Yippie.

still get the entire list, while normal users get a list of projects
for which they are leaders.

who the user is instead of passing ?uid to every page all the way down.
Update login timeout with each useful operation (done in checklogin).
Put default user name in the login box when visiting the page.

move the project information listing from approveproject, and make it
useable from there and from the showproject stuff, but making it a simple
include file.

a text message to go in the email message.

multiple projects.

Also change grp_memb to proj_memb.

This just adds and deletes the database field entries (experiments table)
so that other things will work correctly.