Bug 2431 - feature: mark either read-only editors or read-only resources (1GF5VIJ)
Summary: feature: mark either read-only editors or read-only resources (1GF5VIJ)
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2001-10-10 22:36 EDT by Grant Gayed CLA
Modified: 2002-03-15 16:27 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2001-10-10 22:36:15 EDT 
I like the current behaviour that occurs when a read-only text file is opened in the workbench
(the editor opens in read-only mode).  However it's easy and common for someone to not realize
that a file being opened is read-only, and hence may think that the editor is broken when it displays
the file but does not allow modification.  Some indicator of read-onlyness would definitely be good
for clarity, either on the editor's tab or on the resource itself in the navigator (not just on its property
page).

NOTES:
Comment 1 DJ Houghton CLA 2001-10-29 18:27:44 EST 
PRODUCT VERSION:
0.122
Comment 2 Kevin Haaland CLA 2002-03-15 16:27:31 EST 
The way read only files are handled has changed significantly since the time 
that this defect was reported.