iWork for iOS and Mac Updated, Keynote Gains New Transitions

Bring back 'Facing pages' and perhaps I will start using it again. I did not buy a 27" iMac just so that I could scroll down single pages, Apple.


Microsoft Word allows me to have 4 pages on one screen. Your screen.


Fix it.

If they are starting the updates this quickly wouldn't it have made more sense to release a finished product? Updates re-introducing old/new features doesn't make sense to me. Was anyone really clamoring for a redesign of the iWork suite so badly that releasing an unfinished product was necessary?

It's their product and they know way more than I do about it.

Just an outside-in observation.:confused:

How about bringing back the ability to:

Add a page
Delete a page
Move a page
Duplicate a page
Copy a page

Shouldn't be too complicated... :(

Wow, that was fast!
I'm guessing they actually planned to start restoring the missing features in advance and not just in response to negative publicity.

Bring back 'Facing pages' and perhaps I will start using it again. I did not buy a 27" iMac just so that I could scroll down single pages, Apple.

Microsoft Word allows me to have 4 pages on one screen. Your screen.

Fix it.

For Jackie (as well as everyone else who gave this a thumbs up), I offer the following free advice (worth at least what you paid for it) as a former Apple engineer:

Stuff that's not in Radar is invisible.

My suggestion would be:

1. Go to developer.apple.com and sign up for a free developer account if you don't already have one (using your existing Apple ID).

2. Go to bugreport.apple.com and file a bug. Take note of its number.

Notes:
a) Make the scope of your bug as narrow as possible -- two different things may be assigned different engineers, different teams, different milestones, and it's frustrating to have to break things into pieces all the time as it makes bug reports confusing to read

b) If you get a response asking for more information, please answer it (so many do not)

c) System configs are wonderful things

d) Be polite

3. Go to openradar.appspot.com and add a description of what you filed. That way, other people can say, "Oh, yeah. THAT." And they can then write another bug report referencing yours.

When there are reports that have more duplicates than others, they tend to get higher priority.

Maybe one day they will actually add the ability to open a document which is password protected. Always seem to forget the simple things. :confused:

I actually like Pages again....just waiting for more Newsletter layouts though. I really enjoyed those in the old version. Thanks for the hard work Apple!

Hard work? You must be kidding.

Apple leaves iWork dormant for almost five years, and when they finally release a new version, it has less features than the previous one. In those almost five years, they could have completely re-written iWork and included all the features again and many more. Meanwhile, it sits on a pile of almost US$ 150 billion in cash, which is certainly not being spent on the development of products, especially iWork.

I see many people making this same mistake. Apple did not "remove" any functions. This version of iWork was completely re-written in 64 bit, using Apple's most current development tools.

What happened was they couldn't include every existing function in time for the release. So, people say "then wait till it is finished to release it." But if they did that then there would be just as much bitching about why it is taking too long.

So while on the surface it seems like an "undo" would restore functions, it is really a complete "rewrite" to bring back these functions.

Making it 64 bit is trivial. It's a setting in Xcode. Target > Architecture > Change 32 bit to 64 bit. 90+% of your code requires no changing whatsoever. Most of the changing that needs to take place is trivial - changing one data type with another, which if they've typedef'd and factored properly, is really easy.

Those icons make my eyes bleed! Stop it Jonathan Ive!!

If they are starting the updates this quickly wouldn't it have made more sense to release a finished product? Updates re-introducing old/new features doesn't make sense to me. Was anyone really clamoring for a redesign of the iWork suite so badly that releasing an unfinished product was necessary?

It's their product and they know way more than I do about it.

Just an outside-in observation.:confused:

if you work in software, or creative writing, then youll know -- nothing is ever finished. most often the deadlines eventually get set at some point, but because it's not a hard science and is instead a bit of guesstimation, not everything makes it...you try to get as much as possible. lower-priority items (like these additional transitions) get bumped to future releases.

in a perfect world we'd all produce our code in a neat little dependable way that makes scheduling 100% accurate. but that aint this world. every programmer i know tends to underestimate how long it takes us to do things, whether due to enthusiasm or unexpected challenges.