| 260 |
<li>What are content type aliases? |
<li>What are content type aliases? |
| 261 |
<p>When a content type is marked as an alias for another content type (due |
<p>When a content type is marked as an alias for another content type (due |
| 262 |
to a file spec conflict), all of its properties are ignored, and any associations |
to a file spec conflict), all of its properties are ignored, and any associations |
| 263 |
with it will actually be made on the target type.</li> |
with it will actually be made on the target type.</p></li> |
| 264 |
<li>What are aliases for? |
<li>What are aliases for? |
| 265 |
<p>It is a mechanism to prevent conflicts. When multiple plugins contribute |
<p>It is a mechanism to prevent conflicts. When multiple plugins contribute |
| 266 |
content types associated with the same file specs, we have a conflict. Conflicts |
content types associated with the same file specs, we have a conflict. Conflicts |
| 299 |
</li> |
</li> |
| 300 |
<li>How does a client figure out whether a given file is a text file or not? |
<li>How does a client figure out whether a given file is a text file or not? |
| 301 |
<p>The proposed approach is to check if the file's content type is a kind |
<p>The proposed approach is to check if the file's content type is a kind |
| 302 |
of the "org.eclipse.core.runtime.text" content type, which is intended to |
of the "org.eclipse.core.runtime.text" content type, which is |
| 303 |
be the ancestor for all text oriented content types. If it turns out to |
intended to be the ancestor for all text oriented content types. If it turns |
| 304 |
be a very frequent idiom, we might consider proving a convenience API to |
out to be a very frequent idiom, we might consider proving a convenience |
| 305 |
do that.</p> |
API to do that.</p> |
| 306 |
</li> |
</li> |
| 307 |
<li>Do content types have to contribute content describers? |
<li>Do content types have to contribute content describers? |
| 308 |
<p> No, although if the file has a identifiable signature/format, it is recommended, |
<p> No, although if the file has a identifiable signature/format, it is recommended, |