Re: Getting started with WebKit plugins
Re: Getting started with WebKit plugins
- Subject: Re: Getting started with WebKit plugins
- From: Severin Kurpiers <email@hidden>
- Date: Thu, 12 Jan 2006 21:46:37 +0100
Hi Christopher,
just for the case that you haven't discovered it yet: you can even
debug your plugin. Here the short description how to do this:
1. Put a link (or an alias) to the built debug version of your plugin
into ~/Library/Internet Plug-Ins.
2. Add Safari as a custom executable to your plugin project (menu
Project > New Custom Executable…)
3. Set some breakpoints.
4. Call the menu Debug > Debug Executable (or click the debug button
or use the keyboard shortcut).
It will launch Safari. You can now let Safari open a html page that
uses your plugin and the debugger will recognize the breakpoints.
It's pretty cool :)
Bye,
Severin Kurpiers
Verek Ltd.
On 11. Jan 2006, at 18:49, Christopher Drum wrote:
[...]
(10) This makes sense, and I feel silly for not thinking about the
console for the log file. For some reason it just didn't occur to
me that NSLog was sending it's text anywhere, in the context of a
plugin. Of course, it must and I thank you for reminding me of the
fact.
Christopher
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden