Re: [Design] Read-only-ness in the Cosmo UI

[Priscilla Chung]

On Dec 18, 2006, at 12:00 PM, Matthew Eernisse wrote: 4. Rather than disable all the form elements to indicate 'read only,' I am just disabling the Remove and Save buttons. I did this because disabling text input or textarea form elements also disables scrolling, so it would be impossible to see any text that is longer than the visible area of the form field. Do we want to disable the 'Remove' & 'Save' buttons or would it be better to not even have it appear? There needs to be an no edit icon on the top right of the event details (of a pencil w/ a strike through–see enclosed icon from iCal) If a user tries to click into a form field and starts to create an edit, perhaps we can prompt an error dialog to say this is a read only calendar. This would also appear if the user tries to move an event on the calendar canvas. This has the unhappy effect of allowing people to make changes to the form field values -- they just can't save any changes. A 'fancier' implementation would swap out the text form fields for scrollable div elements or something, but I think the simpler implementation is probably fine for now. I agree whatever is easiest to implement is fine for now. I'm having a bit of problem access qacosmo this morning, so let me know when you have time so I can review the UI behavior for the  'read-only' calendar with you.  Please note the attach images are for reference only, do not use them to implement in Cosmo. I will have the correct images attached in bugzilla. Thanks, -Priscilla

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design