Monday 8/5

Some inconsistencies will be caused by things that are part of a structure, but don't have that structure as a parent or ancestor (like mandible in skull). I can't really help that; it's an FM problem. Maybe in the up-to-date FM it doesn't happen.

There will also be weird things that happen with structures that randomly don't show up in the list from (send TreeRoot:show), like vomer. Also can't help that, since it's a server problem.

Other than that, things seem to be working properly. I'm done editing the functionality of the applet, for now. I can do more of that on weekends, or every once in a while, when I find a bug.

I e-mailed JJ with questions on the new FM thing, so when she replies I can do something with that. Also read a JSP tutorial that Todd gave me.

To do:

1. Get FM Explorer code and read through it.
2. Plan how to fit scenes into it.

---

Tuesday 8/6

JJ will be coming by tomorrow to see see about the DSG thing.

Todd installed Tomcat on this machine so I can serve JSP pages from it. It uses JBuilder's jdk1.3 and can run an old and small (but functional) version of the FME. I read through all the FME code.

Putting scenes into the FME:

• A Scene button in every content page.
• Pushing it pulls up a list of all the terms (and sets of terms) on the page that have models, using the session variables and querying the knowledge base.
• You select stuff to display, and the interface comes up in a new window with the scene loaded.
• Leave the interface up and repeat on another content page to add to the scene, or close the interface and repeat to make a new one.
• Rati's image manager could go into the FME in a very similar way, with a similar interface.
• (There are apparently issues with new windows, but it would be the best way to do it.)

What I want to leave, at the end, is a set of things that are all fully functional and have instructions on how to update them and use them. An applet with swing, an applet without swing, an application, a JSP that can stand alone, and a part of the FME that can do stuff with both scenes and images. Having it in the FME will make it part of current development, which means it's less likely to be left behind. Having it in many, well-documented forms will make it flexible, which also means it's more likely to last.

To do:

1. Study how the current functionality could go into a stand-alone JSP.
2. Get an interface description for the image manager from Rati and others.

---

Wednesday 8/7

When JJ tells me that her server is running, I can try to get the DSG to talk to it (and change 'part of' to 'generic part') to test it.

Started making an JSP interface. Todd pointed out that I can't show Java frames on a client machine. I can only pass values from HTML form elements into the Java classes.

For the image manager, we probably want a second button to go with the scene button. Pushing it would pull up the same list, only you'd be able to rank selections in order of preference. It would then display a set of images. I don't know how much I'll end up programming. At least up through the list, I'd say, and then the source code would have to be different.

To do:

1. Get the JSP interface working by itself, and save a version somewhere.
2. Find out what to do when this is done and Jim and Professor Shapiro are away.

---

Thursday 8/8

Worked on the JSP interface and started to get it functioning. It looks almost exactly like the applets, which is nice. The functionality will be the same soon.

Some things I could do in the future:

• Saving/loading scenes
• Updating things to the new FM
• Bringing the FME, scenes, and images all together
• Making either the server or the interface more intelligent
• Adding images to the database (automatically?)
• Putting somebody's (Andrew's?) applet into JSP
• Putting Emily into JSP

To do:

1. Finish the JSP interface.

---

Friday 8/9

The JSP interface now does everything the applets do.

To do:

1. Make a version that goes into the FME.
2. Work on presentation for the 21st.