Jeffrey Harris wrote:
- It looks like not only UI code, but any modification to ContentItem
attributes must go through this mechanism, right?
Yes, although Ted's busily trying to convince me there's a better way, I
hope he's right ;).
Just to be clear, by "this mechanism" -- we're not saying that all code
using ContentItems needs to call "setAttributeSafely" -- only the UI
needs to worry about when/whether to prompt the user for more information.
Any ContentItem can potentially be a recurring item, so any content item
might need to apply edits to either THIS or THISANDFUTURE.
Is this what you mean here? If not, I may have misunderstood our
previous discussions.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
