Re: difference between frameworks and plugins
Re: difference between frameworks and plugins
- Subject: Re: difference between frameworks and plugins
- From: Andrew Farmer <email@hidden>
- Date: Wed, 2 Feb 2005 20:17:11 -0800
On 2 Feb 2005, at 19:17, Jesse Grosjean wrote:
What I would like to do is allow one plugin to treat (have access to
the symbols at build time) another plugin as if that plugin were a
framework. Is this possible or is there some fundamental difference
between plugins and frameworks that makes doing this impossible.
Right now I can have one plugin talk to another by using
NSClassFromString and performSelector, but I would like to set things
up so that one plugin can use the symbols defined by another plugin
and so that I get some type-checking at compile time. Is this
possible, any thoughts on how best to setup the build environment to
support this?
Of course an hour after posting to the list I came across this:
http://lists.gnu.org/archive/html/gnustep-dev/2003-08/msg00029.html
Which seems to say it's not possible to link into a plugin as you can
link into a framework. So unless someone knows otherwise I'll assume
this is still true. This isn't a killer limitation for me, I think I
can do what I want using protocols, it will just require an extra
layer of code as I'll need to wrap each class that I want to expose in
a protocol.
Note that the referenced message is talking about GNUStep, not Cocoa.
This doesn't necessarily mean that it's incorrect, though.
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________
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