I know about the XML plug-ins for Eclipse. This thread is about why Eclipse doesn't support XML out of the box? This seems like something every IDE/Editor should simply provide. Ok, I know I am complaining about something that is free and that there is a simple solution for with the plugins, however, that is just one more plug-in I have to try and keep updated. Anyone know why Eclipse chose to leave XML support out of the base system?
Because the base system doesn't handle *anything* regarding specific languages. Remember, even support for Java is actually a separate collection of plugins from the base system.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Ilja Preuss: Because the base system doesn't handle *anything* regarding specific languages. Remember, even support for Java is actually a separate collection of plugins from the base system.
I've also been wondering the lack of built-in XML support. What strikes me even more is that by default, Eclipse doesn't include a file association for *.xml files (i.e. I need to map them to the default/text editor by hand).
Eclipse doesn't include a file association for *.xml files (i.e. I need to map them to the default/text editor by hand). Just to agree that this is one of the things that annoyed me most when I first tried to use Eclipse. I would click an XML file to edit it and Eclipse would stupidly pass it on to the OS, which would load it in Internet Explorer instead. I'm a long-time TextPad user, and can't help thinking that an IDE is essentially an editor, and that an editor's job is to at least try and edit files. Is there any sort of global "open all unknown files using the default editor" switch?