This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 58312 - Read-only files are hard to recognize
Summary: Read-only files are hard to recognize
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: mslama
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2005-04-26 07:01 UTC by Roman Strobl
Modified: 2009-05-08 07:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Strobl 2005-04-26 07:01:40 UTC
It is hard for new users to recognize that a file is read-only. We should tell
the users about it in some better way. Here is a VOC record:

--------------%<-----------------
At first I was pulling my hair out trying to figure out why I couldn't seem
to do anything to the sources, didn't let me edit anything. It didn't
tell me anything, just refused to let me edit the source.
Finally I realized that the files were read-only.
You really need to do a pop-up or something when someone tries to edit
a read-only source file, not just be silent about it.
And say something like "This file is read-only and cannot be edited". 
--------------%<-----------------
Comment 1 Miloslav Metelka 2005-05-04 13:21:51 UTC
This needs to be handled in openide/editor. Reassigning.
Comment 2 Petr Nejedly 2005-05-04 14:23:59 UTC
The editor beeps, which is good enough feedback IMO.
Posting a popup is way too intrusive in case I mistakenly type a letter while
browsing such a read-only file, so I disagree with this suggestion.

Reasonable action would be to post a message to the status bar,
and that would have to be handled by the editor library (DefaultKeyTyped)
Comment 3 Roman Strobl 2005-05-04 14:39:42 UTC
Petre, the message is already written to the status bar. The IDE doesn't beep
for me in read-only files - are you sure about the beep? Other actions do beep
for me (like go to declaration of non-existing class). Beeping would solve the
issue IMO, although it may not be available on all computers. 
Comment 4 Miloslav Metelka 2005-05-04 16:50:53 UTC
The beep() in CloneableEditorSupport:1596 is not triggered as the code does not
go into undoAll() at all. Instead it goes through CES:1552.
This is likely a regression caused by the recent introducing of the
modificationListener. Adding Yarda to cc.
Comment 5 Jaroslav Tulach 2005-05-05 12:47:19 UTC
Right, I am sorry. Probably there was no test verifying that Toolkit.beep() is 
called when document is readonly, so the behaviour was easy to be dropped. 
Comment 6 Antonin Nebuzelsky 2008-04-17 15:13:00 UTC
Reassigning to new module owner mslama.
Comment 7 mslama 2009-05-07 16:28:11 UTC
I moved Toolkit.getDefaultToolkit().beep() to CES.notifyModified and tested it is called when document is ro. Still call
of beep() has no effect on my Ubuntu 9.04 notebook. Please test if beep works for you.

core-main #76b2ca528959
Comment 8 Quality Engineering 2009-05-08 07:44:29 UTC
Integrated into 'main-golden', will be available in build *200905080201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/76b2ca528959
User: Marek Slama <mslama@netbeans.org>
Log: #58312: Call beep when editing read only document.