Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 60291

Summary:	[Plan item] Content-type-based infrastructure
Product:	[Eclipse Project] Platform	Reporter:	Jim des Rivieres <jeem>
Component:	Resources	Assignee:	Rafael Chaves <eclipse>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	david_williams, eclipse, ed.burnette, gunnar, john.ruud
Version:	3.0	Keywords:	plan
Target Milestone:	3.0
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	37668

Description Jim des Rivieres

2004-04-28 13:35:03 EDT

The choice of editor is currently based on file name patterns. This is not 
very flexible, and breaks down when fundamentally different types of content 
are found in files with undistinguished file names or internal formats. For 
example, many different models with specialized editors get stored in XML 
format files named *.xml. Eclipse should provide infrastructure support for a 
notion of content type for files and resources.

(This plan item was split off from 3.0 plan item bug 37668.)

Comment 1 Rafael Chaves

2004-04-28 18:03:36 EDT

A content type registry is in place. Since it was done too late, adoption (in
the Eclipse SDK) will be limited, editor-file associations and a central UI for
for manipulating content types being the most noticeable missed use cases.

Here are the scenarios taking advantage of the content type registry:
- non-uniform file encoding in the workspace (bug 37933 - [plan item] Improve
file encoding support)
- file associations in Compare extension points (bug 51791 - Allow binding
filenames to compare extensions)
- content sensitive object contributions, being retrofitted to work with the
content type registry (bug 33018 - [Contributions] plugin.xml context menu
should not have "Run Ant..." item)

Also, the Team team is considering adopting it as well, not sure about the exact
scenario/planned schedule.

Comment 2 Rafael Chaves

2004-05-07 14:29:15 EDT

Fixed.

Comment 3 Rafael Chaves

2004-08-13 13:25:29 EDT

*** Bug 52784 has been marked as a duplicate of this bug. ***