Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
For me, the lack of spell check as you type is no big deal.

I can't stand it and always turn it off when i have to use word.

It is distracting, stops the flow that you need to keep writing effectively, and you can go back and check the doc once you're done anyway.

I find that most of the mistakes I make are typos anyway, and it sux to have to stop just to correct minor things that will be corrected anyway.....


just my 0.02
 
Re: great update, but...

Originally posted by achmafooma
The ONLY THING I really wanted in an AppleWorks update was "Check Spelling As You Type". Considering it's OS-wide, of all companies Apple should be able to implement it into their word processor.

Spell checking is "OS-wide" only in Cocoa apps, just as Services, the Font Pane and sheets are only available in Cocoa apps. AppleWorks is little more than a carbonized version of earlier incarnations of Apple/ClarisWorks, and is really showing its age now. It's almost embarrassing for Apple to still be distributing this barely OSX-compliant product. I use it, but I know Apple can do much better -- and I hope they do, very soon.
 
Re: Re: Export in Appleworks for OSX question

Stu and Doctor Q, Thanks for your help!! Your MOM thanks you : )

It looks like the OSX version with the PDF capabilities of OSX help to get around the lack of EPSF export. This still means that to get a high resolution tiff that the PDF has to be opened in another program (graphics converter?) and then saved as a hi-res tiff. Hopefully, this results in better quality text. I've had the same problems with jagged text when importing into MSWord. Years ago it worked great in ClarisDraw to export EPSF and then import the graphic in word. Now importing any of the formats that Appleworks Draw exports results in poor text in the graphics.

I'm doing my best to stay with Appleworks, but the limitations are making me think I need to switch to using Adobe Illustrator or go back to ClarisDraw which can still export EPSF. Too bad, because Appleworks is simple and for my simple needs does most of the job.

I hope the rumors are true and Apple has a real upgrade to Appleworks in the works. I also hope that when it comes out that it can read Appleworks files! I still can't believe that Appleworks won't read ClarisDraw files. Complain as much as you want about MS proprietary file formats, Apple does the same and then doesn't even support them in futre versions!

MOM
 
Now that's interesting... this updater is only for North American versions of AppleWorks. I thought we were past all that limited regionalisation stuff?
 
Originally posted by robotrenegade
How does Appleworks compare to Word?

I put MS Office on my iBook shortly after acquiring it, but decided to try to use AppleWorks and Keynote instead; I figure, why not go for the whole "switch" enchilada all at once? I never did use any of the advanced Word features so AppleWorks is just fine with me. And I hate and deactivate "check spelling as you type" too; I just wish the 'Works window would automatically open full screen. Also, I avoid any other conflicts by saving as .rtf; people at work use Word and WordPerfect so I don't have to translate for anyone. . .
 
Re: comparison

Originally posted by Qball
Any opinions on how Appleworks compares to Thinkfree Office?

I tried ThinkFree Office and found it too slow and the interface too foreign. Nice effort otherwise!
 
Originally posted by robotrenegade
How does Appleworks compare to Word?
You should either compare AppleWorks word-processing to MS Word, or compare AppleWorks as a whole to the combination of Word/Excel/Powerpoint in MS office. For the latter, the AppleWorks advantages are:

* price

* word-processing: simpler and therefore easier to learn

* spreadsheet: no advantages I can think of; I find it unusable without in-cell editing

* drawing: much easier than trying to use Word's drawing tools, which always seem to have a mind of their own; more oriented towards creating drawing documents, instead of presentations, than PowerPoint

* painting: the AppleWorks module isn't fancy, but at least it's a full member of the suite

If you want to compare AppleWorks word processing with Word, feature by feature, you'll find that Word has everything while AppleWorks has the stuff you need most often.
 
I did the upgrade on two different copies of Appleworks 6.2.4 I have. Both now say 6.2.7 in the get info box, but inside the program "About Appleworks" still says 6.2.4. Anyone else see this?
 
Originally posted by matznentosh
I did the upgrade on two different copies of Appleworks 6.2.4 I have. Both now say 6.2.7 in the get info box, but inside the program "About Appleworks" still says 6.2.4. Anyone else see this?

Nope. My "About Applework" box say 6.2.7.

However, I must say that I'm really not impressed with this. It seems to me, for the amount of time that has gone by since the 6.2.4 upgrade, you'd think they could have managed a little better. The one example I can point to is that, in most apps I work with (both Carbon and Cocoa) when you change a document the close button gets 'dimpled'. This makes it easy to see when a document has been modified. Appleworks still doesn't support this.

Ever since moving to OS X, I've had rather mixed results with Appleworks. I have seen it do things that I'm told it shouldn't be able to do. (Though I've had Apple authorized techs at my local reseller/servicer say that they've seen the same and more from AW). The classic example is having AW crash, and it brings down the Classic environment and any classic apps that are running with it. In general, when I run AW, I try to make sure that I keep Classic shut down, as that seems to improve AW's stability. Go figure...

All of that said, I still prefer AW to MSW. However, not by as much as I used to prefer ClarisWorks. That was a lean, mean program in its day. But I'll be happy when there are more options on the table. (Apple Office, OpenOffice, etc.)
 
Originally posted by Snowy_River
The one example I can point to is that, in most apps I work with (both Carbon and Cocoa) when you change a document the close button gets 'dimpled'.

Take another look and I think you'll find that only Cocoa applications support this behavior.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.