GitLab

linktest running at once (not a likely situation but ...). Also give
the window a meaningful title so that the browser does not stick in
the URL path.

buffering so that it will start to display output line by line.
1024 for Firefox, probably the same for Netscape. I hear that IE is
256 bytes.

* Changed the linktest web page to allow for killing a running
  linktest when called from the showexp page. Puts up a simple Click
  form, whose action is to call "linktest_control -k" which does the
  dirty work.

* Implement a simple frameset when running linktest. I did this cause
  it was something new and besides, it was more fun then trying to
  reverse engineer the modelnet model file. Anyway, when linktest is
  started, put up a new window that has a two window frameset. The
  right hand window is just the spew output from linktest as it runs
  (although with buffering not much turns up at first). The left side
  window has a single click box to stop the running linktest, whose
  action is to call linktest_control -k as above. By the magic of
  javascript, when the linktest finishes, the stop button is removed
  and replaced with a "Linktest Finished" message. So exciting.

in the DB, change that to Stop Linktest instead.

longer using cpuspeed.awk to get the 'exact' speed.

newclient to find it.

can view them.

widearea node.

has NULL or "".

even if the disk is up to date.

Add a sliceNN_alt_image pointer to a web location for downloading
a disk image in case the image isn't stored on the boot CD
(needed to handle heterogenous boot CD media)

Update status of most testbeds.
Tweak language of most boxes.
(still needs reordering, make left-hand column consistent)

troubleshooting entry.

new_nodes table. Thought it would be easy, but ended up doing more
damage then I expected; oh well. New nodes show up in "gold" color
(not listed in the legend).

I added a link from the newnode_edit page. Rob will need to arrange
for a location_info entry to be created when a new node is made live
(but only if building/floor are not null).

that I added to the DB. See revision 1.251 of sql/database-create.sql.
I have removed all of the hardwired names of buildings, images, files,
etc. I have also added MEB floors 1 and 2, but they do not show up on
the status page unlesss there are actually nodes assigned to them.
When you go to set a node location, you do see the little thumbs of
all existing buildings/floors, so you can add nodes to floors that do
not currently have any.

Still needs some work to cleanly display multiple buildings, but thats
for another day.

* Redo all the MEB .png files, removing the existing titles from the
  images, and cropping down the images to the actual floors. Redid the
  thumbnail files at the same time. Note that the existing location_info
  entries need to be updated, which I will do.

* Rework portions of floormap.in in preparation for using the DB to
  describe the image files (still hardwired into the floormap).

* Draw a title in each image using a truetype font, based on what will
  eventually come out of the DB, plus a floor tag.

* Add option (-t) to not draw any titles; just naked images.

admin people allowed. Comment from script:

# * Initially we come in with just a nodeid. Display a page of little maps
#   and titles the user must select (a floor in a building) from. User clicks.
# * Next time through we have a building and floor defined in addition to the
#   the nodeid. We put up that big image with the current nodes on that floor.
#   We use the external floormap program to generate that image, but without
#   an imagemap. Instead, we use a form with an input type=image, which acts
#   as a big submit button; when the user clicks in the image, the browser
#   submits the form, but with the x,y coords added as form arguments.
# * We get all of the above arguments on the final click, including x,y. Verify
#   all the aguments, and then do the insert.
# * If user goes to reset the node location, form includes an additional submit
#   button that says to use the old coords. This allows us to change the contact
#   info for a node without actually changing the location.

Caveats:

* We do not describe buildings in the DB, and so we are currently hardwired
  to MEB for the building, and the images for each floor are still
  hardwired in the external script (vis/floormap.in) that creates the
  image. Needs to be dealt with before we can export this stuff.

* There is no way web interface to delete a location entry. That should be
  easy to deal with when needed, but in the meantime:

	delete from location_info where node_id='pcXXX'

* All nodes get a "Set Location Entry" on the shownode page menu; I leave
  it to admin people to not set the location for a non-wireless node; will
  fix later as needed.

* Coordinates are all in pixels. As Russ points out, this is (way) less
  then ideal, but certainly simple.

the fly, or use heigh/width specs in the img tag, but I hate how the
browser scales things. Short term solution; obviously does not scale
to more then a few floor images.

otherwise the file is created as that user, and is then difficult to
remove in floormap_aux.php3 after it is dished out. There is no reason
to run the external script as the user; all it does is build an image.

passing this to the newnode client, web page, and viewing and
editing it.

(was "actually appeared" order).