On Fri, 7 Apr 2000, Steve Belt wrote:
> Thanks for the reply, Sandy! I'll see if I can check-it-out. :)
>
> Does anybody know about the iCalendaring code?
>
It is coming along nicely. I should finish up the iCalendar objects this
weekend. About 2 weeks ago I said we would have a simple webbased calendar
in two weeks but that hasnt happened. For the web based calendar we need
two more things to happen (after the iCalendar objects are finished).
1. Database persistence. This could get hairy because I designed the
objects from a maximum code resuse perspective. Basically I decided that I
wanted the iCalendar business objects to conform to the layout of the data
rather than the database.
With that being said, database persistence could be a little more
complicated, but a first cut should be in a week.
2. Data presentation. For this it looks like Castor XML and some xsl
transformations will do nicely, but again because of the complexity of the
objects.
Things on the todo list off the top of my head are
1. Use argouml to create UML diagrams of the iCalendar code
Priority - medium
Estimated Time : 1-2 weeks
2. Database persistence
Priority - highest
Estimated Time : 1.5 weeks
3. UI/Presentation -
Priority - Next highest
Estimated Time : 2-3 weeks
4. Write valid iCalendar objects to an iCalendar stream
Priority - Medium
Estimated Time: Cant think that far ahead.
5. Read valid iCalendar objects from an iCalendar stream
Priority - Low
Estimated Time: Cant think that far ahead.
More info on iCalendar.
Some background on iCalendar-
There are five iCalendar objects
1. An event / appointment object
2. A to do object
3. A journal entry
4. A time zone object
5. An alarm object
I may have mentioned them here before, but this here is new stuff.
1. iCalendar objects are made up of properties
2. Properties specify a value such as a summary of an event object.
3. Properties can also have parameters. Parameters provide secondary
information about the particular property value that they are associated
with. An example of this is that on the summary property, on can specify
a language parameter that tells what language the summary is in.
Where we are -
The properties exist (largely untested)
The parameters exist (largely untested)
The good news for most people is that really even though things are
largely untested. The inidividual objects themselves are quite simple.
What has been taking time is the fact that there are about 50 separate
properties and 20 parameters, each with their own business logic.
In addition, most of iCalendar is overkill, at least for our first cut at
a web based calendar. We will probably only be exercising about 15% - 20%
of the code, if that.
Expect the first cut of the web calendar to have a single user to - do
list and event editing and display.
Second cut will probably add email alarms
Third cut.... Again cant think that far ahead and it will most likely
depend on feed back from everyone on the list.
Sorry for being so quiet, just didnt want to have to admit that my 2 weeks
are up and no calendar, yet :(
Jeff Prickett
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
