On Apr 30, 2007, at 10:24 PM, Philippe Bossut wrote:
Philippe Bossut wrote:
I'm trying to get a sense of how read-only items do behave right
now. Does anyone has a read-only ticket I could use for testing?
Aparna gave me a ticket and I tried. So, for everyone's
edification, you can edit anything in a read-only item. Apparently
also the UI in the markup bar is broken and the striked crayon is
not displayed.
So, right now, this is a rather confusing state of affairs for
users indeed... We should at least repair the markup bar.
One proposal:
- if the item is "read-only", the markup bar shows a "striked
crayon" icon
- nothing is editable when this icon is displayed but...
- ...the user can click the "striked crayon" to make the item
editable, a dialog pops-up warning the user (edits will be local
and conflict with edits coming from the server on sync) and the
icon turns into a "non-striked crayon" (note that read-write item
do not display any crayon of any kind so you can make the
difference between a read-write item, a read-only item and a read-
only but edited item...)
I like this proposal, and I think we could take it one step further:
if the user has clicked the icon to make the item editable and has
made some overriding changes, we could allow them to click the icon
again and set the item's values back to the way they are on the
server -- in other words "stop overriding". The sharing layer
wouldn't even need to communicate with the server to do this, as the
server values are cached locally.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
