Re: cocoa scripting
Re: cocoa scripting
- Subject: Re: cocoa scripting
- From: PJ Pritchard <email@hidden>
- Date: Sun, 9 Apr 2006 11:20:03 -0400
In short, look at Automator ...
In my first concept app, Aquifer, the purpose was to provide a GUI-
wrapper to UNIX commands and perl scripts. This was done using
premade XML specifications of commands, which described the options
available for that specific command. So in essence, it was
extensible in the sense that if you wanted to include a new command
in your 'toolkit', like grep, you would just write the XML spec and
viola, it can be used in the workflow. The XML spec defines whether
the command takes input from stdin, or pipes data to stdout, whether
there are input files, output files, access to environmental
variables ....
When I started coding, I realized that there were at least four types
of building blocks, Commands, Connectors, Transforms and Views.
Commands are bits of code or scriptlets, connectors handle process
piping (redirection), transforms change data from say comma-separated
to excel, or XSLT transforms, and views were outlets to applications
or PDF ....
I thought, it would be neat to allow GUI-view of ant scripts and
Makefiles, .... but also to GUI bioinformatics workflows .... and if
that were generalized a bit, Xgridable commands (commands that lend
themselves to parallel processing, or branches of workflow that can
be done on other processors or cpus or subnets).
I really should stop taking up space in Cocoa dev list though ... or
I will get in trouble for getting off topic ...
Email me at email@hidden if you have interest in hearing more ....
_______________________________________________
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