Re: Bundle vs. Framework for plugins
Re: Bundle vs. Framework for plugins
- Subject: Re: Bundle vs. Framework for plugins
- From: "Michael Ash" <email@hidden>
- Date: Mon, 19 Jun 2006 16:19:42 -0400
On 6/19/06, Eric Baur <email@hidden> wrote:
The problem I ran into was when I started using bundles for plugins.
If TCPPacket and IPPacket are in different plugins, then I get a link
error, since the super class isn't present. I can solve this by
changing the plugins to frameworks instead of bundles, but do I loose
anything by doing that? I'm I misusing the concept of frameworks?
I can't speak to whether it would qualify as "abuse", but your idea
should work. I worked on a project which had plugins that got loaded
at runtime, and for no real reason it uses .frameworks for these
plugins rather than loadable bundles. I'm not sure what the difference
in semantics are in this case but this app works just fine with its
frameworks, despite the mismatch. My project has no inter-framework
dependencies but I see no reason why it wouldn't work.
Mike
_______________________________________________
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