Bugzilla – Full Text Bug Listing
| Summary: | When opening the PDE editor, correct page should be selected | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Miles Parker <milesparker> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ankur_sharma, contact |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Miles Parker
Hi Miles, Duplicate of bug 241473 ? Hi Benjamin, Not quite I guess, though it is the same pain. Actually I think my suggestion is actually a third way -- perhaps when that preference is created this could be one of them. Here are the three options that I see.. When a user opens one of MANIFEST.MF, plugin.xml, build.properties.., etc.. 1. Go to page most appropriate *for the actual file that the user just double-clicked*. ;D (My suggestion) 2. Go to page that was last opened for that particular project. (Current Implementation) 3. Go to same page that was opened in the last focussed editor. (Lars' suggestion, I think) 4. Go to the Overview (first) page. My suggestion (1) I think is least violative of POLS. When I double-click on a file, I expect to be able to edit the contents of that file, darn it. :) I think this would be expected behavior for new users but its been so long since I've been one of those that I dunno. The current implementation (2) is actually one of the more confusing possibilities I think. After all, when you open a Java file or any other type (say an EMF editor) you don't expect to go to the last cursor position or page. If you're working with a bunch of files it's confusing to have each page you open go to an apparently random page based on something that you may have been working on in a completely different context. If I want to retain context, I'm likely to just leave the file open. I think Lar's suggestion (3) has a lot to recommend it from a flow of work perspective. Typically when you're opening a bunch of project artifacts you're looking to edit the same things. For example, when I'm editing dependencies (MANIFEST.MF), I'd like to look at that page for a number of different files. Option (4) is most straightforward and as I say I'm not sure that 2) adds that much value compared to it. As far as overall usability goes, I almost always find myself moving to a different page. cheers, Miles I tend to agree with Lars on bug 241473. Current behavior is decent enough and a preference will be added complexity (we already have quite a many). Also, it is debatable that which page is more suited default page when a file can be edited through multiple pages/editors. However, a patch contribution is always welcome. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release. |