Re: Should I try to avoid loading principal class of plug-in?
Re: Should I try to avoid loading principal class of plug-in?
- Subject: Re: Should I try to avoid loading principal class of plug-in?
- From: Gregory Weston <email@hidden>
- Date: Sun, 11 Oct 2009 07:36:42 -0400
Rick Mann wrote:
I'm working on a plug-in-based app. While I have to scan all of the
plug-ins and load some information from their info.plists, I don't
necessarily need to load any of the code until a plug-in is actually
used. My main question is, is it worth it to do this? It seems like
that's one advantage of plug-ins, but now I'm at a point where it's
more elegant if I can determine if the plug-in class derives from a
particular base class, rather than storing a key in info.plist (it
would be redundant).
...
Thoughts?
It occurs to me that if you care to distinguish between different
kinds of plugins a user may add to the environment, it's possible your
users may also want to care. Instead of inventing a new key, why not
make them a different document type, with a different extension and
icon?
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden