Re: Visual Basic versus AppleScript

Subject: Re: Visual Basic versus AppleScript
From: Yvan KOENIG <email@hidden>
Date: Thu, 1 Oct 2009 10:25:32 +0200

Le 1 oct. 2009 à 09:44, Wayne Melrose a écrit :

On 1. okt. 2009, at 09.23, Yvan KOENIG wrote:

Le 1 oct. 2009 à 04:46, Doug Tallman a écrit :

From time to time I find myself in the middle of OS X vs. Windows wars. And occasionally, someone will pipe up that one of the reasons Office is a "better" product is Visual Basic. It strikes me that iWork and AppleScript should be able to many of the same kinds of things. Can someone outline what some of the differences between VB and AS? Is one strikingly "better" than the other?

doug

iWork components are Applescript aware.

What is really missing is a function like the MACRO() which, in AppleWorks allow us to trigger a script without human action.

If iWork's team is fair enough to give us such a function (an solve the awful slowness of the beasts) we would quite be in heaven.

Yvan KOENIG (VALLAURIS, France) jeudi 1 octobre 2009 09:23:09

I'm not really VB savvy, although wouldn't it be safe to say that applescript actually gives better interaction with other apps. and the OS? I guess if we're specifically talking macros then i guess vb/office is more unified?

CAUTION the Appleworks MACRO() function has nothing in common with Excel macros.

It's just a function calling an ApppleScript and passing some parameters.

Here are some formulas using the feature:

=MACRO(":ƒµƒ:µ bessel.app",2,"lecalcul",A1,B1)

=MACRO(":ƒµƒ:µ neg_en_rouge.app",2,"boulot",row(),column(),formula)

=MACRO(":ƒµƒ:µ lettre_en_rouge.app",2,"boulot",row(),column(),formula,letter)

=MACRO(":ƒµƒ:µ colorise.app",2,"boulot",row(),column(),formula,mode,"lim1;lim2;lim3")

The parameter ":ƒµƒ:µ colorise.app" is used to tell to AppleWorks:

call the script which is stored in your SCRIPTS folder in the subfolder "ƒµƒ" and is named "µ colorise.app"

I used these rules so that

(1) I was able to easily recognize scripts written to be triggered by MACRO()

(2) These scripts when't directly reachable by the user in the AppleWorks 's SCRIPT menu.

The function's name may be confusing.

It was defined whan AppleWorks was also able to use macros.

The MACRO() function was able to call macros as well as scripts.

If, as I wish, the Numbers team introduce such a feature, it would be better to use an other name like CALLSCRIPT

Yvan KOENIG (VALLAURIS, France) jeudi 1 octobre 2009 10:25:14

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden

References:
	>Re: Visual Basic versus AppleScript (From: Yvan KOENIG <email@hidden>)
	>Re: Visual Basic versus AppleScript (From: Wayne Melrose <email@hidden>)

Prev by Date: Re: Visual Basic versus AppleScript
Next by Date: Help with ObjC appscript
Previous by thread: Re: Visual Basic versus AppleScript
Next by thread: Visual Basic versus AppleScript
Index(es):
- Date
- Thread