----- Original Message -----
From: "Jan Erik Moström" <[EMAIL PROTECTED]>
| Personally, I don't have any need for a better text editor, I already have an
| excellent text editor. But what I would really like is a command shell ability.
| I would like to be able to enter the name of scripts and give command line
| arguments etc
|
| (Yes, I know OS X or ToolServer/MPW but this would really be an improvement)
I can't think of anything that can't be done with a very simple AppleScript script,
without even mentioning Frontier. The first item in the do script parameters can be
either the pathstring of a script or the text of the script, so you have great
flexibility. MacPerl's Apple Event support is very useful -- even the text suite is
at least partially implemented. Here's a simple example of a command line built in an
AS dialog. Save the perl script, change the path accordingly and run it. What does
it not do that you need it to do? I am sure that with simple modifications you can
get it to do everything you need. 'sampleScript', rather than being a fixed path, can
be the path to an item selected in the Finder, etc......
(* # D:perl:temp.pl has following script:-
foreach (@ARGV) {$x = $x + $_;}
MacPerl::Answer $x;
*)
set sampleScript to "D:perl:temp.pl"
display dialog "
Type command line using '§' as delimiter" default answer ¬
sampleScript & "§1§2§3§4§5"
set s to text returned of result
set AppleScript's text item delimiters to {"§"}
set cmd to text items of s -- ie. make a 'list'
set AppleScript's text item delimiters to {""}
tell application "MacPerl"
activate
Do Script cmd -- the 'list'
end tell
