Home > Articles > Programming > General Programming/Other Languages

How Core Animation Changed Cocoa Drawing

  • Print
  • + Share This
OS X is a descendant of the NeXTSTEP operating system introduced in the mid 1980s. During this time, NeXT and Apple have evolved the display model considerably. David Chisnall looks at how things have changed between Display PostScript and CoreAnimation, and where they might end up in the future.
Like this article? We recommend

Like this article? We recommend

Cocoa has been the standard toolkit for creating applications on OS X since it was released, and is a direct descendent of the OpenStep frameworks used on NeXT workstations previously. With 10.5, Apple introduced the CoreAnimation framework. This made a lot of effects easy. Under the hood, it made some fundamental changes to the Cocoa drawing model. In this article, I'm going to look at how this model has evolved and what the changes mean.

From PostScript to Quartz

The original NeXT workstations licensed Display PostScript from Adobe. PostScript is a stack-based language designed for printing. PostScript is a Turing-complete language, meaning that it can implement any algorithm, and has complex built-in support for drawing Bezier curves. Display PostScript extended this with a few other features, such as support for multiple contexts (so each window could run independent PostScript programs) and event handling.

The OpenStep specification required Display PostScript and provided a set of classes for interacting with it. You could write PostScript programs and send them to the display server to run. A competing system at the time, NeWS from Sun Microsystems, worked on the same idea. This was much more responsive than X11 over a remote connection because entire view objects could be run on the display server and only send high-level events to the program. This functionality was not often used with Display PostScript on NeXT systems.

It turned out, in fact, that no one was really making much use of the DPS layer on NeXT to run real programs on the display server (with the exception of one infamous proof-of-concept remote exploit). Everyone else was just treating it as a canvas for drawing commands.

With OS X, Apple (having bought NeXT) had the opportunity to replace DPS with something a bit more modern. One of the motivating factors for this, no doubt, was the desire to stop paying a license fee to Adobe for every copy sold.

One of the advantages of Display PostScript was the fact that the display server could cache drawing commands, rather than bitmap images. If you have a screen resolution of 1024*768 in 24-bit color, then you need 2.25MB of RAM for the frame buffer. Not a huge amount by modern standards, but close to the limit of video memory for most machines in the 1990s. Now consider what happens when you move one window across another.

There are two common solutions to this problem. The simplest one is when every time a new bit of the bottom window is exposed, to ask the application to redraw it. This is not ideal. It involves several context switches between the display server and the application, and a lot of inter-process communication. The other option is for the display server to keep a buffer of both windows and just composite them. This is conceptually simpler, but requires a lot more RAM. If each window is almost as big as the screen, then you need 2.25MB of RAM for the frame buffer, and 2MB for each window. On a system with 8 to 32MB of RAM, you quickly reach a limit as to the number of windows you can have on screen at once.

Display PostScript had a third option. It could keep copies of the PostScript programs used to generate the window contents—typically much smaller than the rendered images—and just run them again. This was quite fast, didn't use much memory, and generally worked well.

By the time OS X was introduced, RAM was a lot cheaper. The first iMacs had 8MB of dedicated video memory and 64MB of main memory—about as much as the most expensive workstation NeXT ever produced with all of the upgrades. The graphics card was not a simple frame buffer; it could handle things like OpenGL rendering, including textures.

To take advantage of this, Apple made a few changes to the display server architecture. The first change was to switch from a PostScript to a PDF model. Unlike PostScript, which is a full programming language, PDF is just a display language. It does not contain things such as loops or conditionals. This simplified the drawing code a lot, because it just had to handle drawing, not flow control.

The second change was to move to a buffered rendering model. Instead of storing the PDF display lists, the new window server (Quartz) stored a bitmap image for each window. Initially this was just a shared image, but in later versions it was a texture on the GPU. These buffers were then composited by the window server.

There are a few advantages to this. One of the most obvious is that it makes things like transparency and the “genie” effect for miniaturization easy. Each window is just texture on the GPU; it can be drawn on any polygon and with any blending functions. The other big advantage is less obvious and relates to the lower level parts of the operating system.

With Display PostScript, the window server did all of the drawing. Simple and complex drawing commands were equally easy to do in the client; they were just function or method calls that appended a few PostScript commands to the stream. The resulting program ran on the display server. This made process accounting very difficult. Two programs could be using equal amounts of CPU time but one could be responsible for 90 percent of the time the window server spent drawing, yet both would receive equal priorities in the operating system's scheduler. Moving the drawing into the client processes made this much simpler.

The final change introduced with Quartz was to remove the well-defined binary communication interface between clients and servers. If you communicate with the window server on OS X, you go via the QuartzCore framework. This communicates with the display server via a private protocol. This is in contrast with something like X11, where a sufficiently motivated individual can write his or her own client library talking directly to the window server, or can go via one of the existing libraries such as XCB and XLib. If the Quartz window server gains some capabilities, then Apple can update the QuartzCore functions to make use of them. Developers of frameworks such as GTK+, Qt, or GNUstep on X11 can do the same thing, but people (including toolkit authors) using xlib directly have to modify their code to take advantage of new extensions.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020