Re: [MacPerl] clear?

[John Delacour <JD@EREMITA.demon.co.uk>]

At 9:04 am -0500 11/1/00, Chris Nandor wrote:

>Not if you are already using MacPerl.  You may like controlling MacPerl
>from AppleScript, but I think most people will find it is a kludgier way to
>work.  And the speed difference is not an issue for most Macs these days.

I don't see what's kludgy about typing command-B and getting 
immediately the result required, or clicking a button, optionally 
linked to any key-shortcut and getting the result immediately.

Before I did this I was having to switch to the MAcPerl windsow, 
select all and delete and then switch back to the composition window 
-- that's four things, two of them kludgy.

How do you assign a shortcut to your Perl script and how can it be 
said to be anything other than kludgy and inconvenient?

OneClick and Applescript are designed precisely to facilitate 
operations of this kind in applications, especially those like 
MacPerl with a rather primitive interface.  Just because I'm working 
in MacPerl doesn't mean I have to be a perl-purist and not take 
advantage of tools that make the work lighter.

>
>Although, you can also do this, to speed things up:
>
>   #!perl -w
>   # script one
>   use Mac::OSA::Simple;
>   my $script = compile_applescript('close window "MacPerl" of app "MacPerl"');
>   $script->save('some:file');

I can get that far by just typing command-W -- why would I need a script?

This gives me # Can't locate Mac/OSA/Simple.pm in @INC.

So far as I know I did a smooth install of all your stuff and the 
CPAN, so what am I missing and where can I get it?

JD



# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org