I just got the editor and debugger installed and working (Trial). So far it's what I've been looking for with 2 exceptions:

1. If I am in a debugging session that opens a new browser window (working with Multi Operator Chat system atm) watches stop being tracked and break points fail when control is passed from the output window to the new browser instance. This is the only thing stopping me from throwing some $ at NuSphere for the full License

Is there a way to force redirects/target=blank back to the Output window to maintain watches etc.

2. (not a deal breaker, just an observation) It would be nice to see an option for I/O watches per page.
I would find 99% of my var watching simplified by seeing a side by side report of inital vars on page load, and all Vars on page exit/render and maybe an auto-breakpoint on auto refreshes. I guess another way to think of it is a preconfigured batch watch with an auto break on refresh.[/list]

The first point you could probably solve by manually adding the DBGSESSID variable to the new window. The debugger only initiates if it has a cookie and that isn't passed along to the new instance I presume.
By manually specifying the DBGSESSID you can force the debugger to kick in. Take a look here, here or in the rest of the FAQ for more info.

Isn't the profiler a good start for your 2nd point? I'm not sure I completely get what you want.

Right. Although it's not obviuous, but it works as it should. When you open a new browser window from the IDE, IE will create new instance which will not see any temporary cookies from the browser embedded into the IDE. They are in different processes, that's it. To solve this even easier than suggested by Blizz, you may want to use External broser from the beginning. In this case browser won't create new instance (new process) for the new windows and will see all the cookies and will maintain php and debugger sessions properly.