Re: Command Line Argument - Choosing a Style
Re: Command Line Argument - Choosing a Style
- Subject: Re: Command Line Argument - Choosing a Style
- From: Jonathan deWerd <email@hidden>
- Date: Wed, 6 Aug 2008 19:00:57 -0600
I would make plugins of a different type: standard cocoa bundles
(there are a handful of tutorials on google). This way, people could
install and uninstall using the finder (a little known but helpful
feature of the info box), you could use standard cocoa APIs, you
wouldn't have to deal with the overhead of spawning a new process, and
you could provide a template to get devs started. Then I'd just pass
configuration info in a dictionary.
If that isn't an option, I would pass a bunch of --key value pairs to
retain some semblance of standard-ness :)
On Aug 6, 2008, at 4:33 PM, hac wrote:
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 (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:
@gmail.com
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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