Bugzilla – Full Text Bug Listing
| Summary: | Better name for Display view | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Deepak Azad <deepakazad> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | curtis.windatt.public, daniel_megert, markus.kell.r, Michael_Rennie, pawel.1.piech, pbenedict, remy.suen |
| Version: | 3.7 | ||
| Target Milestone: | 3.8 M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Deepak Azad
+1 to change the name. Does it really need a name change? Looking through the history, the view has always been named 'Display'. One could argue the name is fitting as it displays the results of evaluations. If I had to choose a new name though, I would lean more towards 'Evaluate' or 'Evaluations'. 'Evaluator' sounds like a giant robot :) (In reply to comment #2) > If I had to choose a new name though, I would lean more towards 'Evaluate' or > 'Evaluations'. 'Evaluator' sounds like a giant robot :) 'Evaluate' is also fine with me. (Any name which clearly suggests that the view evaluates or executes snippets is fine with me.) (In reply to comment #2) > Does it really need a name change? Yes ;-) 'Evaluate' would also be fine for me. When renaming the view, also consider renaming the 'Display' command (Ctrl+Shift+D). In the Display view, this command evaluates the selection and writes the result into the view. When invoked from somewhere else, it shows the result in a sticky hover with a message at the bottom that tells it can be moved to the Display view. For that use case, it really is just a Display view, since it only shows the result, but not the snippet. This is not a complicated change. We should decide now whether we do a rename or not. Renaming the view is not complicated, but there's quite a list of things to fix afterwards: - 'Display' command name: Change to 'Evaluate'? - it's immediately clear that the result of the Display command is displayed somewhere. For 'Evaluate', that's a lot less clear (what's the difference between 'Evaluate' and 'Execute'? very subtle...) - what about the Ctrl+Shift+D shortcut for 'Evaluate'? Hard to explain... - if not changed: Confusing that the result of the 'Display' command is shown in the 'Evaluate' view. - references to 'Display' in UI strings - references everywhere in the doc, tips & tricks, printed books, etc. I don't think the benefits outweigh the hassles. (In reply to comment #7) I do not suppose we can call it 'Evaluate and Display View' :-) How about 'Scrapbook View'? (Or maybe 'Scratchpad View') - We already have a 'Scrapbook Page' which is also used to evaluate random code snippets. - The 'Display' command can remain as is. It looks OK to me for the result of 'Display' command to be shown in a 'Scrapbook View' > I don't think the benefits outweigh the hassles. Given that most users I talk to are a bit surprised to know that a 'Display' view also evaluates snippets, I think a name change would be worthwhile. (In reply to comment #7) > I don't think the benefits outweigh the hassles. I have to agree with Markus on this one, I also don't see the benefit of the name change in light of the massive amount of work it will take and the re-education of long-time users that know it as the 'Display View'. Proposing to close as WONTFIX. (In reply to comment #9) > (In reply to comment #7) > > I don't think the benefits outweigh the hassles. > > I have to agree with Markus on this one, I also don't see the benefit of the > name change in light of the massive amount of work it will take and the > re-education of long-time users that know it as the 'Display View'. > > Proposing to close as WONTFIX. That's fine for me. All I wanted to achieve is that we either says "yes" or "no" now, because if we don't have the zest to do it now, we also won't do it during a future release. Too bad this won't get fixed! I've always avoided Display since it sounded like another console window -- but when I discovered it evaluates expressions, then I've wondered how it got its poor name. Yes, it's a poor, poor, poor name. Regarding comment #9 on re-education, that shouldn't be a problem; I doubt most people even know what this option does. (In reply to comment #11) > Too bad this won't get fixed! I've always avoided Display since it sounded like > another console window -- but when I discovered it evaluates expressions, then > I've wondered how it got its poor name. Yes, it's a poor, poor, poor name. > Regarding comment #9 on re-education, that shouldn't be a problem; I doubt most > people even know what this option does. Completely agree on all points! I still think the proposal from comment 8 is doable without much effort. But looks like you and me are outnumbered here, such is life... |