Re: Debugging Plugins
Re: Debugging Plugins
- Subject: Re: Debugging Plugins
- From: Shaun Wexler <email@hidden>
- Date: Thu, 18 Sep 2003 13:12:02 -0700
On Sep 18, 2003, at 12:09 PM, The Amazing Llama wrote:
I have an application that uses a ton of plugins (well, it will; right
now it has one). The plugin is one target in the project and the
application is another.
Right now the plugin is doing something very annoying, and it's a
totally simple fix, if I could just put a breakpoint in the plugin.
But I can't, because the plugin is loaded at runtime, and so isn't
included in the normal application.
If both targets are in the same project, as you say, then you should be
able to set breakpoints in the editor window's gutter, as with a
single-target project. It works for me. I wonder what you may have
mis-configured? I can set a breakpoint in any of the umpteen plug-in
bundle targets in my project:
My new Panther-only application framework is 100% dynamic plug-in based
(the main executable is just 12k), and uses one embedded Shared
Framework in the main package, which is linked to by all plug-ins, plus
the app. With my class heirarchy, plug-ins can host other plug-ins,
and it's all coordinated by two subclasses of NSApplication and
NSDocumentController. The main menu is even built by the plug-ins at
runtime. Fully Document based, all doc types are provided by plug-ins,
where their types are added at runtime from each plug-in's Info.plist,
without necessarily loading the executables when registered. When the
user creates or loads a document, the app will dynamically activate the
appropriate plug-in if its classes are not already loaded. Plug-ins
(including those with their own doc types) can also be loaded and
activated by the user at any time during runtime. It only takes one
category on NSDocumentController with three simple methods to add this
dynamic type registration functionality, BTW.
The archives mention something about changing the path in "the
executable tab" but I can't find such a Tab anymore, so I assume it
went the way of the dodo at some point. There is an "Executables" area
under the "Targets" tab, and that has the application the project
builds, but no information for the plugin so I could set the plugins'
executable path to be the application.
I think that's do-do information you gleaned from the archives. I
assume you're using Xcode?
;)
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.