DOCSLIB.ORG

Erwin Data Modeler API Reference

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Erwin Data Modeler API Reference erwin Data Modeler API Reference Release 2019 R1 Legal Notices This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational pur- poses only and is subject to change or withdrawal by erwin Inc. at any time. This Docu- mentation is proprietary information of erwin Inc. and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of erwin Inc. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Docu- mentation for internal use by you and your employees in connection with that software, provided that all erwin Inc. copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to erwin Inc. that all copies and partial copies of the Documentation have been returned to erwin Inc. or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, ERWIN INC. PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL ERWIN INC. BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF ERWIN INC. IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applic- able license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is erwin Inc. Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Govern- ment is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19 (c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright © 2019 erwin Inc. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Contact erwin Understanding your Support Review support maintenance programs and offerings. Registering for Support Access the erwin support site and click Sign in to register for product support. Accessing Technical Support For your convenience, erwin provides easy access to "One Stop" support for all editions of erwin Data Modeler, and includes the following: Online and telephone contact information for technical assistance and customer ser- vices Information about user communities and forums Product and documentation downloads erwin Support policies and guidelines Other helpful resources appropriate for your product For information about other erwin products, visit http://erwin.com/products. Provide Feedback If you have comments or questions, or feedback about erwin product documentation, you can send a message to [email protected]. erwin Data Modeler News and Events Visit www.erwin.com to get up-to-date news, announcements, and events. View video demos and read up on customer success stories and articles by industry experts. 3 Contents Legal Notices 2 Contents 4 Introduction to API 15 Major Features 16 Typical Use Cases 17 Standalone Client 18 Add-in Component or Script 19 API Components 21 Overview 22 Application Tier 23 Model Directory Tier 25 Sessions Tier 26 Model Data Tier 27 Access to Model Data 29 Objects and Properties 31 Object Identifiers 32 Object Identifiers and Type Codes 33 Properties, Property Flags, and Value Facets 34 Scalar and Non-Scalar Property Values 36 Collections and Automation 37 _NewEnum Property of a Collection Object 39 Default Properties 40 4 Optional Parameter 41 The API Sample Client 42 Using the API Sample Client 43 Register the Add-in Component 44 Make a VB.NET Library COM Callable 44 API Tasks 46 Creating the ISCApplication Object 47 Application Properties 48 ISCApplication Interface 49 ISCApplicationEnvironment 50 Accessing a Model 54 Using the API as an Add-in Tool 55 ISCApplication Interface 56 ISCPersistenceUnitCollection Interface 57 ISCPersistenceUnit Interface 58 Property Bag Members for a Persistence Unit 59 ISCPropertyBag Interface 61 Using the API as a Standalone Executable 63 Creating a Model 64 ISCPersistenceUnitCollection Interface 65 ISCPropertyBag Interface 66 Opening an Existing Model 68 ISCPersistenceUnitCollection Interface 69 5 Opening a Session 71 ISCSessionCollection Interface 72 ISCSession Interface 73 Accessing a Model Set 75 ISCPersistenceUnit Interface 76 ISCModelSet Interface 77 ISCModelSetCollection Interface 78 ISCSession Interface 79 Accessing Objects in a Model 82 ISCSession Interface 83 ISCModelObjectCollection Interface 84 ISCModelObject Interface 85 Accessing a Specific Object 88 ISCModelObjectCollection Interface 89 Filtering Object Collections 91 ISCModelObjectCollection Interface 92 Accessing Object Properties 99 Iteration of Properties 100 ISCModelObject Interface 101 ISCModelPropertyCollection Interface 102 ISCModelProperty Interface 103 ISCModelProperty Interface 105 Iterating Over Non-Scalar Property Values 108 6 ISCModelProperty Interface 109 ISCPropertyValueCollection Interface 110 ISCPropertyValue Interface 111 Accessing a Specific Property 115 ISCPropertyValueCollection Interface 116 Filtering Properties 118 ISCModelObject Interface 119 Modifying the Model Using Session Transactions 122 Begin Transaction 124 ISCSession Interface 125 Commit Transaction 127 ISCSession Interface 128 Creating Objects 129 ISCModelObjectCollection Interface 130 Setting Property Values 133 Setting Scalar Property Values 134 ISCModelProperty Interface 135 Setting Non-Scalar Property Values 137 ISCModelProperty Interface 138 Deleting Objects 140 ISCModelObjectCollection Interface 141 Deleting Properties and Property Values 142 ISCModelPropertyCollection Interface 143 7 ISCModelProperty Interface 144 Deleting Non-Scalar Property Values 145 Saving the Model 146 ISCPersistenceUnit Interface 147 Accessing Metamodel Information 149 ISCApplicationEnvironment Interface 150 ISCSession Interface 151 Closing the API 153 ISCSession Interface 154 ISCSessionCollection Interface 155 Clearing Persistence Units 157 ISCPersistenceUnitCollection Interface 158 Error Handling 159 ISCApplicationEnvironment 161 Advanced Tasks 164 Creating User-Defined Properties 165 History Tracking 169 ISCSession Interface 170 API Interfaces Reference 173 ISCApplication 174 API Interfaces 175 ISCApplicationEnvironment 176 ISCApplicationEnvironment::PropertyBag Arguments 177 8 ISCModelDirectory 178 ISCModelDirectory::DirectoryExists Arguments 180 ISCModelDirectory::DirectoryUnitExists Arguments 181 ISCModelDirectory::IsOfType Arguments 182 ISCModelDirectory::LocateDirectory Arguments 183 ISCModelDirectory::LocateDirectoryUnit Arguments 184 ISCModelDirectory::PropertyBag Arguments (Get Function) 185 ISCModelDirectory::PropertyBag Arguments (Set Function) 186 ISCModelDirectoryCollection 187 ISCModelDirectoryCollection::Add Arguments 188 ISCModelDirectoryCollection::Item Arguments 189 ISCModelDirectoryCollection::Remove Arguments 190 ISCModelDirectoryUnit 191 ISCModelDirectoryUnit::IsOfType Arguments 193 ISCModelDirectoryUnit::PropertyBag Arguments (Get Function) 194 ISCModelDirectoryUnit::PropertyBag Arguments (Set Function) 195 ISCModelObject 196 ISCModelObject::CollectProperties Arguments 198 ISCModelObject::IsInstanceOf Arguments 200 ISCModelObjectCollection 201 ISCModelObjectCollection::Add Arguments 203 ISCModelObjectCollection::Collect Arguments 204 ISCModelObjectCollection::Item Arguments 206 9 ISCModelObjectCollection::Remove Arguments 207 ISCModelProperty 208 ISCModelProperty::DataType Arguments 211 ISCModelProperty::RemoveValue Arguments 212 ISCModelProperty::Value Arguments (Get Function) 213 ISCModelProperty::Value Arguments (Set Function) 214 ISCModelProperty::GetValueFacetIds Arguments 215 ISCModelProperty::GetValueFacetNames Arguments 216 ISCModelProperty::SetValueFacets Arguments 217 ISCModelPropertyCollection 218 ISCModelPropertyCollection::Add Arguments 221 ISCModelPropertyCollection::HasProperty Arguments 222 ISCModelPropertyCollection::HasPropertyFacets Arguments 223 ISCModelPropertyCollection::Item Arguments 225 ISCModelPropertyCollection::Remove Arguments 226 ISCModelSet 227 ISCModelSet::PropertyBag Arguments (Get Function) 229 ISCModelSet::PropertyBag Arguments (Set Function) 230 ISCModelSetCollection 231 ISCModelSetCollection::Item Arguments 232 ISCPersistenceUnit 233 ISCPersistenceUnit::PropertyBag Arguments (Get Function) 235 ISCPersistenceUnit::PropertyBag Arguments (Set Function) 236 10 ISCPersistenceUnit::Save Arguments 237 ISCPersistenceUnit::ReverseEngineer 238 ISCPersistenceUnit::ForwardEngineer 246 ISCPersistenceUnitCollection 248 ISCPersistenceUnitCollection::Add Arguments 249 ISCPersistenceUnitCollection::Create Arguments 250 ISCPersistenceUnitCollection::Item Arguments 251 ISCPersistenceUnitCollection::Remove Arguments 252 ISCPropertyBag 253 ISCPropertyBag::Add Arguments 254 ISCPropertyBag::Name Arguments 255 ISCPropertyBag::Value Arguments (Get Function)
Load more

Recommended publications
  • WEKA Manual for Version 3-7-8
    WEKA Manual for Version 3-7-8 Remco R. Bouckaert Eibe Frank Mark Hall Richard Kirkby Peter Reutemann Alex Seewald David Scuse January 21, 2013 ⃝c 2002-2013 University of Waikato, Hamilton, New Zealand Alex Seewald (original Commnd-line primer) David Scuse (original Experimenter tutorial) This manual is licensed under the GNU General Public License version 3. More information about this license can be found at http://www.gnu.org/licenses/gpl-3.0-standalone.html Contents ITheCommand-line 11 1Acommand-lineprimer 13 1.1 Introduction . 13 1.2 Basic concepts . 14 1.2.1 Dataset . 14 1.2.2 Classifier . 16 1.2.3 weka.filters . 17 1.2.4 weka.classifiers . 19 1.3 Examples . 23 1.4 Additional packages and the package manager . .24 1.4.1 Package management . 25 1.4.2 Running installed learning algorithms . 26 II The Graphical User Interface 29 2LaunchingWEKA 31 3PackageManager 35 3.1 Mainwindow ............................. 35 3.2 Installing and removing packages . 36 3.2.1 Unofficalpackages ...................... 37 3.3 Usingahttpproxy.......................... 37 3.4 Using an alternative central package meta data repository . 37 3.5 Package manager property file . 38 4SimpleCLI 39 4.1 Commands . 39 4.2 Invocation . 40 4.3 Command redirection . 40 4.4 Command completion . 41 5Explorer 43 5.1 The user interface . 43 5.1.1 Section Tabs . 43 5.1.2 Status Box . 43 5.1.3 Log Button . 44 5.1.4 WEKA Status Icon . 44 3 4 CONTENTS 5.1.5 Graphical output . 44 5.2 Preprocessing . 45 5.2.1 Loading Data .
    [Show full text]
  • Tinkertool System 7 Reference Manual Ii
    Documentation 0642-1075/2 TinkerTool System 7 Reference Manual ii Version 7.5, August 24, 2021. US-English edition. MBS Documentation 0642-1075/2 © Copyright 2003 – 2021 by Marcel Bresink Software-Systeme Marcel Bresink Software-Systeme Ringstr. 21 56630 Kretz Germany All rights reserved. No part of this publication may be redistributed, translated in other languages, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of the publisher. This publication may contain examples of data used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The publisher may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Make sure that you are using the correct edition of the publication for the level of the product. The version number can be found at the top of this page. Apple, macOS, iCloud, and FireWire are registered trademarks of Apple Inc. Intel is a registered trademark of Intel Corporation. UNIX is a registered trademark of The Open Group. Broadcom is a registered trademark of Broadcom, Inc. Amazon Web Services is a registered trademark of Amazon.com, Inc.
    [Show full text]
  • User Interface Specification for Interactive Software Systems
    User Interface Specification for Interactive Software Systems Process-, Method- and Tool-Support for Interdisciplinary and Collaborative Requirements Modelling and Prototyping-Driven User Interface Specification Dissertation zur Erlangung des akademischen Grades des Doktor der Naturwissenschaften (Dr. rer. nat.) Universität Konstanz Mathematisch-Naturwissenschaftliche Sektion Fachbereich Informatik und Informationswissenschaft Vorgelegt von Thomas Memmel Betreuer der Dissertation: Prof. Dr. Harald Reiterer Tag der mündlichen Prüfung: 29. April 2009 1. Referent: Prof. Dr. Harald Reiterer 2. Referent: Prof. Dr. Rainer Kuhlen Prof. Dr. Rainer Kuhlen For Cathrin Acknowledgements I thank my advisor, Prof. Dr. Harald Reiterer, for more than 6 years of great Prof. Dr. Harald Reiterer teamwork. Since I joined his work group as a student researcher, his guidance and friendship have helped me to reach high goals and achieve scientific recognition. I thank Harald for his creative contributions and his unfailing support, which made him the best supervisor I could imagine. Every time I read the Dr. in front of my name, I will think about the person who made it possible. It was Harald! Moreover, I thank him for teaching me many skills, of which especially purposefulness and per- suasive power opened up a world of possibilities. Among the other researchers in the human-computer interaction work group, spe- My colleague and friend Fredrik cial thanks are due to my colleague Fredrik Gundelsweiler. Fredrik and I started working for Harald at the same time, and since then we have shared many experi- ences. I worked with Fredrik at Siemens AG in Munich, and we both gained interna- tional work experience during our stay at DaimlerChrysler AG in Singapore.
    [Show full text]
  • Vtpin: Practical Vtable Hijacking Protection for Binaries
    VTPin: Practical VTable Hijacking Protection for Binaries Pawel Sarbinowski Vasileios P. Kemerlis Cristiano Giuffrida Vrije Universiteit Amsterdam Brown University Vrije Universiteit Amsterdam [email protected] [email protected] [email protected] Elias Athanasopoulos Vrije Universiteit Amsterdam [email protected] ABSTRACT 1. INTRODUCTION VTable hijacking has lately been promoted to the de facto technique The recent advances in software hardening have undoubtedly for exploiting C++ applications, and in particular web browsers. made exploitation a challenging craft [45]. Yet, despite the plethora VTables, however, can be manipulated without necessarily corrupt- of defenses in place [37], attackers still find ways to compromise ing memory, simply by leveraging use-after-free bugs. In fact, in essential commodity software, like web browsers [5,6]. Modern the recent Pwn2Own competitions all major web browsers were exploits are highly sophisticated and typically leverage a variety of compromised with exploits that employed (among others) use-after- different vulnerabilities to bypass established protections, such as free vulnerabilities and VTable hijacking. address space layout randomization (ASLR) [42], non-executable In this paper, we propose VTPin: a system to protect against memory [12], and sandboxing [18]. To this end, temporal safety VTable hijacking, via use-after-free vulnerabilities, in large C++ errors, and particularly use-after-free vulnerabilities, are becoming binaries that cannot be re-compiled or re-written. The main idea be- a key component of the attackers’ arsenal [1,2,7,8]. Interestingly, hind VTPin is to pin all the freed VTable pointers on a safe VTable exploiting use-after-free bugs does not require corrupting memory; under VTPin’s control.
    [Show full text]
  • United States Patent (19) 11 Patent Number: 6,061,061 Conrad Et Al
    US006061061A United States Patent (19) 11 Patent Number: 6,061,061 Conrad et al. (45) Date of Patent: *May 9, 2000 54) COMPUTER SYSTEM WITH GRAPHICAL 2693810 6/1991 France. USER INTERFACE INCLUDING SPRING LOADED ENCLOSURES OTHER PUBLICATIONS 75 Inventors: Thomas J. Conrad, San Jose; Yin Yin tiMy“M ft WindowSTM 7 User’sSer's Guide.Oude, MiMicroSOIL ft UorporaC Wong, Menlo Park, both of Calif. “Screen Dumps from Microsoft WindowsTM v3.1.” 73 ASSignee: Apple Computer, Inc., Cupertino, Microsoft Corporation, 1985-1992, pp. 1-10. Calif. Jeff Johnson, et al., “The Xerox Star: A Retrospective,” Computer, Sep. 1989, pp. 11-27. * Notice: This patent is subject to a terminal dis- Brad W. Myers, “Window Interfaces, A Taxonomy of Win claimer. dow Manager User Interfaces.” IEEE Computer Graphics and Applications, Sep. 1988, pp. 65-83. 21 Appl. No.: 08/889,719 “Automatic Window Management Mode.” IBM Technical 9 Disclosure Bulletin, vol. 35, No. 4B, Sep. 1992. 22 Filed: Jul. 8, 1997 (List continued on next page.) Related U.S. Application Data Primary Examiner-Crescelle N. dela Torre 63 Continuation of application No. 08/482,186, Jun. 7, 1995, Attorney, Agent, or Firm Blakely, Sokoloff Taylor & Pat. No. 5,680,562, which is a continuation of application Zafman No. 08/076.253, Jun. 11, 1993, Pat. No. 5,583,984. (51) Int. Cl. ................................................ G06F 15/00 57 ABSTRACT 52 U.S. Cl. ............................................. 345/340; 345/348 A new behavior in a graphical user interface allows the user 58 Field of Search ..................................... 345/340, 326, to open and close enclosures, while dragging an object.
    [Show full text]
  • Analysis Server User Guide
    Analysis Server User Guide This manual explains the basic principles and functionality of the Analysis Server, a software system that enables users to incorporate legacy software into reusable components that can be published on a network. This manual also discusses seven utilities for creating new software components: AnalysisLibraryWrapper, FileWrapper, ExcelWrap- per, ScriptWrapper, PerlWrapper, PXCWrapper, and Java Bean component authoring. The Analysis Server answers several questions that have plagued engineering analysis groups for years: l "How can I provide multi-platform access to our legacy software?" l "How do I make our complicated, convoluted codes a little easier for novices to use?" l "Why do I have to spend all day writing input files and parsing output files when I only want a few critical val- ues?" The Analysis Server allows the user to control complex engineering programs through a simple set of commands (e.g. get, set, and execute). This interface is consistent across all Analysis Server components, so users who understand how to manipulate one component can manipulate them all. The result is enhanced user-friendliness without rewriting the original software. Distributed access and ease of use are only the tip of the Analysis Server's capabilities. Its command set can be incor- porated into a client program, which means that other programs can directly access data from Analysis Server com- ponents. An Analysis Server client can transfer data directly from legacy software to an Excel workbook, for example. If the client program has an integration architecture, it is possible to make several previously stand-alone leg- acy programs from geographically distant, hardware distinct machines work together as though modules of a single program.
    [Show full text]
  • Testing and Maintenance of Graphical User Interfaces Valeria Lelli Leitao
    Testing and maintenance of graphical user interfaces Valeria Lelli Leitao To cite this version: Valeria Lelli Leitao. Testing and maintenance of graphical user interfaces. Human-Computer Inter- action [cs.HC]. INSA de Rennes, 2015. English. NNT : 2015ISAR0022. tel-01232388v2 HAL Id: tel-01232388 https://tel.archives-ouvertes.fr/tel-01232388v2 Submitted on 11 Apr 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. THÈSE INSA Rennes présentée par sous le sceau de l’Université Européenne de Bretagne Valéria Lelli Leitão Dan- pour obtenir le grade de tas DOCTEUR DE L’INSA DE RENNES ÉCOLE DOCTORALE : MATISSE Spécialité : Informatique LABORATOIRE : IRISA/INRIA Thèse soutenue le 19 Novembre 2015 devant le jury composé de : Testing and Pascale Sébillot Professeur, Universités IRISA/INSA de Rennes / Présidente maintenance of Lydie du Bousquet Professeur d’informatique, Université Joseph Fourier / Rapporteuse Philippe Palanque graphical user Professeur d’informatique, Université Toulouse III / Rapporteur Francois-Xavier Dormoy interfaces Chef de produit senior, Esterel Technologies / Examinateur Benoit Baudry HDR, Chargé de recherche, INRIA Rennes - Bretagne Atlantique / Directeur de thèse Arnaud Blouin Maître de Conférences, INSA Rennes / Co-encadrant de thèse Testing and Maintenance of Graphical User Interfaces Valéria Lelli Leitão Dantas Document protégé par les droits d’auteur Contents Acknowledgements 5 Abstract 7 Résumé en Français 9 1Introduction 19 1.1 Context ...................................
    [Show full text]
  • GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing
    GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing Atif Memon Ishan Banerjee, Adithya Nagarajan Department of Computer Science Department of Computer Science and Fraunhofer Center for University of Maryland Experimental Software Engineering College Park, Maryland, USA University of Maryland {ishan, sadithya}@cs.umd.edu College Park, Maryland, USA [email protected] Abstract trols that represent everyday objects such as menus, but- tons, lists, and windows. Recognizing the importance of Graphical user interfaces (GUIs) are important parts of GUIs, software developers are dedicating large parts of the today’s software and their correct execution is required to code to implementing GUIs [12]. The correctness of this ensure the correctness of the overall software. A popular code is essential to the correct execution of the overall soft- technique to detect defects in GUIs is to test them by exe- ware. A popular technique to detect defects in software is cuting test cases and checking the execution results. Test testing [3, 2, 23]. During testing, test cases are created and cases may either be created manually or generated auto- executed on the software. Test cases may either be created matically from a model of the GUI. While manual testing manually by a tester [10, 27, 8] or automatically by using a is unacceptably slow for many applications, our experience model of the software derived from its specifications [20]. with GUI testing has shown that creating a model that can In all our work to date [20, 17, 21, 16, 18, 19, 15, 12, 14], be used for automated test case generation is difficult.
    [Show full text]
  • Using-Designer.Pdf
    Using Designer AEM 6.3 Forms Legal notices For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. Last updated 4/26/17 Contents Welcome to Designer . 1 About Designer . 1 Using Designer in the SAP environment . 1 Using Designer in different spaces . 2 New features in Designer . 2 Render XFA forms as HTML5 forms . 2 Support for Turkish Lira locale . 2 Support for Japanese Postal barcode . 3 Accessibility Checker . 3 Add document title to the PDF title bar . 3 Support for Hindi language . 3 New features in Designer . 3 Preview your XDP forms in HTML in Designer . 3 Preview your XDP forms in HTML in forms manager . 4 Accessibility Checker . 4 Add document title to the PDF title bar . 4 Where to find documentation, samples, and tutorials . 4 Get started with samples and tutorials . 5 Add calculations to forms . 5 Enhance forms by using scripts . 5 Getting Started . 7 About forms . 7 Interactive forms . 7 Non-interactive forms . 8 Print and fill forms . 8 About form designs . 8 Form design layouts . 9 i Fixed layout . 9 Flowable layout . 9 Parts of a form design . 10 Master pages . 10 Pages . 11 Content areas . 11 Subforms . 11 Tables . 12 Field objects . 12 Boilerplate or static objects . 13 Installing and configuring Designer . 13 Configuring JVM settings . 13 Looking at the workspace . 14 About editors . 14 About palettes . 17 Customizing the workspace . .23 Managing library palettes . 28 Steps to creating a form design . 33 Basic steps to creating a form design . 33 Plan the form design . 33 Create the form design .
    [Show full text]
  • Mapping Guis to Auditory Interfaces
    Mapping GUIs to Auditory Interfaces Elizabeth D. Mynatt and W. Keith Edwards Graphics, Visualization, and Usability Center College of Computing Georgia Institute of Technology Atlanta, GA 3032-0280 [email protected], [email protected] ABSTRACT little trouble accessing standard ASCII terminals. The line- This paper describes work to provide mappings between X- oriented textual output displayed on the screen was stored in based graphical interfaces and auditory interfaces. In our the computer’s framebuffer. An access program could sim- system, dubbed Mercator, this mapping is transparent to ply copy the contents of the framebuffer to a speech synthe- applications. The primary motivation for this work is to sizer, a Braille terminal or a Braille printer. Conversely, the provide accessibility to graphical applications for users who contents of the framebuffer for a graphical interface are sim- are blind or visually impaired. We describe the design of an ple pixel values. To provide access to GUIs, it is necessary to auditory interface which simulates many of the features of intercept application output before it reaches the screen. This graphical interfaces. We then describe the architecture we intercepted application output becomes the basis for an off- have built to model and transform graphical interfaces. screen model of the application interface.The information in Finally, we conclude with some indications of future the off-screen model is then used to create alternative, acces- research for improving our translation mechanisms and for sible interfaces. creating an auditory “desktop” environment. The goal of this work, called the Mercator1 Project, is to pro- KEYWORDS: Auditory interfaces, GUIs, X, visual impair- vide transparent access to X Windows applications for com- ment, multimodal interfaces.
    [Show full text]
  • Automatically Generating High-Quality User Interfaces for Appliances
    Automatically Generating High-Quality User Interfaces for Appliances Jeffrey Nichols December 2006 CMU-HCII-06-109 Human Computer Interaction Institute School of Computer Science Carnegie Mellon University Pittsburgh, Pennsylvania 15213 Thesis Committee: Brad A. Myers, Chair Scott E. Hudson John Zimmerman Dan R. Olsen, Jr., Brigham Young University Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy Copyright © 2006 Jeffrey Nichols. All rights reserved. This research was supported in part by the National Science Foundation (through the author’s Graduate Re- search Fellowship and grants IIS-0117658 and IIS-0534349), Microsoft, General Motors, the Pittsburgh Digital Greenhouse, and Intel. Equipment supporting this research was generously donated by Mitsubishi Elec- tric Research Laboratories, VividLogic, Lantronix, Lutron, IBM Canada, Symbol Technologies, Hewlett- Packard, and Lucent. The views and conclusions contained herein are those of the author and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of any sponsoring party or the U.S. Government. Keywords: Automatic interface generation, aggregate user interfaces, handheld computers, personal digital assistants, mobile phones, home theater, appliances, personal universal con- troller (PUC), user interface description languages (UIDLs), remote controls, multi-modal interfaces, speech recognition, Smart Templates, user interface consistency, personal consis- tency, familiarity ii Automatically Generating High-Quality User Interfaces for Appliances Jeffrey Nichols iii iv Abstract0B In this dissertation, I show that many appliance usability problems can be addressed by mov- ing the user interface from the appliance to a handheld device that the user is already carrying, such as a Personal Digital Assistant (PDA) or mobile phone.
    [Show full text]
  • Day One: Beginner's Guide to Learning Junos
    DAY ONE: BEGINNER’S GUIDE TO LEARNING JUNOS® The Juniper AmbAssADors Are A Diverse set of inDepenDent network engineers, ConsultAnts, AnD ArChiteCts who work in the fielD with Juniper technologies on A DAily bAsis. Their mission is to spreaD the worD About the power AnD sCAlAbility of Juniper’s network offerings. InDeeD, they Are responsible for over A Dozen ONE: DAY Day One books AnD Countless soCiAl meDiA AppeArAnCes, viDeos, AnD trAining sessions. But they hAve Al- DAY ONE: BEGINNER’S GUIDE TO ways wanteD to fill A mAjor gAp in the networking CAnnon AnD Create A true beginner’s guiDe to the most powerful networking OS in the worlD. AnD now they hAve Done it, the AmbAssADor wAy: hAnDs on, to the ® point, anD complete. It’s all here in the Beginner’s Guide to Learning Junos. LEARNING JUNOS BEGINNER’S GUIDE TO LEARING JUNOS LEARING TO GUIDE BEGINNER’S “Whether you are new to Juniper or not, there isn’t a more complete introduction to Junos available. I wish Nine this book was around when I started my network journey years ago. The Ambassador authors bring together so much knowledge and expert field experience that this book is a one-stop-shop to take you from beginner to Junos expert.” Melchior Aelmans, Lead Engineer Cloud Providers, Juniper Networks The Juniper Ambassadors “Nowadays there are many vendors offering similar services and its difficult to learn them all. What network show you how to stand up engineers need is a clear and easy-to-follow guide to assist them in their learning journey.
    [Show full text]