[cdt-core-dev] CDT ResolverModel vs ContentTypeManager

["Alain Magloire" <alain@xxxxxxx>]

Bonjour,
  The good folks from Timesys contributed the framework for file type resolution,
it contained UI(preference and property page) settings and Core Api(ResolverModel class).
This was done before, the platform IContentTypeManager framework.
                                                                                                                             
  A plan item for CDT-3.0 is to provide an adapter between the two worlds,
but looking closer at the IContentTypeManager framework, it provides all that is
needed now so we can now use the is framework as the backend, with a few caveats:

a) The content-type mappings are global i.e. it can not be set on a per project basis.
But so far, I've not see a real case where it is usefull.
Note: there is an enhancement PR
for this.

b) The content-type framework does not come with a UI
But we can still use the old UI and only change the backend to use the IContentManager.
Note: There is an example plugin provided by the platform/Core folks, hopefully it will
make its way down to the code in the future.

The big advantage; the CDT will no longer be playing alone in its sandbox, so
integration with other Eclipse components will be easier.


Any objection to morph this plan item ?

Comments/Feedbacks ?

-- 
au revoir, alain