Re: applescript-users digest, Vol 2 #1387 - 17 msgs
Re: applescript-users digest, Vol 2 #1387 - 17 msgs
- Subject: Re: applescript-users digest, Vol 2 #1387 - 17 msgs
- From: Paul Abney <email@hidden>
- Date: Tue, 11 Dec 2001 09:26:56 -0600
Thanks
Paul Abney
East Memphis Printing
--
Good health is merely the slowest possible rate at which one can die.
>
From: email@hidden
>
Reply-To: email@hidden
>
Date: Tue, 11 Dec 2001 07:11:46 -0800 (PST)
>
To: email@hidden
>
Subject: applescript-users digest, Vol 2 #1387 - 17 msgs
>
>
Send applescript-users mailing list submissions to
>
email@hidden
>
>
To subscribe or unsubscribe via the World Wide Web, visit
>
http://www.lists.apple.com/mailman/listinfo/applescript-users
>
or, via email, send a message with subject or body 'help' to
>
email@hidden
>
>
You can reach the person managing the list at
>
email@hidden
>
>
When replying, please edit your Subject line so it is more specific
>
than "Re: Contents of applescript-users digest..."
>
>
>
Today's Topics:
>
>
1. Re: Summarize anything? (Michelle Steiner)
>
2. Re: Disappearing Script menu (garbanzito)
>
3. Re: 9.2.2 Update effects on applescript (Simon Topliss)
>
4. AS Quality Assurance (was: Re: 9.2.2 Update effects on
>
applescript) (christian vick)
>
5. Re: AS Quality Assurance (was: Re: 9.2.2 Update effects on
>
applescript) (JollyRoger)
>
6. Re: Disappearing MenuScript (email@hidden)
>
7. List Folder errors (Brandon Carpenter)
>
8. [Announce] RSS/RDF support for osaxen.com (email@hidden)
>
9. Re: URL Access Scripting (Eric Schult)
>
10. Bug or Feature? (Gnarlodious)
>
11. Open for Access Nightmare (Lyle Petro)
>
12. Printer settings (James Hirst)
>
13. Open for Access Nightmare addendum (Lyle Petro)
>
14. Re: 9.2.2 Update effects on applescript (email@hidden)
>
15. Folder actions in OS X (Michael Turner)
>
>
--__--__--
>
>
Message: 1
>
Subject: Re: Summarize anything?
>
Date: Mon, 10 Dec 2001 23:20:34 -0700
>
From: Michelle Steiner <email@hidden>
>
To: "Bob.Kalbaugh" <email@hidden>, "AppleScript-Users"
>
<email@hidden>
>
>
On 12/10/01 10:01 PM, Bob.Kalbaugh <email@hidden> wrote:
>
>
> set the file_to_read to read (choose file of type "TEXT")
>
> set my_synopsis to summarize the file_to_read in 3
>
>
>
> results in
>
> --> An error of type -2804 has occurred.
>
>
It worked for me, using your code.
>
>
> I'm curious if Find by Content and/or File Indexing need to be active in
>
> order for it to work, and I don't want to turn them on if not needed.
>
>
Those are related only to Sherlock; they have nothing to do with this.
>
>
--Michelle
>
>
----------------------------------------------------------------------
>
| Michelle Steiner | We're not human beings having a spiritual |
>
| | experience. We're spiritual beings |
>
| email@hidden | having a human experience. |
>
----------------------------------------------------------------------
>
>
--__--__--
>
>
Message: 2
>
Date: Mon, 10 Dec 2001 23:45:35 -0700
>
To: What does not kill you only makes you stronger <email@hidden>,
>
<email@hidden>, <email@hidden>
>
From: garbanzito <email@hidden>
>
Subject: Re: Disappearing Script menu
>
>
at 2001 12 10, 19:46 -0600, they whom i call What does not kill you
>
only makes you stronger wrote:
>
> I always put them at "/System/Library/CoreServices/Menu Extras/" so they are
>
> available to other users. I don't think I have read anything by Apple
>
> detailing the specific location of a Menu Extra item for an individual user
>
> though.. I guess you could create a Menu Extras directory at
>
> "UserName/Library/" ??
>
>
first, it doesn't appear that the ScriptMenu.menu file needs
>
to be placed anywhere special. mine's in
>
/Applications/Utilities, but dragging it into the menu is
>
what "installs" it. presumably this writes a preference into
>
a plist somewhere, but i don't know where. if this
>
preference is (as many are, unfortunately) in the form of a
>
hard path, then moving the file could disable the menu.
>
>
but if you're putting anything in /System/Library, consider
>
putting it in /Library (for all users) or ~/Library (for
>
specific user) instead. this keeps /System sacred (though
>
some installers will touch it), and makes it much more clear
>
what to preserve if you are going to reinstall your system.
>
>
--
>
steve harley email@hidden
>
>
--__--__--
>
>
Message: 3
>
Date: Tue, 11 Dec 2001 11:25:25 +0000
>
Subject: Re: 9.2.2 Update effects on applescript
>
From: Simon Topliss <email@hidden>
>
To: Applescript Mailing List <email@hidden>
>
CC: Christopher Nebel <email@hidden>
>
>
"Mount volume" (Standard Additions 1.7) still not working with Windows 2000
>
servers in Classic. Does work in OSX, though. Any chance of this being
>
fixed?
>
>
On 10/12/01 11:53 pm, "Christopher Nebel" <email@hidden> wrote:
>
>
> On Monday, December 10, 2001, at 02:27 PM, Joe Kelly wrote:
>
>
>
>> Has anyone submitted a bug report to Apple?
>
>
>
> Yes, and we've written up a few ourselves. (If you think you've got a
>
> new one, though, feel free to submit it.) We've been tracking this
>
> quite closely; I hadn't said anything because we don't have anything
>
> substantive to say yet about how we're going to deal with it. Suffice
>
> it to say that we're working on the problems.
>
>
>
>> Having subscribed to Open Transport and Carbon email lists, I have
>
>> become
>
>> accustomed to actual Apple engineers responding to developers'
>
>> questions,
>
>> which seems not the case with this list.
>
>
>
> I read the list quite regularly, I just don't always respond. For that
>
> matter, most of the team reads the list, but more for informational
>
> purposes. There's a good set of list regulars who can deal with almost
>
> all normal and quite a few abnormal problems, so I try to stay out of it
>
> and write code. (Unless I'm bored or procrastinating!)
>
>
>
>
>
> --Chris Nebel
>
> AppleScript Engineering
>
> _______________________________________________
>
> 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.
>
>
--__--__--
>
>
Message: 4
>
Date: Tue, 11 Dec 2001 13:24:53 +0100
>
Subject: AS Quality Assurance (was: Re: 9.2.2 Update effects on
>
applescript)
>
From: christian vick <email@hidden>
>
To: <email@hidden>
>
>
on 11.12.2001 2:38 Uhr, Jolly Roger at email@hidden wrote:
>
>
> I'm personally amazed that this bug wasn't caught in the QA cycle BEFORE the
>
> product shipped. Has Apple done away with AppleScript quality assurance?
>
> Surely if a QA team had bothered to actually run some scripts in 9.2.2,
>
> they'd have come across this problem, no?
>
>
I don't think there is a dedicated person for QA. The 9.2.2 problems would
>
have been noticed, surely (and many other obvious problems in the past). I
>
don't understand this. It affects thousands of AS developers and even a lot
>
more users who are using our scripts. In my case at least 5000 users are
>
affected if they update to 9.2.2. :-(
>
I can't count the number of hours i spent in the past to adapt scripts to
>
new AS versions and to workaround bugs in general. This is what really
>
bothers me with AS!! I could easily be double-effective if AS would be
>
better tested and bugfixed.
>
>
QA Manager for AS would be a dream job, you could easily test new AS builds
>
with some scripts that involve nearly all of the commands, just looking for
>
the proper end result of the script. :-))
>
>
>
>
From what i know of real Mac programming (that's not much :), the OS toolbox
>
fixes functions by releasing always a new function to _supplement_ the old
>
function. This ensures that apps which rely on a specific behaviour of a
>
function are still calling the old version of the function and therefore
>
just working fine with all newer versions of the OS. That's why even very
>
old apps usually just work fine in current OS versions.
>
I wonder if something like this could be implemented for AS.
>
>
One way could be to using otionally <statement_version>, so if you write
>
"entire contents of" it just compiles to the newest version. But if you
>
explicit provide the version number "entire contents of_101" it uses version
>
1.0.1 of "entire contents".
>
Internally, the script would always store with which version numbers the
>
statements have been compiled, ensuring that it uses always the right
>
version on newer OS releases. If it's running on an older OS than it has
>
compiled on, it just uses the newest function version.
>
>
I can imaging that this is not easy to implement. Maybe it would work to
>
store only the version of AS at compile time in a script and later the OS is
>
running the proper AS environment for that script. This would give the
>
scripter not a choice of which version of a command he want to use, but it
>
would help that older scripts stops working on new OS releases.
>
>
>
>
>
Greetings
>
cris
>
>
--__--__--
>
>
Message: 5
>
Date: Tue, 11 Dec 2001 07:31:36 -0600
>
Subject: Re: AS Quality Assurance (was: Re: 9.2.2 Update effects on
>
applescript)
>
From: JollyRoger <email@hidden>
>
To: Applecript Users <email@hidden>
>
>
On 12/11/2001 6:24 AM, "christian vick" <email@hidden> wrote:
>
>
> on 11.12.2001 2:38 Uhr, Jolly Roger at email@hidden wrote:
>
>
>
>> I'm personally amazed that this bug wasn't caught in the QA cycle BEFORE the
>
>> product shipped. Has Apple done away with AppleScript quality assurance?
>
>> Surely if a QA team had bothered to actually run some scripts in 9.2.2,
>
>> they'd have come across this problem, no?
>
>
>
> I don't think there is a dedicated person for QA. The 9.2.2 problems would
>
> have been noticed, surely (and many other obvious problems in the past). I
>
> don't understand this. It affects thousands of AS developers and even a lot
>
> more users who are using our scripts. In my case at least 5000 users are
>
> affected if they update to 9.2.2. :-(
>
> I can't count the number of hours i spent in the past to adapt scripts to
>
> new AS versions and to workaround bugs in general. This is what really
>
> bothers me with AS!! I could easily be double-effective if AS would be
>
> better tested and bugfixed.
>
>
It's a sad day when Mac users can no longer count on the quality software
>
they are used to getting from Apple, and must instead grow accustomed to
>
putting on software beta tester hats. As you point out, this is especially
>
true for AppleScript, where "one small bug" can effect literally thousands
>
of users.
>
>
> QA Manager for AS would be a dream job, you could easily test new AS builds
>
> with some scripts that involve nearly all of the commands, just looking for
>
> the proper end result of the script. :-))
>
>
Well I doubt it would be a dream job. That really depends on what kinds of
>
development processes are in place in Apple engineering, and of course the
>
pay. ;^) But it could be fun, if the company as a whole supported the QA
>
team.
>
>
> From what i know of real Mac programming (that's not much :), the OS toolbox
>
> fixes functions by releasing always a new function to _supplement_ the old
>
> function. This ensures that apps which rely on a specific behaviour of a
>
> function are still calling the old version of the function and therefore
>
> just working fine with all newer versions of the OS. That's why even very
>
> old apps usually just work fine in current OS versions.
>
>
Toolbox APIs are maintained and added to while maintaining backwards
>
compatibility; but it's rarely done by adding supplemental functions to the
>
mix. Existing toolbox routines are updated regularly to keep up with
>
current OS releases, new technologies, etc. New functionality is fitted
>
into existing functions whenever possible without breaking the existing
>
functionality. For example, new values are added to the accepted range for
>
a parameter in a function - that way older apps can call the function using
>
old values, and newer apps can call the function using newer values. New
>
routines are only added when absolutely necessary.
>
>
--__--__--
>
>
Message: 6
>
From: email@hidden
>
To: email@hidden
>
Date: Tue, 11 Dec 2001 09:10:27 -0500
>
Subject: Re: Disappearing MenuScript
>
>
Thanks to all, for the advice.
>
>
I think I know why it disappeared after installing it I dragged it to a new
>
location. My assumption that dragging it to the menu bar would have copied it
>
to
>
the entrails of the OSX system folders prioved false. I've copied it to
>
Applications/AppleScript/Extras. where it will hopefullly live happily ever
>
after.
>
>
Fred
>
>
--__--__--
>
>
Message: 7
>
Subject: List Folder errors
>
To: email@hidden
>
From: "Brandon Carpenter" <email@hidden>
>
Date: Tue, 11 Dec 2001 08:13:52 -0600
>
>
On the desktop or folder on the Macintosh HD: or using a shared folder on
>
another mac this script works fine. When I attempt this script on a folder
>
on a mounted volume the property of aFolder reads alias "Ingest
>
1LoadImage:00881702022" or "Ingest 1:00881702022"
>
instead of the proper alias "Ingest 1:LoadImage:00881702022"
>
>
set aFolder to choose folder
>
try
>
set fileList to (list folder alias aFolder)
>
on error
>
set fileList to every file of aFolder as alias
>
end try
>
display dialog fileList as text
>
>
If I use the script List Files of a Folder from Macscripter.net the same
>
error occurs of the coericion of the path alias "Ingest 104577802102"
>
>
Also, the "of" doesn't seem to make a differance. The script will work just
>
fine with or without.
>
This script and others like it, still function properly on earlier versions
>
of Applescript.
>
Things I am looking into:
>
The mounted volume is a Wintel Volume. I am mounting the volume through
>
Dave using the IP address of the machine. I will try this mounting the
>
volume through other means.
>
>
Brandon Carpenter
>
806-352-6370 X 107
>
>
I find it ironic that I am surrounded by all these wonderful
>
gadgets that were supposed to make my life easier.
>
What life?
>
>
--__--__--
>
>
Message: 8
>
From: email@hidden
>
Date: Tue, 11 Dec 2001 15:24:25 +0100
>
Subject: [Announce] RSS/RDF support for osaxen.com
>
To: email@hidden
>
>
I'm pleased to announce a RDF/RSS interface to osaxen.com. The URL below
>
fetches a RDF/RSS file with title, version and link to more information
>
of the 10 newest scripting additions added to osaxen.com Feel free to
>
use and distribute the link.
>
>
<http://www.osaxen.com/backend.php>
>
>
- Martin
>
>
--__--__--
>
>
Message: 9
>
Date: Tue, 11 Dec 2001 08:26:35 -0600
>
Subject: Re: URL Access Scripting
>
From: Eric Schult <email@hidden>
>
To: Jolly Roger <email@hidden>, AppleScript Users
>
<email@hidden>
>
>
on 12/10/01 3:59 PM, Jolly Roger at email@hidden wrote:
>
>
> set ftpURL to "ftp://tjt:email@hidden/";
>
>
>
> set localFile to choose file
>
> tell application "URL Access Scripting"
>
> upload localFile to ftpURL replacing yes with progress
>
> end tell
>
>
The above script gave me a permission error, even though you're right, the
>
ftp string does work from inside an ftp client. I checked using Anarchie.
>
>
Somebody early on suggested I try URL-encoding the "@" as "@" in the
>
string, like so:
>
>
set ftpURL to "ftp://tjt:email@hidden@ftpads.journaltimes.com/";
>
>
... but that didn't work either. I guess I'm stuck, at least as far as
>
scripting it with "URL Access". I can do it with Anarchie with my eyes
>
closed, but I was trying to devise a droplet that I could send out to
>
customers who don't have an ftp client.
>
>
Thanks for all the help, though. I learned a lot in the process.
>
>
WES
>
>
--__--__--
>
>
Message: 10
>
Date: Tue, 11 Dec 2001 07:31:34 -0700
>
Subject: Bug or Feature?
>
From: Gnarlodious <email@hidden>
>
To: "AppleScript (Gnarlodious)" <email@hidden>
>
>
Am I correct in assuming that in order to use the "Property" statement the
>
script must run as an Application?
>
>
Rachel http://www.gnarlodious.com
>
>
--__--__--
>
>
Message: 11
>
Date: Tue, 11 Dec 2001 08:36:55 -0700
>
From: Lyle Petro <email@hidden>
>
Reply-To: email@hidden
>
To: email@hidden
>
Subject: Open for Access Nightmare
>
>
Hi,
>
I use open for access extensively in scripts to create temporary
>
files, etc. in the majority of my scripts. Last week, our System
>
Administrator installed a new router and at the same time created a new
>
AppleTalk zone. He has put one Mac on this new zone. Any open for
>
access commands run on this Mac now do not work. I am at a loss to
>
explain the problem. The error I get is (name of file specification)
>
does not understand the open for access message. Can anyone point to
>
any solutions? Thanks.
>
Lyle Petro
>
Application Specialist/Scanner
>
Saskatoon StarPhoenix
>
>
--__--__--
>
>
Message: 12
>
Date: Tue, 11 Dec 2001 14:48:48 GMT
>
From: "James Hirst"<email@hidden>
>
To: <email@hidden>
>
Subject: Printer settings
>
>
Has anyone found a scripting addition or utility such that allows applescript
>
to
>
access & change printer driver setings?
>
>
Thanks,
>
James
>
>
--__--__--
>
>
Message: 13
>
Date: Tue, 11 Dec 2001 08:53:05 -0700
>
From: Lyle Petro <email@hidden>
>
Reply-To: email@hidden
>
To: email@hidden
>
Subject: Open for Access Nightmare addendum
>
>
Hi,
>
A quick addendum to my open for access problem (get errors trying to
>
create a file using open for access command, error is (file spec) does
>
not understand open for access command). I have noticed that the
>
AppleTalk Zones for the servers I am trying to create the files on using
>
open for access are now different than the AppleTalk Zone that the Mac
>
in question are on (the Mac has had its zone changed). They used to be
>
one the same zone. Also, I have used Tanaka's osax to create a file
>
successfully. The problem seems only to occur with the open for access
>
command in the Standard Additions. While Tanaka's works, I would prefer
>
to stick with the Standard Additions.
>
Lyle Petro
>
Application Specialist/Scanner
>
Saskatoon StarPhoenix
>
>
--__--__--
>
>
Message: 14
>
Date: Tue, 11 Dec 2001 10:03:58 -0500
>
From: email@hidden
>
Subject: Re: 9.2.2 Update effects on applescript
>
To: email@hidden
>
>
On Mon, 10 Dec 2001 20:43:03 -0800, Paul Berkowitz <email@hidden>
>
suggested,
>
>
>>> set fileList to list folder of aFolder without invisibles
>
>
> i think the problem is the word "of", as I mentioned earlier.
>
>
I tried it with and without "of", and that doesn't affect the events that are
>
sent. The event viewer shows 'list folder "Disk:path" without invisibles' in
>
both cases and AETracker shows the same sequence of events and same data.
>
>
Now, it may be that in the new AppleScript, there is a difference in the
>
compiler's behavior that makes an explicit "of" for the direct parameter of a
>
command different than the implicit "of" you get when you write "list folder
>
[of] aFolder". That would be a bad change.
>
--
>
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
>
>
--__--__--
>
>
Message: 15
>
Date: Tue, 11 Dec 2001 10:07:22 -0500
>
Subject: Folder actions in OS X
>
From: Michael Turner <email@hidden>
>
To: email@hidden
>
>
Folder actions in OS X.2
>
>
Don't exist ?
>
>
/Michael
>
>
>
--__--__--
>
>
_______________________________________________
>
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.
>
>
>
End of applescript-users Digest