[riena-dev] SWT Ridget implementations becoming API ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[riena-dev] SWT Ridget implementations becoming API ?

From: Elias Volanakis <elias@xxxxxxxxxxxxxxxxx>
Date: Wed, 1 Apr 2009 10:16:04 -0700
Delivered-to: riena-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/riena-dev>
List-help: <mailto:riena-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/riena-dev>, <mailto:riena-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/riena-dev>, <mailto:riena-dev-request@eclipse.org?subject=unsubscribe>

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 | +1 503 929 5537 | http://eclipsesource.com

Follow-Ups:
- Re: [riena-dev] SWT Ridget implementations becoming API ?
  - From: Christian Campo
- Re: [riena-dev] SWT Ridget implementations becoming API ?
  - From: Scott Lewis

Prev by Date: Re: Antw: Re: [riena-dev] Interface not visible from class loader!
Next by Date: Re: [riena-dev] SWT Ridget implementations becoming API ?
Previous by thread: [riena-dev] Interface not visible from class loader!
Next by thread: Re: [riena-dev] SWT Ridget implementations becoming API ?
Index(es):
- Date
- Thread

Breadcrumbs