DOCSLIB.ORG

The DELPHI Run Database Presenter

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The DELPHI Run Database Presenter DELPHI Collaboration DELPHI 94-2 DAS 146 January 1994 The DELPHI Run DataBase presenter R. Schulze2, B. Schulze1,2 ABSTRACT The DELPHI Run Database(DRDB) Presenter is a software tool to monitor the characteristics of the data taking contained in this database of the CERN DELPHI LEP experiment. The pertinent information residing on the DRDB data base is updated along with the experiment running. The Presenter enables the user to con- sult this information as a function of time, by means of simple listing, summaries or more elaborated histograms analysis. The DRDB Presenter is running under the VMS environment with an X based user interface developed using OSF/Motif, the interface builder VUIT and the CERN library HIGZ graphics tools. 1Universita di Roma II and INFN, Tor Vergata, I-00173 Rome, Italy 2 LAFEX/CBPF/CNPq, Rua Dr. Xavier Sigaud, 150, Urca, CEP 22290, Rio de Janeiro, Rj, Brazil 1 - Introduction In the data acquisition environment of an High Energy Physics detector it is very use- ful to give the user a natural access to the needed information, in particular when there is the stress of a potential problem. As other tools of the DELPHI experiment, the DRDB Pre- senter has been developed to provide the user with a friendly environment to follow the evolution of the data taking operation. The DRDB keeps track of runs recorded and of the status of process of the physics data.As such it is a bookkeeping data base containing information on the characteristics of the data taking such as run number, run start time, LEP fill number, magnet current, etc... The DRDB Presenter provides the user with the facilities to consult its content, make listings according to different formats, analysis through plots and statistics, make print-outs and refer to an on-line help. The implementation of this presenter is based on: a) already existing tools to manipulate the bookkeeping data base and the run time library of access routines, and b) new tools defined according to the user’s need. An X based interface was added integrating analysis plots & statistics, listing and an on-line help. With that interface one can navigate through the database and get a sensible follow up of the behavior of the data taking by tracing back and correlating problems. Section 2 presents on which basis the presenter was conceived, focusing on its pur- pose and its planning. Section 3 describes the software implementation after a brief descrip- tion of DELPHI On-line cluster, the structure of the User Interface, the languages, packages and tools used and how they were integrated. It also presents some examples of the current implementation. In section 4, we draw preliminary conclusion from the experience gained in running Version 1.0 in the experiment site. 2 Author 2 - Software conception 2.1 Software purpose The purpose of the DRDB Presenter is to provide a standard X11 framework to the former DRDB so that it could run at DELPHI on-line cluster and the display can be made on any remote X11 display connected through network, add new tools to it using graphics visualization, and provide the user with an easy-to-use package. 2.2 Design goals The DRDB Presenter was designed on a structured analysis basis to add new tools and also to incorporate the tools that already existed. The interface was planned on a “GUI” way (Graphical User Interface) characterized by: pull-down menus, multiple windows, icons, and mouse-driven commands, which implies thinking in an object-oriented approach. This software should be modular to allow easy portability. DRDB Plot details Display plots DRDB Plots Plots displayed Run,Fill,Date, details Detail of Generate option analysis analysis Statistics User’s Verify User’s Verify USER command command details Statistics Display displayed is valid of statistics USER command valid option Details of option Generate list listings Details Listings Listings option Display displayed listings List DRDB details DRDB Figure 2.1 An expansion of the DFD Author 3 3 - Software implementation 3.1 DELPHI On-line cluster The main on-line computer capacity is provided by a Local Area VAX Cluster run- ning VMS operating system. The principle component of the On-line cluster consists of two main frames VAX 6510 and VAX 8700 which are dedicated to handle the data flow from the central readout. By run By fill Plot / Listing Display By date X Protocol DecNet TCP/IP Plot / DRDB List Presenter DRDB file Write Data characteristics of the data physics CERN taking data LEP DELPHI Experiment Figure 3.1 DELPHI data flow for DRDB Presenter 3.2 Software Architecture For the implementation of the software, it was necessary to integrate different envi- ronments, following the short description below. For the user interface, it was decided to use OSF/Motif, generated with a Interface Builder, DEC-VUIT (Visual User Interface Tool). The main program which starts the appli- cation and runs as the Xclient is written in C. The routines to produce the plots display were 4 Author written in FORTRAN 77, using calls to the HIGZ/CERNLIB. All the other routines for checking, validation, etc were written in C. UIL Motif Toolkit XToolkit HIGZ XLibrary DRDB Toolkit Former DRDB VAX-VMS Requests/XEvents to /from XServer Display Figure 3.2 Hierarquical dependence of the DRDB Presenter In the present implementation, the interface is composed of two basics windows: one for the interface itself and another one for the plots. For the interface, it was created one main window using Motif widgets while for the plots, it was used the HIGZ default win- dow. The interface is an Xserver process running on the Xdisplay, talking to its correspond- ing Xclient process running on the cluster where the database resides. This client-server processing is already inherent to the usage of the Motif/X11 and the transport is either TCP/IP or DECnet. Callbacks Motif Interface Motif Motif Main Program (.UIL) string program (.C) struct System Calls Routines per RUN (.C) Routines per FILL (.C) DRDB List (DCL) DRDB Toolkit (.C) $DESCRIPTOR DRDB (.FOR) $DESCRIPTOR $DESCRIPTOR Routines make plot (.FOR) Figure 3.3 Diagram of routines Author 5 The basic integration of the different pieces and tools is based on the possibility to pass strings between these different parts. These strings can be seen as objects which con- tain basic pieces of information and which are either concatenated or split accordingly. To manipulate strings between C and FORTRAN and vice-versa, the $DESCRIPTOR (ref) structure is used, which is similar to an equivalent X structure which translates strings from the UIL to C. The basic fields in these structures are size, string and string type. They are needed since strings are seen differently by each language. While strings are used to inte- grate C and FORTRAN, they are also used to integrate the existing tools under DCL(VMS). For example, to implement the LIST module, command strings are issued with system calls, and the returned strings are send to a file, for print/list on the DRDB screen. 3.3 The structure of the User Interface Six basic modules are proposed: ■ DESCRIPTION: Display the description of the DRDB file. At the moment, it is implemented using the “label widget” from Motif which leads it to be static. ■ LIMITS: Selection of either run, fill intervals. Currently, only run limits is implemented. Fill limits and Date Limits are under implementation. ■ LIST: Lists the contents of the DRDB file. This module is being implemented as similar as possible to the one present in the former DRDB except that now the display is on an X11 window and the commands are available in a pull down menu. ■ ANALYSIS: Analysis of the run data either through “Plots” or “Statistics”. Pres- ently, only the module “Plots” is implemented. ■ PRINT: printout of the plots and of the listing. ■ HELP: Information on the DRDB Presenter such as how to use the presenter and how the presenter is organized. 3.4 Current implementation Presently, there is a version being tested at DELPHI with the appearance as shown by the next figures. 6 Author a d e c b Figure 3.4 User Interface Windows window a: Selection of limits to be used both by plot and by list modules; window b: Set first limit. In this example, it is showed the First Run window; window c: On-line help; window d: Plotting and/or listing; window e: An example of a plot. 3.4.1 Options available The following options are available for PLOTS: ■ a) DAS ■ Make plots for the DAS family according the interval given by the first & last run.The results are given per run or per fill, depending on the plot. For some plots average is also given. #TRIG/RUN Make plots with the number of triggers per run within the given interval; #TRIG/FILL Make plots with the number of triggers per fill within the given interval; Author 7 #TRIG/FILE Make plots with the number of triggers per file within the given interval. It also gives the average of the number of triggers per file; RUN DURATION Make plots for the duration of the run. The result is given in minutes. It also gives the average, in minutes, of the duration of the runs within the given interval; #FILES/RUN Make plots with the number of files per run. It also gives the average of the number of files per run; DAS Rate Make plots for the DAS Rate per fill. The result is given in Hz. It also gives the average, in Hz, of the DAS Rate within the given interval; RUN_LIVE Make plots for the Run_Live per run within a given interval; ■ b) LEP ■ Make plots for the LEP family according the interval given by the first & last run.The results are given per run or per fill, depending on the plot.
Load more

Recommended publications
  • User Interface Software Tools
    User Interface Software Tools Brad A. Myers August 1994 CMU-CS-94-182 School of Computer Science Carnegie Mellon University Pittsburgh, PA 15213 Also appears as Human-Computer Interaction Institute Technical Report CMU-HCII-94-107 This report supersedes CMU-CS-92-114 from February, 1992, published as: Brad A. Myers. ‘‘State of the Art in User Interface Software Tools,’’ Advances in Human- Computer Interaction, Volume 4. Edited by H. Rex Hartson and Deborah Hix. Norwood, NJ: Ablex Publishing, 1993. pp. 110-150. Abstract Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. This article discusses the different kinds of user interface software tools, and investigates why some approaches have worked and others have not. Many examples of commercial and research systems are included. Finally, current research directions and open issues in the field are discussed. This research was sponsored by NCCOSC under Contract No. N66001-94-C-6037, ARPA Order No. B326. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the official policies, either expressed or implied, of NCCOSC or the U.S. Government. CR CATEGORIES AND SUBJECT DESCRIPTORS: D.2.2 [Software Engineering]: Tools and Techniques-User Interfaces; H.1.2 [Models and Principles]: User/Machine Systems-Human Factors; H.5.2 [Information Interfaces and Presentation]: User Interfaces-User Interface Management Systems; I.2.2 [Artificial Intelligence]: Automatic Programming-Program Synthesis; ADDITIONAL KEYWORDS AND PHRASES: User Interface Software, Toolkits, Interface Builders, User Interface Development Environments.
    [Show full text]
  • An Introduction to Qt 4
    AnAn IntroductionIntroduction toto QtQt 44 Jason Trent [email protected] OOuutltliinnee . Why Trolltech? . Why Qt? . Qt 4 Widgets, Datatypes, and Structures . Qt Designer . qmake . Qt without C++ . Demo WWhhyy TTrroolllltetecchh?? .. QQtt aanndd QQttooppiiaa CCoorree aarree OOppeenn SSoouurrccee .. SSuuppppoorrtteedd bbyy mmuullttii--mmiilllliioonn ddoollllaarr ccoommppaannyy WWhhyy QQt?t? .. MMuullttii--ppllaattffoorrmm – No “virtual machines” or emulation layers – Native compilation for Windows, X11, and Mac • Utilizes core OS technologies (Core, Aero, …) – Extensions - ActiveQt, Motif Migration WWhhyy QQt?t? Over 400 C++ Classes . Not just a GUI toolkit – File handling – Networking – Process handling – Threading – Database access – Event loop processing – XML processing – OpenGL integration – and beyond WWhhyy QQt?t? .. IInntteerrnnaattiioonnaalliizzaattiioonn – Built in support for Unicode and Translation • Language and font aware layouts • Bidirectional font support • Mixed-international interface .. SSeeee QQtt LLiinngguuiisstt ffoorr mmoorree WWhhyy QQt?t? .. NNoott jjuusstt mmuuttllii--ppllaattiiffoorrmm,, mmuullttii--aarrcchhiitteeccttuurree .. QQttooppiiaa CCoorree 44 SSeerriieess – Support for embedded devices • Cell phones, PDAs, etc… – Supports Qt4 widgets with little to no code change QQWWiiddggeett TThhee mmeeeekk mmaayy iinnhheerriitt tthhee eeaarrtthh…… ……bbuutt tthhee eeaarrtthh sshhaallll iinnhheerriitt QQWWiiddggeett QWidget QQtt 44 WWiiddggeetsts .. IInnhheerriitt tthhee aallll--ppoowweerrffuull QQWWiiddggeett .. IInncclluuddee::
    [Show full text]
  • Programming Java for OS X
    Programming Java for OS X hat’s so different about Java on a Mac? Pure Java applica- tions run on any operating system that supports Java. W Popular Java tools run on OS X. From the developer’s point of view, Java is Java, no matter where it runs. Users do not agree. To an OS X user, pure Java applications that ignore the feel and features of OS X are less desirable, meaning the customers will take their money elsewhere. Fewer sales translates into unhappy managers and all the awkwardness that follows. In this book, I show how to build GUIs that feel and behave like OS X users expect them to behave. I explain development tools and libraries found on the Mac. I explore bundling of Java applications for deployment on OS X. I also discuss interfacing Java with other languages commonly used on the Mac. This chapter is about the background and basics of Java develop- ment on OS X. I explain the history of Java development. I show you around Apple’s developer Web site. Finally, I go over the IDEs commonly used for Java development on the Mac. In This Chapter Reviewing Apple Java History Exploring the history of Apple embraced Java technologies long before the first version of Java on Apple computers OS X graced a blue and white Mac tower. Refugees from the old Installing developer tan Macs of the 1990s may vaguely remember using what was tools on OS X called the MRJ when their PC counterparts were busy using JVMs. Looking at the MRJ stands for Mac OS Runtime for Java.
    [Show full text]
  • User Interface Software Technology BRAD A
    User Interface Software Technology BRAD A. MYERS Human Computer Interaction Institute, Carnegie Mellon University ^[email protected]& The user interface of an application is the application to draw pictures on the the part that the person using the soft- screen and get input from the user, and ware sees and interacts with. The part the window manager allows the end of the software that makes the user user to move windows around, and is interface work is often large, complex, responsible for displaying the title lines, and difficult to implement, debug, and borders, and icons around the windows. modify. Today direct manipulation in- However, many people and systems use terfaces (also called graphical user in- the name “window manager” to refer to terface (GUI’s)) are almost universal, both layers, since systems such as the and the part of the software that han- Macintosh and Microsoft Windows do dles the user interface generally takes a not separate them. significant percentage of the total sys- On top of the windowing system is the tem design and implementation time toolkit, which contains many commonly [Myers and Rosson 1992]. Therefore, used widgets such as menus, buttons, specialized software tools have been cre- scroll bars, and text-input fields. Tool- ated to ease the programmer’s burden, kits usually connect to application pro- and today virtually all new user inter- grams through call-back procedures de- face software uses tools that make the fined by the application programmer implementation easier. Many of these that are used when a widget is operated tools have demonstrated significant pro- by the end user.
    [Show full text]
  • Using Xmlfor User Interface Documentation And
    Journal of Theoretical and Applied Information Technology © 2005 - 2010 JATIT & LLS. All rights reserved. www.jatit.org USING XML FOR USER INTERFACE DOCUMENTATION AND DIFFERENTIAL EVALUATION 1MOHAMMAD TUBISHAT, 2IZZAT ALSMADI, AND 3MOHAMMED AL-KABI 1Lecturer, Computer Science Department, Yarmouk University, Irbid, Jordan 2Asstt. Prof., Computer Information Systems Department, Yarmouk University, Irbid, Jordan 3Asstt. Prof., Computer Information Systems Department, Yarmouk University, Irbid, Jordan E-mail: [email protected] , [email protected] , [email protected] ABSTRACT In any software product, the user interface is one of the most important parts that defines the communication between the user and the system. One of the challenges in user interfaces is in the ability to save its state at any time as in many cases, especially in problems such as power interruptions; there is a need to save the last “good” state. In some other cases, there is a need to see if the user interface state is changed or to compare the current state with a previous one. This is required for several possible cases such as: evaluation, and changes in requirements, design and implementation. The format used for storing the state of the Graphical User Interface (GUI) should be global and can be easily used by different types of applications (such as the XML format). A GUI state is usually defined as the overall combination of properties of all the components or widgets of the GUI. In this paper an alternative back end representation is proposed for user interfaces and their state from their original format within the applications. In this approach the user interface is converted to an XML file.
    [Show full text]
  • Ultimate++ Forum
    Subject: Porting (Mac OS X) and "reference application" idea Posted by mirek on Thu, 17 May 2007 15:35:21 GMT View Forum Message <> Reply to Message I have an idea how to speed-up the porting (MacOS X now, be it is general). The most time consuming part of problem is to find out all the information about implementing required things on target platform, something that developer that knows the platform would find primitive. OTOH, target platform guru's are unlikely to know about U++ implementation details. So my idea is to create "reference application" that will contain all the function for minimal (and perhaps later, advanced) target platform support. Target platform guru will reimplement this application (using the most straighforward way) and submit the code, which will serve as great boost to development speed (sort of U++ oriented knowledge base). Thoughts? Mirek Subject: Re: Porting (Mac OS X) and "reference application" idea Posted by captainc on Sun, 14 Sep 2008 13:08:14 GMT View Forum Message <> Reply to Message luzr wrote on Thu, 17 May 2007 11:35I have an idea how to speed-up the porting (MacOS X now, be it is general). The most time consuming part of problem is to find out all the information about implementing required things on target platform, something that developer that knows the platform would find primitive. OTOH, target platform guru's are unlikely to know about U++ implementation details. So my idea is to create "reference application" that will contain all the function for minimal (and perhaps later, advanced) target platform support.
    [Show full text]
  • 51. Graphical User Interface Programming
    Brad A. Myers Graphical User Interface Programming - 1 51. Graphical User Interface Programming Brad A. Myers* Human Computer Interaction Institute Carnegie Mellon University 5000 Forbes Avenue Pittsburgh, PA 15213 [email protected] http://www.cs.cmu.edu/~bam (412) 268-5150 FAX: (412) 268-1266 *This paper is revised from an earlier version that appeared as: Brad A. Myers. “User Interface Software Tools,” ACM Transactions on Computer-Human Interaction. vol. 2, no. 1, March, 1995. pp. 64-103. Draft of: January 27, 2003 To appear in: CRC HANDBOOK OF COMPUTER SCIENCE AND ENGINEERING – 2nd Edition, 2003. Allen B. Tucker, Editor-in-chief Brad A. Myers Graphical User Interface Programming - 2 51.1. Introduction Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. Virtually all applications today are built using some form of user interface tool [Myers 2000]. User interface (UI) software is often large, complex and difficult to implement, debug, and modify. As interfaces become easier to use, they become harder to create [Myers 1994]. Today, direct manipulation interfaces (also called “GUIs” for Graphical User Interfaces) are almost universal. These interfaces require that the programmer deal with elaborate graphics, multiple ways for giving the same command, multiple asynchronous input devices (usually a keyboard and a pointing device such as a mouse), a “mode free” interface where the user can give any command at virtually any time, and rapid “semantic feedback” where determining the appropriate response to user actions requires specialized information about the objects in the program.
    [Show full text]
  • 302 Using Interface Builder in Xcode 4 Final DDF
    Using Interface Builder in Xcode 4 Joey Hagedorn Interface Builder Engineer These are confidential sessions—please refrain from streaming, blogging, or taking pictures 1 What Is Interface Builder? 2 Agenda 1 Tour of Interface Builder in Xcode 2 Building a basic application 3 Integrating new Mac OS X Lion features X 3 1 Tour of Interface Builder in Xcode 4 5 6 7 8 9 10 11 Agenda 1 Tour of Interface Builder in Xcode 2 Building a basic application 3 Integrating new Mac OS X Lion features X 12 2 Building a basic application 13 Demo Building a basic application using Interface Builder 14 Agenda 1 Tour of Interface Builder in Xcode 2 Building a basic application 3 Integrating new Mac OS X Lion features X 15 3 Integrating new Mac OS X Lion features X 16 17 18 19 Integrating New Mac OS X Lion Features Demo 20 Using Interface Builder in Xcode 4 Kevin Cathey Interface Builder Engineer 21 Demo Creating Popovers in Interface Builder 22 Autolayout What is Autolayout? Button {{20, 64}, {70, 20}} Aqua guides are one-time visual helpers to produce the frame of a view 23 Autolayout What is Autolayout? {{20, 64}, {70, 20}} Autolayout reverses this: guides kept as constraints which is input, frame is output 24 What Is Autolayout? • Persist the aqua guides as objects called constraints • Constraints are relationships that must hold • Constraints involve one or two views • Constraints are objects you interact with in your document 25 Why Autolayout? • Dynamism: Improved responsiveness to changes in the application • Simplicity: Creation of basic interfaces
    [Show full text]
  • CERN Computer Newsletter Has Become a Sort of Historical Institution by Itself
    CERN COMPUTER CERN - IT Division CH-1211 Geneve 23 NEWSLETTER SWITZERLAND CERN-CNL-2000-001 January – April 2000 Vol. XXXIV, issue no 1 Contents If you need Help i Editorial iv 1 Physics Computing 1 1.1 ALICE Data Challenge 2000 . .......................................... 1 2 Desktop Computing 3 2.1 Central Computing Helpdesk - Outlines and Strategy ............................... 3 2.2 Service Handbook for the Desktop Support Contract with IT Division . ................ 4 2.3 Backing up Data on your Unix Desktop Machine . ............................... 5 2.4 Linux Red Hat 6.1 now Certified .......................................... 5 2.5 Operating System Certification - Present List . ............................... 5 2.6 Range of UNIX platforms served by ASIS . ............................... 6 3 Internet Services and Network 7 3.1 Improvement of CERN Connectivity to the Global Internet . ........................... 7 3.2 Rationalisation of Support for Network Protocols . ............................... 7 3.3 Connecting Computing Equipment onto the CERN Network ........................... 8 4 Scientific Applications and Software Engineering 9 4.1 Garfield Version 7.02 . .............................................. 9 4.2 Magboltz 2 . .................................................. 10 4.3 News from the Software Development Tools Service ............................... 10 5 Desktop Publishing 12 5.1 XML-related Developments . .......................................... 12 6 The Learning Zone 14 6.1 X11 Desktop Environments (KDE and GNOME)
    [Show full text]
  • MAD Week 1 App Intro.Pptx
    Mobile Applicaon Development Aileen Pierce STARTING IOS APPLICATION DEVELOPMENT iOS Development Differences • Limited screen size • Each app has one window • Limited system resources – Apps need to start and quit quickly • Might not always have Internet access • Uses Objecve-C – Flavor of C based on NeXTSTEP • No physical keyboard and mouse for interac,on iOS Device Tour • iPhone 5 – 4 inches diagonally – 1136 x 640 resoluon • iPhone 4/4S – 3.5 inches diagonally – 480 x 320 resolu,on, 960 x 640 re,na • iPad mini – 7.9 inches diagonally – 1024 x 768 resoluon • iPad – 9.7 inches diagonally – 1024 x 768 resolu,on, 2048 x 1536 re,na • Mul,-touch operaons • Landscape or portrait mode SDK Components • Xcode – Integrated Development Environment (IDE) to create and manage development projects – Interface Builder • Tool to build your applicaon user interfaces • Frameworks – So_ware libraries that provide specific func,onality • Simulator – Simulates running your apps on your Mac • Instruments – Gather and analyze data on your apps behavior Developing apps • Start with an Xcode template • Design the user interface (UI) • Hook up the UI and the code • Write the code using the frameworks • Build and run your app (iteravely) – Compiles your files creang a single library • Test and debug un,l you’re done Geng Started with Xcode • Integrated Development Environment (IDE) • Projects • iOS Applicaon • Templates – Enables you to easily create different types of apps • Product – iPhone, iPad, or universal Single View Applicaon • Good for apps with a single view
    [Show full text]
  • BLAISE PASCAL MAGAZINE ALL ABOUT DELPHI and DELPHI PRISM(.Net) , LAZARUS & PASCAL and RELATED LANGUAGES Pascal8
    BLAISE PASCAL MAGAZINE ALL ABOUT DELPHI AND DELPHI PRISM(.Net) , LAZARUS & PASCAL AND RELATED LANGUAGES Pascal8 Delphi 2010 – what a feeling! - Bob Swart page 7 Gestures could be the new ’must’ in our computers future Counters - David Dirkse page 11 Learning counting again, - could wel be a hobby... Virus in Delphi? - Nick Hodges page 14 Nick explains how to get rid of the virus and block it. Dezign for databases - Marco Roessen page 16 A fantastic alternative for its expensive competitors, and it’s even cheaper. Customizing the T-Field data display - Henk Schreij page 18 Diving deeper into the possibility’s Using Free Pascal and Lazarus to create applications for OSX - Jeremy North page 20 Working on the Mac is hot Writing Delphi Components II: Custom Properties and Windows Controls - Marco Cantù page 22 In the new Delphi versions it looks all different. My Top Five Delphi 2010 New Features - Pawel Glowacki page 24 Except for guestures ther is a lot of news... Fast Graphic deformation by using Scanlines - Peter Bijlsma page 28 Control your own image or blow it up! Berlusconi on the edge Wide Information Bus (Introduction) - Fikret Hasovic page 33 What is it and what the use for it? Freehand Drawing (Introduction) - David Dirkse page 36 shows how to create your own paint program October 2009 Publisher: Foundation for Supporting the Pascal Programming Language in collaboration with the Dutch Pascal User Group (Pascal Gebruikers Groep) © Stichting Ondersteuning Programeertaal Pascal Cover price Europe: € 10.00 / UK £ 10.00 / US $ 10.00 BLAISE PASCAL MAGAZINE 8 ALL ABOUT DELPHI AND DELPHI PRISM(.Net) ,LAZARUS & PASCAL AND RELATED LANGUAGES CONTENTS Volume 8, ISSN 1876-0589 Editor in chief Articles Detlef D.
    [Show full text]
  • User Interface Software Tools
    User Interface Software Tools Brad A. Myers August 1994 CMU-CS-94-182 School of Computer Science Carnegie Mellon University Pittsburgh, PA 15213 Also appears as Human-Computer Interaction Institute Technical Report CMU-HCII-94-107 This report supersedes CMU-CS-92-114 from February, 1992, published as: Brad A. Myers. ‘‘State of the Art in User Interface Software Tools,’’ Advances in Human- Computer Interaction, Volume 4. Edited by H. Rex Hartson and Deborah Hix. Norwood, NJ: Ablex Publishing, 1993. pp. 110-150. Abstract Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. This article discusses the different kinds of user interface software tools, and investigates why some approaches have worked and others have not. Many examples of commercial and research systems are included. Finally, current research directions and open issues in the field are discussed. This research was sponsored by NCCOSC under Contract No. N66001-94-C-6037, ARPA Order No. B326. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the official policies, either expressed or implied, of NCCOSC or the U.S. Government. CR CATEGORIES AND SUBJECT DESCRIPTORS: D.2.2 [Software Engineering]: Tools and Techniques-User Interfaces; H.1.2 [Models and Principles]: User/Machine Systems-Human Factors; H.5.2 [Information Interfaces and Presentation]: User Interfaces-User Interface Management Systems; I.2.2 [Artificial Intelligence]: Automatic Programming-Program Synthesis; ADDITIONAL KEYWORDS AND PHRASES: User Interface Software, Toolkits, Interface Builders, User Interface Development Environments.
    [Show full text]