Jared Rypka-Hauer, Lead ColdFusion Developer, Minneapolis, MN
Proud Parents of SQLSurveyor and PayPalMX
Viewing By Category : CFEclipse / Main
November 5, 2006 - back to top
Eclipse... the Hot Thing in IDEs for many members of the ColdFusion community these days. It's full-featured, but more than that it can take a bajillion plugins.
So what if you change machines? Since Eclipse is a project-based (as opposed to directory-based like HomeSite or CFStudio), moving from machine to machine can be a huge pain. Having to copy the folders over to a new computer and create all your old projects by hand... egads, what a time-consuming waste of energy. Or not.
If you right-click in the Navigator pane, hit Import... then under General choose Existing Projects into Workspace..., select your root folder (in my case it's the webroot of my local server) and tell it to go, it'll find all your existing projects and add them to your navigator pane automatically.
I think this is an especially handy tool as FlexBuilder2 just came out for OSX and many of us have been using Eclipse for a while now. If you're running the bundled product (not the Eclipse plugin) and you want to move your Eclipse projects into FlexBuilder2, this is the way to go!
Laterz...
So what if you change machines? Since Eclipse is a project-based (as opposed to directory-based like HomeSite or CFStudio), moving from machine to machine can be a huge pain. Having to copy the folders over to a new computer and create all your old projects by hand... egads, what a time-consuming waste of energy. Or not.
If you right-click in the Navigator pane, hit Import... then under General choose Existing Projects into Workspace..., select your root folder (in my case it's the webroot of my local server) and tell it to go, it'll find all your existing projects and add them to your navigator pane automatically.
I think this is an especially handy tool as FlexBuilder2 just came out for OSX and many of us have been using Eclipse for a while now. If you're running the bundled product (not the Eclipse plugin) and you want to move your Eclipse projects into FlexBuilder2, this is the way to go!
Laterz...
May 24, 2006 - back to top
I just got an IM from Mark Drew of the CFEclipse team that they have schwag for sale at Cafe Press.
This is a good time for me to point out that CFEclipse is a huge undertaking and a labor of love for the people involved. They ask for nothing but some gratitude from those who use the software they've been producing, enhancing, and supporting for a while now. I think it's high time we, as a community, show that gratitude in the form of... cash.
They've got a variety of items available and prices range from $10.99USD to $20USD.
Go forth, buy, wear, and promote!!
Laterz!
This is a good time for me to point out that CFEclipse is a huge undertaking and a labor of love for the people involved. They ask for nothing but some gratitude from those who use the software they've been producing, enhancing, and supporting for a while now. I think it's high time we, as a community, show that gratitude in the form of... cash.
They've got a variety of items available and prices range from $10.99USD to $20USD.
Go forth, buy, wear, and promote!!
Laterz!
April 12, 2006 - back to top
[Note: It's not correct to say that Swing apps can't run on OSX. What is correct is that SWT applications and AWT apps cause the JVM to hang when they try to communicate with eachother in a running application. So, for example, if a SWT application (like Eclipse) tried to launch an AWT widget (like xPath Explorer), the result would be a hang, or at least a crash of some or all parts of the application. The problem is explained clearly in the link to Comment 110 below. OK, I hope I got that right.]
For those of you out there who want to run FlexBuilder2 on a Mac (without using an Intel Mac and Windows), you may be happy to hear that, according to a thread on bugs.eclipse.org, Apple is working to patch this long-standing breakage. What would this mean? Well, it would mean that the Visual HTML builder in MyEclipse (as well as the UML tool) would work. FlexBuilder would work. even xPath Explorer would work.
Layman's Overview: Basically, there's a problem with the the Java SWT and the Swing windowing library, and it means that Swing applications can't run on OSX. The subsystems that allow Swing applications to run on OSX (handled by Cocoa) basically hang the JVM because SWT has the relevant thread blocked.
The last few messages in this thread on bugs.eclipse.org indicate that Apple has worked thru some of the key points and is on the way to releasing a fix that would make all our lives a LOT happer (oooh, FB2 on OSX! Happy Day!)
Yeah, I'm a geek.
Anyway, some interesting posts in this thread are:
Laterz!
For those of you out there who want to run FlexBuilder2 on a Mac (without using an Intel Mac and Windows), you may be happy to hear that, according to a thread on bugs.eclipse.org, Apple is working to patch this long-standing breakage. What would this mean? Well, it would mean that the Visual HTML builder in MyEclipse (as well as the UML tool) would work. FlexBuilder would work. even xPath Explorer would work.
Layman's Overview: Basically, there's a problem with the the Java SWT and the Swing windowing library, and it means that Swing applications can't run on OSX. The subsystems that allow Swing applications to run on OSX (handled by Cocoa) basically hang the JVM because SWT has the relevant thread blocked.
The last few messages in this thread on bugs.eclipse.org indicate that Apple has worked thru some of the key points and is on the way to releasing a fix that would make all our lives a LOT happer (oooh, FB2 on OSX! Happy Day!)
Yeah, I'm a geek.
Anyway, some interesting posts in this thread are:
- Comment 81 (See, this whole Adobe thing is Good Stuff®)
- Comment 110 (a good rundown on the bug)
- Comments 123 & 124 (just goes to show how reading up helps!)
- Comment 127 (getting closer)
- Comment 130 (sigh, but there's hope!)
Laterz!
September 20, 2005 - back to top
Well, it's been a while since I posted anything, but I just got a long-standing issue taken care of that I have been asked about by others in the past and it got me to get back to blogging.
A while back, Phill Nacelli was asking me about using Eclipse w/CFE and XMLBuddy to edit files with names like *.xml.cfm that, by default would open in CFEclipse instead of the XMLBuddy editor like one would wish. Well, Phill, this ones for you.
Open your Eclipse Prefs panel, go to General: Editor: File Types, slide down the list to *.cfm in the top pane, and click Add... in the lower pane. Scroll down to the end of list list of editors where you'll find XMLBuddy and click OK. Yep, that's right... add XMLBuddy as an editor for your .cfm files. The nice thing is this: Eclipse keeps track of which files were opened last in which editor.
Then, in the Navigator view, right-click on your config.xml.cfm file and go to Open With > and behold the XMLBuddy entry. Yeppers, click on XMLBuddy and voila... your .cfm file will open and be displayed in all its XML glory even though the file extension is truly .cfm.
I'll grant you that there's probably a more elegant, automatic solution to this problem. I know some have told me this, anyway. But, after adding all sorts of file types, content types, and editor configurations, this is the one that actually let me open a ModelGlue.xml.cfm file in XMLBuddy with no issues. And, honestly, what works is what's going to get used.
If it ain't broke, don't fix it may be true... but the definition of insanity is doing the same thing over and over again expecting a different result each time. Reality, and sanity, are somewhere in the middle. In this case, the workaround is actually effective in all respects. So, if you have a better solution, by all means send it along... but for now, here ya go Phill!
Laterz!
A while back, Phill Nacelli was asking me about using Eclipse w/CFE and XMLBuddy to edit files with names like *.xml.cfm that, by default would open in CFEclipse instead of the XMLBuddy editor like one would wish. Well, Phill, this ones for you.
Open your Eclipse Prefs panel, go to General: Editor: File Types, slide down the list to *.cfm in the top pane, and click Add... in the lower pane. Scroll down to the end of list list of editors where you'll find XMLBuddy and click OK. Yep, that's right... add XMLBuddy as an editor for your .cfm files. The nice thing is this: Eclipse keeps track of which files were opened last in which editor.
Then, in the Navigator view, right-click on your config.xml.cfm file and go to Open With > and behold the XMLBuddy entry. Yeppers, click on XMLBuddy and voila... your .cfm file will open and be displayed in all its XML glory even though the file extension is truly .cfm.
I'll grant you that there's probably a more elegant, automatic solution to this problem. I know some have told me this, anyway. But, after adding all sorts of file types, content types, and editor configurations, this is the one that actually let me open a ModelGlue.xml.cfm file in XMLBuddy with no issues. And, honestly, what works is what's going to get used.
If it ain't broke, don't fix it may be true... but the definition of insanity is doing the same thing over and over again expecting a different result each time. Reality, and sanity, are somewhere in the middle. In this case, the workaround is actually effective in all respects. So, if you have a better solution, by all means send it along... but for now, here ya go Phill!
Laterz!