Hi again devs, 1. I have created a CellEditor for the CDateTime widget:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196498 This raises the question of how to express the dependency on the JFace CellEditor class and framework classes in general. I am leaning towards making JFace an optional plugin dependency. JFace is only required if the client code is using that specific class, and the client already must be manipulating other JFace classes before the CellEditor would be useful. It's very likely that the client code will already depend on JFace. It also doesn't seem like it's worth creating a whole new plugin for this one class. However, I'd like to document the supported versions of JFace. Do any of you have strong opinions on these issues? 2. The Nebula website does not clearly document the supported versions of dependencies. I'd like to remedy this, and also include the versions in the plugin manifests so they can be verified. Have you tested your widgets against specific versions of the JRE and SWT? I suspect that some of the widgets might be compatible as far back as Eclipse 3.0 and Java 1.3, but it is easy to introduce unintentional dependencies by compiling against more recent versions. Should we make a collective policy decision on what the minimum requirements should be for Nebula? Thanks in advance.... -- Peter _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
