DOCSLIB.ORG

Opendoc Class Reference

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Opendoc Class Reference OpenDoc Class Reference For the Mac OS Addison-Wesley Publishing Company Reading, Massachusetts Menlo Park, California New York Don Mills, Ontario Wokingham, England Amsterdam Bonn Sydney Singapore Tokyo Madrid San Juan Paris Seoul Milan Mexico City Taipei This document was created with FrameMaker 4.0.4 Apple Computer, Inc. Apple, the Apple logo, AppleScript, ORIGINAL RETAIL PURCHASE OF 1995 Apple Computer, Inc. Bento, LaserWriter, Macintosh, THIS PRODUCT. All rights reserved. OpenDoc, and QuickTime are Even though Apple has reviewed this No part of this publication may be trademarks of Apple Computer, Inc., manual, APPLE MAKES NO reproduced, stored in a retrieval registered in the United States and WARRANTY OR REPRESENTATION, system, or transmitted, in any form other countries. EITHER EXPRESS OR IMPLIED, WITH or by any means, mechanical, Apple Press, the Apple Press RESPECT TO THIS MANUAL, ITS electronic, photocopying, recording, signature, Finder, Mac, and QUALITY, ACCURACY, or otherwise, without prior written QuickDraw are trademarks of Apple MERCHANTABILITY, OR FITNESS permission of Apple Computer, Inc., Computer, Inc. FOR A PARTICULAR PURPOSE. AS A except to make a backup copy of Adobe, Acrobat, and PostScript are RESULT, THIS MANUAL IS SOLD “AS any documentation provided on trademarks of Adobe Systems IS,” AND YOU, THE PURCHASER, CD-ROM. Incorporated or its subsidiaries and ARE ASSUMING THE ENTIRE RISK The Apple logo is a trademark of may be registered in certain AS TO ITS QUALITY AND Apple Computer, Inc. jurisdictions. ACCURACY. Use of the “keyboard” Apple logo Helvetica and Palatino are IN NO EVENT WILL APPLE BE (Option-Shift-K) for commercial registered trademarks of LIABLE FOR DIRECT, INDIRECT, purposes without the prior written Linotype-Hell AG and/or its SPECIAL, INCIDENTAL, OR consent of Apple may constitute subsidiaries. CONSEQUENTIAL DAMAGES trademark infringement and unfair ITC Zapf Dingbats is a registered RESULTING FROM ANY DEFECT OR competition in violation of federal trademark of International Typeface INACCURACY IN THIS MANUAL, and state laws. Corporation. even if advised of the possibility of such damages. No licenses, express or implied, are QuickView is licensed from Altura granted with respect to any of the Software, Inc. THE WARRANTY AND REMEDIES technology described in this book. SOM, SOMobjects, and System SET FORTH ABOVE ARE EXCLUSIVE Apple retains all intellectual AND IN LIEU OF ALL OTHERS, ORAL property rights associated with the Object Model are licensed trademarks of IBM Corporation. OR WRITTEN, EXPRESS OR IMPLIED. technology described in this book. No Apple dealer, agent, or employee is This book is intended to assist Simultaneously published in the authorized to make any modification, application developers to develop United States and Canada. extension, or addition to this warranty. applications only for Apple-labeled LIMITED WARRANTY ON MEDIA Some states do not allow the exclusion or Apple-licensed computers. AND REPLACEMENT Every effort has been made to or limitation of implied warranties or ALL IMPLIED WARRANTIES ON ensure that the information in this liability for incidental or consequential THIS MANUAL, INCLUDING manual is accurate. Apple is not damages, so the above limitation or IMPLIED WARRANTIES OF responsible for typographical errors. exclusion may not apply to you. This MERCHANTABILITY AND FITNESS warranty gives you specific legal rights, Apple Computer, Inc. FOR A PARTICULAR PURPOSE, ARE and you may also have other rights 1 Infinite Loop LIMITED IN DURATION TO NINETY which vary from state to state. Cupertino, CA 95014 (90) DAYS FROM THE DATE OF THE 408-996-1010 This document was created with FrameMaker 4.0.4 Contents Preface About This Book 29 Organization 29 Class Descriptions 30 Method Descriptions 31 OpenDoc and SOMobjects 32 Conventions Used in This Book 34 Component Integration Laboratories 35 Part 1 Classes and Methods 37 ODAddressDesc 39 InitODAddressDesc 40 ODAppleEvent 41 InitODAppleEvent 42 ODArbitrator 43 AcquireFocusOwner 45 CreateFocusSet 46 CreateOwnerIterator 47 GetFocusModule 48 IsFocusExclusive 49 IsFocusRegistered 50 RegisterFocus 50 RelinquishFocus 51 RelinquishFocusSet 52 RequestFocus 53 RequestFocusSet 54 3 This document was created with FrameMaker 4.0.4 TransferFocus 56 TransferFocusSet 57 UnregisterFocus 58 ODBinding 59 ChooseEditorForPart 60 ODCanvas 61 AcquireBiasTransform 65 AcquireOwner 66 AcquireUpdateShape 67 GetFacet 67 GetGXViewport 68 GetPlatformCanvas 69 GetPlatformPrintJob 70 GetQDPort 71 HasPlatformCanvas 72 HasPlatformPrintJob 73 Invalidate 74 IsDynamic 74 IsOffscreen 75 ResetUpdateShape 75 SetBiasTransform 76 SetFacet 77 SetOwner 77 SetPlatformCanvas 78 SetPlatformPrintJob 79 Validate 80 ODClipboard 81 ActionDone 84 ActionRedone 85 ActionUndone 86 Clear 87 DraftClosing 88 DraftSaved 89 ExportClipboard 89 GetContentStorageUnit 90 4 GetUpdateID 91 SetPlatformClipboard 92 ShowPasteAsDialog 93 ODContainer 96 AcquireDocument 98 GetID 99 GetName 99 GetStorageSystem 100 SetName 100 ODDesc 102 GetDescType 103 GetRawData 104 InitODDesc 104 SetDescType 105 SetRawData 105 ODDescList 106 InitODDescList 107 ODDispatcher 108 AddDispatchModule 111 AddMonitor 112 Dispatch 113 Exit 114 GetDispatchModule 115 GetMouseRegion 116 GetSleepTime 116 InvalidateFacetUnderMouse 117 Redispatch 117 RegisterIdle 119 RemoveDispatchModule 119 RemoveMonitor 120 SetIdleFrequency 121 SetMouseRegion 122 ShouldExit 122 UnregisterIdle 123 Yield 124 5 ODDispatchModule 125 Dispatch 127 InitDispatchModule 128 ODDocument 130 AcquireBaseDraft 132 AcquireDraft 134 CollapseDrafts 136 CreateDraft 137 Exists 138 GetContainer 140 GetID 140 GetName 141 SaveToAPrevDraft 142 SetBaseDraftFromForeignDraft 143 SetName 143 ODDraft 145 AbortClone 149 AcquireDraftProperties 150 AcquireFrame 151 AcquireLink 152 AcquireLinkSource 153 AcquirePart 154 AcquirePersistentObject 155 AcquireStorageUnit 156 BeginClone 157 ChangedFromPrev 158 Clone 159 CreateFrame 162 CreateLinkSource 163 CreateLinkSpec 164 CreatePart 166 CreateStorageUnit 167 EndClone 167 Externalize 169 GetDocument 169 GetID 170 6 GetPermissions 170 GetPersistentObjectID 171 IsValidID 172 ReleasePart 173 RemoveChanges 173 RemoveFrame 174 RemoveFromDocument 175 RemoveLink 175 RemoveLinkSource 176 RemovePart 177 RemoveStorageUnit 178 SaveToAPrevious 179 SetChangedFromPrev 180 WeakClone 181 ODDragAndDrop 184 Clear 186 GetContentStorageUnit 187 GetDragAttributes 187 GetDragReference 189 ShowPasteAsDialog 189 StartDrag 192 ODDragItemIterator 194 First 195 IsNotComplete 196 Next 197 ODEmbeddedFramesIterator 198 CheckValid 201 First 202 InitEmbeddedFramesIterator 203 IsNotComplete 204 IsValid 205 Next 205 PartRemoved 206 ODExtension 208 BaseRemoved 211 7 CheckValid 212 GetBase 213 InitExtension 213 IsValid 214 ODFacet 215 AcquireActiveShape 220 AcquireAggregateClipShape 221 AcquireClipShape 222 AcquireContentTransform 222 AcquireExternalTransform 223 AcquireFrameTransform 224 AcquireWindowAggregateClipShape 225 AcquireWindowContentTransform 226 AcquireWindowFrameTransform 227 ActiveBorderContainsPoint 228 ChangeActiveShape 229 ChangeCanvas 229 ChangeGeometry 230 ChangeHighlight 231 ContainsPoint 232 CreateCanvas 232 CreateEmbeddedFacet 234 CreateFacetIterator 235 CreateShape 236 CreateTransform 237 Draw 238 DrawActiveBorder 238 DrawChildren 239 DrawChildrenAlways 240 DrawnIn 241 GetCanvas 241 GetContainingFacet 242 GetFrame 242 GetHighlight 243 GetPartInfo 243 GetWindow 244 HasCanvas 245 8 Invalidate 245 InvalidateActiveBorder 246 IsSelected 247 MoveBefore 247 MoveBehind 248 RemoveFacet 249 SetPartInfo 250 SetSelected 250 Update 251 Validate 252 ODFacetIterator 253 First 254 IsNotComplete 255 Next 256 SkipChildren 257 ODFocusModule 258 AbortRelinquishFocus 261 AcquireFocusOwner 262 BeginRelinquishFocus 263 CommitRelinquishFocus 264 CreateOwnerIterator 265 InitFocusModule 266 IsFocusExclusive 267 SetFocusOwnership 268 TransferFocusOwnership 269 UnsetFocusOwnership 270 ODFocusOwnerIterator 272 First 274 InitFocusOwnerIterator 275 IsNotComplete 276 Next 277 ODFocusSet 279 Add 280 Contains 281 CreateIterator 282 9 Remove 282 ODFocusSetIterator 284 First 285 IsNotComplete 286 Next 286 ODFrame 288 AcquireContainingFrame 295 AcquireFrameShape 296 AcquireInternalTransform 297 AcquirePart 297 AcquireUsedShape 298 AcquireWindow 299 ChangeContentExtent 299 ChangeFrameShape 300 ChangeInternalTransform 301 ChangeLinkStatus 302 ChangePart 303 ChangePresentation 304 ChangeSequenceNumber 305 ChangeUsedShape 305 ChangeViewType 306 Close 307 ContentUpdated 308 CreateFacetIterator 308 CreateShape 309 CreateTransform 310 DoesPropagateEvents 310 DrawActiveBorder 311 EditInLink 311 FacetAdded 312 FacetRemoved 313 GetContentExtent 313 GetFrameGroup 314 GetLinkStatus 314 GetPartInfo 315 GetPresentation 316 10 GetSequenceNumber 316 GetViewType 316 Invalidate 317 InvalidateActiveBorder 318 IsDragging 318 IsDroppable 319 IsFrozen 320 IsInLimbo 320 IsOverlaid 321 IsRoot 321 IsSubframe 322 Remove 322 RequestFrameShape 323 SetContainingFrame 324 SetDragging 325 SetDroppable 326 SetFrameGroup 326 SetFrozen 327 SetInLimbo 327 SetPartInfo 328 SetPresentation 328 SetPropagateEvents 329 SetSubframe 330 SetViewType 330 SetWindow 331 Validate 332 ODFrameFacetIterator 333 First 334 IsNotComplete 335 Next 335 ODInfo 337 ShowPartFrameInfo 338 ODLink 339 GetChangeTime 342 GetContentStorageUnit 343 11 GetUpdateID 344 Lock 345 RegisterDependent 346 ShowLinkDestinationInfo 347 ShowSourceContent 349 Unlock 351 UnregisterDependent 351 ODLinkManager 353 AnyLinkImported 355 DraftClosing
Load more

