Linked by Eugenia Loli on Sun 24th Jul 2005 21:08 UTC
Mac OS X Do you want to make the most of your Mac applications? Like all operating systems, the Mac has many different levels of programming, and more than 80 percent of all applications built for OS X leverage AppleScript as an automation tool. In this introductory article, Matthew David tells you how you can best leverage AppleScript for your Mac applications.
Thread beginning with comment 8569
To read all comments associated with this story, please click here.
some options...
by soapdog on Mon 25th Jul 2005 01:18 UTC
soapdog
Member since:
2005-07-25

The linux/oss advocates here are missing the point. The cool thing about AppleScript is automation. To be able to code app interaction. for example, fetch a file list from the finder, pipe them to Quark express, build thumbnail gallery and page, save as HTML, upload to FTP... all driven by applescript. although we have hooks for Python to support AppleEvents and thus work this app interation, it still far from the easy to use experience of AppleScript, a language that anyone can understand, heck, I've seen designers make scripts to automate lots of things that would require a skilled python or perl code to do in other environments.

As for other options, I can remember from memory:
There is UserTalk from Userland Frontier (wasn't it a osascript language?!)
There is AREXX on the Amiga
There is BeScript for BeOS/Zeta which expose BeOS messaging system as applescript like language... I find it strange, but it is a nice try.

Reply Score: 1

RE: some options...
by duncanbojangles on Mon 25th Jul 2005 04:09 in reply to "some options..."
duncanbojangles Member since:
2005-07-06

The linux/oss advocates here are missing the point. The cool thing about AppleScript is automation. To be able to code app interaction. for example, fetch a file list from the finder, pipe them to Quark express, build thumbnail gallery and page, save as HTML, upload to FTP... all driven by applescript.

As I've already said in a previous post, you are able to do this with KDE's DCOP interface. It's not just some protocol that you can only use in C++, you can call it from the command line with the ever so simple command dcop or the graphical equivalent kdcop. If you need to push a button, get the text from a textbox, fill in a form, etc. from a shell script, perl script, C program, etc. you can do it with DCOP. You have the interaction, you just have to add your own language of choice.

Someone mentioned zenity for GNOME. There's a similar program for KDE called kdialog. It's pretty nifty, allowing you to create message bosex, buttons, sliders, pretty much any simple application you can think of is possible with kdialog.

Also, please don't generalize the Linux/OSS equivalents, since the first poster asked what options were out there. It's no surprise then that some people are going to give Linux/OSS options, since that's what many OSNews readers use daily. The wonderful thing about Linux and Open Source is choice, ie you're not bound to just Applescript, you can use whatever suits you best. If your programming language can perform a system call, it can use DCOP. Don't forget, if it weren't for Open Source, Darwin, FreeBSD, and all the other OSS projects Apple's borrowed from, OSX might have sucked.

Reply Parent Score: 1

RE[2]: some options...
by soapdog on Mon 25th Jul 2005 04:49 in reply to "RE: some options..."
soapdog Member since:
2005-07-25

ops sorry if I was misunderstood. I was just pointing differences between both architectures, not trying to start a flamewar. anyway, thanks for the DCOP entrypoint, I am reading about it at this very moment.

I am not in any way one of those that disagree with F/OSS and I also don't put them in a melting pot.

learning from your comments. Also any language can implement OSA, I know only two however, applescript and frontier...

Reply Parent Score: 1