DOCSLIB.ORG

Tema I Introducción a X-Window System (16 De Febrero De 2011)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tema I Introducción a X-Window System (16 De Febrero De 2011) Tema I Introducci´ona X-Window System (16 de febrero de 2011) Programaci´onen Entornos Interactivos. 16 de febrero de 2011 Dpto. Lenguajes y Sistemas Inform´aticos Universidad de Alicante 1 / 20 Resumen Visi´ongeneral de X-Window System. Uso de X-Window System. Configuraci´ona varios niveles de X-Window System. Ejecuci´onde aplicaciones en X-Window System. 2 / 20 Preliminares. • Desarrollado en el MIT con ayuda de DEC. • Las versiones m´asimportantes: X10 y X11 • Adoptado como est´andar por una serie de vendedores Hardware y Software. • Disponible en la mayor´ıade sistemas Unix. • No define un estilo de interfaz est´andar. 3 / 20 Preliminares. • Desarrollado en el MIT con ayuda de DEC. • Las versiones m´asimportantes: X10 y X11 • Adoptado como est´andar por una serie de vendedores Hardware y Software. • Disponible en la mayor´ıade sistemas Unix. • No define un estilo de interfaz est´andar. 3 / 20 Preliminares. • Desarrollado en el MIT con ayuda de DEC. • Las versiones m´asimportantes: X10 y X11 • Adoptado como est´andar por una serie de vendedores Hardware y Software. • Disponible en la mayor´ıade sistemas Unix. • No define un estilo de interfaz est´andar. 3 / 20 Preliminares. • Desarrollado en el MIT con ayuda de DEC. • Las versiones m´asimportantes: X10 y X11 • Adoptado como est´andar por una serie de vendedores Hardware y Software. • Disponible en la mayor´ıade sistemas Unix. • No define un estilo de interfaz est´andar. 3 / 20 Preliminares. • Desarrollado en el MIT con ayuda de DEC. • Las versiones m´asimportantes: X10 y X11 • Adoptado como est´andar por una serie de vendedores Hardware y Software. • Disponible en la mayor´ıade sistemas Unix. • No define un estilo de interfaz est´andar. 3 / 20 Modelo Cliente-Servidor • La arquitectura de X-Window System se basa en el modelo Cliente-Servidor. • Existe un ´unicoproceso servidor que se encarga de gestionar todos los dispositivos de entrada y salida. • Cualquier aplicaci´onque use las facilidades proporcionadas por el servidor X, se denomina cliente. • Los clientes se comunican con el servidor de manera as´ıncronaa trav´esde una red. Esta comunicaci´onpuede ser N a N. • Esto permite que el servidor y un cliente puedan estar ejecut´andose en distintas m´aquinasconectadas en red. • Lo primero que debe hacer un cliente es abrir una conexi´oncon el servidor. Desde ese momento puede usar cualquier screen que sea controlada por el servidor. 4 / 20 Modelo Cliente-Servidor • La arquitectura de X-Window System se basa en el modelo Cliente-Servidor. • Existe un ´unicoproceso servidor que se encarga de gestionar todos los dispositivos de entrada y salida. • Cualquier aplicaci´onque use las facilidades proporcionadas por el servidor X, se denomina cliente. • Los clientes se comunican con el servidor de manera as´ıncronaa trav´esde una red. Esta comunicaci´onpuede ser N a N. • Esto permite que el servidor y un cliente puedan estar ejecut´andose en distintas m´aquinasconectadas en red. • Lo primero que debe hacer un cliente es abrir una conexi´oncon el servidor. Desde ese momento puede usar cualquier screen que sea controlada por el servidor. 4 / 20 Modelo Cliente-Servidor • La arquitectura de X-Window System se basa en el modelo Cliente-Servidor. • Existe un ´unicoproceso servidor que se encarga de gestionar todos los dispositivos de entrada y salida. • Cualquier aplicaci´onque use las facilidades proporcionadas por el servidor X, se denomina cliente. • Los clientes se comunican con el servidor de manera as´ıncronaa trav´esde una red. Esta comunicaci´onpuede ser N a N. • Esto permite que el servidor y un cliente puedan estar ejecut´andose en distintas m´aquinasconectadas en red. • Lo primero que debe hacer un cliente es abrir una conexi´oncon el servidor. Desde ese momento puede usar cualquier screen que sea controlada por el servidor. 4 / 20 Modelo Cliente-Servidor • La arquitectura de X-Window System se basa en el modelo Cliente-Servidor. • Existe un ´unicoproceso servidor que se encarga de gestionar todos los dispositivos de entrada y salida. • Cualquier aplicaci´onque use las facilidades proporcionadas por el servidor X, se denomina cliente. • Los clientes se comunican con el servidor de manera as´ıncronaa trav´esde una red. Esta comunicaci´onpuede ser N a N. • Esto permite que el servidor y un cliente puedan estar ejecut´andose en distintas m´aquinasconectadas en red. • Lo primero que debe hacer un cliente es abrir una conexi´oncon el servidor. Desde ese momento puede usar cualquier screen que sea controlada por el servidor. 4 / 20 Modelo Cliente-Servidor • La arquitectura de X-Window System se basa en el modelo Cliente-Servidor. • Existe un ´unicoproceso servidor que se encarga de gestionar todos los dispositivos de entrada y salida. • Cualquier aplicaci´onque use las facilidades proporcionadas por el servidor X, se denomina cliente. • Los clientes se comunican con el servidor de manera as´ıncronaa trav´esde una red. Esta comunicaci´onpuede ser N a N. • Esto permite que el servidor y un cliente puedan estar ejecut´andose en distintas m´aquinasconectadas en red. • Lo primero que debe hacer un cliente es abrir una conexi´oncon el servidor. Desde ese momento puede usar cualquier screen que sea controlada por el servidor. 4 / 20 Modelo Cliente-Servidor • La arquitectura de X-Window System se basa en el modelo Cliente-Servidor. • Existe un ´unicoproceso servidor que se encarga de gestionar todos los dispositivos de entrada y salida. • Cualquier aplicaci´onque use las facilidades proporcionadas por el servidor X, se denomina cliente. • Los clientes se comunican con el servidor de manera as´ıncronaa trav´esde una red. Esta comunicaci´onpuede ser N a N. • Esto permite que el servidor y un cliente puedan estar ejecut´andose en distintas m´aquinasconectadas en red. • Lo primero que debe hacer un cliente es abrir una conexi´oncon el servidor. Desde ese momento puede usar cualquier screen que sea controlada por el servidor. 4 / 20 Conceptos Display y Screen • Denominaremos display a un ´unico proceso servidor de X. • Este display atiende, normalmente, a un rat´on,un teclado y un monitor. • Denominaremos screen al monitor en el que se realiza la salida gr´afica. • Un display X puede soportar diversos screens. • Antiguamente se sol´ıausar los t´erminosde display y screen intercambiadamente. 5 / 20 Conceptos Display y Screen • Denominaremos display a un ´unico proceso servidor de X. • Este display atiende, normalmente, a un rat´on,un teclado y un monitor. • Denominaremos screen al monitor en el que se realiza la salida gr´afica. • Un display X puede soportar diversos screens. • Antiguamente se sol´ıausar los t´erminosde display y screen intercambiadamente. 5 / 20 Conceptos Display y Screen • Denominaremos display a un ´unico proceso servidor de X. • Este display atiende, normalmente, a un rat´on,un teclado y un monitor. • Denominaremos screen al monitor en el que se realiza la salida gr´afica. • Un display X puede soportar diversos screens. • Antiguamente se sol´ıausar los t´erminosde display y screen intercambiadamente. 5 / 20 Conceptos Display y Screen • Denominaremos display a un ´unico proceso servidor de X. • Este display atiende, normalmente, a un rat´on,un teclado y un monitor. • Denominaremos screen al monitor en el que se realiza la salida gr´afica. • Un display X puede soportar diversos screens. • Antiguamente se sol´ıausar los t´erminosde display y screen intercambiadamente. 5 / 20 Conceptos Display y Screen • Denominaremos display a un ´unico proceso servidor de X. • Este display atiende, normalmente, a un rat´on,un teclado y un monitor. • Denominaremos screen al monitor en el que se realiza la salida gr´afica. • Un display X puede soportar diversos screens. • Antiguamente se sol´ıausar los t´erminosde display y screen intercambiadamente. 5 / 20 Peticiones -Requests- • Cualquier petici´onde servicio que quiera llevar a cabo un cliente es solicitada por ´esteal servidor -crear y destruir ventanas, realizar salida gr´afica,etc. -. • El Servidor X se ejecuta de manera as´ıncrona∗ respecto a los clientes, y ´estosrespecto al servidor. • Las peticiones no tienen porqu´eser atendidas por el servidor en el orden en el que llegaron, tampoco de manera inmediata. Estas peticiones van a parar a una cola. 6 / 20 Peticiones -Requests- • Cualquier petici´onde servicio que quiera llevar a cabo un cliente es solicitada por ´esteal servidor -crear y destruir ventanas, realizar salida gr´afica,etc. -. • El Servidor X se ejecuta de manera as´ıncrona∗ respecto a los clientes, y ´estosrespecto al servidor. • Las peticiones no tienen porqu´eser atendidas por el servidor en el orden en el que llegaron, tampoco de manera inmediata. Estas peticiones van a parar a una cola. 6 / 20 Peticiones -Requests- • Cualquier petici´onde servicio que quiera llevar a cabo un cliente es solicitada por ´esteal servidor -crear y destruir ventanas, realizar salida gr´afica,etc. -. • El Servidor X se ejecuta de manera as´ıncrona∗ respecto a los clientes, y ´estosrespecto al servidor. • Las peticiones no tienen porqu´eser atendidas por el servidor en el orden en el que llegaron, tampoco de manera inmediata. Estas peticiones van a parar a una cola. 6 / 20 Ventanas (I) • Constituyen uno de los conceptos clave en X. Son un ´arearectangular de la pantalla. • No tienen t´ıtulo,barras de desplazamiento (scroll) u otros adornos, solo un borde delimitador. • Se pueden combinar varias ventanas para crear t´ıtulos,barras de scroll, etc. • Una ventana se crea a petici´onde un cliente, pero puede ser manipulada por peticiones de cualquier otro. • Las ventanas se organizan jer´arquicamente(toda ventana tiene un ascendente), siendo la ventana principal la que se denomina ventana ra´ız(root window), la cual no tiene ascendente. 7 / 20 Ventanas (I) • Constituyen uno de los conceptos clave en X. Son un ´arearectangular de la pantalla.
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]
  • VTWM Vtwm, Aka Virtual Tabbed Window Manager, Est Né En 1992 Sur Les Sources De Twm En Y Ajoutant La Gestion Des Bureaux Virtuels
    VTWM vtwm, aka Virtual Tabbed Window Manager, est né en 1992 sur les sources de twm en y ajoutant la gestion des bureaux virtuels. c'est un gestionnaire de fenêtre ultra basic mais avec de nombreuses options. ancien, il se configure depuis un unique fichier ~/.vtwmrc. c'est un 'floating', c'est à dire qu'il laisse l'utilisateur placer les fenêtres. il est rapide, réactif et très léger. il convient parfaitement pour les petites configurations matérielles. Sommaire VTWM.................................................................................................................................1 Screenshots....................................................................................................................1 installation......................................................................................................................2 composants....................................................................................................................2 configuration...................................................................................................................2 utilisation........................................................................................................................3 Screenshots 1 installation vtwm est présent dans les dépots de la plupart des distributions. pour Debian, dans un terminal: # apt-get install vtwm composants la session vtwm dispose de plusieurs éléments: • IconManager : une boite à icones servant aussi de tasklist. • VirtualDesktop : un pager simple. • Vtwm
    [Show full text]
  • October 13, 1983 Oste (W,G-6Axl,Fl)7A Battles at Schoolcraft Gym Vs
    Volume 19 Number 32 Thursday. Ootober 13.1983 * Westland, Michigan Twenty-five cents Ji-v&'> :'-r- :::mm.mm§. io^gjafc^rj^-^fetr^i^.al^^Ti^.ik Ml: ^ii^ilMiilllS ••, v.- .:-i :-, i c-..-... -V • '». : ( • lyt:.-.-. v:| Ki,-1:. ki .• r. Candidates call for development at chamber lunch By 8andrs Armbru«tsr Asked If such Illegal transfers were editor made while he was finance director, Herbert said, "Absolutely not. Three Gearing remarks to the concerns of years ago the city had a $1 million sur­ their business audience, six of v eight plus, There wasn't the need. Why would candidates running for city council ad­ anyone do that with a surplus?" dressed Issues concerning Westland's economic development during speeches QUESTIONING Herbert about the before the chamber of commerce. surplus, Elizabeth Davis, Pickering's But it was Mayor Charles Pickering secretary, asked why there was a defi­ who fired the opening salvo during the cit when the mayor took office. • question and answer period by charg­ "There was $1.7 million In the banks ing that the "incumbents are running and on deposit when I walked out the their campaign based on my record, door," said Pickering. not theirs." . He admitted, however, that his de­ Pickering asked Councilman Kent partment had predicted a $300,000 def­ Herbert, whose appointment the mayor icit by June that year and had submit­ had vetoed, if he would accept blame ted a plan on how it should be handled. for "bad deals" made while Herbert "Unfortunately, nothing was done," was the city's finance director.
    [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]
  • The Complete Solutions Guide for Every Linux/Windows System Administrator!
    Integrating Linux and Windows Integrating Linux and Windows By Mike McCune Publisher : Prentice Hall PTR Pub Date : December 19, 2000 ISBN : 0-13-030670-3 • Pages : 416 The complete solutions guide for every Linux/Windows system administrator! This complete Linux/Windows integration guide offers detailed coverage of dual- boot issues, data compatibility, and networking. It also handles topics such as implementing Samba file/print services for Windows workstations and providing cross-platform database access. Running Linux and Windows in the same environment? Here's the comprehensive, up-to-the-minute solutions guide you've been searching for! In Integrating Linux and Windows, top consultant Mike McCune brings together hundreds of solutions for the problems that Linux/Windows system administrators encounter most often. McCune focuses on the critical interoperability issues real businesses face: networking, program/data compatibility, dual-boot systems, and more. You'll discover exactly how to: Use Samba and Linux to deliver high-performance, low-cost file and print services to Windows workstations Compare and implement the best Linux/Windows connectivity techniques: NFS, FTP, remote commands, secure shell, telnet, and more Provide reliable data exchange between Microsoft Office and StarOffice for Linux Provide high-performance cross-platform database access via ODBC Make the most of platform-independent, browser-based applications Manage Linux and Windows on the same workstation: boot managers, partitioning, compressed drives, file systems, and more. For anyone running both Linux and Windows, McCune delivers honest and objective explanations of all your integration options, plus realistic, proven solutions you won't find anywhere else. Integrating Linux and Windows will help you keep your users happy, your costs under control, and your sanity intact! 1 Integrating Linux and Windows 2 Integrating Linux and Windows Library of Congress Cataloging-in-Publication Data McCune, Mike.
    [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]
  • 2009 Št Pán Zelman Ě
    tato strana je na pevných deskách Jiho eská univerzita v eských Bud jovicích Pedagogická fakulta BAKALÁ SKÁ PRÁCE 2009 t pán Zelman JIHO ESKÁ UNIVERZITA V ESKÝCH BUD JOVICÍCH PEDAGOGICKÁ FAKULTA KATEDRA FYZIKY BAKALÁ SKÁ PRÁCE Gentoo Linux Vedoucí práce: Ing. Michal erý Vypracovala: t pán Zelman Studijní obor: M ící a výpo etní technika eské Bud jovice, 2009 1 Anotace: Bakalá ská práce si klade za cíl prozkoumat vyuitelnost linuxových distribucí na desktopech, shrnout základní rozdíly mezi linuxovými distribucemi a ostatními opera ními systémy (zejména momentáln nej ast ji se vyskytujícími desktopovými systémy Windows XP a Windows Vista) a objektivn shrnout pozitivní a negativní stránky nasazení linuxové distribuce na desktopu. Sou ástí práce je podrobný popis nej ast ji se vyskytujících komponent linuxové distribuce ur ené pro desktop i notebook a stru ný souhrn nejpopulárn jích distribucí zam ených na uivatele stolních po íta a notebook . Samostatná kapitola je v nována podrobnému popisu distribuce Gentoo Linux, která je od ostatních distribucí v mnoha aspektech odliná, dalí kapitola je v nována praktickému nasazení Linuxu na desktopy ve firemním prost edí. Záv r práce je v nován monostem pouití programovacího jazyka BASIC typického pro prost edí MS-DOS a Windows v linuxových distribucích. Annotation: The aim of this bachelor work is a reconnaissance of using linux distribution on desktop,to summarize the basic differences between linux distributions and the other operation systems(especially the most frequently used desktops system like WindowsXP and Windows Vista) and to summarize objectively a positive and a negative aspects of setting of linux distribution on the desktop.
    [Show full text]