Re: ColorsyncScripting
Re: ColorsyncScripting
- Subject: Re: ColorsyncScripting
- From: Steve Upton <email@hidden>
- Date: Tue, 1 Sep 2009 16:38:29 -0700
At 4:18 PM -0700 9/1/09, John Gnaegy wrote:
>>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.
fair enough. And thanks for pointing us in the right direction, that can save tons of time.
>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.
also understood but there are a few problems with this:
1) "Normal" AppleScript "Developers" (and you know what I mean by the quotes) aren't likely to be the types who subscribe to ADC and get developer seeds. As you know, AppleScript is marketed as being usable by the average, or perhaps above average, user. Also, I suspect that the vast majority of subscribers to this list are not signed up for seeds. So....
2) Something like this should probably be handled on a staged basis. It's completely understandable that you can't divulge Snow Leopard's bit before their due. That seems to me to be the perfect justification of a staged deprecation. Round 1, perform the action but warn the user (once per user session or somesuch) that the scripting piece is going away. Then, round 2, take it away.
I'm afraid of all the scripts that are out there that are going to die, without notice, when people upgrade to Snow....
<covers head, sound of glass breaking>
It seems that an interim ColorSyncScripting app that wraps the new calls could stand in in the meantime?
Regards,
Steve
________________________________________________________________________
o Steve Upton CHROMiX www.chromix.com
o (hueman) 866.CHROMiX
o email@hidden 206.985.6837
________________________________________________________________________
--
_______________________________________________
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