| «« Unrecognized XSLTC extension Redirect:write | My Experience Moving RCP Apps from 3.0 to 3.1 »» |
|
About
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
Projects
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005 » Former committer for RadRails (now Aptana) » I also have a few Rails side-projects in development: 1. wheretogoinTO.com Toronto nightlife 2. Hey Heads Up! TODO list and sharing 3. Layered Genealogy family history research 4. foos for foosball scoring 5. fanconcert for music fans (on hold) Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada »» Email: rails AT ryanlowe DOT ca
BulletBlog
Now hosted on Hey! Heads Up -- check it out!
Syndication
Pings
Recent
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
blog@ryanlowe.ca no more Forging Email Headers: Good, Bad or Ugly? Sarcastic Dictionary (Part 1 of Many) Tags Hierarchies Twisting Rails is Risky Business Risky Business? My Take on Early Alphas Whoa, it's August 2007 Closing Comments A Postscript to "Growth at the grassroots" »» All Blog Posts
Linkage
del.icio.us/ryanlowe
technorati/ryanlowe.ca/blog Aurora Roy Jim Andrew Trasker Travis Kibbee Karen Dr. Unk Ayana Van Bloggers Joel Spolsky Robert Scoble Tim Bray Dave Winer Raymond Chen James Robertson Ruby/Rails Bloggers rubyonrails.org weblog David Heinemeier Hansson Dave Thomas James Duncan Davidson Mike Clark Jamis Buck Signal vs. Noise Tobias Luetke Amy Hoy: (24)slash7 Jeremy Voorhis Eclipse Bloggers Planet Eclipse EclipseZone Luis de la Rosa Eclipse Foundation Kim Horne Billy Biggs Ian Skerrett Mike Milinkovich Bjorn Freeman-Benson Denis Roy
Archives
  
|
Content Type Support Saves Me Time
Eclipse 3.1's new support for content types is already helping me out. Durham has a lot of Ant build files, many of which don't have the default Ant build file name  Eclipse 3.1 looks at the file's contents, sees that its an Ant XML build file and associates the file with the Ant editor right out of the box. This is especially helpful with XML files because there are so many different file types with the extension Fannnnntastic. It's little things like this that save me loads of time in the long run. That's exactly what using an IDE is all about. Posted at July 10, 2005 at 10:50 AM ESTLast updated July 10, 2005 at 10:50 AM EST Comments
Hmm, is that *really* what it's doing, cos my experience appears to be kinda the reverse. Are you sure it hasnt just associated the Ant editor as the default editor for *all* .xml files? [Check Preferences -> General -> Editor -> File Associations]. I find that on a clean Eclipse 3.1 install, only build.xml files get opened in the Ant editor, all other .xml files use the basic text editor. It does, however, appear to remember if you've specifically used "Open With" to use the non-default editor. The problem I'm having is that I've installed a plugin for editing xml files; it appears under the file associations (but isnt set as default). However, unless I specifically use "Open With", or set it as the default XML editor then it's not used. But if I select it as the default XML editor, then my Ant build files no longer open up in the Ant Editor (by default). » Posted by: Eric at July 12, 2005 10:33 AMEric, there's a simple way to verify that the content type is being used. Copy one of your Ant build.xml files alongside the original (I used the name test.xml). Notice that it uses the Ant editor, just like build.xml. Replace the entire contents of the copied file with a different tag, like <test/> save the file and then close the editor. Notice that the Ant editor icon is removed from the file in the Package Explorer. When you reopen the file it opens in a plain text editor. » Posted by: Ryan at July 12, 2005 12:26 PMNeat, so it does. Its a shame then, that logic apparently gets skipped when I set the default editor for .xml files - what happens for me when I do this, is that build.xml files show with a different icon in the Package Explorer, and open in that editor, rather than the Ant editor. And, once a default editor is set, I couldnt find a way to unset it - that is, return to the original behaviour - without a fresh install of Eclipse (and clean .metadata folder). I guess, what I want to be able to do is use a different editor (ie not the plain text editor) for all non-Ant .xml files. I have it installed, and can force it via "Open With", but havent yet found a way to do this automagically, via File Associations. » Posted by: Eric at July 12, 2005 01:45 PM |
