TableViewerColumn - Eclipse 3.3

[frankc01]

What is the projected support for widgets, controls, viewers, etc. that are added/enhanced in eclipse 3.3?

In the meantime, is there a way to add them to the Palette?

Thanks

[Eric Clayberg]

Other that TableViewerColumn, what did you have in mind? We do plan to support the new column viewers at some point after we finish adding support for eSWT/eRCP.

We have already added support for DateTime and the new Eclipse Data Binding API.



Simple widgets that follow standard SWT conventions can be added to the palette using the Palette Manager...

[frankc01]

My main focus was on the TableViewerColumn and 3.3 in general.

Various area's of generated code (primarily in a new app/plugin from the Instantiations wizards) have deprecated entites, etc. Not critical but curious

Thanks,
Frank

[Eric Clayberg]

Various area's of generated code (primarily in a new app/plugin from the Instantiations wizards) have deprecated entites, etc.

Was there a specifc wizard you are referring to?

Keep in mind that Designer supports Eclipse versions 2.1, 3.0, 3.1, 3.2, 3.3 and 3.4. We typically try to generate code that will run on as many different Eclipse platforms as possible.

[frankc01]

The New->RCP->New RCP Application Project produces Application.java with deprecated IPlatformRunnable.

It would seem that if you provide support for the variations that you give the developer the option to choose which level they are generating for.

Thanks,
Frank

[Eric Clayberg]

The New->RCP->New RCP Application Project produces Application.java with deprecated IPlatformRunnable. It would seem that if you provide support for the variations that you give the developer the option to choose which level they are generating for.

Ah. I was not sure what you were talking about because that wizard is not part of WindowBuilder / SWT Designer. I will pass that comment on to the RCP Developer team that is responsible for that wizard.

The choice of what to do about IPlatformRunnable is not so clear. IPlatformRunnable was only deprecated as of Eclipse 3.3 and has been the standard with the prior three versions of Eclipse which are still very much in general use. Many of our biggest customers are still using Eclipse 3.2 where the replacement APIs aren't even available.

We will probably add a preference to control whether you want to create 3.3-specific code or code that will run on any Eclipse version. If you are building a pure RCP app in 3.3 you would choose the second option. If you are building an Eclipse plugin, you would be better off chossing the first option in order to ensure that your code actually runs in different Eclipse environments thta are in active use.

[frankc01]

I agree and that is why I suggested giving the developer the option. They would know best what they want to target and require from a version standpoint (i.e. 3.3 versus > 3.3)

[Eric Clayberg]

I agree and that is why I suggested giving the developer the option. They would know best what they want to target and require from a version standpoint (i.e. 3.3 versus > 3.3)

Agreed. Look for that enhancement in RCP Developer soon.

[martin.lackner]

How do I use the TableViewerColumn and the TableColumnLayout.
In the palette I've the item "table column" under the topic "JFace Viewers", but it creates a TableColumn not a TableViewerColumn.

[Eric Clayberg]

Neither of those is avalable in the shipping product yet, but will be soon.