Hi Jeffrey,
The spec looks good, and I'm comfortable with the overall design. The
diagrams were indeed useful, btw.
A couple of comments...
> If the user changes any of the following fields: title, location, ...
The set of fields here is not limited to calendar event attributes, but
applies to attributes from any stamp as well (and also the stamp
itself). You might want to be careful here, as Andi pointed out, it
won't necessarily apply to *every* attribute.
> At first glance, this might seem a little drastic. OK, at second
> glance it looks that way, too ...
Yes, I'm a little concerned the "currentlyModifying" mode is awkward.
Would it be less awkward to have a separate method for THISANDFUTURE
modifications, instead of requiring the caller to set the
currentlyModifying attribute?
For example:
item.displayName = "foobar"
would by default apply to THIS, as you currently have it, and:
item.setThisAndFuture("displayName", "foobar")
would apply to THISANDFUTURE.
My understanding is that you and Alec are going to do some pair
programming to start implementing this, sounds good.
Cheers,
Katie
Jeffrey Harris wrote:
Hi Folks,
The Recurrence spec
(http://viewcvs.o11n.org/docs/trunk/docs/specs/rel0_6/Reccurence-0.6.html)
is pretty much done, unless folks on the dev list have more they'd like
to say about it. I'm going to start implementing the spec very soon.
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
