Re: New Office for Mac Beta and Applescript
Re: New Office for Mac Beta and Applescript
- Subject: Re: New Office for Mac Beta and Applescript
- From: has <email@hidden>
- Date: Fri, 13 Mar 2015 10:14:40 +0000
|
On 13/03/2015 08:29, Christian Prinoth
wrote:
I just sent feedback to MS about this, let's see
what I can get out of it. In the meantime, would you care
explaining how I would go about exporting the old terminology
and then applying it to new excel?
See dump() in appscript.terminology:
http://sourceforge.net/p/appscript/code/HEAD/tree/py-appscript/trunk/appscript_3x/lib/appscript/terminology.py
FWIW, I believe the Mac Office team use(d) appscript themselves to
drive automated builds for their test farm, so might be a little
more sympathetic to your feedback. However, AppleScript is the de
facto specification against which ALL scriptable apps are developed
and tested since 1993. So app developers will respond [quite
rightly] that their scripting support is tested and working
correctly with AppleScript, therefore it's your AE bridge that's at
fault for not implementing that spec correctly.
Alas, since Apple 1. have proven they're incapable of implementing
AE bridges correctly themselves (Hi, Chris!), and 2. have made it
impractical for third-parties to do at all, you're probably SOOL in
the long run as far as AppleScript alternatives go. If your IPC
workload is modest then my recommendation would be to call into
AppleScript via the AppleScript-ObjC bridge, which is quite easy to
do in 10.10+. I've posted a quick How To that shows how to do this
from ObjC and Python+PyObjC:
http://appscript.sourceforge.net/asoc.html
If you've any general ASOC questions, Shane Stanley's your go-to guy
for those.
HTH
has
|
_______________________________________________
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