maqetta/maqetta — Issue #1200: Should users be able to open read-only theme files such as claro.theme?
Author: JonFerraiolo
Created: 2011-11-09 18:47:35+00:00
State: open
Labels: Files View, Priority Med

(Not for M4)

@peller, @jhpedemonte, @billreed63 (not something that needs to be addressed for M4)

Right now the theme files show as read-only in the Files palette, which is fantastic. Users can click on them to bring up the files in the editor.

For example, users can double-click on claro.theme to bring up the theme editor. When they attempt to change properties, they see the dialog but not being allowed to change read-only CSS files within a theme. Also, users can double-click on claro.css or other theme CSS files and up comes the text editor. The user can modify the text within the editor and click on the Save button, but because the file is readonly, the save action doesn't actually happen. (No error messages to user, which of course is bad)

So what should we do? Some options:

1. Head off at pass - Don't bring up an editor for read-only resources. However, this prevents a user from opening up a read-only file, modifying it, and then saving into a writable folder.
2. Post warning upon opening - Tell user the file is readonly and that he cannot save modifications to the same location.
3. Post error when attempting to save into a read-only area.

We need to research how other applications deal with this issue. My instincts are that we should do 2 and 3.