On Sunday, July 13, 2003, at 03:29 AM, David Ledger wrote:
The sooner 'Project Builder' can create perl or shell projects
directly the better.
What sort of projects? A simple .pl file doesn't really need a
project - it's just a single file. You can use PB to edit it,
although BBEdit is
Le samedi, 12 juil 2003, à 17:25 Europe/Paris, Steven Bach a écrit :
But I fully agree with Chris that it is purely a matter of opinion
whether Perl is hard compared to AS, and I would add that programming
backgrounds, learning styles and other factors are likely to come into
play.
May I add
I agree that the semantic distinction is very tenuous. However, I
disclaim any ownership or responsibility for it - it's not *my*
distinction. It's a marketing distinction, and personally I find
it not only a patently false distinction but also an intentionally
misleading one - AppleScript
On Sunday, July 13, 2003, at 03:29 AM, David Ledger wrote:
The sooner 'Project Builder' can create perl or shell projects directly
the better.
What sort of projects? A simple .pl file doesn't really need a project -
it's just a single file. You can use PB to edit it, although BBEdit is
On Saturday, July 12, 2003, at 07:30 am, Jeff Lowrey wrote:
AppleScript, on the whole, has a shorter learning time FOR A
PROGRAMMER to be productive than Perl does.
Given that any language will try to provide the functionality that the
user culture currently requires of it, all languages have
Well, that's flat-out ridiculous.
Perl is HARD compared to Applescript.
That is a matter of opinion.
Actually, it's NOT a matter of opinion. Many people have differing
opinions, but that's not the same thing.
It's a matter of marketing, flat out.
...
However, AppleScript is a scripting
At 10:25 AM -0500 7/12/03, Steven Bach wrote:
Well, that's flat-out ridiculous.
Perl is HARD compared to Applescript.
That is a matter of opinion.
Actually, it's NOT a matter of opinion. Many people have
differing opinions, but that's not the same thing.
It's a matter of marketing, flat
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
go ahead and use Perl as the scripting
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
and here's a Perl tutorial:
[snip way too many lines of tutorial, apparently intended to make perl look
a lot harder than it is]
Here is what, perhaps, you meant:
Open BBEdit
Type
print Hello, world.
Run the script
Yes, that's one way to run a
On Friday, July 11, 2003 14:14 -0500 Chip Howland [EMAIL PROTECTED]
wrote:
I think you might be a special case. Not everyone has written Mac::Glue
or maintained MacPerl. If you are claiming that you can do everything
with Perl and Mac::Glue that you can with Applescript, then I won't
dispute
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
and here's a Perl tutorial:
[snip way too many lines of tutorial, apparently intended to make perl look
a lot harder than it is]
Here is what, perhaps, you meant:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (David Cantrell) wrote:
It matters not that he wrote Mac::Glue. He's published it, so I can use it
too. And I have just as much difficulty with using Mac::Glue as I do with
using Applescript. That difficulty is solely because Applescript
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
On Sunday, May 11, 2003, at 7:04 AM, John Delacour wrote:
Whatever you can do with DropScript you can do more conveniently with
Perl in an AppleScript droplet that _does_ know where it is.
On Thursday, July 10, 2003, at 03:37 am, Wilfredo Sánchez wrote:
The assumption that your working
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
go ahead and use Perl as the scripting language and put AppleScript
to bed along with OS9
Well, that's flat-out
On Sunday, May 11, 2003, at 7:04 AM, John Delacour wrote:
Whatever you can do with DropScript you can do more conveniently with
Perl in an AppleScript droplet that _does_ know where it is.
The assumption that your working directory is where your script lives
is broken.
You script's path is
Thanks for the help so far guys, I've got a much better picture of what's
going on now!
Does the @ARGV array contain the full paths to the file, or just their names
(ie, do the files HAVE to be in the same directory as the dropscript?)
Cheers,
-Shannon
On 6/9/02 12:51 AM, in article
At 12:05 pm +1000 6/9/02, Shannon Murdoch wrote:
Thanks for the help so far guys, I've got a much better picture of what's
going on now!
Does the ARGV array contain the full paths to the file, or just their names
(ie, do the files HAVE to be in the same directory as the dropscript?)
The full
Hi Pete,
Unfortunately I'm not a command-line wiz :(. Could you explain how the
target file/directory parameters are usually passed to the script when it IS
called from the command line?
Cheers,
-Shannon
On 5/9/02 2:59 AM, in article [EMAIL PROTECTED],
[EMAIL PROTECTED] [EMAIL PROTECTED]
Well, you might call a script like this:
perl foo.pl file1 file2 file3
where each argument to the script (in this case 3 files) is passed in
to the script, separated by a space.
If I created a DropScript out of my foo.pl, and dropped file1, file2,
and file3 onto it, it would be just like
More to the point,
%ARGV
-Charles
[EMAIL PROTECTED]
At 1:42 PM + 9/5/2002, [EMAIL PROTECTED] wrote:
Well, you might call a script like this:
perl foo.pl file1 file2 file3
where each argument to the script (in this case 3 files) is passed in
to the script, separated by a space.
If
On Sunday, December 2, 2001, at 08:11 PM, Wilfredo Sanchez wrote:
The potentially surprising event here is that the script is running
twice. I was actually aware of this, but had forgotten. If the Finder
has been written in Cocoa, I think you'd see the script invoked only
once, with
Fred -
Thanks for the help. Now I can see the errors that the script is
generating, but I'm still not sure how to access argv from my perl
script. For example, if I want to assign the contents of argv to
@some_array how do I do that?
Tantalizingly, if i just write:
code
#!/usr/bin/perl -w
At 4:25 PM -0600 12/1/01, Joshua Kaufman wrote:
Thanks for the help. Now I can see the errors that the script is
generating, but I'm still not sure how to access argv from my perl
script. For example, if I want to assign the contents of argv to
@some_array how do I do that?
Tantalizingly, if
bruce-
thanks for the response. i am dropping multiple files, but only one
is being written to the log file. the problem is that i don't know
how to access the list of arguments that is passed to the shell by
the droplet (or how to pass that directly to perl). $* would work in
a shell
At 1:43 PM -0600 11/30/01, Joshua Kaufman wrote:
I'm interested in using Wilfredo Sanchez's DropScript to make some
of my perl scripts available to users who prefer not to use the
command line.
How are the names of the dropped files passed to the script? For
example, when I make the
What happens if you try to make a droplet out of the simple script:
/bin/sh -c /usr/bin/perl -e '$cmd = `touch foo`'
will foo get created then?
-s-
At 2:51 PM -0600 11/30/01, Joshua Kaufman wrote:
Thanks for the reply Sandor, but further investigation reveals that
the following also fails to
On Friday, November 30, 2001, at 12:51 PM, Joshua Kaufman wrote:
Thanks for the reply Sandor, but further investigation reveals that the
following also fails to create the file 'foo' as expected when made
into a droplet:
script
#!/usr/bin/perl -w
use strict;
my $cmd = `touch foo`;
File names are passed via argv[]. I would suggest that you monitor
the console log (run Console.app) while creating the droplet and see if
there are any errors, and if none do the same while dropping files on
the new droplet. Error reporting via the UI is nonexistant. Perhaps
it's
Oh, I wrote an article on DropScript for MacTech, which you might find
useful, if not more than you need to know. August 2001. My copy of it
is at:
http://www.mit.edu/people/wsanchez/papers/DropScript/
-Fred
30 matches
Mail list logo
