<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Apple Inc.</title>	<link>http://tc.eserver.org/publisher/Apple_Inc.</link>
	<description>A listing of works published by Apple Inc. in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Apple Inc.</title>
		<link>http://tc.eserver.org/dir/Apple_Inc.</link>
	</image>
	<item>
		<title>HelpHook</title>
		<link>http://tc.eserver.org/29970.html</link>
		<guid>http://tc.eserver.org/29970.html</guid>
		<description>This is a very simple example of integrating a J2SE application with the Apple Help Viewer application. This sample code has been updated to include a project that produces a universal binary. No code changes were required for it to run correctly on Intel-based Macintosh computers.</description>
	</item>
	<item>
		<title>Apple Publications Style Guide</title>
		<link>http://tc.eserver.org/27313.html</link>
		<guid>http://tc.eserver.org/27313.html</guid>
		<description>The Apple Publications Style Guide provides editorial guidelines for text in Apple instructional publications, technical documentation, reference information, training programs, and the software user interface.</description>
	</item>
	<item>
		<title>Delivering Content with RSS for Web Developers</title>
		<link>http://tc.eserver.org/27316.html</link>
		<guid>http://tc.eserver.org/27316.html</guid>
		<description>The delivery of web content is being revolutionized by a new technique known as syndication. The most common format for syndication is RSS, or Really Simple Syndication, an XML (eXtensible Markup Language) format for coordinating the delivery of time-based content streams, or &apos;feeds.&apos; This means that RSS can be used to deliver content that changes over time. RSS provides for the inclusion of additional data, similar to email attachments, using the ENCLOSURE tag.</description>
	</item>
	<item>
		<title>HTML Scripting Guide for QuickTime</title>
		<link>http://tc.eserver.org/27314.html</link>
		<guid>http://tc.eserver.org/27314.html</guid>
		<description>You can use QuickTime and HTML together to present various kinds of multimedia over the Internet or from a local disk. There are specific HTML tags and parameters that cause a browser to load QuickTime and allow the HTML author to control QuickTime&apos;s behavior.</description>
	</item>
	<item>
		<title>Introduction to Apple Human Interface Guidelines</title>
		<link>http://tc.eserver.org/27312.html</link>
		<guid>http://tc.eserver.org/27312.html</guid>
		<description>These guidelines are designed to assist you in developing products that provide Mac OS X users with a consistent visual and behavioral experience across applications and the operating system.</description>
	</item>
	<item>
		<title>Safari FAQ for Web Developers</title>
		<link>http://tc.eserver.org/27315.html</link>
		<guid>http://tc.eserver.org/27315.html</guid>
		<description>Most developers are happy to follow the W3C guidelines and have their pages &apos;just work,&apos; with no need for browser-specific HTML. Safari has the features you&apos;d expect of a modern browser plus a few unique ones; understanding these, as well as a few Safari development tricks, will ensure your pages work exactly the way you and your users expect.</description>
	</item>
	<item>
		<title>Typographical Features of the Cocoa Text System</title>
		<link>http://tc.eserver.org/27310.html</link>
		<guid>http://tc.eserver.org/27310.html</guid>
		<description>It is common, especially in technical writing, to mix languages with differing text direction, such as English and Hebrew, in the same line. Some writing systems even alternate layout direction in every other line (an arrangement called boustrophedonic writing). Some languages do not group glyphs into words separated by spaces. Moreover, some applications call for arbitrary arrangements of glyphs; a graphic layout may require glyphs to be arranged on a nonlinear path.</description>
	</item>
	<item>
		<title>Universal Access: Computers That Everyone Can Use</title>
		<link>http://tc.eserver.org/27311.html</link>
		<guid>http://tc.eserver.org/27311.html</guid>
		<description>Apple has been working hard on Universal Access and it&apos;s time for you, the developer, to incorporate Universal Access into your application if you haven&apos;t done so already. This article guides you through the reasons you will want to provide Universal Access, the architecture underlying the technology, and how to get started incorporating these features into your application.</description>
	</item>
	<item>
		<title>Accessibility</title>
		<link>http://tc.eserver.org/27300.html</link>
		<guid>http://tc.eserver.org/27300.html</guid>
		<description>Since the discourse over creating accessible Web pages began, the standards organizations that helped inform the new Federal rules have stressed the separation of design and content. If the Internet is to reach its full potential, content will need to be authored so that it can be rendered by a broad array of devices: browsers, assistive technologies, PDAs, and devices that have yet to be imagined. Only by separating content from design will this be possible.&#xD;&#xD;By following the rules in Section 508, you will be doing more than providing access for those with disabilities; you will be creating content that is available to all users, no matter what devices are used to read it.</description>
	</item>
	<item>
		<title>Cross Browser Animation</title>
		<link>http://tc.eserver.org/27292.html</link>
		<guid>http://tc.eserver.org/27292.html</guid>
		<description>Dynamic HTML (DHTML) provides a new range of ways to animate a page. DHTML can animate both text and images and animations can move throughout the browser window, instead of being anchored in one spot. Unfortunately, DHTML can be tricky because of differences between browsers.&#xD;&#xD;This article will cover the basics of cross-browser animation. You’ll learn how to animate text and images. Plus you’ll see how to move HTML elements around the screen. After you’ve finished reading this article, you should be able to add cross-browser compatible DHTML animations to your web pages.&#xD;</description>
	</item>
	<item>
		<title>Dynamic Content with DOM-2 (Part I)</title>
		<link>http://tc.eserver.org/27297.html</link>
		<guid>http://tc.eserver.org/27297.html</guid>
		<description>The relatively recent emergence of peer-to-peer distributed computing and the renewed interest in real-time data exchange have stoked the embers of a hot topic: displaying dynamic content over the Web. Unfortunately, the statelessness of HTTP and the limitations of the rendering components of different browsers present significant challenges to web developers wishing to get fresh information to the client without sending additional requests to a server.</description>
	</item>
	<item>
		<title>Dynamic Content with DOM-2 (Part II)</title>
		<link>http://tc.eserver.org/27298.html</link>
		<guid>http://tc.eserver.org/27298.html</guid>
		<description>This article dives into the JavaScript node interface and examines the different ways of altering the visible properties of an element or text node. You’ll first learn how to alter element attributes with DOM element methods, then you’ll see how to change an element’s style properties through the DOM Level 2 (DOM2) Style specification interface.</description>
	</item>
	<item>
		<title>Dynamic Forms with DHTML</title>
		<link>http://tc.eserver.org/27293.html</link>
		<guid>http://tc.eserver.org/27293.html</guid>
		<description>This approach uses Dynamic HTML (DHTML), which has several benefits over using IFRAMES to make life a bit easier for the users of your site. First, DHTML allows for more flexible formatting than IFRAMEs permit. You can apply background images, borders, fonts, and all the other features you’ve learned to expect from HTML and Cascading Style Sheets to DHTML objects. In contrast, IFRAMES have almost no configurable features. Second, if someone fills out one form, switches to another, then switches back, there’s a good chance that the browser will lose the information that was initially entered. This problem doesn’t exist in the DHTML solution. Third, with DHTML you can do tricky things like clipping and moving the form around the page. You could do these things by combining IFRAMES and DHTML, but you might as well just use DHTML in the first place.</description>
	</item>
	<item>
		<title>Dynamic HTML and XML: The XMLHttpRequest Object</title>
		<link>http://tc.eserver.org/27309.html</link>
		<guid>http://tc.eserver.org/27309.html</guid>
		<description>As deployment of XML data and web services becomes more widespread, you may occasionally find it convenient to connect an HTML presentation directly to XML data for interim updates without reloading the page. Thanks to the little-known XMLHttpRequest object, an increasing range of web clients can retrieve and submit XML data directly, all in the background. To convert retrieved XML data into renderable HTML content, rely on the client-side Document Object Model (DOM) to read the XML document node tree and compose HTML elements that the user sees.</description>
	</item>
	<item>
		<title>Fonts</title>
		<link>http://tc.eserver.org/27301.html</link>
		<guid>http://tc.eserver.org/27301.html</guid>
		<description>The ability to customize fonts— in Mac OS, in word processing documents, in Web pages— is really nothing new. However, when it comes to changing fonts on Web pages, the mechanism is decidedly less intuitive and certainly less than easy. Having to litter a Web page with FONT FACE tags makes for larger files, and larger headaches as you weed through these tags to find that one misspelled word. CSS makes the process of selecting a font easy, and even better, it provides a fallback mechanism for those times when users don&apos;’t have the fonts you wanted to appear.</description>
	</item>
	<item>
		<title>Form Validation</title>
		<link>http://tc.eserver.org/27299.html</link>
		<guid>http://tc.eserver.org/27299.html</guid>
		<description>Any sort of interactive site is going to have form inputs — a place where your users input who they are, what they want to buy, where they live, and so forth. This data is passed to whatever handles your back end — a Perl CGI script, a PHP engine, a database like Oracle, or some other technology you’ve invested in. Whatever system is back there, you can bet that it doesn’t appreciate having its time wasted with bogus information, and chances are the user doesn’t appreciate it either. If the data the user submits to the CGI contains an error, there will be a noticeable lag — typically several seconds — before the information travels over the Internet to the server, is examined on the server, and then returns to the user along with an irritating error message.&#xD;&#xD;If you run a little preliminary validation of the user’s form input before the form is submitted, there will be no wait time. Client-side validation is instantaneous because it doesn’t have to transmit any data. JavaScript catches any erroneous data the user enters before it goes anywhere.</description>
	</item>
	<item>
		<title>Hide/Show Layer</title>
		<link>http://tc.eserver.org/27302.html</link>
		<guid>http://tc.eserver.org/27302.html</guid>
		<description>This script uses dynamic HTML (DHTML) to pop open a box with info in it when you click on a link. In my demo I’ve used this to pop up contextual help about filling in a form. It could also be used, for example, to give pop-up definitions for terms in an article. In both cases, it makes sense to give the information in context, modelessly. Likewise, this solution avoids the problems of statelessness and latency.</description>
	</item>
	<item>
		<title>Horizontal Sizing in CSS</title>
		<link>http://tc.eserver.org/27303.html</link>
		<guid>http://tc.eserver.org/27303.html</guid>
		<description>This article covers horizontal sizing and shows how to determine the width of elements with CSS. Once you’ve mastered both height and width, you should be well on your way to effectively using CSS.</description>
	</item>
	<item>
		<title>Modifying Styles</title>
		<link>http://tc.eserver.org/27307.html</link>
		<guid>http://tc.eserver.org/27307.html</guid>
		<description>With the release of W3 compliant browsers however, we now have the ability to change styles on the fly from JavaScript, using the W3C DOM. Unfortunately, due to a distinction between the way that embedded and remote stylesheet properties are exposed as opposed to the way that inline STYLE properties are exposed, this can be tricky.</description>
	</item>
	<item>
		<title>Object Detection</title>
		<link>http://tc.eserver.org/27295.html</link>
		<guid>http://tc.eserver.org/27295.html</guid>
		<description>The pace of new browser releases may be slower than it was in the early days, but developers must still confront a bemusing array of browser versions and brands that support some JavaScript features but not others. To combat the problem, scripters commonly provide two or more code branches so that a browser follows an execution path containing statements that it supports. Browser sniffing — the task of inspecting navigator object properties for version information — has become largely unmanageable given the browser version permutations available today. This article presents details on an alternative solution — object detection — that frees JavaScript developers from most of this versioning mess.</description>
	</item>
	<item>
		<title>Plug-In Detection</title>
		<link>http://tc.eserver.org/27306.html</link>
		<guid>http://tc.eserver.org/27306.html</guid>
		<description>Since there are clearly times when it makes sense to use a plug-in, the question arises of how to deal with those who don’t have the required plug-in installed. As Web developers, we have several choices. One option is to do nothing, simply serving the plug-in-dependent content. The trouble is that those that don’t have the required plug-in will get a rather disturbing page with a broken plug-in icon where your beautiful multimedia should be. Another option is to give visitors a choice between the plug-in version and the static HTML version of each page. Sometimes this may be the best choice, since it gives your visitors control over their experience. There are two problems, however. First of all, the choice itself interrupts a visitor’s experience of the site. Second, it requires them to know what plug-ins they have installed. But why should they need to know? Many users don’t know a plug-in from a spark plug?&#xD;&#xD;The final and often best option, the one this script is designed to help with, is to check to see if each visitor has a given plug-in. If they do, you can go ahead and serve them the page with the plug-in embedded. </description>
	</item>
	<item>
		<title>Remote Scripting with IFRAME</title>
		<link>http://tc.eserver.org/27294.html</link>
		<guid>http://tc.eserver.org/27294.html</guid>
		<description>As web sites become more and more like traditional applications, the call-response-reload model used in HTTP transactions becomes increasingly cumbersome. Instead of delivering a single dynamic page, the DHTML or JavaScript developer must create a series of separate pages. The flow of the application is interrupted by page reloads whenever the client communicates with the server. Remote scripting provides a solution to this problem, easing development of complex JavaScript applications, and providing a better experience for the end user.</description>
	</item>
	<item>
		<title>Supporting Three Event Models at Once</title>
		<link>http://tc.eserver.org/27296.html</link>
		<guid>http://tc.eserver.org/27296.html</guid>
		<description>Events make the client-side JavaScript world go ‘round. After a Web page loads, the only way a script can run is in response to a system or user action. While simple events have been part of the JavaScript vocabulary since the first scriptable browsers, more recent browsers implement robust event models that allow scripts to process events more intelligently. The problem, however, is that in order to support a wide range of browsers you must contend with multiple advanced event models. Three, to be exact.</description>
	</item>
	<item>
		<title>Using SOAP with PHP</title>
		<link>http://tc.eserver.org/27291.html</link>
		<guid>http://tc.eserver.org/27291.html</guid>
		<description>SOAP, the Simple Object Access Protocol, is the powerhouse of web services. It&apos;s a highly adaptable, object-oriented protocol that exists in over 80 implementations on every popular platform, including AppleScript, JavaScript, and Cocoa. It provides a flexible communication layer between applications, regardless of platform and location. As long as they both speak SOAP, a PHP-based web application can ask a C++ database application on another continent to look up the price of a book and have the answer right away.</description>
	</item>
	<item>
		<title>Vertical Sizing in CSS</title>
		<link>http://tc.eserver.org/27304.html</link>
		<guid>http://tc.eserver.org/27304.html</guid>
		<description>This article covers vertical sizing and shows how to determine the height of elements with CSS. Once you’ve mastered both height and width, you should be well on your way to effectively using CSS.</description>
	</item>
	<item>
		<title>Web Page Development: Best Practices</title>
		<link>http://tc.eserver.org/27305.html</link>
		<guid>http://tc.eserver.org/27305.html</guid>
		<description>This article gives some practical hints on how to create standards-conforming websites, and to work around some of issues that will arise for Explorer for Windows. Before you start coding your website you must make a few decisions—which DOCTYPE do you use? Do you use pure CSS, or CSS with Minimal Tables? We&apos;ll discuss these topics, and then go into some design guidelines and issues to consider with XHTML and CSS.</description>
	</item>
	<item>
		<title>WebObjects</title>
		<link>http://tc.eserver.org/27308.html</link>
		<guid>http://tc.eserver.org/27308.html</guid>
		<description>WebObjects is Apple&apos;s suite of tools and object-oriented frameworks for creating and deploying scalable, reusable web and Java applications for the Internet and intranets. WebObjects supports the development, deployment, and extension of standards-based web services without the need to write low-level SOAP, XML or WSDL code. Tools enable code-free generation, configuration, and testing of web services from existing data assets.</description>
	</item>
	<item>
		<title>XML Transformations with CSS and DOM</title>
		<link>http://tc.eserver.org/27290.html</link>
		<guid>http://tc.eserver.org/27290.html</guid>
		<description>Mozilla permits XML to be rendered in the browser with CSS, and manipulated with the DOM. This is a real boon to those of us eager to experiment with XML transformations (both visual and structural) without having to delve into unfamiliar technologies such as XPath, the verbose traversal language of XSLT. If you’re already familiar with CSS and DOM, you’re more than halfway to achieving XML transformations in Mozilla.</description>
	</item>
	<item>
		<title>Apple Human Interface Guidelines</title>
		<link>http://tc.eserver.org/21743.html</link>
		<guid>http://tc.eserver.org/21743.html</guid>
		<description>These guidelines are designed to assist you in developing products that provide Mac OS X users with a consistent visual and behavioral experience across applications and the operating system. </description>
	</item>
	<item>
		<title>User Experience</title>
		<link>http://tc.eserver.org/21742.html</link>
		<guid>http://tc.eserver.org/21742.html</guid>
		<description>This document outlines typical areas of concern when porting a Microsoft Windows application to Mac OS X, and provides guidance for transitioning to the Mac OS X UI.</description>
	</item>
	<item>
		<title>Apple Publications Style Guide (2003)</title>
		<link>http://tc.eserver.org/19711.html</link>
		<guid>http://tc.eserver.org/19711.html</guid>
		<description>The May 2003 edition of the standard reference for Apple publications.</description>
	</item>
	<item>
		<title>Human Interface Design Principles</title>
		<link>http://tc.eserver.org/19004.html</link>
		<guid>http://tc.eserver.org/19004.html</guid>
		<description>This section provides a theoretical base for the wealth of practical information on implementing the Aqua interface elements presented in the rest of this book.&#xD;&#xD;You’ll undoubtedly find that you can’t design in accordance with all of the principles all the time. In those situations, you’ll have to make decisions based on which principle or set of principles is most important in the context of the task you’re solving. User testing is often an excellent way to decide between conflicting principles in a particular context.&#xD;</description>
	</item>
	<item>
		<title>Macintosh OS X: Aqua Human Interface Guidelines</title>
		<link>http://tc.eserver.org/19003.html</link>
		<guid>http://tc.eserver.org/19003.html</guid>
		<description>This document, which covers features up to Mac OS X version 10.2, describes what you need to do to design your application for Aqua. Primarily intended for Carbon and Cocoa developers who want their applications to look right and behave correctly in Mac OS X, these guidelines provide examples of how to use Aqua interface elements. Java application developers will also find these guidelines useful.</description>
	</item>
	<item>
		<title>International Technologies</title>
		<link>http://tc.eserver.org/18488.html</link>
		<guid>http://tc.eserver.org/18488.html</guid>
		<description>International technologies describes a collection of Macintosh technologies and resources developers can use to internationalize or localize their applications. Internationalization is the process of readying your software to handle different text systems and locale-specific features. Localization is the process of translating an application&apos;s text elements, and adjusting the user interface for a specific language or region.&#xD;</description>
	</item>
	<item>
		<title>Online Documentation and Online Help</title>
		<link>http://tc.eserver.org/14810.html</link>
		<guid>http://tc.eserver.org/14810.html</guid>
		<description>A bibliography that presents major works on topics discussed in the book &lt;i&gt;Inside Macintosh: Macintosh Human Interface Guidelines&lt;/i&gt;.</description>
	</item>
	<item>
		<title>Strategies for Producing Browser-Based Technical Documentation</title>
		<link>http://tc.eserver.org/14811.html</link>
		<guid>http://tc.eserver.org/14811.html</guid>
		<description>This Technical Note attempts to provide a few good strategies for resolving some of the issues around producing and viewing Web-based technical documentation.&#xD;The Note may be useful for engineers, technical writers and&#xD;content producers who must wrestle with issues of producing&#xD;documents such as ReadMe files, Release Notes, technical&#xD;articles, and other forms of technical communication that&#xD;land on the Web.</description>
	</item>
	<item>
		<title>Mac OS Help</title>
		<link>http://tc.eserver.org/13781.html</link>
		<guid>http://tc.eserver.org/13781.html</guid>
		<description>Online help facilities are an important part of any software product in today&apos;s marketplace. Apple has a number of technologies specifically designed for providing both convenient to use and easy to understand online help. Interested developers can take advantage of these technologies and use them to build online help facilities into their own products. This page provides an overview of the current Apple help technologies along with links to other related resources.</description>
	</item>
	<item>
		<title>Macintosh OS 8 Human Interface Guidelines</title>
		<link>http://tc.eserver.org/13584.html</link>
		<guid>http://tc.eserver.org/13584.html</guid>
		<description>This document describes the additions and changes to Macintosh Human Interface Guidelines related to the release of Mac OS 8. Specifically, it presents guidelines for taking advantage of the Mac OS platinum appearance and the Appearance Manager. This document does not replace Macintosh Human Interface Guidelines.</description>
	</item>
	<item>
		<title>Apple Publications Style Guide (2003)</title>
		<link>http://tc.eserver.org/13518.html</link>
		<guid>http://tc.eserver.org/13518.html</guid>
		<description>An updated version of the style guide used by writers and editors in Apple publications groups.</description>
	</item>
	<item>
		<title>Apple Guide Complete: Designing and Developing Onscreen Assistance</title>
		<link>http://tc.eserver.org/10701.html</link>
		<guid>http://tc.eserver.org/10701.html</guid>
		<description>If you&apos;ve been waiting to give your users more than just onscreen reference information, now you can with Apple Guide, Apple Computer&apos;s innovative help delivery system. With Apple Guide, you can produce guide files that actually lead users, step by step, through complex tasks and concepts. If you want to provide task-oriented, context-specific instructions, Apple Guide gives you the ease and flexibility to do so. You&apos;ll learn about the complete cycle of designing, scripting, and coding guide files in the four parts of this book.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Apple_Inc..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>