Drosera requires Safari 3.1 or 3.0. It cannot be used with Safari 2.
If you are using a nightly build of WebKit, Drosera is already enabled for you.
To allow Drosera to attach to Safari 3, enter the following command in Terminal:
defaults write com.apple.Safari WebKitScriptDebuggerEnabled -bool true
If you would like to debug your own WebKit-based application using Drosera, simply replace com.apple.Safari in the above command with your own application's bundle identifier or add the WebKitScriptDebuggerEnabled with a value of true to your Info.plist.
Once Drosera is launched, you're presented with the Attach window, showing all running applications capable of being debugged with Drosera. Select the application you want to debug to load the debugging window.
Double clicking a line number in the editor window sets a new breakpoint. To delete a breakpoint, simply drag the breakpoint arrow from the line number.
Function and Variable Stacks
While a script is paused, you can examine the contents of the variables within various scopes of the code.
Drosera on Windows
Most of Drosera has been ported to windows and can now run and attach to a Safari on Windows instance. Drosera is not currently in a nightly and will need to be built from the source.
Much of the design of Drosera on Windows is intentionally extremely similar to the design of Drosera on Mac, however, because of the many small differences, for clarity, this section will only focus on the design on Windows without identifying the divergences.
The ServerConnection object implements IWebScriptDebugListener and encapsulates all of the interactions with the remote WebKit server.