BillBlalock wrote:Thanks for the prompt reply and clear explanation. I understand the reasoning for not support these widgets and agree with them. I think these widgets are needed and Eclipse will eventually provide them.
We do plan to support all of Nebula eventually but many of those components will require special support since they don't follow normal SWT rules. We will also wait for them to mature a bit, so we aren't wasting engineering effort adding support for them prematurely.
BillBlalock wrote:Do you have suggestions about how to implement most of the functionality of these "widgets" with the tools available in SWT Designer?
If I were the author of those components, I would simply re-write them to be real widgets - either Text subclasses or Composites holding onto a single Text widget. If I wanted to use them right now, I would simply wrapper them in a custom Composite. The following could be used as a custom widget in Designer directly:
- Code: Select all
import org.eclipse.nebula.widgets.formattedtext.FormattedText;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.Composite;
public class MyFormattedText extends Composite {
private FormattedText ft;
public MyFormattedText(Composite parent, int style) {
super(parent, style);
setLayout(new FillLayout());
ft = new FormattedText(this, style);
}
public String getText() {
return ft.getControl().getText();
}
public void setText(String text) {
ft.getControl().setText(text);
}
}
BillBlalock wrote:I think users trying to understand and use data binding would appreciate samples / snippets of using SWT Designer with data binding for different kinds of editing, validation and formatting.
A number of different
DB examples are included in our
DB docs.
Keep in mind that we did not create the DB framework itself. It is the responsibility of Eclipse.org to supply docs, examples and snippets to show how to use the DB API. Any examples we provide are intended to show how to access the DB API from Designer. They are not provided as an exhaustive tutorial on what you can do with the DB API itself.