Re: ColorsyncScripting
Re: ColorsyncScripting
- Subject: Re: ColorsyncScripting
- From: John Gnaegy <email@hidden>
- Date: Tue, 1 Sep 2009 16:18:47 -0700
I was using it to find out the monitor profiles in use for each one
connected and return the result to another application.
You can do:
tell app "Image Events" to get display profile of display 1
Scripts that use ColorSyncScripting should be able to be rewritten to
use sips and/or Image Events, they will need to be updated but it's
not the case that we dropped scripting of ColorSync. The scripts that
ship now in /Library/ColorSync/Scripting use sips, they're there not
only to be used as tools but also as sample code.
Remember that "command line utility" doesn't mean "not usable in
Applescript". Command line utilities are absolutely usable in
Applescript, and in Automator, perl, and the command line. The
coercions you need to be careful about are no more difficult than the
file, string, or alias coercions you routinely have to guess at in
Applescript. Well, that I routinely have to guess at.
This isn't a recent change, it's been in Snowleopard for quite some
time. Developers who've been getting the developer seeds would have
seen this long ago. I can't disclose on the list or to anyone
individually what's going to be in any unreleased piece of software
Apple makes, that's just how it is. Because of legal requirements the
only way to see if something you've created which depends on Apple API
will work correctly is to sign up as a developer and gets the seed
builds.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden