| Summary: | Confusion about external tool config dialog | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | John Arthorne <john.arthorne> |
| Component: | UI | Assignee: | Ryan Cooper <ryan_cooper> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P1 | CC: | rodrigo, simon_arsenault |
| Version: | 2.0 | Keywords: | usability |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
John Arthorne
Important to get the labeling right here. I do not see changing the label as a viable solution... The word "script" by itself has a specific "domain" meaning which is why we changed to using External Tools. If we add the word ant, then people will want other words too (like makefile, etc). We need to come up with another way so users will understand this External Tool concept and what is applies to. Maybe a short 1-2 line description at the top of the configure dialog is our best option for release 2.0 Update the description for both the configure and new/edit dialogs to be more specific and refer to Ant build files. Also, in the new/edit dialog, when an XML file is specified, the message changes to indicate how to choose the ant targets. In build > 2002-05-29 |