Re: Providing application resources to a Plugin
Re: Providing application resources to a Plugin
- Subject: Re: Providing application resources to a Plugin
- From: d2kagw <email@hidden>
- Date: Tue, 22 Aug 2006 19:43:05 +1000
Aaaah, fair enough =)
Well I guess this opens the discussion up to, from a development &
distribution point of view, which is the best way to develop a plugin
architecture? Im not really fussed about how complex it is for me to
develop, but I definitely want it to be easy as pie for people to
develop for...
On 22/08/2006, at 10:49 AM, Rainer Brockerhoff wrote:
At 15:47 -0700 21/8/06, email@hidden wrote:
From: d2kagw <email@hidden>
To: Cocoa Development Development <email@hidden>
On this note, are there any good examples/tutorials floating
around on how to build solid plugin platforms/API's?
The only tutorial I have found is http://cocoadevcentral.com/
articles/000068.php which doesn't seem like the best way to do it,
well, for starters it doesn't use a framework...
Seems I wrote that :-)
I haven't quite understood what you mean with "for starters it
doesn't use a framework".
If you want to provide some sort of framework for the plugins to
use, and include that framework within the application, I suppose
you could do that easily, but from the viewpoint of the plugins it
makes no difference at all whether the classes it's using are
physically located inside the application executable or in a
framework. The ObjC runtime sorts that out for you.
--
Rainer Brockerhoff <email@hidden>
Belo Horizonte, Brazil
"In the affairs of others even fools are wise
In their own business even sages err."
Weblog: http://www.brockerhoff.net/bb/viewtopic.php
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden