[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [nebula-dev] Dependencies / Versioning
|
Hi Peter,
1.) Using an optional dependency seems to make sense in your case. In
situations where there's more significant JFace code, I'd prefer
separating it out into another plugin. If nothing else, its easier to
ensure that JFace references don't creep into other parts.
2.) Another good point. This is something we haven't done a good job
on. We did have some discussions initially about supported JRE, SWT.
As for the JRE, in order to be included in SWT you would need to support
CLDC (1.1 variation). Obviously not everyone is gonna want to do that.
So instead we agreed to support 1.4 as most. We have not moved to 1.5
(and I don't believe the main Platform has either, right?). As for SWT,
the general rule was that we were going to try to stay concurrent with
SWT development. This was before we decided to split off into separate
plugin projects. I don't think it matters much now that we can specify
the dependencies individually. We just need to do a better job of
enumerating and displaying these dependencies on each widget's web page.
Regards,
-Chris
Peter Centgraf wrote:
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
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
