Plug Ins - To Subclass or to Protocol?
Plug Ins - To Subclass or to Protocol?
- Subject: Plug Ins - To Subclass or to Protocol?
- From: Lee Morgan <email@hidden>
- Date: Wed, 21 Jul 2004 17:27:39 -0400
I'm working on a app that uses plug-in extensively.
And I need to decided if I should...
Create a class that plug-in developers would sub-class to make a
plug-in?
Or define a protocol that the plug-in will have to follow?
The tricky part is...a single plug-in might work on different parts of
data.
For example there might be a "placement" plug-in that sets the location
of a given object.
But the plug-in might be passed a text object, a graphic object or some
other object.
So when the plug-in is loaded it should return what kind of objects it
can work on.
From what I've seen I could use either style of making plug-ins. But I
was wondering what advantages / disadvantages I'm overlooking.
thanks,
lee
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.