Re: Debugging Plugins
Re: Debugging Plugins
- Subject: Re: Debugging Plugins
- From: Eric Wang <email@hidden>
- Date: Sat, 20 Sep 2003 20:18:30 -0400
on 9/20/03 1:23 AM, Shaun Wexler at email@hidden wrote:
>
I added a category to NSDocumentController, with a method to return the
>
private _types array, and another to add any new types by replacing
>
that array with a new copy. My subclass overrides
>
-documentClassForType: to post a notification when an unknown class is
>
encountered, and the -openDocument method to present a multi-doc open
>
panel when asked to create a new document. There are several added
>
methods to support my plug-in scheme as well as KVC/KVO compliance. To
>
allow double-clicking plug-ins in the Finder, I created a sole document
>
type for the app itself, which triggers a proxy document class which
>
just uses -readFromFile:ofType: to load the plug-ins, and then goes
>
away. The application subclass manages all plug-in registration and
>
activation, and tracks which classes belong to which plugins. With the
>
new controller layer in Panther, subclassing NSApplication is much more
>
useful than it used to be. It's amazing how well this new app
>
structure came together, with little effort, and minimal coding. Maybe
>
I should write a paper? Or sell some software... ;)
You should do both. ;-)
--Eric
_______________________________________________
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.