Speeding up Eclipse PHP debugging by using an external web browser
Today I got my environment for debugging PHP web pages working much more snappily, and I'm excited to share my tips. My experience only applies directly to you if you are running Eclipse and debugging PHP on a Macintosh with OS X.
Last weekend I scored a free VGA LCD monitor from my brother-in-law who didn't take it to law school with him and is now loaning it to me for at least a couple years. I was thinking "Free screen real estate, what could be better? I should be able to put the debugging web browser on one and screen the rest of my debugging windows on the other." After I got the right adapter to connect it, that is.
Once it was connected, the new monitor was somewhat convenient, but I quickly discovered that I couldn't put my Eclipse internal web browser in it's own window and move it to the other monitor. For some reason, Eclipse kept insisting on opening a new internal browser in the pane with the editing windows even if I had already opened the internal web browser in it's own window with "Window | Show View | Other... | Internal Web Browser" before I started the debugging session. And I was not allowed to "detach" the internal web browser tab from that pane and make it a separate window.
So I tried setting Eclipse to use an external browser for debugging at "Eclipse | Preferences... | General | Web Browser", reasoning that I could surely leave the external web browser's window on a different monitor from the Eclipse window I was using. Well, after a lot of time trying things I was left with only Firefox seeming to work. But it seemed slow and if Eclipse was running, Firefox was *always* starting the debugger in Eclipse and being very slow. Firefox is my browser of choice because of the Firebug plug-in, and Eclipse is about always running on my system. I just couldn't stand my main tool always being slowed to a crawl.
So I started trying every other Mac browser I could find until I discovered Camino. And it worked and even got invoked by the Eclipse debugger at the right time, but unfortunately it gave me errors like:
So here the main tip. Edit the settings for launching Camino at "Eclipse | Preferences... | General | Web Browser". In the Parameters edit box add the command-line option "-url %URL%" and Camino will start working as your Eclipse debugging browser.
The coolest thing is that my debugging between breakpoints started going several times faster. I was thinking that perhaps I needed a new computer to get faster debugging. But, it seems, that Eclipse's internal web server really bogs it down. So not only do I get more space for my other debugging panels with the new scheme I get a much faster PHP debugging system overall. Good deal! It would have been a good idea to do this even without getting a second monitor. If only I had known sooner that my setup for PHP debugging could be so quick and responsive. But at least I know now, -- and hopefully reading my story will help some fellow developers.
Comments
How do you treat the pop up
How do you treat the pop up message "Camino is already running on this system. Only one copy can be run at a time."
I changed my workflow for debugging
To deal with the "Camino is already running..." popup I had to modify my debugging workflow slightly. Basically, when I finish with debugging one thing I try to close my Camino instance. And when I start to debug a new thing I first check that there is not an instance of running (in case I failed the last step). Failing that, I learned on my Mac how I can close that popup fast (with just a return) if I do get it.
That said, I find that I can debug much faster than I used to, and since the Camino instance stays connected to the Zend debugger, I can do more debugging by clicking a link on the last page I debugged. So I don't have to close it as often as one would think.
That said, when I installed XDebug I found that this tip only works well with Zend debugger. XDebug tries to open another Camino instance when a session ends. So your proiblem (if it is REALLY annoying) may be caused by using XDebug.
I now have both debuggers installed and only use XDebug if I really need it. But for day-to-day debugging I use Zend debugger.
Quitting Camino with a keyboard shortcut
Following the above necessitates quitting Camino frequently. This often involves a switch out Eclipse, then close Camino, then back to Eclipse. To automate the process, you can add a keyboard shortcut to close Camino directly. I used this brief tutorial to do just that:
http://lifehacker.com/343328/create-a-keyboard-shortcut-for-any-menu-act...
I set up 'Control Q' just for Camino and it works perfect.
Does not work for me
I created the shortcut as you suggested but it only works within Camino, which defeats the purpose, since you might as well do ⌘-Q at that point.
Note: that Camino can be quit by going to it on the Dock and hitting ⌘-Q. And if you ever goof and get the error dialog that you are only allowed one instance of Camino, that one can be dispelled by going to it on the dock and hitting [enter].