Bug 145027 - Targets tab - Name vs Description columns width
Summary: Targets tab - Name vs Description columns width
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2006-06-02 04:16 EDT by Maxime Daniel CLA
Modified: 2019-09-06 15:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Daniel CLA 2006-06-02 04:16:36 EDT
3.2 - I20060602-0010
We have some scripts into which we do not use target descriptions at all (could be considered as bad practice... but pls read on). The target names are explicit, but a bit long sometimes. When checking the targets in the Run an Ant buildfile dialog, we face a Targets tab into which we cannot tell one target from the other without widening the Name column first.
(If you want to try it yourself, org.eclipse.jdt.core/scripts/exportplugin.xml -> a series of 'export p' names.)
So here is my suggestion: when descriptions are short, especially shorter than the names, or even empty, balance the respective width of the Name and Description columns in the favor of the Name column.
I would not want such feature to dissuade people from documenting their targets, but, in many circumstances, a clear name makes the trick without any supplementary description (especially if you use patterns and a planned codification, like we do for other entities like plugins for example).
Another way of doing it would be to have a 'show names only' checkbox (sticky).
Yet another way would be to memorize the resize the user applies if any (but this is weaker than auto balance, and complementary in fact: user choice overrides).

I have checked that the column width gets reset from one invocation to the other. I have not checked the behavior on other OSs.

Last but not least, the suggested ways to get the trick done are just the first ideas that came to my mind - whatever you do to alleviate the pain point will be much appreciated.
Comment 1 Darin Swanson CLA 2006-06-02 10:38:48 EDT
Do in conjunction with bug 139190.
Comment 2 Darin Swanson CLA 2007-02-17 00:53:25 EST
Not planned for 3.3
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:38:13 EDT
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.