Re: plug-ins and app-updates
Re: plug-ins and app-updates
- Subject: Re: plug-ins and app-updates
- From: j o a r <email@hidden>
- Date: Mon, 13 Jan 2003 10:18:19 +0100
I think that you should support all library domains - including the app
wrapper - and decide on a hierarchy of precedence for plugins found at
these locations. Something like this:
App wrapper // Default, lowest priority
/Network/Library/Application Support/MyApp/Plugins
/Library/Application Support/MyApp/Plugins
~/Library/Application Support/MyApp/Plugins // Highest priority
You should probably also version your plugins, and take into account
the versions before deciding which to load.
j o a r
On Monday, Jan 13, 2003, at 10:07 Europe/Stockholm, m wrote:
we had a discussion going on about the proper way to implement
plug-ins in our app. while my developer opted for inclusion inside of
the package, i (as the ui-guy) opted for the creation of a folder in
app-support.
he then hit me whith the HIG.
bummer. ;)
now, the reason i wanted a folder outside of our app was to keep
3rd-party plug-ins installed when we provide an update to our
application. i also gotta admit that i didn't know about the finder's
feature of adding/removing plug-ins via "get info".
how do y'all handle this?
i feel that it'd be a bad idea to use the finder feature, as our users
will have to re-add their plug-ins once we update our app. i also feel
that it'd be easier to update plug-ins that way, as it's a simple
drag'n'drop, instead of a bunch of clicks.
then again, enabling/disabling of plug-ins is so much easier using
"get info" then moving a plug-in into or out of a folder nested inside
an obscure folder.
any thoughts, comments, insights?
_______________________________________________
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.