iWork Smarter, not Harder (Part II)


In iWork Smarter, not Harder I mainly talked about Pages, but the iWork suite also consists of Keynote and Numbers.

Keynote is for giving presentations, and if you’ve ever used PowerPoint, well, it’s like that, except you don’t want to kill yourself while you are using it. I mean, I’m sure there are people who enjoy using PowerPoint. I think they are called masochists. (I kid, I kid!)

PowerPoint, you’re fine for the Windows-wielding corporate drones of the world. Make your charts & graphs showing projections for the 4th fiscal quarter… someone has to do it. Is it my background as a designer that makes me feel like Keynote “gets it” where PowerPoint does not? I don’t know… but I actually like using Keynote for building presentations. In the olden days (2006) I’d probably be all hellbent on using S5 or some (web-)standards based presentation thingy, to avoid using a PDF, or a PowerPoint file, or some other thing I deemed “evil” or such… but I guess I’ve mellowed a bit… and, I like Keynote.

As for Numbers, I have less use for it, but appreciate the fact that I have a spreadsheet application that runs on my own computer instead of the cloud, and feels cleaner and functions better than the offerings of NeoOffice or OpenOffice. I tend to use spreadsheets as spreadsheets and not databases, as many people do, so I don’t use it a lot. I did find that making charts & graphs was pretty damn easy. I never knew how to make a damn chart in Excel, but Numbers was intuitive. In the olden days (2004) I’d probably be all hellbent on writing some Perl code to generate an SVG file if I needed a graph. It is nice to have Numbers around as an option though.

So while I’m thankful for these useful tools, I’m still a fan of writing HTML for presentations, and (being able to) write code to generate charts & graphs. I mean, choice is a good thing… right?

See Also: iWork Smarter, not Harder (Part I)


iWork Smarter, not Harder


I have a confession to make… I’m becoming a fan of Apple iWork.

I’ve always hated office suites. I entered the work world through the creative door, and we used tools like QuarkXPress, and Photoshop, and when I got into web development I used text editors. I never really had a need for office suites to create anything. My relationship with them was always in the form of document transcoders. Transcoding documents was not always easy in the times before free office suites like OpenOffice or NeoOffice.

Oh yes, OpenOffice and NeoOffice… When these came along I was thankful. Very very thankful. Finally, we could open those damn Word documents, and get the text out of them for whatever purpose we needed! Print brochure, web site, whatever. They were like can openers (or crowbars) for those .doc formatted files.

Years ago I did a contract job as a web developer in a Windows shop. They gave me Microsoft Word for some work I had to do, and no matter what I did, I could not get the thing to work the way I wanted it to work. Maybe I was used to QuarkXPress or InDesign, which are page layout applications where you have control over everything, but Word seemed to have a mind of it’s own as to where it would place things and how it would format them. It was maddening!

Sadly, while OpenOffice and NeoOffice are free alternatives, and great open source projects, I still didn’t find either one that good for creating documents. They just seem to do “weird” things that I don’t want. But recently, I started using Pages… lo and behold, it actually seems to do things that make sense. It actually seems to work the way I expect it to work. I don’t know if there’s some “Do What I Mean, Not What I Say” magic in there or what…

My only gripe about Pages so far is that it can’t open .odt documents. This would be an ideal feature, as I could easily open all those files I’ve created with OpenOffice and NeoOffice. Sadly, to get the most widespread ability to open a document, it looks like .doc is the best option. It can be opened by Pages, TextEdit, OpenOffice, NeoOffice, Microsoft Word, and many others… It’s not an ideal solution, but it works.

And Apple, why can TextEdit open .odt files but Pages can’t? You obviously have the capabilities. Yes, there is some loss of formatting, but it would save one more step in the chain… Hmmm, maybe you’re working on better .odt support for Pages… yeah, that must be it.)

See Also: iWork Smarter, not Harder (Part II)