| 
| File type associations [message #450685] | Wed, 07 June 2006 12:44  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: andrew.easter.gmail.com 
 How exactly does eclipse deal with file type associations. For example...
 
 The plugin.xml file is a simple xml file that happens to describe a particular plugin. Given that this file is only an xml file (.xml extension) how does Eclipse determine:
 
 1) That the icon rendered in the tree should be the plugin editor icon and not just a standard xml file icon.
 
 2) That the PDE editor should be displayed rather than just a simple XML editor when double clicking to edit the file.
 
 I am confused by all of this. How would one, for example, go about editing the plugin.xml file without the PDE editor (i.e. with a standard xml file editor) and, also, what happens if more than one plugin specifies an editor for the same type? (e.g. two WSDL editors).
 
 Thanks for any help anyone can give me,
 
 Andrew
 |  |  |  | 
|  | 
| 
| Re: File type associations [message #450694 is a reply to message #450686] | Wed, 07 June 2006 22:57  |  | 
| Eclipse User  |  |  |  |  | Here is an answer to part of your question, but I don't think it addresses everything. 
 When you plug into the 'org.eclipse.ui.editors' extension-point, one of the things you specify is
 the file extension. That means, when Eclipse is asked to open a file of that type, it will use your
 editor. (I think there are clever tricky things that happen if more than one editor specifies the
 same extension.)
 
 In the Window -> Properties -> (enter text) File Associations you can see what other plugins have
 plugged into this extension-point.
 
 There is also Window -> Properties -> (enter text) Content Types -- where you can see that Eclipse
 has some secret way of "locking" an association. That I do not get.
 
 HTH,
 Paul
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.44880 seconds