Xforms Xforms

Total Page:16

File Type:pdf, Size:1020Kb

Xforms Xforms XForms XForms (Forms Library) A Graphical User Interface Toolkit for X Library Version 1.2 January 2014 i Table of Contents ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Preface :::::::::::::::::::::::::::::::::::::::::::::: 2 Part I - Using the Forms Library :::::::::::::::: 7 1 Introduction::::::::::::::::::::::::::::::::::::: 8 2 Getting Started:::::::::::::::::::::::::::::::: 10 2.1 Naming Conventions :::::::::::::::::::::::::::::::::::::::::: 10 2.2 Some Examples ::::::::::::::::::::::::::::::::::::::::::::::: 10 2.3 Programming Model :::::::::::::::::::::::::::::::::::::::::: 14 3 Defining Forms :::::::::::::::::::::::::::::::: 16 3.1 Starting and Ending a Form Definition :::::::::::::::::::::::: 16 3.2 Boxes ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 3.3 Texts ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 18 3.4 Buttons::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 3.5 Sliders :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 20 3.6 ValSliders ::::::::::::::::::::::::::::::::::::::::::::::::::::: 21 3.7 Input Fields :::::::::::::::::::::::::::::::::::::::::::::::::: 21 3.8 Grouping Objects ::::::::::::::::::::::::::::::::::::::::::::: 22 3.9 Hiding and Showing::::::::::::::::::::::::::::::::::::::::::: 23 3.10 Deactivating and Triggering Objects ::::::::::::::::::::::::: 23 3.11 Changing Attributes ::::::::::::::::::::::::::::::::::::::::: 24 3.11.1 Color ::::::::::::::::::::::::::::::::::::::::::::::::::: 24 3.11.2 Bounding Boxes::::::::::::::::::::::::::::::::::::::::: 27 3.11.3 Label Attributes and Fonts :::::::::::::::::::::::::::::: 28 3.11.4 Tool Tips ::::::::::::::::::::::::::::::::::::::::::::::: 32 3.11.5 Redrawing Objects :::::::::::::::::::::::::::::::::::::: 32 3.11.6 Changing Many Attributes :::::::::::::::::::::::::::::: 33 3.11.7 Symbols :::::::::::::::::::::::::::::::::::::::::::::::: 33 3.12 Adding and Removing Objects ::::::::::::::::::::::::::::::: 36 3.13 Freeing Objects :::::::::::::::::::::::::::::::::::::::::::::: 36 4 Doing Interaction:::::::::::::::::::::::::::::: 38 4.1 Displaying a Form :::::::::::::::::::::::::::::::::::::::::::: 38 4.2 Simple Interaction :::::::::::::::::::::::::::::::::::::::::::: 44 4.3 Periodic Events and Non-blocking Interaction:::::::::::::::::: 46 4.4 Dealing With Multiple Windows :::::::::::::::::::::::::::::: 49 4.5 Using Callback Functions ::::::::::::::::::::::::::::::::::::: 52 4.6 Handling Other Input Sources ::::::::::::::::::::::::::::::::: 55 ii 5 Free Objects ::::::::::::::::::::::::::::::::::: 57 5.1 Free Object ::::::::::::::::::::::::::::::::::::::::::::::::::: 57 5.2 An Example :::::::::::::::::::::::::::::::::::::::::::::::::: 60 6 Goodies :::::::::::::::::::::::::::::::::::::::: 70 6.1 Messages and Questions ::::::::::::::::::::::::::::::::::::::: 70 6.2 Command Log :::::::::::::::::::::::::::::::::::::::::::::::: 74 6.3 Colormap ::::::::::::::::::::::::::::::::::::::::::::::::::::: 75 6.4 File Selector :::::::::::::::::::::::::::::::::::::::::::::::::: 76 Part II - The Form Designer ::::::::::::::::::: 82 7 Introduction ::::::::::::::::::::::::::::::::::: 83 8 Getting Started:::::::::::::::::::::::::::::::: 84 9 Command Line Arguments ::::::::::::::::::: 87 10 Creating Forms::::::::::::::::::::::::::::::: 89 10.1 Creating and Changing Forms:::::::::::::::::::::::::::::::: 89 10.2 Adding Objects :::::::::::::::::::::::::::::::::::::::::::::: 89 10.3 Selecting Objects :::::::::::::::::::::::::::::::::::::::::::: 89 10.4 Moving and Scaling :::::::::::::::::::::::::::::::::::::::::: 90 10.5 Aligning Objects ::::::::::::::::::::::::::::::::::::::::::::: 90 10.6 Raising and Lowering :::::::::::::::::::::::::::::::::::::::: 91 10.7 Setting Attributes:::::::::::::::::::::::::::::::::::::::::::: 91 10.8 Generic Attributes ::::::::::::::::::::::::::::::::::::::::::: 91 10.8.1 Basic Attributes :::::::::::::::::::::::::::::::::::::::: 92 10.8.2 Font :::::::::::::::::::::::::::::::::::::::::::::::::::: 93 10.8.3 Misc. Attributes :::::::::::::::::::::::::::::::::::::::: 93 10.8.4 Colors :::::::::::::::::::::::::::::::::::::::::::::::::: 93 10.9 Object Specific Attributes:::::::::::::::::::::::::::::::::::: 93 10.10 Cut, Copy and Paste:::::::::::::::::::::::::::::::::::::::: 94 10.11 Groups ::::::::::::::::::::::::::::::::::::::::::::::::::::: 94 10.12 Hiding and Showing Objects :::::::::::::::::::::::::::::::: 95 10.13 Testing Forms :::::::::::::::::::::::::::::::::::::::::::::: 95 11 Saving and Loading Forms :::::::::::::::::: 96 12 Language Filters :::::::::::::::::::::::::::: 102 12.1 External Filters::::::::::::::::::::::::::::::::::::::::::::: 102 12.2 Command Line Arguments of the Filter ::::::::::::::::::::: 103 13 Generating Hardcopies ::::::::::::::::::::: 104 iii Part III - Object Classes ::::::::::::::::::::::: 106 14 Introduction ::::::::::::::::::::::::::::::::: 107 15 Static Objects ::::::::::::::::::::::::::::::: 109 15.1 Box Object ::::::::::::::::::::::::::::::::::::::::::::::::: 109 15.1.1 Adding Box Objects ::::::::::::::::::::::::::::::::::: 109 15.1.2 Box Types ::::::::::::::::::::::::::::::::::::::::::::: 109 15.1.3 Box Attributes ::::::::::::::::::::::::::::::::::::::::: 109 15.1.4 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 110 15.2 Frame Object::::::::::::::::::::::::::::::::::::::::::::::: 110 15.2.1 Adding Frame Objects ::::::::::::::::::::::::::::::::: 110 15.2.2 Frame Types::::::::::::::::::::::::::::::::::::::::::: 110 15.2.3 Frame Attributes :::::::::::::::::::::::::::::::::::::: 111 15.2.4 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 111 15.3 LabelFrame Object ::::::::::::::::::::::::::::::::::::::::: 111 15.3.1 Adding LabelFrame Objects:::::::::::::::::::::::::::: 111 15.3.2 LabelFrame Types ::::::::::::::::::::::::::::::::::::: 111 15.3.3 Attributes ::::::::::::::::::::::::::::::::::::::::::::: 112 15.3.4 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 112 15.4 Text Object :::::::::::::::::::::::::::::::::::::::::::::::: 112 15.4.1 Adding Text Objects::::::::::::::::::::::::::::::::::: 112 15.4.2 Text Types :::::::::::::::::::::::::::::::::::::::::::: 112 15.4.3 Text Attributes :::::::::::::::::::::::::::::::::::::::: 112 15.4.4 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 112 15.5 Bitmap Object:::::::::::::::::::::::::::::::::::::::::::::: 113 15.5.1 Adding Bitmap Objects :::::::::::::::::::::::::::::::: 113 15.5.2 Bitmap Types ::::::::::::::::::::::::::::::::::::::::: 113 15.5.3 Bitmap Interaction::::::::::::::::::::::::::::::::::::: 113 15.5.4 Other Bitmap Routines :::::::::::::::::::::::::::::::: 113 15.5.5 Bitmap Attributes ::::::::::::::::::::::::::::::::::::: 114 15.5.6 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 114 15.6 Pixmap Object ::::::::::::::::::::::::::::::::::::::::::::: 114 15.6.1 Adding Pixmap Objects:::::::::::::::::::::::::::::::: 114 15.6.2 Pixmap Types ::::::::::::::::::::::::::::::::::::::::: 114 15.6.3 Pixmap Interaction :::::::::::::::::::::::::::::::::::: 114 15.6.4 Other Pixmap Routines :::::::::::::::::::::::::::::::: 114 15.6.5 Pixmap Attributes ::::::::::::::::::::::::::::::::::::: 115 15.6.6 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 115 15.7 Clock Object ::::::::::::::::::::::::::::::::::::::::::::::: 116 15.7.1 Adding Clock Objects:::::::::::::::::::::::::::::::::: 116 15.7.2 Clock Types ::::::::::::::::::::::::::::::::::::::::::: 116 15.7.3 Clock Interaction :::::::::::::::::::::::::::::::::::::: 116 15.7.4 Other Clock Routines :::::::::::::::::::::::::::::::::: 116 15.7.5 Clock Attributes ::::::::::::::::::::::::::::::::::::::: 117 15.7.6 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 117 15.8 Chart Object ::::::::::::::::::::::::::::::::::::::::::::::: 117 iv 15.8.1 Adding Chart Objects ::::::::::::::::::::::::::::::::: 117 15.8.2 Chart Types ::::::::::::::::::::::::::::::::::::::::::: 117 15.8.3 Chart Interaction :::::::::::::::::::::::::::::::::::::: 118 15.8.4 Other Chart Routines :::::::::::::::::::::::::::::::::: 118 15.8.5 Chart Attributes ::::::::::::::::::::::::::::::::::::::: 119 15.8.6 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 119 16 Button-like Objects ::::::::::::::::::::::::: 120 16.1 Adding Button Objects ::::::::::::::::::::::::::::::::::::: 120 16.2 Button Types::::::::::::::::::::::::::::::::::::::::::::::: 122 16.3 Button Interaction :::::::::::::::::::::::::::::::::::::::::: 123 16.4 Other Button Routines ::::::::::::::::::::::::::::::::::::: 123 16.5 Button Attributes :::::::::::::::::::::::::::::::::::::::::: 126 16.6 Remarks:::::::::::::::::::::::::::::::::::::::::::::::::::: 126 17 Valuator Objects :::::::::::::::::::::::::::: 127 17.1 Slider Object ::::::::::::::::::::::::::::::::::::::::::::::: 127 17.1.1 Adding Slider Objects:::::::::::::::::::::::::::::::::: 127 17.1.2 Slider Types ::::::::::::::::::::::::::::::::::::::::::: 127 17.1.3 Slider Interaction :::::::::::::::::::::::::::::::::::::: 128 17.1.4 Other Slider Routines :::::::::::::::::::::::::::::::::: 129 17.1.5 Slider Attributes ::::::::::::::::::::::::::::::::::::::: 129 17.1.6 Remarks ::::::::::::::::::::::::::::::::::::::::::::::: 130 17.2 Scrollbar Object :::::::::::::::::::::::::::::::::::::::::::: 130 17.2.1 Adding Scrollbar Objects :::::::::::::::::::::::::::::: 131 17.2.2 Scrollbar Types :::::::::::::::::::::::::::::::::::::::: 131 17.2.3 Scrollbar Interaction ::::::::::::::::::::::::::::::::::: 132 17.2.4 Other Scrollbar Routines ::::::::::::::::::::::::::::::: 132 17.2.5 Scrollbar Attributes :::::::::::::::::::::::::::::::::::: 133 17.2.6 Remarks
Recommended publications
  • Eves2005-Dformstfp04
    Chapter 1 Disjoint Forms in Graphical User Interfaces Sander Evers, Peter Achten, Rinus Plasmeijer1 Abstract: Forms are parts of a graphical user interface (GUI) that show a (struc- tured) value and allow the user to update it. Some forms express a choice between two or more (structured) values using radio buttons or check boxes. We show that explicitly modelling such a choice leads to a cleaner separation of logic and lay- out. This is done by extending the combinator library FunctionalForms with dis- joint form combinators. To implement these, we have generalized the technique of compositional functional references which underlies the library. 1.1 INTRODUCTION Forms are parts of a graphical user interface (GUI) that show a (structured) value and allow the user to update it. For example, the omnipresent dialogs labeled Options, Settings and Preferences are forms. An address book can also be con- sidered a form. In our previous work, we have developed the combinator library FunctionalForms[2] for building forms in a concise, compositional way. Many real-life forms allow a choice between two or more alternatives, some of which require extra information. For example, the form in Fig. 1.1 indicates whether the user wishes to receive a certain newsletter; if s/he does, the text entry field next to this option should contain his/her email adress. If s/he does not, this text field is irrelevant (some GUIs provide a visual clue for this: the control is dimmed). Usually, the information in such a form is processed as a product-like data structure containing the choice (e.g.
    [Show full text]
  • Comparison of Common Xml-Based Web User Interface Languages
    Journal of Web Engineering, Vol. 9, No. 2 (2010) 095–115 c Rinton Press COMPARISON OF COMMON XML-BASED WEB USER INTERFACE LANGUAGES MIKKO POHJA Department of Media Technology, Aalto University P.O. Box 15400, FI-00076 Aalto, Finland mikko.pohja@hut.fi Received August 1, 2009 Revised February 25, 2010 In addition to being a platform for information access, the World Wide Web is increas- ingly becoming an application platform. While web applications have several benefits compared to desktop applications, there are also some problems. With legacy HTML, for example, one cannot produce user interfaces such as those that users have become accustomed to with desktop applications. What worked for static documents is not suf- ficient for the complicated web applications of today. Several parties have addressed this problem by defining a specific UI description language. In addition, the renewal of HTML aims to enhance support for web applications. This study evaluated five XML- based UI description formats, including HTML 5, in order to determine which language is best suited for modern web application development. The study also assessed what kind of applications are suited to each format. The requirements for a Web UI descrip- tion language from the literature were revised and three use cases were defined, through which the languages are evaluated. The paper also presents the model differences of the languages. Keywords: Web User Interface Description Language, Web Application Communicated by: D. Lowe & O. Pastor 1 Introduction Commerce and communication tasks, such as the use of e-mail, are common today on the World Wide Web (WWW), as is a trend towards realizing higher interaction tasks, such as in- formation authoring.
    [Show full text]
  • 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]
  • Model-Driven Architecture for Cancer Research
    Model-driven architecture for cancer research Radu Calinescu, Steve Harris, Jeremy Gibbons and Jim Davies Computing Laboratory, University of Oxford Wolfson Building, Parks Road, Oxford OX1 3QD, UK Igor Toujilov and Sylvia B. Nagl Oncology Department, The Royal Free and University College Medical School Hampstead Campus, Rowland Hill Street, Hampstead, London NW3 2PF, UK Abstract trial designer tool provides oncology clinicians with an in- tegrated environment for the design of cancer clinical trials It is a common phenomenon for research projects to col- that are instances of the metamodel. This use of a common lect and analyse valuable data using ad-hoc information metamodel for the design of different clinical trials enables systems. These costly-to-build systems are often composed the model-driven development of reusable software compo- of incompatible variants of the same modules, and record nents for cancer research. Additionally, the tool enforces data in ways that prevent any meaningful result analysis the consistent use of controlled cancer vocabulary and com- across similar projects. We present a framework that uses a mon data elements (i.e., cancer metadata)—a key factor for combination of formal methods, model-driven development sharing data across clinical trials. Starting from a set of and service-oriented architecture (SOA) technologies to au- trial designs produced by means of this tool, an assembly tomate the generation of data management systems for can- of software artefact generators build the complete code for cer clinical trial research, an area particularly affected by the services, electronic forms and documentation that com- these problems. The SOA solution generated by the frame- pose a trial management system.
    [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]
  • 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]
  • 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]
  • 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]
  • A Declarative Approach Based on Xforms
    Helsinki University of Technology Publications in Telecommunications Software and Multimedia Teknillisen korkeakoulun tietoliikenneohjelmistojen ja multimedian julkaisuja Espoo 2006 TML-A16 WEB USER INTERACTION - A DECLARATIVE APPROACH BASED ON XFORMS Mikko Honkala Dissertation for the degree of Doctor of Science in Technology to be presented with due permission of the Department of Computer Science and Engineering, for pub- lic examination and debate in Auditorium T2 at Helsinki University of Technology (Espoo, Finland) on the 12th of January, 2007, at 12 noon. Helsinki University of Technology Department of Computer Science and Engineering Telecommunications Software and Multimedia Laboratory Teknillinen korkeakoulu Tietotekniikan osasto Tietoliikenneohjelmistojen ja multimedian laboratorio Distribution: Helsinki University of Technology Telecommunications Software and Multimedia Laboratory P.O.Box 5400 FIN-02015 HUT Tel. +358-9-451 2870 Fax. +358-9-451 5014 c Mikko Honkala ISBN-13 978-951-22-8565-5 ISBN-10 951-22-8565-7 ISSN 1456-7911 ISBN-13 978-951-22-8566-2 (PDF) ISBN-10 951-22-8566-5 (PDF) ISSN 1455 9722 (PDF) URL: http://lib.tkk.fi/Diss/ Otamedia Oy Espoo 2006 ABSTRACT Author Mikko Honkala Title Web User Interaction - a Declarative Approach Based on XForms Published Doctoral thesis, Helsinki University of Technology, 2006 Keywords XML, User Interfaces, User Interaction, XForms, UIDL, XHTML This thesis studies next-generation web user interaction definition languages, as well as browser software architectures. The motivation comes from new end-user requirements for web applications: demand for higher interaction, adaptation for mobile and multimodal usage, and rich multimedia content. At the same time, there is a requirement for non- programmers to be able to author, customize, and maintain web user interfaces.
    [Show full text]
  • SMIL and SVG in Teaching
    SMIL and SVG in teaching Horst Eidenberger* Vienna University of Technology, Institute of Software Technology and Interactive Systems, Favoritenstrasse 9-11, 1040 Vienna, Austria ABSTRACT This paper describes how the web standards Synchronized Multimedia Integration Language (SMIL) and Scalable Vector Graphics (SVG) are used in teaching at the Vienna University of Technology. SMIL and SVG are used in courses on multimedia authoring. Didactically, the goal is to teach students how to use media objects and timing concepts to build interactive media applications. Additionally, SMIL is applied to generate multimedia content from a database using a content management system. The paper gives background information on the SMIL and SVG standards and sketches how teaching multimedia is organised at the Vienna University of Technology. Courses from the summer term 2003 are described and illustrated in two case studies. General design problems of SMIL-based presentations are modelled as patterns. Additionally, suggestions for improvement in the standards are given and shortcomings of existing user agents are summarised. Our conclusion is that SMIL and SVG are very well suited for teaching multimedia. Currently, the main problem is that all existing SMIL players lack some properties desired for teaching applications (stability, correctness, etc.). Keywords: Multimedia authoring, Synchronized Multimedia Integration Language, SMIL, Scalable Vector Graphics, SVG, content management, CMS, education, case study, personalisation, CC/PP 1. INTRODUCTION In recent years universities all over the world and, especially, in the German-speaking countries, that offer computer engineering studies have established courses on multimedia and temporal media processing. So at the Vienna University of Technology. Since the year 2000 it offers a very popular media informatics curriculum (about 350 beginners per year).
    [Show full text]
  • Multiplatformní GUI Toolkity GTK+ a Qt
    Multiplatformní GUI toolkity GTK+ a Qt Jan Outrata KATEDRA INFORMATIKY UNIVERZITA PALACKÉHO V OLOMOUCI GUI toolkit (widget toolkit) (1) = programová knihovna (nebo kolekce knihoven) implementující prvky GUI = widgety (tlačítka, seznamy, menu, posuvník, bary, dialog, okno atd.) a umožňující tvorbu GUI (grafického uživatelského rozhraní) aplikace vlastní jednotný nebo nativní (pro platformu/systém) vzhled widgetů, možnost stylování nízkoúrovňové (Xt a Xlib v X Windows System a libwayland ve Waylandu na unixových systémech, GDI Windows API, Quartz a Carbon v Apple Mac OS) a vysokoúrovňové (MFC, WTL, WPF a Windows Forms v MS Windows, Cocoa v Apple Mac OS X, Motif/Lesstif, Xaw a XForms na unixových systémech) multiplatformní = pro více platforem (MS Windows, GNU/Linux, Apple Mac OS X, mobilní) nebo platformově nezávislé (Java) – aplikace může být také (většinou) událostmi řízené programování (event-driven programming) – toolkit v hlavní smyčce zachytává události (uživatelské od myši nebo klávesnice, od časovače, systému, aplikace samotné atd.) a umožňuje implementaci vlastních obsluh (even handler, callback function), objektově orientované programování (objekty = widgety aj.) – nevyžaduje OO programovací jazyk! Jan Outrata (Univerzita Palackého v Olomouci) Multiplatformní GUI toolkity duben 2015 1 / 10 GUI toolkit (widget toolkit) (2) language binding = API (aplikační programové rozhraní) toolkitu v jiném prog. jazyce než původní API a toolkit samotný GUI designer/builder = WYSIWYG nástroj pro tvorbu GUI s využitím toolkitu, hierarchicky skládáním prvků, z uloženého XML pak generuje kód nebo GUI vytvoří za běhu aplikace nekomerční (GNU (L)GPL, MIT, open source) i komerční licence např. GTK+ (C), Qt (C++), wxWidgets (C++), FLTK (C++), CEGUI (C++), Swing/JFC (Java), SWT (Java), JavaFX (Java), Tcl/Tk (Tcl), XUL (XML) aj.
    [Show full text]