Community
Participate
Working Groups
We should integrate the resolver Model with the content type see PR: https://bugs.eclipse.org/bugs/show_bug.cgi?id=72796 This will allow many things to work correctly, Comparator, structure viewer(With CVS) etc ... except for the Editor see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=37668 schedule for Eclipse-3.1 only
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.