Hi Katie, Katie Capps Parlante wrote: > Mimi Yin wrote: >> *So...What are our options?* >> *2. Ideal from the design perspective: Per-item access controls.* >> Batsheva should never be allowed to edit the Item 'Danger, Will >> Robinson' no matter what other collections she adds it to. > > Is there general agreement that this solution is the preferred solution > in the long term? (which of course does not necessarily mean that we > should tackle it for Preview). What is the scope of this solution?
Just as Chandler allows users to edit emails they receive (which isn't the normal behavior), I'd like to be able to edit read-only items I receive. Admittedly, the changes I'd be likely to make will probably be annotations, which may eventually get modeled differently, but we haven't gotten near to implementing annotations yet, so as a first cut I'd like to edit items I get from read-only sources. Anyway, I'd say there's room for more debate on whether per-item access controls is the ideal long term solution. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
