platform-core-home/plan_content_types.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.2 - (view) (download) (as text)

1 : rchaves 1.1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2 :     <html>
3 :     <head>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
6 :     <title>Content types in Eclipse</title>
7 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
8 :     </head>
9 :     <body text="#000000" bgcolor="#FFFFFF">
10 :     &nbsp;
11 :     <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
12 :     <tr>
13 :     <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">
14 :     Content types in Eclipse - details</font></font></b></td>
15 :     </tr>
16 :     <tr>
17 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
18 :     <td WIDTH="98%">
19 :     <p><b>Plan item</b></p>
20 :     <p><i>&quot;Content-type-based editor lookup. The choice of editor is currently
21 :     based on file name pattern. This is not very flexible, and breaks down
22 :     when fundamentally different types of content are found in files with
23 :     undistinguished file names or internal formats. For example, many different
24 :     models with specialized editors get stored in XML format files named *.xml.
25 :     Eclipse should support a notion of content type for files and resources,
26 :     and use these to drive decisions like which editor to use. This feature
27 :     would also be used by team providers when doing comparisons based on file
28 :     type. The several existing file-type registries in Eclipse should be consolidated.
29 :     [Platform Core, Platform UI] [Theme: User experience] (bug <a
30 :     href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=37668">37668</a>, <a
31 :     href="http://dev.eclipse.org/bugs/show_bug.cgi?id=51791">51791</a>, <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=52784">52784</a>)&quot;</i></p>
32 :     </td>
33 :     </tr>
34 :    
35 :     <tr>
36 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
37 :     <td WIDTH="98%">
38 :     <p><b>Overview document</b></p>
39 :     <p>An overview of the proposed solution is available <a href="documents/content_types.html">here</a>.</p>
40 :     </td>
41 :     </tr>
42 :     <tr>
43 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
44 :     <td WIDTH="98%">
45 :     <p><b>Related bug reports</b></p>
46 :     <p>A list of related bug reports is available <a href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=substring&short_desc=%5Bcontent+type%5D&product=Platform&component=Core">here</a>.</p>
47 :     </td>
48 :     </tr>
49 :     <tr>
50 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
51 :     <td>
52 :     <p><b>Current status</b></p>
53 :     <p><em>May 5th, 2004</em></p>
54 :     <p>Core content type infrastructure is being currently used by the new encoding support (Resources),
55 :     content-sensitive object contributions (UI) and structured content comparisons (Compare)</p>
56 :     <p><em>April 28th, 2004</em></p>
57 :     <p>The adoption of content types for editor lookup has been postponed for after 3.0. Core content type
58 :     infrastructure will be available for 3.0 (bug <a
59 :     href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=60291">60291</a>)</p>
60 :     <p><em>April 6th, 2004</em></p>
61 :     <p><a href="documents/content_types.html">Proposal</a> was made available. </p>
62 :     <p>Gathering feedback from the community.</p>
63 :     </td>
64 :     </tr>
65 :     </table>
66 :    
67 :     </body>
68 :     </html>