| Summary: | [Decorators] Adding a readonly decorator | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mickey Math <mathmickey> | ||||
| Component: | UI | Assignee: | Tod Creasey <Tod_Creasey> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P4 | CC: | dj.houghton, thomasf, Tod_Creasey | ||||
| Version: | 2.1 | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Windows 2000 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Mickey Math
Created attachment 5865 [details]
Original + modified eclipse source files (zip)
This zip file contains the original files from Eclipse SDK 2.1.0 and the
modified ones) so that to easily track the changes.
Only source files are included (jar files are too big)
Don't miss the README file.
Added DJ for a core perspective. This is an interesting idea but I think this can already be done in Eclipse. Any view that has resources has a resource change listener - is it the case that changing the read only flag does not fire the listener? If it doesn't then you should log a PR. Another thing that the Eclipse Workbench is being careful to avoid is references to its own decorators as they are meant only as a passive object that labels are built from. I think you can write this decorator without any changes from us but I am interested in why you needed to make them to be sure that we don't have more subtle problems somewhere. Thx for your feedback. I'll try to have a look this WE, and see whether a listener is fired, and if not, try to write an accurate explanation why I made those changes in the workbench. I have seen several Eclipse users stumble when dealing with read-only files, especially when working with external revision control systems. Having some additional annotation in the editors as well as a label decorator would definitely be worthwhile. Marking as help wanted as this interesting but not likely something we will have time for in the R3.0 timeframe. |