• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: scripting Photoshop
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: scripting Photoshop


  • Subject: Re: scripting Photoshop
  • From: Leonard Rosenthol <email@hidden>
  • Date: Tue, 12 Dec 2000 08:42:29 -0500

Let's stop making stuff off because it sounds good. If you don't know the REAL truth - don't start spouting off with crap...If you want to do that, find another list to vent on!


At 4:31 PM -0800 12/11/00, email@hidden wrote:
> Once a command or function is created to operate by menu
> or button within a program, why isn't the Apple Script access to that command
or function simply made available by the developers?

Because Adobe apparently (a) didn't think of Applescript during development
of Photoshop,

Bzzt - sorry, thanks for playing!

Not only did Adobe think about AppleScript during the development of the Photoshop Actions architecture, but if you actually LOOKED inside of a PS Action, you'd find that it uses the EXACTLY SAME technology as AppleScript (event classes, ID's, lists, etc.)


(b) implemented their own internal-only and therefore very
limited scripting system instead, and

Again, WRONG!

You will find that the Photoshop Actions architecture is actually MORE powerful than AppleScript, because they looked at AS's limitations and flaws (like a single flat namespace) and addressed them in it's implementation.


(c) would rather be lazy and let third
parties do all the Applescript work.

This is actually Cal's fault more than Adobe's.

Originally (PS4) there WERE plans for REAL AppleScript support (since hooking up the two architectures is pretty trivial given their similarity) - BUT Cal came to Adobe (and has many times since) to convince them NOT to do their own scripting support because that would take away his livelihood (aka Photoscripter). Since users were happy, and Adobe could put engineers on other features that more people could use, that was fine with them - common business sense.


What you end up with is scripting
support that costs dearly, and isn't as good as it could be if it were built
into the app.

Actually, I would argue that Cal & Eric did a BETTER job than Adobe's engineers would have done at the time since they had MUCH more experience with AS/scripting than almost anyone working on Photoshop or related technologies did.

Today, of course, Adobe has some GREAT engineers (Sue and Andy) to address the scripting aspects of Adobe products - the functionality in Illustrator 9 being the result!


Leonard
--
----------------------------------------------------------------------------
You've got a SmartFriend in Pennsylvania
----------------------------------------------------------------------------
Leonard Rosenthol Internet: email@hidden
America Online: MACgician
Web Site: <http://www.lazerware.com/>
FTP Site: <ftp://ftp.lazerware.com/>
PGP Fingerprint: C76E 0497 C459 182D 0C6B AB6B CA10 B4DF 8067 5E65


  • Follow-Ups:
    • Re: scripting Photoshop
      • From: Shane Stanley <email@hidden>
    • Re: scripting Photoshop
      • From: JollyRoger <email@hidden>
  • Prev by Date: RE: scripting Photoshop
  • Next by Date: Re: scripting Photoshop
  • Previous by thread: Re: scripting Photoshop
  • Next by thread: Re: scripting Photoshop
  • Index(es):
    • Date
    • Thread