DOCSLIB.ORG

Adobe Systems, Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Adobe Systems, Inc April 30, 2004 Position on Web Applications and Compound Documents Jon Ferraiolo Adobe Systems, Inc. Summary Position • Any new activity should proceed systematically and start with identification of prior related work, identification of use cases, and a statement of requirements. • Existing W3C specifications already contain most of the protocol definitions that are necessary to address industry requirements in both areas, but there are gaps. Instead of launching major new language definition efforts around either topic, we recommend that the W3C first look at existing W3C specifications, in-process W3C work, and related best-in-class technology efforts that have proven successful in industry. Attempt to codify and integrate what exists today, accept precedent whenever possible, and do not attempt technology invention via standards committee. • Rich-client web applications often require a combination of multiple W3C languages, particularly XHTML and SVG.. • A key focus must be the mobile industry and emerging alternate devices. The mobile industry, particularly the low end, is still young and market dynamics promote standards adoption. Within the mobile industry, there is strong demand for both web applications and compound documents. The first W3C deliverables in these areas must address the requirements of low-end cell phones and other emerging devices. • For web applications, the W3C should leverage its existing standards (e.g., DOM, XForms, XHTML, SVG) and all of the applications-related features that are in SVG 1.2, particularly RCC/XBL, the features on the “Window” interface, and the SVG Tiny uDOM that has been developed in conjunction with J2ME and JCP/JSR226. • For compound documents, the W3C should take a low-ambition approach and codify the rules for existing loose-cou- pling approaches to compound documents (e.g., <html:object>, <svg:foreignObject>, <fo:foreignObject>). The W3C should not attempt to build new content standards or augment existing content standards in order to work around the lack of a packaging standard. 1/4 Background and Experience Background and Experience Adobe has institutional expertise and experience in the design and implementation of document formats for desktop appli- cations (i.e., FrameMaker, InDesign), server tools, and widely deployed clients. We have adopted XML throughout our product line. We develop tools, servers and clients to support both web applications and compound documents. PDF, par- ticularly with its Intelligent Document features, is a web application format and a compound document format. Table 1, below, describes some of Adobe’s products and technologies as they relate to web applications and compound documents. Product or Technology Description Adobe Acrobat Supports web service invocation, export of XML from PDF content, XMP metadata. Adobe Designer Recently announced beta program. For creating XML-cen- tric forms applications and intelligent documents targeting PDF or HTML delivery. When using PDF, PDF becomes a compound document format and a web applications format. Adobe Document Server Document generation services. Formats a combination of XSL-FO and SVG into PDF. Provides web service inter- face. Adobe Forms Server Forms automation services. Supports XML form data. Pro- vides web service interface. Adobe FrameMaker A WYSIWYG XML authoring and publishing solution. Generates templates that support both XHTML and SVG and which feed into Adobe Document Server. Adobe GoLive Web application designer. Includes XML editing support. Supports XHTML with embedded SVG. Strong mobile fea- ture set, including MMS. Adobe Graphics Server Graphics creation and manipulation services. Renders SVG as raster or PDF. Adobe Illustrator Vector-based editing product. Supports SVG import and export. Generates SVG with embedded XHTML-like text flows that feed into Adobe’s server products. Adobe InDesign Desktop publishing product. Supports import and export XML content. Adobe PDF Open specification portable document format which is also (via subsets) an approved official standard. Supports XML form data, XMP metadata, and XDP packaging. Adobe SVG Viewer Free SVG renderer for Windows and Macintosh browsers. The version 6 Technology Preview release supports embed- ded XHTML and RCC support (predecessor for XBL). XMP XML- and RDF-based metadata technology that allows metadata to be embedded within various file formats. Freely available specification and SDK. Partial list of Adobe’s XML-enabled products and technologies 2/4 Position on Web Applications and Compound Documents Start with use cases and requirements Start with use cases and requirements Any W3C activity in these areas should proceed in a systematic manner and start with identification of use cases, identifi- cation and collection of prior work, and a statement of requirements. Among the prior work which should be studied, the W3C should review the findings of the ui-tech task force from a couple of years ago. Requirements should take into account issues such as accessibility, multi-modal, and different types of devices, particularly mobile devices, but also take servers into account, where XSL-FO+SVG plays a key role as a common example for compound documents. The W3C should focus on codifying and integrating what exists today Instead of launching major new language definition efforts around either topic, we recommend that the W3C first look at existing W3C specifications, in-process W3C work, and related best-in-class technology efforts that have proven success- ful in industry. Attempt to codify and integrate what exists today, accept precedent whenever possible, and do not attempt technology invention via standards committees. As a general rule, avoid inventing new markup languages; instead build on specifications and features that already exist. In fact, often it might turn out that it makes sense to “shrink” existing specifications by consolidating common features of different markup languages into shared namespaces, versus defining new markup. Rich-client web applications require both XHTML and SVG Adobe has considerable industry experience from its PDF, ePaper, Intelligent Document and SVG initatives, and we see strong industry demand for what analysts call “rich client” solutions. To a large extent, Adobe’s Intelligent Document Platform is a major strategy push into the rich client arena leveraging PDF, which we have done in response to strong industry demand. A large number of developers are also leveraging SVG for rich web applications. Within the SVG developer community, the largest set of requested enhancements to the SVG language are those that support web applica- tions, where SVG is used as the graphically rich front-end to data-driven applications. Among the most requested SVG enhancements are UI widgets, adjustable layout, and text flows, all of which are found in XHTML. Usually, the preferred solution for web applications involves a combination of technologies. For applications with reflow- able content, XTHML and CSS are often the appropriate standards-based technologies. For applications involving vector graphics or rich user interfaces not possible with XHTML and CSS, SVG is often the appropriate standards-based tech- nology. Very often, the solution requires a combination of both; in other words, the total solution requires some notion of a compound document. Strong focus on mobile requirements A key focus must be the mobile industry and emerging alternate devices. The mobile industry, particularly the low end, is still young and market dynamics promote standards adoption. There is strong demand in the mobile world for both web applications and compound documents, and a good set of W3C mobile standards will promote new mobile solutions. The first W3C deliverables in these areas must address the requirements of low-end cell phones and other emerging devices. The most important focus should be integrating XHTML-Basic, SVG-Tiny 1.2 (which includes major subset of SMIL- Basic), CSS-Mobile, a mobile DOM (building on the SVG Tiny 1.2 DOM that is being developed in conjunction with the Position on Web Applications and Compound Documents 3/4 Web applications JCP/JSR226). Of course, any solution needs to include XHTML. The SVG Tiny module (with all of its SMIL features) is also critical because of the importance of multimedia, infotainment, and location-based services on mobile devices. To meet the requirements for rich user interfaces and mobile web applications, some subset of XBL and XForms probably also will be needed. Web applications For web applications, the W3C should leverage its existing standards (e.g., DOM, XForms, XHTML, SVG) and all of the applications-related features that are in SVG 1.2, particularly RCC/XBL, the features on the “Window” interface, and the SVG Tiny uDOM that has been developed in conjunction with J2ME and JCP/JSR226. XBL (fka RCC) provides the low-level framework for custom rich-client user interfaces and provides the mechansim for mapping XForms controls into SVG presentation. All modern application systems include an extensibility UI component framework. An early version of XBL already ships with Mozilla. Microsoft’s Longhorn OS includes the VisualTree facil- ity, which is very similar to XBL. Something like XBL is a necessity for web applications. Modern web applications need to communicate with servers and other clients. The Window interface in SVG 1.2 is the appropriate low-level starting point for delivering this critical technology. SOAP and Web Services facilities can
Load more

