Re: solutions to scripting addition terminology confilicts [goi
Re: solutions to scripting addition terminology confilicts [goi
- Subject: Re: solutions to scripting addition terminology confilicts [goi
- From: Mr Tea <email@hidden>
- Date: Mon, 28 Jan 2002 22:01:45 +0000
This from Arthur J Knapp at @722 on Mon, Jan 28, 2002
>
It often seems like
>
a beginning AppleScripter has to work harder than a beginning C
>
programmer, precisely because there are so few libraries or complete
>
scripts to make immediate use of.
Yes indeed. And like has, who kicked off this sub-thread, I don't want to
be continually re-inventing the wheel, so long as I have some idea how
the spokes work.
One problem is that the Script Editor offers no built-in way to easily
mangage and deploy libraries. As a 'rest of us' AS user, I've actually
found the concept of handlers quite troublesome. It's 6 years since I
produced my first tentative script to clean up the desktop on my old
performa 5200, but it's only in the last year that I've started using
handlers with any confidence.
Then again, farming all the gnarly bits of my scripts out to modular
widgets would probably be overkill, as the vast majority of them fit
inside the script editor's window without troubling the vertical scroll
bar a jot. Still, it would be nice to have quick and easy access to
useful bits of code from within the script editor. (I tried to make an
ClarisWorks database of handy snippets once upon a time, but it didn't
really cut the mustard, what with the paltry 256 character limit on AW
database fields - if memory serves). So, a folder stuffed with jumbled
heaps of confusingly named text files is it until something better comes
along...
At the risk of starting a major kerfuffle, might I ask what methods and
equipment the big boys and girls on this list have found useful in taming
their own script libraries?
Mr Tea
--
Dunk of the day: Foxes Butter Crinkle