Summary: | Integrate the Resolver Model with Eclispe-3.0 ContentTypes framework | ||
---|---|---|---|
Product: | [Tools] CDT | Reporter: | Alain Magloire <alain> |
Component: | cdt-core | Assignee: | Alain Magloire <alain> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | gheorghe, leo.treggiari, mlists, sam.robb |
Version: | 2.0 | ||
Target Milestone: | 3.0 | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | 72796 | ||
Bug Blocks: |
Description
Alain Magloire
2004-08-27 15:49:55 EDT
Integrate CDT to the ContentType framework Folks(Sam, gheorghe), I do not know if you been following the discussion with Rafael. Basically, I want CDT to use the new IContentManager/IContentType scheme instead of the ResolverModel, it will provide better integration to eclipse. So we still use the same UI provided by Sam(Preference/Property) but instead the types will be save on the IContentManager instead. To help the transistion we can provide an Adapter between the ResolverModel and the IContentManager Any comments/feedbacks ? We are waiting on Eclipse-3.1 architecture. The ResolverModel class been updated to provide an adapter for the IContentManager. Sam ... what about long term solution ... discussion: shoud we migrate to use IContentManager only any feedback welcome Marking this as fixed. In the head. |