Re: plugin theory
Re: plugin theory
- Subject: Re: plugin theory
- From: Jesse Grosjean <email@hidden>
- Date: Mon, 10 Apr 2006 08:51:36 -0400
You can also add keys to the Info.plist or some property list file
of your own design inside the plugin bundle. Then you can use those
keys to get some basic information about a plugin *before* you decide
whether you'll even load the class. That way, you can e.g. have
importer plugins not loaded until the user actually exports to that
particular file format.
I've just done some cleanup work on Blocks, and open source plugin
framework for Cocoa. The cleanups are in trunk, no release yet.
http://svn.hogbaysoftware.com/public/Blocks/trunk/
Blocks provides a much simplified implementation, but similar design
to the plugin architecture used by the eclipse.org IDE project. The
important feature being that plugins can them-self load other
plugins. This makes it possible for your entire application to be
implemented in terms of plugins. I have two applications Clockwork,
and Mori that are implemented this way.
Anyway even if you are not interested in going that far there is
probably some code that will help you write your own plugin stuff in
the Sources folder of the Blocks release. That's where the core
classes for finding, loading, and instantiating plugins is. Here's
some Blocks documentation, though the documentation is beginning to
age compared to the code in trunk.
http://www.hogbaysoftware.com/book/blocksframeworkguide
Jesse
_______________________________________________
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