Bug 92868 - [Forms] ambiguous spec on IManagedForm
Summary: [Forms] ambiguous spec on IManagedForm
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Dejan Glozic CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2005-04-27 01:35 EDT by Jim des Rivieres CLA
Modified: 2005-04-29 18:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim des Rivieres CLA 2005-04-27 01:35:32 EDT
3.1 HEAD

 * Although many Eclipse Forms classes expect IManagedForm interface,
 * implementing it is not required. Instead, ManagedForm should
 * either be used as-is or subclassed.
 * @see ManagedForm
 * @since 3.0
 */
public interface IManagedForm {

- it's unclear from this spec whether clients are allowed to implement 
IManagedForm if they so choose. I believe the intent was that they must use 
ManagedForm instead. The spec need to be clear on this. Use standard 
boilerplate.

(initialize() was added in 3.1 cycle, and would be a breaking change if this 
were not the case.
Comment 1 Dejan Glozic CLA 2005-04-29 18:36:11 EDT
Thanks - I have improved the Javadoc to make it clear that ManagedForm should 
be used.