Bundle vs. Framework for plugins
Bundle vs. Framework for plugins
- Subject: Bundle vs. Framework for plugins
- From: "Eric Baur" <email@hidden>
- Date: Sun, 18 Jun 2006 21:47:41 -0700
I started writing a plug in interface for my application, but I ran
into a small hiccup... and I'm not sure if the way I solved it is okay
(from a best practices standpoint), so I thought I'd run it by the
list and see what anyone else thought.
Basically, I'm writing an application that decodes network traffic. A
packet may have an ethernet frame that encapsulates IP, which may
encapsulate TCP, etc. I started out (internally) using sub-classes
for each type. So, I have a TCPPacket that inherits from IPPacket
that inherits from EthernetPacket. This works great, since each layer
only has to implement things that are unique to it.
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?
(Eventually, I'd like to have custom preference views / data views in
NIB files within the plug in as well... I'm worried that I'll run into
more problems down the line with this as well.)
Any thoughts / suggestions are greatly appreciated!
Thanks,
Eric
_______________________________________________
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