Quote:
Originally posted by Carson O'Genic
Do I undrestand you correctly that you think Apple may be waiting to put enough of CI/CV and the speculative CO in 10.3.5 for their own use in Appleworks, but locked out from the rest of the developer community, i.e. frameworks = core system level code? What funsctions would you guess CO to have?
Not quite. The first iteration of the frameworks would be "locked" because it would only have been developed enough to ship AppleWorks. It takes a lot longer to polish a framework up for general use. If Apple ships AppleWorks with a private version of Core Office, they have any number of months to refine, update and debug the framework before they make it generally available, and they have an application they can use to prove the framework. This is exactly what they did with Core Video and Motion.
I would expect "Core Office" to be Core Text (already in process), Core Data (in process), and since Apple already has excellent, high-performance math libraries, that's really it. Really, the more I think about it the more I realize that they're really close.
I believe that the holdup has to do with the fact that the old WP paradigm is too manual, too dated, too complex. I mean, why should you need Quark to make a paragraph look good? It's possible, with OS X's text and layout engines, to have a word processor that's much smarter than the current ones are with respect to leading, kerning, spacing, styles, font handling, etc. But it requires a great deal of under-the-hood work, and it has to be highly polished to be worth the trouble.
(Note that I'm not talking about positioning AppleWorks as a competitor to Quark and InDesign! I'm just saying that there's no reason, given the sophistication and power of modern systems, why your college paper or newsletter or other AppleWorks-appropriate document shouldn't look attractively laid out and professionally typeset without your lifting a finger. Obviously, for midsize to large projects, anything targeted at professional printers, and anything with an involved layout, you'd still want a page layout application.)