FROM : Michael Ash
DATE : Mon Jun 19 22:19:42 2006
On 6/19/06, Eric Baur <<email_removed>> 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
DATE : Mon Jun 19 22:19:42 2006
On 6/19/06, Eric Baur <<email_removed>> 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
| Related mails | Author | Date |
|---|---|---|
| Eric Baur | Jun 19, 06:47 | |
| Greg Herlihy | Jun 19, 15:28 | |
| Eric Baur | Jun 19, 22:12 | |
| Michael Ash | Jun 19, 22:19 |






Cocoa mail archive

