| Summary: | [JFace] Need uniform stratergy to handle truncation. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Tejas Parajia <tparajia> |
| Component: | UI | Assignee: | Susan McCourt <susan> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | bpasero, tparajia |
| Version: | 3.3 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tejas Parajia
I believe the code that produced that truncated string should probably live in JFace and the string the fed to SWT? Not clear that uniform strategy is appropriate, as it may differ for different UI elements. An application policy would have to also allow different strategies for different UI elements. In some cases we even truncate the ellipsis since it provides little value when real estate is tight. I think it would be challenging to come up with a strategy that fits all cases, but public methods to handle truncation in different ways might be nice (vs. the many implementors of shortenText* that we have now). *** This bug has been marked as a duplicate of bug 119644 *** |