Ian S. Worthington wrote:
James --
I think its great someone's finally done this. You realise that everyone will
be after you for their favorite stages now though, don't you?! :)
For me, I'm a bit concerned that I seem to need to drive it from a C# program
that I need to compile, which does away with one of the great interactvity
benefits of pipelines.
ian
...
I agree that running only from a compiled program is not the best
environment.
Included with the demo application is a program named "pipe.exe".
This is a console application that excepts a pipeline definition as a
string.
An even better solution is to install MicroSoft's PowerShell.
It is available at:
http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx
With PowerShell you can write scripts like the following:
$pipe = "shell ls"+
"|frlabel ----"+
"|drop 1"+
"|Locate 1"+
"|nfind d"+
"|spec w6 1"+
"|console"
.\pipe $pipe
The Shell stage executes PowerShell commands. In the case the "ls"
command returns a directory list, that except for the headings, looks
like a linx "ls" command. The next three stages get rid of the
heading, the nfind stage excludes directory entries and the last stage
extracts the file name.
Currently you can not use "Var" or "Stem" stages with "pipe.exe". You
will have to write any output data to a file from the pipeline or
redirect the output from "pipe.exe" ie:
" .\pipe &pipe > output.data"
James Johnson
