Hi, I'm developing an application to support third-party extensions that filter text. Each filter consists mainly of a property list and an executable. The idea is that the text of the current document goes into the executable along with settings specified in the property list (as arguments); text to replace the document text comes out as the standard output.
Right now I am stuck trying to decide how I should pass both the document text and the settings to the executable. I see three options: 1. Have the first argument be the document text, and the second an XML string containing the settings as key-value pairs. 2. Have the first argument be the docucument text, the second a setting key, the third a setting value, the fourth a setting key, etc... 3. Have the first argument be the docucument text, have each successive argument be a setting value, in an order specified in the property list so as to determine the key for each. I can easily set up the application to support any of these methods. My problem is that each one seems to have some inconveniences for the developer of the filter, and I would like to make this as convenient as possible for anyone who makes a filter. Could someone tell me which method would be the most appropriate? Thanks. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
