via Daring Fireball
The top comment on the YouTube video sums up the failings of this new system compared to the old. User yexuyouyong writes:
A flaw with this is you need to know the key word before you could search. Say someone wants to create a bookmark but doesn’t know the ‘bookmark’ keyword. Instead he/she types in something like ‘remember this page’ and he won’t get the bookmark option. A menu system presents all options up front, while a search-only system puts you in the wild with the whole dictionary as options. Until AI can understand natural languages, I see this as a step backward.
Using a phrase from Microsoft, I doubt this will work because it requires a “posture change”. Consider a GUI heavy app like a drawing app will likely have the user’s hands divided to keyboard and mouse, where the keyboard hand is likely executing known shortcuts. For the rest, the primary mouse hand locates the menu item or button until the referenced keyboard shortcut is learned by the keyboard hand. Everything can be accomplished within reach of the wrist.
In the new HUD system, a posture change occurs when the user must remove one hand from the mouse, and the other away from the Ctrl or Meta keys. When the command is found, the hands return. Functions the user can’t remember or discover a shortcut require moving outside the distance covered by the wrists.
Effectively, this increases the time to complete a task per Fitt’s law, because the user has to contend not only with GUI targets, but repetitively switching to and away from the home row (or comfortable hunt-and-peck typing posistion).
John Gruber comments:
This is Apple at its worst. Let’s hope this just the work of an overzealous lawyer, and not their actual intention.
It’s got to only cover the sale of an iBooks Author output file, and the exact binary output of the iBooks Author file type. The content of the book, the plain text, images, diagrams, media, questions and answers must surely be retained by the writer/publisher for their own use.
I can’t see Apple getting mad that a publisher decides to publish an iBooks Author version and an ePub or HTML5 version, selling each in their respective stores. But if a publisher used the output of iBooks Author to be converted as-is, or wholly imported into a competitor’s product or interpreter, I could see a cause for being upset. Apple has an interest in not fragmenting their Store system, and so this claim seems fine and consistent with it’s other well known App Store regulations regarding free corporate and education app distribution.
It’s hardly like Apple makes the claim that because Angry Birds is on iOS that they are legally bound to not sell their product on any other platform.
It would be impossible to defend the point that a letter drafted in MS Office would belong to MS given a similar interpreted EULA. The binary output, perhaps could have those rights withheld, but the author would retain the ability to take their content and place it in some other container or file format, one that that MS wouldn’t own, and therefore only have rights to the MS Word derivative. However, MS word is not sold as a a means of creating products of value and/or for sale by it’s end users.
If you think this is a new concept, of claiming ownership or control of use of the output of a software product, you’re highly mistaken. Companies that make software for research (as in math and science) often have student, evaluation, and full versions that might be full featured form a technical sense, but contain license agreements that work done with these be limited to classwork, in-class demonstrations, or research purposes. Why should a researcher grift a software company when grant money is meant to pay for this sort of technical development? They’re free to take their input elsewhere to be processed into results or grow their own solution. But for many, the problems to entry have already been solved and is affordable to those individuals.
For the case of interactive, reliable, media-driven book-like apps, the problem was just recently solved by iBooks Author, where previously there was no off-the-shelf solution. And with some apps never getting updates by being dropped by their developers, the problem was likely to be just as bad as physical books being out of date the moment they’re printed, because these attempts at coffee-table apps required a technical niche to be readable. The iPad being “popular” as a device does not negate the issue of development being a niche.
Compatible file formats, maintained by a central body, being the same body that manufactures the devices, focused on providing consistent experiences, and being able to fix bugs when authors and developers are long unable to return to the source. It makes sense that Apple wants to be assured that a publisher won’t try to swindle the tool-makers or collude with the competition with Apple’s own hard work without their fair share.
This interpretation of the EULA will likely be yet another misinterpreted policy or intention that will remain a talking point in freedom-airheads such as Richard Stallman and Cory Doctrow (although I really enjoyed his speech at 28c3).
Popcorn on the stove - rarely burned.
Popcorn in the microwave - rarely edible.” —from @kiodane on Twitter - http://bit.ly/zRlT3B
-film: Topsy-Turvy” —from http://bit.ly/tNpaJ6
Work policy asks to keep one earphone off so to hear coworkers…
… but it sure makes stereo Beatles albums sound weird.” —from http://bit.ly/tNpaJ6