Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 22921 - [Decorators] Types pane with no CVS labels (configurable)
Summary: [Decorators] Types pane with no CVS labels (configurable)
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-27 17:38 EDT by Gary Gregory CLA
Modified: 2006-06-22 08:34 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Gregory CLA 2002-08-27 17:38:21 EDT
I really like having the CVS labels "(ASKII -kkv)" etc and icons for files in 
the Repository perspective. I would like to configure the Java perspective's 
Type pane SEPARATELY. I do not care to see the "(ASKII -kkv)" business in the 
Types pane, it really does not add any value for me, in fact, it is very 
distracting and makes it harder to deal with concepts like classes and objects 
when each class name is decorated with "(ASKII -kkv)" or whatever other 
settings. It add beacoups de value other views of course.

Thank you for considering this,
Gary
Comment 1 Erich Gamma CLA 2002-08-28 05:06:33 EDT
Currently decorators can only be enabled/disabled globally. There is no support 
to control decorators on a perspective/view basis.

Moving to Platform UI
Comment 2 Tod Creasey CLA 2002-08-29 13:03:52 EDT
One way you could do this now while you are waiting for this feature is to go 
to org.eclipse.team.cvs.ui\plugin.xml and change the adaptable flag on the 
org.eclipse.team.cvs.ui.decorator decorator to false.

Would you find being able to turn off an on the adaptability of the decorator 
a useful feature for a Preference?
Comment 3 Gary Gregory CLA 2002-08-29 18:27:26 EDT
Wow, there is so many ways to slice and dice this one... I am glad you asked 
since I had not quite realized what usage patterns I had.

Background: 

(1) I do my day to day programming in the Java Browsing Perspective.
(2) I do my day to day commits to CVS from both the Java Browsing Perspective 
and the Resource Perspective, but mostly from the Resource Perspective in order 
to see the non .java files I have changed.
(3) I sometimes go fish around with the CVS Repository Exploring Perspective.

Usage Patterns:

(1) For my day to day programming in the Java Browsing Perspective I do /not/ 
want to see the version number and the "ASCII/Binary -whatever". But I /do/ 
want to see the dirty flag. What I care about here are objects and what I may 
have "touched". So this applies to the Types pane, Hierarchy pane and the 
Outline pane (and others perhaps). 

(2) When I work in the Resource Perspective I want to see /every/ bell and 
whistle decorator.

(3) When I work in the CVS Repository Exploring Perspective I want to 
see /every/ bell and whistle decorator.

(4) I am whacking away in the Java Browsing Perspective and I chat with a 
colleague about a class I am looking at and he asks what version of the class I 
am using. Since I have my decorators set up so that the version and 
ASCII/Binary settings are not there I just right-click on the class and choose 
Properties, click on the CVS tree node and get to the information I need. So I 
have not lost the ability to easily get this information from this 
Perspective's Types View.

Bottom Line:

The bottom line is that I think the setting level I am looking for is at the 
Perspective level, not the global "Preferences" level. A instance of a view 
belongs in an instance of a perspective, so I see a well established 
relationship there. Is the "Customize Perspective" dialog and system set up to 
handle this type of customization?. I think I am saying that some Preferences 
(I have not thought if this makes sense for all Preferences) should have the 
ability to be overridden from the Customize Perspective dialog. You have your 
global Preferences, some of which can be overridden in a Perspective's 
Customize dialog. Having two levels of preferences could be confusing to some 
users, so that must be considered as well.

Alternative 1:

Have the current CVS Preferences list all of the Views with an on/off toggle 
indicating which views the decorators apply to. This would mean of course that 
the View would not be customizable from Perspective to Perspective, which would 
be too bad. The View in each perspective would remember this setting from run 
to run.

Alternative 2:

Add a menu item to the context menu with a toggle "Display CVS Decorators". 
This is not great either since not displaying the CVS label decorator would 
hide or show everything. So I could not see what classes/files have changed if 
I hid the decorators to avoid looking at the version number and ASCII/Binary 
settings. The View in each perspective would remember this setting from run to 
run.

I hope this helps you understand where I am coming from and... I really like 
eclipse!

Gary
Comment 4 Tod Creasey CLA 2002-08-30 07:30:38 EDT
Thanks Gary. You option 1 looks like a good idea as it is something we can do 
to expand the decorators registry to have view subscribe to it. I'll be sure 
to add your comments into our decorators review.
Comment 5 Gary Gregory CLA 2002-08-30 10:47:34 EDT
Tod,

You're most welcome. *Now* I remember another font/color view feature from my 
old Smalltalk days. It would go something like this in eclipse:

(1) Be able to toggle how "deep" any Types view can be (Especially Hierarchy 
and Types but not necessarily Outline). The current 2.0 eclipse is "just this 
package" but the toggle would let you view objects in all "sub" packages. [Yes, 
I know, there is no such things as sub-packages, packages are unrelated 
namespaces, but most folks use packages as a hierarchical organization 
tools, "Ed"]. So If I have classes in com.me, com.me.a and com.me.b, selecting 
com.me, displays all the types in com.me.a and com.me.b.

(2) *Then*, the kicker is that when classes are displayed in a types-type of 
view, the types from the selected package (aka the current context) are (for 
example, the way we had it:) in bold and others are not normal font. So if I 
have "View types in sub-packages" turned on and I select com.me, I see all 
types in com.me in bold, com.me.a in normal font and com.me.b in normal font.

The bold vs. normal is an example and would be configurable. Now it makes to me 
sense that I recalled certain bold vs. ~bold view elements.

When you are using fonts and colors in clever ways, it then becomes much more 
feasible to navigate large hierarchies (Java 1.4 has 11,000 classes I've read). 
Then you can start thinking about using font and colors to distinguish between 
types in the context where the package or type is selected vs. the other types 
based on what classpath entry or Jar/Zip file each type comes from... woa. 
First things first though.

Gary
Comment 6 Gary Gregory CLA 2002-08-30 17:51:10 EDT
I would like to link this discussion with 
http://bugs.eclipse.org/bugs/show_bug.cgi?id=23011
Comment 7 Kevin McGuire CLA 2002-08-30 18:29:24 EDT
Rather than piecemeal being able to configure decorators for different views, 
we should investigate global tasks.  We've discussed this in the past but got 
confused.

In this solution, you would turn on "doing CVS stuff" when you wanted, which 
would enable the decorators (either globally or in that perspective), as well 
as the menus.
Comment 8 Tod Creasey CLA 2006-06-22 08:34:46 EDT
There are currently no plans to work on this feature