Re: Finding "myself" in a plugin architecture
Re: Finding "myself" in a plugin architecture
- Subject: Re: Finding "myself" in a plugin architecture
- From: "Dirk Stegemann (Mailing-Lists)" <email@hidden>
- Date: Tue, 20 Feb 2007 19:02:16 +0200
Hello,
Am 20.02.2007 um 18:40 schrieb Shawn Erickson:
IMHO it seems a little weird to have the framework attempt to look
outside itself, if you are doing that why not just compile that
code directly into the plugin code.
You will get into problems when two different plug-ins are loaded
into the same host application, and both plug-ins have been built
using different versions of the same class. The runtime will not be
able to distinguish those classes (they have the same name) and load
only one class, posting a corresponding warning message to stdout (or
stderr? it shows up in console.app).
The only way to work around this issue seems to be to outsource that
class into a framework which getshas to be loaded by the different
plug-ins.
Best regards,
Dirk Stegemann
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden