Todd's Blog Well...... on Thursday and Friday I made the changes that Jason and I discussed last Monday after class. The data is now being added via Jason's array to a table. The hope here is this will allow us to more easily use event handlers, which will be the next step. We feel the additional fuctionalty grealy improve the site.Here, finally, is the merged version of what we've been working on. Getting 'finished' bits of code out of the main html document turned out to be more of a challenge than I expected. I'd temporarily forgotten how picky the mapQuest API is about ordering, and I jumped ahead of myself and tried to do code cleanup at the same time. In the end, it all worked out. Now, all of the sections that we are reasonable certain we are done with are in two files called maps.js and events.js, leaving mostly the stuff we're still working on in the main html file. There are some exceptions, in that the main file contains several lines of code near the end that I'm pretty sure we're done with, but the mapQuest API doesn't seem to like having those lines in the head. All three of the files can be viewed here:
http://people.emich.edu/jkeswick/IS449/project/
The Iteration 2 file includes the use of a dynamic table for displaying info on the events that are currently being mapped. I'm going to see if I can work with the format of the page a bit today, but I'm not sure whether or not I'll be able to get it ready in advance of class.
Also note that the array currently being used to store the event info now contains a start and end date/time attribute that we should be able to use in iteration 3 to handle filtering by a date range, but the code is not in place to do that quite yet. I did find a javascript calendar widget that we might be able to use for user input, but I've not been able to experiment with it sufficiently to say for certain.