Recommended publications
  • Develop-21 9503 March 1995.Pdf
    develop E D I T O R I A L S T A F F T H I N G S T O K N O W C O N T A C T I N G U S Editor-in-Cheek Caroline Rose develop, The Apple Technical Feedback. Send editorial suggestions Managing Editor Toni Moccia Journal, a quarterly publication of or comments to Caroline Rose at Technical Buckstopper Dave Johnson Apple Computer’s Developer Press AppleLink CROSE, Internet group, is published in March, June, [email protected], or fax Bookmark CD Leader Alex Dosher September, and December. develop (408)974-6395. Send technical Able Assistants Meredith Best, Liz Hujsak articles and code have been reviewed questions about develop to Dave Our Boss Greg Joswiak for robustness by Apple engineers. Johnson at AppleLink JOHNSON.DK, His Boss Dennis Matthews Internet [email protected], CompuServe This issue’s CD. Subscription issues Review Board Pete “Luke” Alexander, Dave 75300,715, or fax (408)974-6395. Or of develop are accompanied by the Radcliffe, Jim Reekes, Bryan K. “Beaker” write to Caroline or Dave at Apple develop Bookmark CD. The Bookmark Ressler, Larry Rosenstein, Andy Shebanow, Computer, Inc., One Infinite Loop, CD contains a subset of the materials Gregg Williams M/S 303-4DP, Cupertino, CA 95014. on the monthly Developer CD Series, Contributing Editors Lorraine Anderson, which is available from APDA. Article submissions. Ask for our Steve Chernicoff, Toni Haskell, Judy Included on the CD are this issue and Author’s Guidelines and a submission Helfand, Cheryl Potter all back issues of develop along with the form at AppleLink DEVELOP, Indexer Marc Savage code that the articles describe.
    [Show full text]
  • XXX Format Assessment
    Digital Preservation Assessment: Date: 20/09/2016 Preservation Open Document Text (ODT) Format Team Preservation Assessment Version: 1.0 Open Document Text (ODT) Format Preservation Assessment Document History Date Version Author(s) Circulation 20/09/2016 1.0 Michael Day, Paul Wheatley External British Library Digital Preservation Team [email protected] This work is licensed under the Creative Commons Attribution 4.0 International License. Page 1 of 12 Digital Preservation Assessment: Date: 20/09/2016 Preservation Open Document Text (ODT) Format Team Preservation Assessment Version: 1.0 1. Introduction This document provides a high-level, non-collection specific assessment of the OpenDocument Text (ODT) file format with regard to preservation risks and the practicalities of preserving data in this format. The OpenDocument Format is based on the Extensible Markup Language (XML), so this assessment should be read in conjunction with the British Library’s generic format assessment of XML [1]. This assessment is one of a series of format reviews carried out by the British Library’s Digital Preservation Team. Some parts of this review have been based on format assessments undertaken by Paul Wheatley for Harvard University Library. An explanation of the criteria used in this assessment is provided in italics below each heading. [Text in italic font is taken (or adapted) from the Harvard University Library assessment] 1.1 Scope This document will primarily focus on the version of OpenDocument Text defined in OpenDocument Format (ODF) version 1.2, which was approved as ISO/IEC 26300-1:2015 by ISO/IEC JTC1/SC34 in June 2015 [2]. Note that this assessment considers format issues only, and does not explore other factors essential to a preservation planning exercise, such as collection specific characteristics, that should always be considered before implementing preservation actions.
    [Show full text]
  • Foxit Mobilepdf SDK Developer Guide
    Foxit MobilePDF SDK Developer Guide TABLE OF CONTENTS 1 Introduction to Foxit MobilePDF SDK ...........................................................................................1 1.1 Why Foxit MobilePDF SDK is your choice .............................................................................. 1 1.2 Foxit MobilePDF SDK .............................................................................................................. 2 1.3 Key features ........................................................................................................................... 3 1.4 Evaluation ............................................................................................................................... 5 1.5 License .................................................................................................................................... 5 1.6 About this Guide .................................................................................................................... 5 2 Getting Started ...........................................................................................................................7 2.1 Requirements ......................................................................................................................... 7 2.2 What is in the Package ........................................................................................................... 7 2.3 How to run a demo ...............................................................................................................
    [Show full text]
  • TP-1996-789.Pdf (141.1Kb)
    Nationaal Lucht- en Ruimtevaartlaboratorium National Aerospace Laboratory NLR NLR TP 96789 Overview and discussion of electronic exchange standards for technical information H. Kuiper and J.C. Donker DOCUMENT CONTROL SHEET ORIGINATOR'S REF. SECURITY CLASS. NLR TP 96789 U Unclassified ORIGINATOR National Aerospace Laboratory NLR, Amsterdam, The Netherlands TITLE Overview and discussion of electronic exchange standards for technical information PRESENTED AT the CALS Europe'96 conference, Paris, May 29-31, under the title "SGML, HTML, the paperless office... what about the forests and the trees", upon invitation of the NL MOD Representative in the conference committee. AUTHORS DATE pp ref H. Kuiper and J.C. Donker 960725 36 8 DESCRIPTORS Computer graphics Multimedia Document storage Software tools Document markup languages Standards Format Texts Hypertext Word processing Information dissemination ABSTRACT Nowadays more and more information is being exchanged electronically. Reasons for this include a higher degree of cooperation between information suppliers and users, an increasing demand for speed (of production and modification, and reduction of time to market), and cost reduction. On the technology side, the advent of the electronic highway enables effective and efficient electronic information exchange. For reasons of timeliness and life cycle costs, standards and specifications are becoming more important. The aim of this paper is to provide an overview of standards and specifications for electronic exchange of (technical document) information and to discuss the most common ones currently available for text, images, and document exchange. Emerging standards and specifications, such as for audio, video and virtual environments are also briefly discussed. Finally, a brief description is given of a standard for enterprise integration and product data exchange.
    [Show full text]
  • Nitro PDF Professional 5.X User Guide 2 Nitro PDF Professional User Guide
    Nitro PDF Professional 5.x User Guide 2 Nitro PDF Professional User Guide Table of Contents Part I START 7 Part II Help & Registration 7 1 Getting Started................................................................................................................................... guide 7 2 Online help................................................................................................................................... 7 3 Checking ...................................................................................................................................for software updates 8 4 Registering................................................................................................................................... product 8 Part III Workspace 8 1 Ribbon interface................................................................................................................................... 9 Hiding & showing the.......................................................................................................................................................... ribbon 10 Ribbon shortcuts .......................................................................................................................................................... 11 2 Quick Access................................................................................................................................... Toolbar 11 3 Nitro PDF..................................................................................................................................
    [Show full text]
  • Opendoc Spreadsheet Function File Date
    Opendoc Spreadsheet Function File Date Braless Ignacius fordid homologically. Is Sayre asthenic or unkindled after rock-bottom Olaf bosom so whacking? Solly compromising gymnastically as inward Ira flukes her releasers fraternized tacitly. The simple example will be used for use org requires extra buttons opendoc spreadsheet function file date entries from sql insertion. Depending on our security that describe presentation, an integer values of numbers, and a reference, store opendoc spreadsheet function file date, gives a really funny face when converting html. There are zeros if omitted, gnumeric can have existing session names in a text documents or a draw page. Yank subtree belonging to backup data management and attributes that is currently selected by using resources below opendoc spreadsheet function file date as word lists, as you could have. Each field form a few minutes open the width number of opendoc spreadsheet function file date used a cell cannot find any warranty disclaimers may overlap with a namespace and xforms model. The characters need to jpg image data according to. The currently visible or linked into exceptions must rest api offers different formats would be used for a packaging system along with two. The partition splits into your desktop version. Java works as timezone in jpg or reference returns an example, while they respect you? The first dereferenced, view it is explicitly defined in several instances, such a data pilot table of text is sometimes we will thus free. List for those that you need to grant patent licenses. Both versions might automatically terminate. This application opendoc spreadsheet function file date and quitting fellows and are unique address within a regular expression is stored there is automatic style.
    [Show full text]
  • 16-02-15 Willkie Buono
    CorporateThe Metropolitan Counsel® www.metrocorpcounsel.com Volume 16, No. 2 © 2008 The Metropolitan Corporate Counsel, Inc. February 2008 The Power Of Choice: Massachusetts Wisely Embraces Multiple Document Format Standards To Drive Greater Competition And Innovation Francis M. Buono closely than in Massachusetts. issued a report entitled “Open Standards, From the moment certain Massachusetts Closed Government: ITD’s Deliberate Disre- and McLean Sieverding government IT officials set in motion a plan to gard for Public Process,” in which it sharply mandate the use of the OpenDocument For- criticized the ITD for: (1) releasing the ETRM WILLKIE FARR & GALLAGHER LLP mat (“ODF”) as the default format for gov- despite public testimony that ODF may impair ernment documents, to the exclusion of other A “document format” (also known as a IT accessibility for thousands of workers with formats, the thorough and very public vetting “file format”) is a particular way to encode disabilities; (2) failing to conduct a cost analy- of the goals, potential impact, and resolution information for storage in a computer file.1 sis or develop implementation documents of the plan has caused many to question the Numerous document formats exist for encod- prior to issuing the ETRM; and (3) issuing appropriate role that government should play ing and storing the same type of information provisions in the ETRM relating to public in selecting and/or excluding technology solu- in word processing, spreadsheet, presentation, records management without the requisite tions (standards-based or otherwise), and on and other document types. Such document statutory authority.4 These shortcomings were what basis. Fortunately for Massachusetts and formats can complement each other by offer- its citizens, the goals of technical neutrality, later detailed in a comprehensive report by the ing different functionality, compete with one 5 choice, and inclusiveness prevailed, and other Auditor of the Commonwealth.
    [Show full text]
  • Automatic Digital Document Processing and Management
    Advances in Pattern Recognition For other titles published in this series, go to www.springer.com/series/4205 Stefano Ferilli Automatic Digital Document Processing and Management Problems, Algorithms and Techniques Stefano Ferilli Dipartimento di Informatica Università di Bari Via E. Orabona 4 70126 Bari Italy [email protected] Series Editor Professor Sameer Singh, PhD Research School of Informatics Loughborough University Loughborough UK ISSN 1617-7916 ISBN 978-0-85729-197-4 e-ISBN 978-0-85729-198-1 DOI 10.1007/978-0-85729-198-1 Springer London Dordrecht Heidelberg New York British Library Cataloguing in Publication Data A catalogue record for this book is available from the British Library © Springer-Verlag London Limited 2011 Apart from any fair dealing for the purposes of research or private study, or criticism or review, as per- mitted under the Copyright, Designs and Patents Act 1988, this publication may only be reproduced, stored or transmitted, in any form or by any means, with the prior permission in writing of the publish- ers, or in the case of reprographic reproduction in accordance with the terms of licenses issued by the Copyright Licensing Agency. Enquiries concerning reproduction outside those terms should be sent to the publishers. The use of registered names, trademarks, etc., in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant laws and regulations and therefore free for general use. The publisher makes no representation, express or implied, with regard to the accuracy of the information contained in this book and cannot accept any legal responsibility or liability for any errors or omissions that may be made.
    [Show full text]
  • Linux World News
    LINUX WORLD NEWS LINUX WORLD NEWS FIRST NEW ZEALAND OPEN SOURCE AWARD In October, more than 200 sion won the prize for “Open Additionally, the NZOSS honored people – among them the Source Use in Government,” and the work of the Open Polytechnic country’s Minister of Infor- the category “Open Source Use in and Michael Koziarski with two mation Technology, Hon. Business” went to Zoomin and Pro- special awards. David Cunliff – celebrated jectX for online mapping of New The jury of seven, convened the achievements of New Zealand. by Don Christie, the president Zealanders in the develop- New Zealand’s own “Summer of of NZOSS, had to choose from ment and use of open source Code” project received the prize in 34 finalists, the essence of more at the Intercontinental Hotel the category “Open Source Use in than 130 nominations. The in Wellington. The privately Education,” and the not-for-profit awards were presented for the sponsored “New Zealand VetLearn Foundation, which pro- first time. Open Source Award” was vides a successful Moodle portal http:// www. nzosa. org. nz/ presented in eight categories. for veterinarians, won the category http:// nzoss. org. nz/ Peter Harrison, the founder “Open Source Use for Community http:// nz. youtube. com/ and former president of the Organizations.” results?search_query=NZOSA07 New Zealand Open Source Society (NZOSS), went Another portal, Julian Oliver’s http:// www. gwprojects. org/ forum/ home with the title “Open Source Ambassador,” SelectParks, aimed at open source http:// www. e. govt. nz/ policy/ and Perlmonger Chris Cormack won the “Open game developers and artists, went open-source/ Source Contributor” category.
    [Show full text]
  • The Future of XML: How Will You Use XML in Years to Come?
    The future of XML How will you use XML in years to come? Level: Intermediate Elliotte Rusty Harold ([email protected]), Adjunct Professor, Polytechnic University 05 Feb 2008 Elliotte Rusty Harold prognosticates what he thinks is in store for XML. The wheels of progress turn slowly, but turn they do. The crystal ball might be a little hazy, but the outline of XML's future is becoming clear. The exact time line is a tad uncertain, but where XML is going isn't. XML's future lies with the Web, and more specifically with Web publishing. It seems a little funny to have to say that. After all, isn't publishing what the Web is about? The Web was designed first and foremost as a mechanism to publish information. What else can it do? Quite a lot. The last three years have seen an explosion of interest in Web applications that go far beyond traditional Web sites. Word processors, spreadsheets, games, diagramming tools, and more are all migrating into the browser. This trend will only accelerate in the coming year as local storage in Web browsers makes it increasingly possible to work offline. But XML is still firmly grounded in Web 1.0 publishing, and that's still very important. Oneiromancy Several dreams are coming true this year. Sun's dream of network deployed applications is happening now, although shockingly the language of choice for these applications is JavaScript™, not Java™. This is a missed opportunity of the first order: Sun could have delivered this 10 years ago, but sadly it never had the experience, vision, or interest in the client to make it happen; now Sun is playing a desperate (and doomed) game of catch-up.
    [Show full text]
  • SAP Businessobjects Live Office User Guide ■ SAP Businessobjects Business Intelligence Platform 4.1 Support Package 2
    SAP BusinessObjects Live Office User Guide ■ SAP BusinessObjects Business Intelligence platform 4.1 Support Package 2 2013-11-21 Copyright © 2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. 2013-11-21 Contents Chapter 1 About this document ..............................................................................................................7 1.1 Who should read this
    [Show full text]
  • MVP: Model-View-Presenter the Taligent Programming Model for C++ and Java
    (C) Copyright Taligent, Inc. 1996 - All Rights Reserved MVP: Model-View-Presenter The Taligent Programming Model for C++ and Java Mike Potel VP & CTO Taligent, Inc. Taligent, a wholly-owned subsidiary of IBM, is developing a next generation programming model for the C++ and Java programming languages, called Model-View-Presenter or MVP, based on a generalization of the classic MVC programming model of Smalltalk. MVP provides a powerful yet easy to understand design methodology for a broad range of application and component development tasks. Taligent’s framework-based implementation of these concepts adds great value to developer programs that employ MVP. MVP also is adaptable across multiple client/server and multi-tier application architectures. MVP will enable IBM to deliver a unified conceptual programming model across all its major object-oriented language environments. Smalltalk Programming Model The most familiar example of a programming model is the Model-View-Controller (MVC) model1 of Smalltalk developed at Xerox PARC in the late 1970’s. MVC is the fundamental design pattern used in Smalltalk for implementing graphical user interface (GUI) objects, and it has been reused and adopted to varying degrees in most other GUI class libraries and application frameworks since. Controller data gestures change & events notification Model View data access Smalltalk represents a GUI object such as a check box or text entry field using the three core abstractions of MVC. A model represents the data underlying the object, for example, the on-off state of a check box or the text string from a text entry field. The view accesses the data from the model and specifies how the data from the model is drawn on the screen, for example, an actual checked or unchecked check box, or a text entry box containing the string.
    [Show full text]