I worked on the website a lot this weekend, because I realized that this is actually one of the few slow points I have coming up. I wanted to make sure that I got my three development goals finished on schedule.

Here are the improvements I made:
1) There is now a SimMap content type. This content type requires a TIF file and .map file to be uploaded. It then translates this information, and displays the Google Maps interface we are used to.

2) I also created a SimMapFolder content type. This type requires a Latitude and Longitude value. It then acts as a folder, only when you click to view the folder it displays a blank Google Map centered on the specified location.

3) Finally, I created a SimMapNav portlet. This portlet essentially copies the standard navigation portlet, and creates the checkboxes for SimMap content types. However, there appears to be a bug in the implementation of the the way Plone 3 renders portlets, so this ends up changing the functionality of the standard navigation portlet. I can explain this in more detail at our meeting.

I also ran across a simple plone portlet to add static text. This should allow us to implement the legend display we talked about last meeting.

Here is a URL which serves as an example of how to display a legend:

http://twiki.rehearsal.uiuc.edu/cgi-bin ... 388517.map

This evening I worked at adding a new content type to meet the requirements we discussed at the meeting on Tuesday. I added the SimMap type, which allows a user to upload both a TIF file, and the accompanying .map file. I tested it out, and it appears to work fine.

The next step for this will be to integrate it into the navigation portlet, so that the checkboxes will show up next to this content type as well.

I worked on defining a workflow. A hand-drawn picture has been created to depict the workflow. This will be converted to a Visio drawing and all transitions will be refined based on testing and our Mantis' customizability

Mantis system workflow was also altered based on the drafted workflow process. 3 types of users will exist: 492-Developer (the original developer of the feature, or has most extensive knowledge of an area), 492-Test (tester on the 492 team that will review bugs and pass along those which are more complicated), LEAM-User (actual LEAM user, who can only create issues then send it down to the rest of the 492 team to solve)