On Feb 16, 2008, at 12:18 AM, Arne Scheffler wrote:
After all the only workable solution to this problem is to create
the Objective-C classes at runtime.
Just have your application just contain an embedded framework against
which plug-ins must link.
Then the Objective-C classes that would normally be replicated in
every plug-in can be put in the framework instead. You won't have
Objective-C class name conflicts in the plug-ins then, and you will
also be able to roll out changes to the Objective-C classes very easily.
Providing a "toolkit" which consists of source code to link into each
plug-in sounds like a maintenance nightmare. How would you deal with
code linked against version 1.1 of the toolkit trying to load into
version 3.0 of the application? These are the kinds of problems
frameworks were designed to solve.
-- Chris
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
