Monday 8/19

The presentation looks fine, according to Jim. All the technical things work, but the window layout is strange on Marie's computer. The reason seems to be that it needs Java Runtime Environment 2 v1.4.0. If I can get it downloaded before the presentation, that'd be good, although it's not totally necessary.

These are the ideas from last week for stuff to do next:
+ Saving/loading scenes
+ Updating things to the new FM
+ Putting Rati's stuff into the FME when she leaves
- Making the server or the interface intelligent (not enough time to do this justice)
+ Adding images to the database
- Putting other things into JSP
+ Local documentation, webpage, and a paper for CR.

To do:
  1. Try the save/load stuff.


Tuesday 8/20

Tried to figure out how to save scenes the way the DSG does, but I'm really not sure the DSG thing works, anyway. It doesn't seem to make an .str file, just an .anat file and a jpeg. I certainly can't get it to load scenes. Maybe I could save one with the DSG and try to load it in the applet.

Made the presentation sentences shorter and in larger print, on Professor Shapiro's suggestion. Jim advised making screen shots in case the live demonstrations don't work.

To do:
  1. Make screen shots of programs.
  2. Try saving state from DSG and loading into applet.


Wednesday 8/21

I put up a series of screen shots, just in case. They'll be good to put up on the website, in case things get changed in the future. They have to become jpegs, though, instead of bitmaps, for better compatibility.

Whoa, saving from the DSG and loading in the applet worked! That was unexpected. But I'm still having trouble saving. Should be able to get it worked out, though.

To do:
  1. Get saving to work.
  2. Get Jim's help with updating the FM.


Thursday 8/22

I got the basic saving and loading to work. The problem was with the CGI file moveImg.cgi, which picked up an Internal Server Error whenever I saved it from WordPad. But it turns out the moving isn't really necessary, so I'm not using it anyway. Now the Java code saves simply by calling the save-state command, does VRML by calling the save-vrml-file command, and loads by calling the load-state command.

Issues with loading: I'm actually confused about what the save and load commands do. It must be internal to skandha, because it certainly doesn't depend on any file in my dsg directory. I assume skandha is creating such a file somewhere, but I have no idea where.

The applets can talk to the new FM server with (term-server-connect "quad" 8098) just after making the connection to skandha. It can be used to generate scenes.

Issues with new server: To do:
  1. Figure out loading issues.
  2. Figure out why there are differences with the new server.