[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [riena-dev] SWT Ridget implementations becoming API ?
|
Hi Elias,
Provisional API -> Full API does not have to include a package name
change (although this is what p2 decided to do). It can simply be a
matter of having/removing x-internal markup in manifest (and this *is*
required I believe).
See this Architecture Council bug for ongoing conventions discussion:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261874
Scott
Elias Volanakis wrote:
Hi committers,
I've noticed that some parts of the Ridget implementations
(AbstractActionRidget, etc.) have been moved to
org.eclipse.riena.ui.ridgets.swt. I know that some of you are working
on custom ridgets using this stuff.
One concern I have is that we may restrict ourselves too much in the
future, by promoting these implementations to API status too early.
Let me know your thoughts on this...
Kind regards,
Elias.
PS: A middle ground would to promote these classes to "provisional"
api status. The drawback is that is adds an additional refactoring
step of making the official API (package move). However it is
understood by consumers that provisional APIs may change.
--
Elias Volanakis | Technical Lead | EclipseSource Portland
elias@xxxxxxxxxxxxxxxxx <mailto:elias@xxxxxxxxxxxxxxxxx> | +1 503 929
5537 | http://eclipsesource.com
------------------------------------------------------------------------
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
