• 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: Default AppleScript Formatting
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Default AppleScript Formatting


  • Subject: Re: Default AppleScript Formatting
  • From: email@hidden
  • Date: Fri, 26 Oct 2001 13:20:21 -0400

Here's what I use. (Everything is plain and black unless otherwise noted.
Colors are the "Crayon Picker" names.)

New text (uncompiled) Courier 10 pt
Operators - Geneva 10 pt
Language Keywords - Geneva 10 pt BOLD
Application keywords - Geneva 10 pt Blue-violet
Comments - Geneva 9 pt italic
Values (numbers, strings, lists) - Geneva 10 pt
Variables (and subroutine names) - Palatino 10 pt
References - Palatino 10 pt Seaweed

My basic rationale was to make make apparent from the font those things that
don't show from context.

I used the most significant attribute (font face), with the strongest contrast,
to indicate the difference between "my" terms (variable names) and the
language's terms (keywords). If I accidentially name a variable or handler with
a word that is a language or application term, I need to know that.

Bold differentiates between a language keyword and a value (which includes
constant names), and the color flags application keywords. Keeping track of who
I'm talking to is helpful.

I don't see any need to differentiate between an operator and a value. Context
is sufficient there, so I didn't make their styles different.

The colors I chose are muted, so I don't get an "angry fruit salad" appearance
to the screen. I chose Palatino and Geneva because they render well on the
screen, contrast well with each other, and are efficient. (Times would be more
efficient, but doesn't look good and renders a little too small for my taste.)
I wanted the English-like nature of the language to work for me, so I picked
font attributes that didn't get in the way of reading the script like text. Too
many different colors, styles and sizes slow down the reading process.

I didn't use underlines at all, because they interfere with reading.

I chose Courier for the uncompiled text because it symbolized not-ready,
typed-but-not-typeset text. Like the "flash forms" magazines use for
late-breaking news.

--
Scott Norton Phone: +1-703-299-1656
DTI Associates, Inc. Fax: +1-703-706-0476
2920 South Glebe Road Internet: email@hidden
Arlington, VA 22206-2768 or email@hidden


  • Prev by Date: Re: Recommendations for AppleScript Formatting
  • Next by Date: how do you tell what folder a file is in? - how to tell if a file exists part II
  • Previous by thread: Re: Default AppleScript Formatting
  • Next by thread: Eudora weirdness when failing to set a var to selected text
  • Index(es):
    • Date
    • Thread