RE: Appleworks.
RE: Appleworks.
- Subject: RE: Appleworks.
- From: "Ruby Madraswala" <email@hidden>
- Date: Wed, 20 Oct 2004 08:57:32 -0400
- Thread-topic: Appleworks.
Yes, I do owe a more detail explanation. I have bunch of scripts which works fine with TextEdit files. Using it for a year now. We are moving our users from OS 9 to OSX, and most are opting to use Appleworks as their word processor. The scripts I have, does not work with the Appleworks files. If I manually save the Appleworks (.cwk) files as text, the script works fine. So I thought the easy way out would be to add a handler that would save the Applescript (.cwk) as text file, and all the scripts would work fine. Is there a better or more efficient way of handling this?
Ruby
-----Original Message-----
From: applescript-users-bounces+rubym=email@hidden [mailto:applescript-users-bounces+rubym=email@hidden] On Behalf Of Mr Tea
Sent: Wednesday, October 20, 2004 5:03 AM
To: AS Users
Subject: Re: Appleworks.
This from Paul Berkowitz - dated 20/10/04 8·45 am:
> On 10/20/04 12:34 AM, "Mr Tea" <email@hidden> wrote:
>> Let's be helpful here, rather than judgemental.
>
> So why isn't the suggestion to change the creator code helpful, Nick? That
> will keep it as a text file belonging to AppleWorks - which seemed to be the
> point of the request, no?
You left off my smiley. :<(
How was that the point of the request, Paul?
This from Ruby Madraswala - dated 19/10/04 6·59 pm:
> can anyone give me the syntax for the following.
>
> 1. Open a text file (from TextEdit) in Appleworks.
>
> 2. Save Appleworks document as text file.
In truth, there's not a lot of information there, but there are good reasons
for not wanting to assign an AppleWorks creator code to a text document. AW
doesn't actually 'open' TEXT documents, it imports their contents to a new
untitled document and asks if you want to save your changes when you try to
close it - even though you haven't made any changes. Messy. Inconvenient.
Lame. Far better to leave the document so that it opens in an editor that
deals with plain text files more gracefully.
But perhaps, like me, the original poster has some existing scripts that
work with Appleworks, and wants to use these on the text. We'll have to ask
Ruby what went on between the two bits of syntax she requested.
Many Mac users started out with AppleWorks/ClarisWorks as their first word
processor, and it follows that those who also discovered the joy of
AppleScript will have dabbled with AW/CW's scripting dictionary. Maybe they
even started out with the examples in the ASLG. I have a bunch of AppleWorks
scripts from prehistoric times that still work, and are pretty much the only
reason I still have AW installed. If I could just change the app name in
them to Word, or Nisus Writer Express, or Tex-Edit Plus, or BBEdit, or
Stickies - and have them still work, well hey! I'd do it in a flash. But
that's not how AppleScript functions, as we all know.
In the meantime, there's a compelling case to be made for _not_ saving a
text document edited in AppleWorks as an AppleWorks text document.
Nick
pp Mr Tea
--
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden