| 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: April 6th, 2004</font> </p> |
<p><font size="-1">Last modified: May 12th, 2004</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 |
| 138 |
about an arbitrary stream of bytes. These information are filled partially by |
about an arbitrary stream of bytes. These information are filled partially by |
| 139 |
the platform and partially by the content describer elected (if any).</p> |
the platform and partially by the content describer elected (if any).</p> |
| 140 |
<h3>Conflict resolution</h3> |
<h3>Conflict resolution</h3> |
| 141 |
<p>Content types are managed by the platform but, except for a few cases, plug-ins |
<p>Content types are managed by the platform but plug-ins |
| 142 |
are in charge of contributing content types. While this provides good flexibility, |
are in charge of contributing content types. While this provides good flexibility, |
| 143 |
it also opens oportunities for conflicts. There are a few scenarios where conflicts |
it also opens oportunities for conflicts. There are a few scenarios where conflicts |
| 144 |
may arise:</p> |
may arise:</p> |
Parent Directory
| 
Revision Log
| 
Patch