Re: protocol/plug-in question
Re: protocol/plug-in question
- Subject: Re: protocol/plug-in question
- From: Ondra Cada <email@hidden>
- Date: Thu, 6 Apr 2006 02:53:52 +0200
Ryan,
On 6.4.2006, at 2:43, Ryan Glover wrote:
I am attempting to create an app that I want to be expandable via
plug-ins. I have read up on protocols and they seem the right
solution.
Perhaps they do, but pretty often they don't. Consider also informal
protocols etc.
Formal protocols are hell upgrading: you cannot extend the current
one lest the old conformats get out of sync.
... But each plug-in might have different inputs.
For example, a cube only needs to know the length of one side while a
cylinder needs to know height and a radius. If the array is presented
in a table and I click on a particular row in the table (which
represents an instance of a shape) how does the code know what
parameters are applicable? Do individual instances present a list of
their methods that can be interrogated at run time?
Depends, and completely up to you. Each plugin object may present its
own UI view. Or all may be set up with a string, whose contents each
will parse its own way. Or you can invent your own protocol in which
the plug-in would return a formal list of arguments it wants (their
types, descriptions, etc.)
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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