Hi Morgen:
I ran into these kind of problems in the past and concluded that the only viable solution is to separate display info from data -- which means not storing color info on the ItemCollection.
John
Morgen Sagen wrote:
Ok, sharing now handles mixins by including the constituent kinds' info. I'm weighing various options on how to keep calendar colors "semi-private", meaning sharees can change the color at will without those changes percolating out to anyone else.
On Apr 26, 2005, at 12:07 PM, Morgen Sagen wrote:
The sharing framework doesn't yet handle sharing of items whose kinds are mix-ins, and now that any item collection that is assigned a calendar color becomes an instance of a mix-in kind, you can't currently share them (well you can share them but you can't subscribe to them). I'm working on a solution. For now you can only share a collection that you haven't viewed in week view (that's when a color gets assigned). I've already filed bug 2888 against myself to track this:
https://bugzilla.osafoundation.org/show_bug.cgi?id=2888
~morgen
P.S. The reason this breaks is because the Kind of a Calendar-Collection-with-Color becomes something like: //Schema/Core/Mixins/mixin_708eb5fc, which doesn't mean anything on the sharees' end. For items of a mix-in kind, I'll need to include all the individual mixed-in kinds' info in the XML.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