Recommended publications
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • Security Analysis of Firefox Webextensions
    6.857: Computer and Network Security Due: May 16, 2018 Security Analysis of Firefox WebExtensions Srilaya Bhavaraju, Tara Smith, Benny Zhang srilayab, tsmith12, felicity Abstract With the deprecation of Legacy addons, Mozilla recently introduced the WebExtensions API for the development of Firefox browser extensions. WebExtensions was designed for cross-browser compatibility and in response to several issues in the legacy addon model. We performed a security analysis of the new WebExtensions model. The goal of this paper is to analyze how well WebExtensions responds to threats in the previous legacy model as well as identify any potential vulnerabilities in the new model. 1 Introduction Firefox release 57, otherwise known as Firefox Quantum, brings a large overhaul to the open-source web browser. Major changes with this release include the deprecation of its initial XUL/XPCOM/XBL extensions API to shift to its own WebExtensions API. This WebExtensions API is currently in use by both Google Chrome and Opera, but Firefox distinguishes itself with further restrictions and additional functionalities. Mozilla’s goals with the new extension API is to support cross-browser extension development, as well as offer greater security than the XPCOM API. Our goal in this paper is to analyze how well the WebExtensions model responds to the vulnerabilities present in legacy addons and discuss any potential vulnerabilities in the new model. We present the old security model of Firefox extensions and examine the new model by looking at the structure, permissions model, and extension review process. We then identify various threats and attacks that may occur or have occurred before moving onto recommendations.
    [Show full text]
  • SGML As a Framework for Digital Preservation and Access. INSTITUTION Commission on Preservation and Access, Washington, DC
    DOCUMENT RESUME ED 417 748 IR 056 976 AUTHOR Coleman, James; Willis, Don TITLE SGML as a Framework for Digital Preservation and Access. INSTITUTION Commission on Preservation and Access, Washington, DC. ISBN ISBN-1-887334-54-8 PUB DATE 1997-07-00 NOTE 55p. AVAILABLE FROM Commission on Preservation and Access, A Program of the Council on Library and Information Resources, 1400 16th Street, NW, Suite 740, Washington, DC 20036-2217 ($20). PUB TYPE Reports Evaluative (142) EDRS PRICE MF01/PC03 Plus Postage. DESCRIPTORS *Access to Information; Computer Oriented Programs; *Electronic Libraries; *Information Retrieval; Library Automation; Online Catalogs; *Preservation; Standards IDENTIFIERS Digital Technology; *SGML ABSTRACT This report explores the suitability of Standard Generalized Markup Language (SGML) as a framework for building, managing, and providing access to digital libraries, with special emphasis on preservation and access issues. SGML is an international standard (ISO 8879) designed to promote text interchange. It is used to define markup languages, which can then encode the logical structure and content of any so-defined document. The connection between SGML and the traditional concerns of preservation and access may not be immediately apparent, but the use of descriptive markup tools such as SGML is crucial to the quality and long-term accessibility of digitized materials. Beginning with a general exploration of digital formats for preservation and access, the report provides a staged technical tutorial on the features and uses of SGML. The tutorial covers SGML and related standards, SGML Document Type Definitions in current use, and related projects now under development. A tiered metadata model is described that could incorporate SGML along with other standards to facilitate discovery and retrieval of digital documents.
    [Show full text]
  • Putting DDI in the Driver's Seat
    Putting DDI in the driver’s seat Using Metadata to control data capture Samuel Spencer Australian Bureau of Statistics 2010: XForms and DDI January: XForms transform demonstrated within ABS June: XForms live-demo at IASSIST 2010 July: XForms research put on hold October: Commercial Census web-form tool investigated ABS DDI Data Collection Projects Internet Activity Survey Agricultural Census Questionnaire Design Tool (QDT) Internet Activity Survey Then: Survey used in DDI/XForms research eForms solution using ABS developed technology Custom tool creates XForms, rendered using Orbeon Internet Activity Survey Then: Survey used in DDI/XForms research eForms solution using ABS developed technology Custom tool creates XForms, rendered using Orbeon Now: Candidate for migration to custom IBM web-form solution Agricultural Census Now: Currently running on IBM web-form solution Forms displayed using AJAX which interprets proprietary hand-crafted XML Agricultural Census Now: Currently running on IBM web-form solution Forms displayed using AJAX which interprets proprietary hand-crafted XML Future: Research into DDI to XML transforms Questionnaire Design Tool Then: Online app for questionnaire metadata management Manages creation of Blaise and paper forms Uses ABS-built proprietary XML (QDT-ML) Now: Investigations into replacing QDT-ML with DDI Research into using QDT to create web-forms How can it made simpler? The XForms standard describes a structured format for capturing form questions, control structures and complex data structures needed for accurate information capture. However, to be useful it needs to be transformed, as its not able to be displayed natively in current generation browsers. The DDI 3.0 standard describes a structured format for capturing form questions, control structures and complex data structures needed for accurate information capture.
    [Show full text]
  • Cross Site Scripting Attacks Xss Exploits and Defense.Pdf
    436_XSS_FM.qxd 4/20/07 1:18 PM Page ii 436_XSS_FM.qxd 4/20/07 1:18 PM Page i Visit us at www.syngress.com Syngress is committed to publishing high-quality books for IT Professionals and deliv- ering those books in media and formats that fit the demands of our customers. We are also committed to extending the utility of the book you purchase via additional mate- rials available from our Web site. SOLUTIONS WEB SITE To register your book, visit www.syngress.com/solutions. Once registered, you can access our [email protected] Web pages. There you may find an assortment of value- added features such as free e-books related to the topic of this book, URLs of related Web sites, FAQs from the book, corrections, and any updates from the author(s). ULTIMATE CDs Our Ultimate CD product line offers our readers budget-conscious compilations of some of our best-selling backlist titles in Adobe PDF form. These CDs are the perfect way to extend your reference library on key topics pertaining to your area of expertise, including Cisco Engineering, Microsoft Windows System Administration, CyberCrime Investigation, Open Source Security, and Firewall Configuration, to name a few. DOWNLOADABLE E-BOOKS For readers who can’t wait for hard copy, we offer most of our titles in downloadable Adobe PDF form. These e-books are often available weeks before hard copies, and are priced affordably. SYNGRESS OUTLET Our outlet store at syngress.com features overstocked, out-of-print, or slightly hurt books at significant savings. SITE LICENSING Syngress has a well-established program for site licensing our e-books onto servers in corporations, educational institutions, and large organizations.
    [Show full text]
  • Jørn Klungsøyr & Remi Andre Valvik (University of Bergen)
    DESIGN www.openXdata.org COLLECT www.openxdata.org MANAGE DESIGN Video tutorials available at: doc.openXdata.org www.openXdata.org [email protected] Usable data for informed decision making Jørn Klungsøyr ([email protected]) Remi Andre Valvik ([email protected]) Usable data for informed decision making Security Ease of Use Costs Scalability Integration Topics of this presentation • Functionalities • Ease of use • Change management • Security • Integration • Costs • Scalability • Open source community • Demonstrations Functionalities Design – Collect - Manage Design • Design complex forms in graphical interface • Supported question types include e.g.: Text, Numbers, Date, Time, Single / Multi-select, Multimedia, Geo tagging • Define skip logic & answer validation criteria Collect – Mobile phones <30$ Structured SMS – manually coded forms – for any phone eCollect – Android/iPhone/Pads/Laptops eCollect is a mini version openXdata web interface. • Stores data locally for offline functionality. • Users use regular browsers. • Android packag for native features like camera. Collect – Android with ODK-collect / JR Users can use ODK-collect due to a OpenROSA / JavaROSA standards API plugin. Collect - Web • Web-based forms can be accessed through desktop computer, laptop, netbook, pads/tabs and smartphones with access to the internet and JavaScript support Manage • Own your data - host on your own servers • Define roles for different types of users (e.g. administrator, study manager, mobile data collector) • Export data to CSV or direct to a relational database • Manage data and forms using a standard web-browser Ease of use Case reports from MoTeCH implementations MoTeCH – summary from interviews • Initial assumption to use structured SMS by health workers to create and update medical records using their own phones using "free" SMS.
    [Show full text]
  • Design Decisions for a Structured Front End to LATEX Documents
    Design decisions for a structured front end to LATEX documents Barry MacKichan MacKichan Software, Inc. barry dot mackichan at mackichan dot com 1 Logical design Procedural Scientific WorkPlace and Scientific Word are word processors that have been designed from the start to TeX handle mathematics gracefully. Their design philos- PostScript ophy is descended from Brian Reid’s Scribe,1 which emphasized the separation of content from form and 2 was also an inspiration for LATEX. This logical de- sign philosophy holds that the author of a document should concern him- or herself with the content of the document, and with identifying the role that each bit of text plays, such as a header, a footnote, Structured or a quote. The details of formatting should be ig- Unstructured nored by the author, and handled instead by a pre- defined (or custom) style specification. LaTeX There are several very compelling reasons for the separation of content from form. • The expertise of the author is in the content; PDF the expertise of the publisher is in the presen- tation. Declarative • Worrying and fussing about the presentation is wasted effort when done by the author, since Thus, PostScript is a powerful programming the publisher will impose its own formatting on language, but it was later supplemented by PDF, the paper. which is not a programming language, but instead contains declarations of where individual characters • Applying formatting algorithmically is the eas- are placed. PDF is not structured, but Adobe has iest way to assure consistency of presentation. been adding a structural overlay. LATEX is quite • When a document is re-purposed it can be re- structured, but it still contains visible signs of the formatted automatically for its new purpose.
    [Show full text]
  • Interactive Topographic Web Mapping Using Scalable Vector Graphics
    University of Nebraska at Omaha DigitalCommons@UNO Student Work 12-1-2003 Interactive topographic web mapping using scalable vector graphics Peter Pavlicko University of Nebraska at Omaha Follow this and additional works at: https://digitalcommons.unomaha.edu/studentwork Recommended Citation Pavlicko, Peter, "Interactive topographic web mapping using scalable vector graphics" (2003). Student Work. 589. https://digitalcommons.unomaha.edu/studentwork/589 This Thesis is brought to you for free and open access by DigitalCommons@UNO. It has been accepted for inclusion in Student Work by an authorized administrator of DigitalCommons@UNO. For more information, please contact [email protected]. INTERACTIVE TOPOGRAPHIC WEB MAPPING USING SCALABLE VECTOR GRAPHICS A Thesis Presented to the Department of Geography-Geology and the Faculty of the Graduate College University of Nebraska in Partial Fulfillment of the Requirements for the Degree Master of Arts University of Nebraska at Omaha by Peter Pavlicko December, 2003 UMI Number: EP73227 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. Dissertation WWisMng UMI EP73227 Published by ProQuest LLC (2015). Copyright in the Dissertation held by the Author. Microform Edition © ProQuest LLC. All rights reserved. This work is protected against unauthorized copying under Title 17, United States Code ProQuest LLC. 789 East Eisenhower Parkway P.O. Box 1346 Ann Arbor, Ml 48106-1346 THESIS ACCEPTANCE Acceptance for the faculty of the Graduate College, University of Nebraska, in Partial fulfillment of the requirements for the degree Master of Arts University of Nebraska Omaha Committee ----------- Uf.A [JL___ Chairperson.
    [Show full text]
  • Microsoft, Adobe & W3C to Shake up Electronic Forms Market
    Vol. 11, No, 8 October 2003 www.gilbane.com Published by: Bluebill Advisors, Inc. 763 Massachusetts Ave. Cambridge, MA 02139 USA (617) 497.9443 Fax (617) 497.5256 www.bluebilladvisors.com Editor: Frank Gilbane [email protected] (617) 497.9443 Content Technology Works! Editors Emeriti: Tim Bray [email protected] (604) 708.9592 MICROSOFT, ADOBE & XFORMS TO David Weinberger [email protected] (617) 738.8323 SHAKE UP ELECTRONIC FORMS MARKET Senior Editors: Sebastian Holst [email protected] Our title this month reads like a news headline on purpose. There are a number Bill Trippe [email protected] of new, and upcoming, developments in electronic forms (eForms) technology (617) 497.9443 that should be grabbing your attention. Some of these are of major importance Recent Contributors: on their own, but taken together, they signal the start of a major improvement Kathleen Reidy in businesses’ ability to easily collect, integrate, and process information. [email protected] Bob Doyle [email protected] “Electronic forms” have been around for years, but the term refers to a wide variety of technologies – from scanned image applications to HTML forms – Production Assistant: Sarah G. Dionne that are not at all similar and far from equal in their ability to accelerate and [email protected] smooth business processes. What eForm technology has shared is: a level of (617) 497.9443 difficulty that kept it out of the reach of office professionals who were com- Subscriptions: fortable enough with documents and spreadsheets, but scared-off by forms, [email protected] (617) 497.9443 and proprietary data formats that made information integration costly and complex.
    [Show full text]
  • Cumulus User Guide
    Cumulus 8.6 Client User Guide Copyright 2012, Canto GmbH. All rights reserved. Canto, the Canto logo, the Cumulus logo, and Cumulus are registered trade- marks of Canto, registered in the U.S. and other countries. Apple, Mac, Macintosh and QuickTime are registered trademarks of Apple Com- puter, Inc. , registered in the U.S. and other countries. Microsoft, Windows, Windows Vista, and Windows NT are either trademarks or registered trademarks of the Microsoft Corporation in the U.S. and other coun- tries. Other third-party product and company names mentioned in this document are trademarks or registered trademarks of their respective holders. Feedback? Tell us what you think about this manual. We welcome all of your comments and suggestions. Please e-mail comments to [email protected] or via fax at +49-30-390 48 555. CU-WC-861-MN-Z-1 3 Table of Contents Renaming Records . 27 Intro 7 Editing a Record’s Category Assignments . 28 Things You Can Do with Records . 28 Cumulus . 8 Things You Can Do with Assets . 29 This User Guide . 8 Categories . 29 Category Types. 30 Organization. 8 Creating Categories . 31 Cross-Platform Issues . 9 Custom Ordering of Categories. 32 User Interface Item Conventions. 9 Category Fields. 33 Cumulus Step by Step. 9 Category Information Window. 33 Your Experience . 9 Editing Category Information . 33 Categories and Auto-cataloging . 34 Understanding Cumulus . 10 Individual Category Tabs (optional) . 35 Assets . 10 Things You Can Do with Categories. 35 Catalogs . 10 Collections . 10 Information Window. 36 Categories . 10 • THE INFORMATION WINDOW....................................................................... 36 Records . 11 Sets and Templates .
    [Show full text]
  • Jump Start Html5 by Tiffany B
    Summary of Contents Preface . xix 1. Basics: What is HTML5? . 1 2. Basics: The Anatomy of HTML5 . 7 3. Basics: Structuring Documents . 17 4. Basics: HTML5 Forms . 33 5. Basics: Multimedia, Audio and Video . 51 6. Multimedia: Preparing Your Media . 59 7. Multimedia: Using Native HTML5 Audio . 69 8. Multimedia: Using Native HTML5 Video . 77 9. Multimedia: The source Element . 87 10. Mutimedia: The track Element . 93 11. Multimedia: Scripting Media Players . 111 12. Canvas & SVG: An Introduction to Canvas . 123 13. Canvas & SVG: Canvas Basics . 127 14. Canvas & SVG: Handling Non-supporting Browsers . 137 15. Canvas & SVG: Canvas Gradients . 139 16. Canvas & SVG: Canvas Images and Videos . 145 17. Canvas & SVG: An Introduction to SVG . 149 18. Canvas & SVG: Using SVG . 159 19. Canvas & SVG: SVG Bézier Curves . 163 20. Canvas & SVG: SVG Filter Effects . 169 21. Canvas & SVG: Canvas or SVG? . 175 22. Offline Apps: Detecting When the User Is Connected . 179 23. Offline Apps: Application Cache . 185 24. Offline Apps: Web Storage . 197 25. Offline Apps: Storing Data With Client-side Databases . 215 26. APIs: Overview . 233 27. APIs: Web Workers . 239 28. APIs: The Geolocation API . 249 29. APIs: Server Sent Events . 255 30. APIs: The WebSocket API . 263 31. APIs: The Cross-document Messaging API . 269 JUMP START HTML5 BY TIFFANY B. BROWN KERRY BUTTERS SANDEEP PANDA iv Jump Start HTML5 by Tiffany B. Brown, Kerry Butters, and Sandeep Panda Copyright © 2014 SitePoint Pty. Ltd. Product Manager: Simon Mackie English Editor: Paul Fitzpatrick Technical Editor: Craig Buckler Cover Designer: Alex Walker Notice of Rights All rights reserved.
    [Show full text]