Barebones SW conflict with Standard Additions' offset
Barebones SW conflict with Standard Additions' offset
- Subject: Barebones SW conflict with Standard Additions' offset
- From: Brennan <email@hidden>
- Date: Wed, 19 Nov 2003 12:41:42 +0100
Apologies if this has been discussed before.
Recent versions of BareBones' software applications (BBEdit and Mailsmith)
- both admirable for their thorough-going Applescript implementations and
general robustness - now employ the terminology 'offset' - a property of
the 'text object' superclass which conflicts with the 'offset' provided by
'Standard Additions'.
A great number of my scripts broke when I upgraded, and now I have to farm
out all my offsets to a handler outside tell blocks to those applications.
on offfset(lookforStr, str)
return offset of lookforStr in str
end offfset
I brought this up on their (excellent) support mailing lists, but been
somewhat shouted down because terminology conflicts are precisely the flaw
of scripting additions. (Implicit: Don't use them).
While I agree that most of the work traditionally handled by scripting
additions pre-OSX should now be handled by applications (faceless,
background ones, if necessary), we still have 'Standard Additions'
providing essential commands and classes which do not really belong in the
core, they are installed as part of every OSX and - I would argue - the
terminology used in 'Standard Additions' should *not* be trampled on by
other apps, no matter what the pedigree.
Barebones engineering appear to disagree, but have agreed to review the
issue.
So who is right?
Are there official guidelines for Applescript implementors about
terminology from the standard set of OSAXen?
Brennan
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.