platform-core-home/documents/content_types.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.7, Mon Jan 17 17:17:37 2005 UTC revision 1.8, Wed Feb 16 16:23:03 2005 UTC
# Line 6  Line 6 
6  </head>  </head>
7  <body text="#000000" bgcolor="#ffffff">  <body text="#000000" bgcolor="#ffffff">
8  <h1>A central content type catalog for Eclipse</h1>  <h1>A central content type catalog for Eclipse</h1>
9  <p><font size="-1">Last modified: May 12th, 2004</font> </p>  <p><font size="-1">Last modified: Feb 16, 2005</font></p>
10  <p><cite><strong>Plan item description:</strong> Content-type-based editor lookup.  <p><cite><strong>Plan item description:</strong> Content-type-based editor lookup.
11    The choice of editor is currently based on file name pattern. This is not very    The choice of editor is currently based on file name pattern. This is not very
12    flexible, and breaks down when fundamentally different types of content are    flexible, and breaks down when fundamentally different types of content are
# Line 313  Line 313 
313    should be discussed in the platform-core-dev list, or bug <a    should be discussed in the platform-core-dev list, or bug <a
314   href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=37668">37668</a>. </em></p>   href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=37668">37668</a>. </em></p>
315  <h2>Addendum: issues to be addressed in the 3.1 cycle</h2>  <h2>Addendum: issues to be addressed in the 3.1 cycle</h2>
 <p><font size="-1">Last modified: January 17th, 2005</font></p>  
316  <p>The solution described above was implemented and relatively succesful. Some  <p>The solution described above was implemented and relatively succesful. Some
317    components took advantage of the new content type infrastructure, but still    components took advantage of the new content type infrastructure, but still
318    in many cases file-association is being done in an ad-hoc manner. Also, no UI    in many cases file-association is being done in an ad-hoc manner. Also, no UI
# Line 367  Line 366 
366    objects for a given content type (editors, views, comparators, etc). Users cannot    objects for a given content type (editors, views, comparators, etc). Users cannot
367    provide content type detection code, so user-defined content types would be    provide content type detection code, so user-defined content types would be
368    useful only for cases where content type detection is file name based (like    useful only for cases where content type detection is file name based (like
369    for non-formatted text files, such as source files, configuration files, etc).    for non-formatted text files, such as source files, configuration files, etc).</p>
370  </p>  <p>A simple plug-in that allows users to add/remove file associations is available
371      in the <a href="../downloads.html">downloads page</a>.</p>
372  <h3>Improve content type determination</h3>  <h3>Improve content type determination</h3>
373  <p>Ensure content type detection works (or can be made to work) appropriately  <p>Ensure content type detection works (or can be made to work) appropriately
374    when incompatible products are deployed together.</p>    when incompatible products are deployed together.</p>
Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8