Bug 187262 - [DataBinding] Consider making converter classes API
Summary: [DataBinding] Consider making converter classes API
Status: RESOLVED DUPLICATE of bug 183055
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-16 10:10 EDT by Dave Orme CLA
Modified: 2007-05-16 14:30 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Orme CLA 2007-05-16 10:10:45 EDT 
When creating anything custom using data binding, one often needs to work with existing converters.  IConverter is API, but currently our library of standard converters is not.  The result will be that folks will have to copy the standard converters into their own projects, resulting in duplication.

Since IConverter is already API anyway, I see no harm in making our library of standard converters API also.  We won't have any need to change their names.  We will only add to them.  If we make API changes to IConverter, we will make corresponding API changes to Converter and our existing implementations as necessary.
Comment 1 Peter Centgraf CLA 2007-05-16 14:01:38 EDT 
I believe this is essentially the same request as bug 183055.  I've found that the existing converters and validators are not sufficiently flexible, and I think they should be improved before promoting them to API.  Since we're talking about 3.4 API, there should be plenty of time to do so.
Comment 2 Dave Orme CLA 2007-05-16 14:30:33 EDT 
Hi Peter,

If you believe that our current API is inadaquate, and that fixing it will require making breaking changes, we must do that *now*.  After 3.3 ships, we're stuck with the API we've got.

*** This bug has been marked as a duplicate of bug 183055 ***