Bugzilla – Full Text Bug Listing
| Summary: | use of new motif 2.1 widgets (1G8H23J) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Greg Adams <greg_adams> |
| Component: | SWT | Assignee: | Steve Northover <snorthov> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | Keywords: | helpwanted |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux-Motif | ||
| Whiteboard: | |||
We can look at this again post R2.0. Also anyone in the community who is keen to use the new widgets should feel free to investigate implementing the current functionality with them. Moving from Later. Motif is dead. We WONTFIX this. |
preamble from greg: At the moment this is not a request but more of a question/observation I wanted to log a pr to at leats capture the discussion. - There are some issues with the choices of widgets for the motif 2.1 implementation of SWT - XmContainer widget to do tree displays - Container Widget/Icon Gadget - display tabular and tree-structured information. - Notebook Widget - Spinbox Widget - Combo Box/Drop Down List Widget (appear to be used already) <GDA> Can you elaborate on the above & what you mean by "issues with the choices of widgets" </GDA> <DN> Motif 2.1 has new widgets. Are you making use of the new widgets? We noticed that the combo box widget has been changed in SWT to use the newer motif widget. Our resident motif guy wants OTI to be aware of the new widgets. That's all. </DN> <GDA-2> Ah, now I understand the nature of the question. Yes we are aware of the new widgets. We believe we're actually using the Spinbox for the Motif example of "how to build new widgets using natives" in the custom widget doc we are writing. We are looking at the other widgets, but haven't made decisions about whether or not to use them. At the moment this is not a priority 1. </GDA-2> NOTES: SN (2/5/01 5:22:03 PM) JH looked at the Motif widgets and found them to be lacking. In particular, the tree widget did not have enough API to be useful. We need to revisit this decision for each native widget. Not a priority right now.