DOCSLIB.ORG

This Material Is Posted Here with Permission of the IEEE. Such

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
This Material Is Posted Here with Permission of the IEEE. Such This material is posted here with permission of the IEEE. Such permission of the IEEE does not in any way imply IEEE endorsement of any of Helsinki University of Technology's products or services. Internal or personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution must be obtained from the IEEE by writing to [email protected]. By choosing to view this document, you agree to all provisions of the copyright laws protecting it. ©2004 IEEE. Reprinted, with permission, from Proc. of the IEEE Sixth International Symposium on Multimedia Software Engineering (MSE2004), Miami, FL, USA, December, 2004, pages 232-239. A Configurable XForms Implementation Mikko Honkala Petri Vuorimaa Helsinki University of Technology, TML Helsinki University of Technology, TML P.O. Box 5400, FIN-02015 HUT, FINLAND P.O. Box 5400, FIN-02015 HUT, FINLAND Mikko.Honkala@hut.fi Petri.Vuorimaa@hut.fi Abstract scripting and markup can be cumbersome, since it creates semantic and performance discontinuities [4]. XForms is a new language for defining dynamic forms Interaction in an application often depends on the device and user interfaces for the World Wide Web. In order to and environment at hand. For instance, the interaction with take advantage of the user interaction related features in a mouse and a desktop computer differs from the interac- the language, a client side processor is needed. This paper tion with a smartphone, let alone speech interaction with a describes a configurable open source software implementa- normal phone. The traditional interaction technologies usu- tion of XForms. The main goal of the implementation is to ally target just one environment or device. Applications run- conform to the World Wide Web Consortium’s XForms Rec- ning in the WWW can be accessed with different kinds of ommendation. The other goals are external to the XForms devices, but still the interaction is usually designed to just specification and are related to the portability and config- one or few different usage environments. Due to limitations urability of the processor. The important questions are re- in HTML forms, it is not easy to target the same applica- lated to implementing an XForms processor for diverse en- tion to different devices. vironments, and the integration of XForms and other XML Due to these problems, W3C has developed a successor languages with different layout models. In the paper, more to HTML forms, XForms [5]. It removes need for scripts, detailed requirements are gathered from these goals. Also, and separates content from the presentation. Furthermore, the design and implementation are presented in detail, in it uses an abstraction of an user interface, enabling inter- order to give insight to the more difficult and non-obvious action across different modalities and devices. Other im- parts of the software. The results of the paper cover the run- portant questions are related to implementing an XForms time requirements of the XForms processor. processor for diverse environments, and the integration of XForms and other XML languages with different layout models. Currently, the most interoperable option for developing a cross-platform client, (i.e., a browser), is Java. Programs 1. Introduction written in Java can be run in desktops, smartphones and digital-TV set-top boxes. All of them have different libraries Although HyperText Markup Language (HTML), the available, though. main content language of the World Wide Web, was orig- There are XML-based form technologies that predate inally just a document description language, lately WWW XForms, including XFDL 1 and XFA 2. Also, there is cur- has been transformed into a platform for interactive services rently a lot of effort put into XML-based GUI technologies. [1]. HTML, being a device and operating-system indepen- Some of them are mainly designed for defining GUIs for dent, is still used to describe the user interface of the ser- stand alone applications, including Glade 3, Netscape XUL vices. However, the GUI technology behind the services, 4 and Microsoft XAML 5 , while some address the office HTML forms, is now outdated. The complexity of today’s applications is far greater than what was imagined when the 1 Extensible Forms Description Language (XFDL) 4.0, John Boyer, technology was first invented. Therefore, today’s high-end Tim Bray, Maureen Gordon, 2 September 1998. Available at: forms have to use complex client-side ECMAScript [2] pro- http://www.w3.org/TR/NOTE-XFDL 2 XFA-Template Version 1.0, Gavin McKenzie, 14 June 1999. Avail- gramming to achieve form field validation and simple com- able at: http://www.w3.org/1999/05/XFA/xfa-formcalc.html putations (or bounce the form back and forth to the server). 3 Glade. Available at: http://glade.gnome.org/ Heavy use of scripting inevitably leads to low maintain- 4 XML User Interface Language (XUL) 1.0, David Hyatt (ed.), Avail- ability and accessibility [3]. Also, for the author, using both able at: http://www.mozilla.org/projects/xul/xul.html application space, namely InfoPath 6 . The configurable im- plementation reported in this paper is based on an earlier prototype the authors have made [6]. Dynamic calculations, and their implementation within XForms have been stud- ied in [3]. Dynamic user interfaces, such as repeating con- structs have been studied in [7]. The relationship between the latest XHTML 2.0 and XForms has been described in [8]. 2. The XForms language XForms 1.0 Recommendation [5] is the next-generation Figure 2. The external requirements. Web forms language. It solves some of the problems found in the HTML forms by separating the purpose from the pre- sentation and using declarative markup to describe the most it’s use is optional to the author. The Model Item Proper- common operations in form-based applications. ties (MIP) are dynamic constraints written in XPath. They can reference other values in the instance data and are dy- namically evaluated by the XForms Processor. With MIPs, it is possible to define dynamic calculations and cross-value checks, which are not possible with XML Schema. Fig. 1 also depicts the typical usage scenario of XForms. It consists of a client, which includes an XForms processor and an HTTP server with application specific software. The user interface of the application is defined with static doc- uments, written in XForms combined with a host language, such as XHTML. Similarly, the structure of the data is de- scribed with static XML Schema documents. The applica- tion logic is responsible for sending and receiving XML in- stance data, which correspond to the data gathered from the user. Compared to current Web applications with HTML, a lot Figure 1. The XForms layers. of the user interface processing is transferred to the client in XForms. This frees bandwith and improves the user expe- rience. Additionally, the application data is separated from XForms separates the form into three main lay- the user interface, which helps to build modular software, ers: Model, Instance, and User Interface (cf. Fig. 1). which is easier to maintain. Instance An arbitrary XML document that is modified by Because of the quite heavy dependencies on XML pro- clientside user interaction, then submitted to a server. cessing tools, such as XML Schema and XPath, XForms may be difficult to implement in a restricted device, such as Model Uses XML to define the constraints on items of the a smartphone. To overcome this problem, W3C has speci- instance, which includes data types and ranges as well fied a smaller profile of the language, called XForms Basic as computational relationships. [9], which does not include full Schema capabilities. User Interface Defines how the form is shown and ex- presses bindings to instance items. User input is gov- 3. Requirements for the XForms processor erned by rules in the model for the instance item being modified (through a bound input control). The requirements for the XForms processor come from The Model layer includes the XML Schema and the multiple directions. The main goals can be divided into five Model Item Properties. The structure and the data types categories, as depicted in Fig. 2. The main goal was to have of the instance data can be defined using the schema, but a conforming XForms processor. The other goals were ex- ternal to the XForms specification and were related to the 5 XAML, Available at: http://msdn.microsoft.com/. portability and configurability of the processor. They are 6 Microsoft InfoPath, Available at: Java VM support, XML Processing Libraries, UI Toolk- http://www.microsoft.com/office/infopath/prodinfo/default.mspx its, and Host Languages. The requirements that we derived from these goals are described in detail in the following list. These requirements are the focus of the implementation part of this paper. XForms Processor: Requirements. XForms Full XForms 1.0 Support. XForms Basic Can be configured to run in XForms Basic mode with reduced processing. Java VM Support: Requirements. Desktop Java 2 Standard Edition (J2SE) support. Personal Java Runs in Personal Java 1.1 and Java 2 Micro Edition (J2ME) Personal Profile. Figure 3. The architecture of the processor. MHP Multimedia Home Platform (MHP) support. XML Processing: Requirements. <bind nodeset="items/item/total" XML Should allow third party XML parser, XPath, calculate="../units * ../price" and XML Schema libraries. relevant="../units > 0" /> UI Toolkits: Requirements. <bind nodeset="totals/subtotal" Swing Supports Swing Toolkit in Desktop. calculate= "sum(../../items/item/total)"/> AWT Supports Abstract Windowing Toolkit (AWT). <bind nodeset="totals/tax" Havi Uses Havi Toolkit in digital tv set-top boxes. calculate="../subtotal * Host Languages: Requirements. ../../info/tax"/> CSS Languages Supports CSS flow and box model.
Load more

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]
  • 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]
  • 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]
  • 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]
  • 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]
  • List of Versions Added in ARL #2547 Publisher Product Version
    List of Versions Added in ARL #2547 Publisher Product Version 2BrightSparks SyncBackLite 8.5 2BrightSparks SyncBackLite 8.6 2BrightSparks SyncBackLite 8.8 2BrightSparks SyncBackLite 8.9 2BrightSparks SyncBackPro 5.9 3Dconnexion 3DxWare 1.2 3Dconnexion 3DxWare Unspecified 3S-Smart Software Solutions CODESYS 3.4 3S-Smart Software Solutions CODESYS 3.5 3S-Smart Software Solutions CODESYS Automation Platform Unspecified 4Clicks Solutions License Service 2.6 4Clicks Solutions License Service Unspecified Acarda Sales Technologies VoxPlayer 1.2 Acro Software CutePDF Writer 4.0 Actian PSQL Client 8.0 Actian PSQL Client 8.1 Acuity Brands Lighting Version Analyzer Unspecified Acuity Brands Lighting Visual Lighting 2.0 Acuity Brands Lighting Visual Lighting Unspecified Adobe Creative Cloud Suite 2020 Adobe JetForm Unspecified Alastri Software Rapid Reserver 1.4 ALDYN Software SvCom Unspecified Alexey Kopytov sysbench 1.0 Alliance for Sustainable Energy OpenStudio 1.11 Alliance for Sustainable Energy OpenStudio 1.12 Alliance for Sustainable Energy OpenStudio 1.5 Alliance for Sustainable Energy OpenStudio 1.9 Alliance for Sustainable Energy OpenStudio 2.8 alta4 AG Voyager 1.2 alta4 AG Voyager 1.3 alta4 AG Voyager 1.4 ALTER WAY WampServer 3.2 Alteryx Alteryx Connect 2019.4 Alteryx Alteryx Platform 2019.2 Alteryx Alteryx Server 10.5 Alteryx Alteryx Server 2019.3 Amazon AWS Command Line Interface 1 Amazon AWS Command Line Interface 2 Amazon AWS SDK for Java 1.11 Amazon CloudWatch Agent 1.20 Amazon CloudWatch Agent 1.21 Amazon CloudWatch Agent 1.23 Amazon
    [Show full text]
  • An MVC-Based Intelligent Document Model Using UIML
    Information 2015, 6, 122-133; doi:10.3390/info6020122 OPEN ACCESS information ISSN 2078-2489 www.mdpi.com/journal/information Article An MVC-based Intelligent Document Model Using UIML Yunmei Shi *, Xuhong Liu †, Ning Li † and Xia Hou Computer School, Beijing Information Science & Technology University, No 35 Beisihuan Zhonglu, Chaoyang District, Beijing 100101, China; E-Mails: [email protected] (X.L.); [email protected] (N.L.); [email protected] (X.H.) † These authors contributed equally to this work. * Author to whom correspondence should be addressed; E-Mail: [email protected]; Tel./Fax: +86-10-6488-4434. Academic Editor: Willy Susilo Received: 29 December 2014 / Accepted: 11 March 2015 /Published: 27 March 2015 Abstract: Aiming at the common problems of intelligent document platform-dependency, this paper proposes an MVC-based (Model View Controller-based) intelligent document model using UIML (User Interface Markup Language). The model is made on the basis of the previous work of our team, and the difference is that the new model separates user interface and interaction descriptions from the view component to make the intelligent document model much more independent of platform and programming language. To verify the intelligent document model, we implemented a prototype, which can support intelligent operations. The test result shows that our approach is correct. The model not only follows MVC framework, but also provides good flexibility and independence. Keywords: intelligent document; user interface; UIML; MVC 1. Introduction Traditionally, a document can only display content by office software according to the static description information of the document. These kinds of documents are usually called “static documents”, whose characteristic is lacking of interactivity and operability.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • X Window System Architecture Overview HOWTO
    X Window System Architecture Overview HOWTO Daniel Manrique [email protected] Revision History Revision 1.0.1 2001−05−22 Revised by: dm Some grammatical corrections, pointed out by Bill Staehle Revision 1.0 2001−05−20 Revised by: dm Initial LDP release. This document provides an overview of the X Window System's architecture, give a better understanding of its design, which components integrate with X and fit together to provide a working graphical environment and what choices are there regarding such components as window managers, toolkits and widget libraries, and desktop environments. X Window System Architecture Overview HOWTO Table of Contents 1. Preface..............................................................................................................................................................1 2. Introduction.....................................................................................................................................................2 3. The X Window System Architecture: overview...........................................................................................3 4. Window Managers..........................................................................................................................................4 5. Client Applications..........................................................................................................................................5 6. Widget Libraries or toolkits...........................................................................................................................6
    [Show full text]
  • Debian Build Dependecies
    Debian build dependecies Valtteri Rahkonen valtteri.rahkonen@movial.fi Debian build dependecies by Valtteri Rahkonen Revision history Version: Author: Description: 2004-04-29 Rahkonen Changed title 2004-04-20 Rahkonen Added introduction, reorganized document 2004-04-19 Rahkonen Initial version Table of Contents 1. Introduction............................................................................................................................................1 2. Required source packages.....................................................................................................................2 2.1. Build dependencies .....................................................................................................................2 2.2. Misc packages .............................................................................................................................4 3. Optional source packages......................................................................................................................5 3.1. Build dependencies .....................................................................................................................5 3.2. Misc packages ...........................................................................................................................19 A. Required sources library dependencies ............................................................................................21 B. Optional sources library dependencies .............................................................................................22
    [Show full text]
  • Slobodan Softver U Obrazovanju
    I SVEUČILIŠTE U ZAGREBU UČITELJSKI FAKULTET Slobodan softver u obrazovanju Predrag Oreški Vladimir Šimović Zagreb, 2013. II Izdavač Učiteljski fakultet Sveučilišta u Zagrebu Savska cesta 77, Zagreb Za izdavača dr. sc. Ivan Prskalo, redoviti profesor Urednik dr. sc. Vladimir Šimović, redoviti profesor Recenzenti dr. sc. Nenad Prelog, redoviti profesor dr. sc. Ljubica Bakić Tomić, izvanredni profesor dr. sc. Dragutin Kermek, izvanredni profesor Lektorica Zdenka Župan Milković, prof. Ilustracija na naslovnici: Vector Open Stock Team, http://www.vectoropenstock.com/963-Vector-abstract-tree-vector Attribution No Derivatives 3.0 Unported License Prijelom: Nataša Rogulja Naklada 200 tiskanih primjeraka + online izdanje UDK 004.4.057.8:37 373.3:004 ISBN 978-953-7210-63-2 Tisak dovršen u 2013. Ovo djelo je dano na korištenje pod licencijom Creative Commons Imenovanje-Nekomercijalno-Bez prerada 3.0 nelokalizirana licencija. http://creativecommons.org/licenses/by-nc-nd/3.0/deed.hr III IV Sadržaj Predgovor ....................................................................................................................... VII Sažetak ......................................................................................................................... VIII 1. Uvod .............................................................................................................................. 1 2. Intelektualno vlasništvo ................................................................................................ 8 2.1. Intelektualno vlasništvo
    [Show full text]