| UROP | Jigsaw
Project description
The Project Peter will be working on for his summer UROP at the World Wide
Web Consortium is to write a shared calendar resource accessible over the
web. This resource should be able to accept and display information in a
variety of forms. He will need to know Java, Perl, and the workings of the
Jigsaw server in order to complete this project.
Summer UROP Proposal (Kinda corny, I know)
The intent of my summer UROP with the World Wide Web Consortium is to create a fully
functional shared calender resource. This calender will be accessible over the web, and
multiple users will be able to input important dates and events on the calender, and then the cal-
ender will notify them when they have something scheduled. The final product should be able to
recieve, display, and send data through many different means.
Over the 11 week period there are three goals I will
accomplish during my UROP. The first is to learn all the tools I will need to work on the project.
I will need to learn Jigsaw (a HTTP server written in Java), how to create new resources in Jig-
saw, and the Java programming language. By the end of the first couple of weeks as a test to see
if I have accomplished my first goal, I will make something that runs inside the Jigsaw server. My
second goal, which will take the majority of the summer to accomplish, is to make a functional
calender. It will not have all the features of the complete calender, but it will have the important
ones. The calender will be accessible over the web and by multiple users. My final goal will be to
finish fine tuning the calender. It will be able to recieve, send, and display information in many
different ways (the main ways will probably be through e-mail, or directly through the web site).
The calender will then be used and tested by people at the World Wide Web Consortium and I will
get feedback on how to improve the calender resource.
There are many benefits I will get out of my summer UROP experience. The first is I will
learn about human interface, groupware, and personal information management while creating
this calender. I will learn how to make programs more useful for users, the best ways to display
data to users, and what users really need in a program. Another benefit I will gain through the
UROP, is learning to do real Java development, at this point in time I have just been fiddling
around with Java, but once the summer is through I should be a very competent Java programmer.
And the final benifit is that I will be working with the World Wide Web Consortium, and I will be
doing actual software engineering. This is the first time that I will be working in an environment
like the World Wide Web Consortium and it should be very rewarding.
Tentative Mile Stones
-
Aug 20 - Sept 20, 1996
-
Test the code and make revisions and additions.
-
June 24 - Aug 20, 1996
-
Code the Calendar.
-
July 19
-
user interface demo
-
July 3
-
minimal functionality: enter an event, view it
-
June 3 - June 24, 1996
-
Learn Java, Jigsaw, and Perl.
Status/Log
-
Calendar in Progress- will not work sometimes
as I alter it-http://wave.w3.org
-
August 13 - altered the code so it will work on the lastest version of Jigsaw, took out the stipulation that the creator can only edit an event because it is too restrictive and everyone at the w3c should trust everyone else, you still need a password to get in though.
-
August 12 - made it so the calendar shows multiple day events on the month view. Finished first version, going to show it to people.
-
July 30 - added event ownership, password protection can add events
through e-mail (have to make it so that the mail program can get through the password protection), people and groups now have address, e-mail, full name, and phone number fields. Added url field to events, making setup program, it is thread safe, made the sorting program binary.
-
July 19 - most of user interface is done, can add, edit, remove, and view dates somewhat easily, spent the last two days looking for a bug, not fun, not productive, but found it and fixed it. The algorithm for searching and sorting is still n^2 will work on that, and I can make it more efficent in area's.
-
July 3 - Redesigned storage scheme, every event is now a jigsaw resource,
Created a URLAttribute which is basically a StringAttribute to store the
URL with a static method which will find the URL for you, also made a
StringVectorAttribute, not sure it was all that important but it is a bit
easier to use than using a StringArrayAttribute in some cases.
-
June 16 - Working on the front end now, basically I'm making the Calendar
out of a bunch of subclass of the PostableResource class, I have made a Calendar
generator in which the user gives it a month and a year and it makes a Calendar
of that month.
information, and learning about Jigsaw
-
June 12 - Decided to use DBM for now, maybe something more sophisticated
later on.
-
June 10 - Finished mail parser. Trying to figure database scheme for
-
June 3 - Learning Perl and writing mail parser.
Things I need to do
-
make a really good first page
-
clean up the code
-
clean up program-if there is a problem this program will search through the Events directory and rebuild the DatesArray and build up the pointers to/from Locations and Events
-
make mail interface-talk to Kay Lie and other people
References:
Staff
-
Peter Ju
-
summer UROP: June thru Aug 1996 thru Aug
-
Dan Connolly, supervisor
Peter Ju, pju@w3.org, April 1996