On May 1, 2007, at 1:48 PM, Mimi Yin wrote:
On May 1, 2007, at 11:48 AM, Philippe Bossut wrote:
Mimi Yin wrote:
So we can repurpose the Lock icon to be the read-only icon?
You mean: the logo (the "lock" instead of the "crayon" metaphor)
or the spot on the markupbar?
Yes. Morgen proposed this in his original sharing format write-up.
Priscilla also expected the lock to mean: edit this otherwise un-
editable item. So perhaps we should just replace the crayon icon
with the lock icon. That way, it will have the appropriate rollover
states as well so that users know it's clickable.
I've checked in new icons for the 'unlocked' states that show the
lock as open.
+ MarkupPrivateStamped.png
+ MarkupPrivateStampedRollover.png
+ MarkupPrivateStampedPressed.png
Morgen, does that make sense?
So there are three states:
A) No lock at all means it's a regular read/write item
B) A locked lock means it's read-only and the user cannot modify any
field of the item
C) An unlocked lock means the user has chosen to override values and
can modify any field of the item
An item is in state A if the item is not shared, or is a member of
any read-write collections.
An item is in state B if the item is a member of only read-only
collections
An item goes from B to C if the user "unlocks the lock".
An item goes from C to B if the user then "locks the lock" -- any
local changes are discarded, so we should probably have a
confirmation dialog?
Implementation details:
- I think we need to add a new attribute,
ContentItem.readOnlyOverride (defaultValue=False), to record whether
the user has elected to allow overriding edits on an item
- if sharing.isReadOnly(item) is False, no lock is shown
- if sharing.isReadOnly(item) is True, a lock is shown, and If
readOnlyOverride is False, the lock will appear locked, otherwise
unlocked
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
