DOCSLIB.ORG

Unix Tools As Visual Programming Components in a GUI-Builder

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Unix Tools as Visual Programming Components Ý in a GUI-builder Environment £ Diomidis Spinellis Department of Management Science and Technology Athens University of Economics and Business Patision 76, GR-104 34 Athens, Greece email: [email protected] September, 2001 Abstract Introduction A number of environments support the visual composition Development environments based on ActiveX controls and of graphical user interfaces (GUIs) using components with a JavaBeans are marketed as “visual programming” plat- predefined set of interfaces. In addition, technologies such forms; in practice their visual dimension is limited to the as ActiveX and JavaBeans allow the development of visual design and implementation of an application’s graphical components (typically GUI elements) that can be seamlessly user interface (GUI. The availability of sophisticated GUI incorporated into an integrated development environment development environments and visual component develop- (IDE) and subsequently used in application development. In ment frameworks is now providing viable platforms for this article we present how visual IDEs and components can implementing visual programming within general-purpose be extended beyond GUI development to support visual pro- platforms, i.e. for the specification of non-GUI program gramming for a particular domain. functionality using visual representations. We describe A visual programming language can be informally de- how specially-designed reflective components can be used in an industry-standard visual programming environment fined as a programming language with a syntax that in- cludes visual expressions such as diagrams, free-hand to graphically specify sophisticated data transformation sketches, icons, or graphical manipulations [1]. Visual pipelines that interact with GUI elements. The components are based on Unix-style filters repackaged as ActiveX con- programming approaches aim towards easing the program- ming learning curve or enhancing programming productiv- trols. Their visual layout on the development environment canvas is used to specify the connection topology of the ity. Their adoption was based on a number of premises [2]: resultant pipeline. The process of converting filter-style ¯ pictures may be able to concisely convey meaning programs as visual controls is automated using a domain- more efficiently than words, specific language. We demonstrate the approach through the design and the visual implementation of a GUI-based ¯ pictures could help understanding and remembering, spelling checker. ¯ pictures may enhance the experience of programming by making it more interesting, and Keywords ¯ culturally-neutral pictures can be understandable re- gardless of what language people speak. Visual programming, components, reflection, Unix tools, However, empirical studies did not find visual programming pipe and filter architecture, reuse. inherently superior to text-based programs; the extent to which a given notation is suitable for expressing a partic- £ Software—Practice and Experiece, 32(1):57–71, 2002. ular task depends on the context in which the language is Ý This is a machine-readable rendering of a working paper draft that led employed [3, 4, 5]. Early work on visual programming, to a publication. The publication should always be cited in preference to this draft using the reference in the previous footnote. This material is although promising when applied to “toy” problems, ran presented to ensure timely dissemination of scholarly and technical work. into difficulties when the methods were tried on problems Copyright and all rights therein are retained by authors or by other copy- of realistic size. Two approaches for alleviating this prob- right holders. All persons copying this information are expected to adhere lem were followed: a number of researchers applied visual to the terms and constraints invoked by each author’s copyright. In most cases, these works may not be reposted without the explicit permission of programming languages to limited or domain-specific parts the copyright holder. of software development such as GUI programming, the 1 graphic depiction of data structure behaviour, or the combi- ponents and their execution environment; Section presents nation of textually programmed units to build new programs how the controls we have implemented support visual pro- [1]. Others, proposed the design of visual programming gramming; in Section we analyse the design and implemen- languages based on formalisms used by existing, standard, tation of the visual controls, in Section we present how the component-based visual engineering languages such as the control creation process can be automated, in Section we ITU-T MSC standard for message sequence charts, or the describe an exemplar application utilising visual program- IEC-1131 standard for function block languages [6]. ming controls, and in Section we evaluate the approach we In our approach we capitalise on the strength of exist- propose. Section concludes the paper with directions for ing GUI-builder IDEs by crafting industry-standard soft- further work. ware components that can be used within the GUI-designer The elements of our approach: visual programming, of the IDE to perform data-flow-oriented visual program- component-based development, a graphical front-end to ming. Although we demonstrate our method in the context Unix tools, data-flow visual languages, and pipe and filter of a specific domain (the visual composition of data-flow architectures have been extensively studied. See for exam- pipelines), the same underlying principles can be applied to ple the references [2, 14, 1, 15, 6] (discussing visual pro- different visual programming domains. gramming and providing examples of specific approaches), We define a software component as a unit of composition [16, 17, 18, 3] (discussing graphical Unix-tool front ends), with contractually specified interfaces and explicit context [19, 20, 21, 7, 22] (discussing component-based develop- dependencies only; one that can be deployed independently ment), [17, 23, 24, 25, 26, 27] (discussing visual data-flow and is subject to third-party composition [7]. Components, approaches), and [28, 29] (discussing pipe and filter archi- in common with objects, encapsulate state, allow access tectures). The main contributions of this paper are: the pro- to it through separately described interfaces, and support posal to use standard GUI builders as visual programming modular design based on separation of concerns. However, environments by means of specially crafted reflective com- components differ from objects in a number of ways: they ponents, the idea that GUI builders can be used to configure can be implemented in different languages, they are often sophisticated component interactions and deployment sce- packaged in binary containers, they can encapsulate multi- narios, and the demonstration of visual programming and ple objects, and are typically more robustly packaged than GUI interfacing utilising the well-known Unix text process- objects [8]. Components that support visual composition ing tools encapsulated as ActiveX components. implement a set of interfaces defined by the visual pro- gramming environment that supports their use. These inter- faces allow the visual placement of components on forms, Component Source and Execution En- the handling of user-input events, and the persistent spec- ification of their properties at program design time. Two vironment widespread families of visual components are JavaBeans [9] and ActiveX controls [10]. Most existing visual components (also known as controls Visual components are supported by a number of IDEs. or widgets) provide GUI interface elements. Typical exam- Typical examples are Visual Basic (VB), Delphi, JBuilder, ples include text-input boxes, buttons, list boxes, grids, ra- Latte, and Visual Caf´e. Although ActiveX controls, Jav- dio buttons, graphs, and file selection dialogs. The few vi- aBeans, and their respective environments are marketed as sual components that do provide computationally interest- “visual programming” technologies, in practice, their vi- ing processing (such as Microsoft’s Internet Transfer con- sual dimension is limited to the design and implementa- trol used to perform HTTP/FTP data transfers) do not utilise tion of graphical user interfaces (GUIs). A number of sys- their visual dimension; they are presumably packaged as tems such as Khoros/Cantata [11, 12] and LabVIEW [13] visual components in order to expose their properties for support component-based visual programming — also re- editing using the standard IDE property editing mecha- ferred to as coarse-grained visual programming — using nisms. Our candidates for repackaging as visual compo- specialised components and a corresponding dedicated de- nents had to provide non-trivial computational functional- velopment environment. Now, the availability of sophisti- ity, be amenable to visual manipulation, and be available for cated GUI-builder IDEs and the respective component de- reuse. We decided to base our work on the numerous user velopment frameworks provides us with an alternative ap- and system programs available under the Unix operating proach for implementing coarse-grained visual program- system implementations. Based on the Unix tool-centred ming: one based on widely deployed, industry-standard philosophy, software developers have created a large collec- platforms. tion of programs that provide a single service (e.g. compare In the following sections we present how specially-
Recommended publications
  • By Sebastiano Vigna and Todd M. Lewis Copyright C 1993-1998 Sebastiano Vigna Copyright C 1999-2021 Todd M

    By Sebastiano Vigna and Todd M. Lewis Copyright C 1993-1998 Sebastiano Vigna Copyright C 1999-2021 Todd M

    ne A nice editor Version 3.3.1 by Sebastiano Vigna and Todd M. Lewis Copyright c 1993-1998 Sebastiano Vigna Copyright c 1999-2021 Todd M. Lewis and Sebastiano Vigna Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Chapter 1: Introduction 1 1 Introduction ne is a full screen text editor for UN*X (or, more precisely, for POSIX: see Chapter 7 [Motivations and Design], page 65). I came to the decision to write such an editor after getting completely sick of vi, both from a feature and user interface point of view. I needed an editor that I could use through a telnet connection or a phone line and that wouldn’t fire off a full-blown LITHP1 operating system just to do some editing. A concise overview of the main features follows: • three user interfaces: control keystrokes, command line, and menus; keystrokes and menus are completely configurable; • syntax highlighting; • full support for UTF-8 files, including multiple-column characters; • 64-bit
  • Pipe and Filter Architectural Style Group Number: 5 Group Members: Fan Zhao 20571694 Yu Gan 20563500 Yuxiao Yu 20594369

    Pipe and Filter Architectural Style Group Number: 5 Group Members: Fan Zhao 20571694 Yu Gan 20563500 Yuxiao Yu 20594369

    Pipe and Filter Architectural Style Group Number: 5 Group Members: Fan Zhao 20571694 Yu Gan 20563500 Yuxiao Yu 20594369 1. Have its own vocabulary for its components and connectors? (define) The Pipe and Filter is an architectural pattern for stream processing. It consists of one or more components called filters. These filters will transform or filter ​ ​ data and then pass it on via connectors called pipes. These filters, which merely ​ ​ consume and produce data, can be seen as functions like sorting and counting. All of these filters can work at the same time. Also, every pipe connected to a filter has its own role in the function of the filter. When data is sent from the producer (pump), it ​ ​ goes through the pipes and filters, and arrives the destination (sink). The pump can ​ ​ be a static text file or a keyboard input. The sink can be a file, a database or a computer screen. 2. Impose specific topological constraints? (diagram) Figure 1 shows a basic structure of Pipe and Filter architecture style. In this example, there are five filters and eight pipes. Each filter will get input from one or more pipes and pass it via pipes. The combination of several filters and pipes can be regarded as a “big” filter. Figure 2 is an specific example using Pipe and Filter architecture style. This example demonstrates a simple process of making sandwiches. To begin with, the first 4 filters can work simultaneously for preparation. Once they are done, the 5th filter can get the output and combine them together. Next, a following filter will add sauce to it and pass it to customer through a pipe.
  • Digital Filter Graphical User Interface

    Digital Filter Graphical User Interface

    University of Southern Maine USM Digital Commons Thinking Matters Symposium Archive Student Scholarship Spring 2018 Digital Filter Graphical User Interface Tony Finn University of Southern Maine Follow this and additional works at: https://digitalcommons.usm.maine.edu/thinking_matters Recommended Citation Finn, Tony, "Digital Filter Graphical User Interface" (2018). Thinking Matters Symposium Archive. 135. https://digitalcommons.usm.maine.edu/thinking_matters/135 This Poster Session is brought to you for free and open access by the Student Scholarship at USM Digital Commons. It has been accepted for inclusion in Thinking Matters Symposium Archive by an authorized administrator of USM Digital Commons. For more information, please contact [email protected]. By Tony Finn Digital Filter Graphical User Interface EGN 402 Fall 2017 Problem Statements - Digital FIR (finite impulse response) filter design Results requires tedious computations, with each requiring Illustrated in Figure 3 is the final design of the user interface, truncation of an impulse response (seen in Figure 1.) one will find buttons to change design type and filter type as - In order to obtain the desired effects from a filter, one well as clickable buttons to give the user feedback or an output. may need to try multiple filters, so many computations - Play Original Audio: emits the input audio as is; unfiltered. would be necessary. - Play Filtered Audio: emits the input audio with the designed Therefore the desire to simplify the digital filter design filter applied. process is necessary to provide users an easier, more intuitive method for design. - Return Filtered Audio: returns the filtered audio. - Print Filter: returns the filter specifications.
  • A Highly Configurable High-Level Synthesis Functional Pattern Library

    A Highly Configurable High-Level Synthesis Functional Pattern Library

    electronics Article A Highly Configurable High-Level Synthesis Functional Pattern Library Lan Huang 1,2,‡, Teng Gao 1,‡, Dalin Li 1,†, Zihao Wang 1 and Kangping Wang 1,2,* 1 College of Computer Science and Technology, Jilin University, Changchun 130012, China; [email protected] (L.H.); [email protected] (T.G.); [email protected] (D.L.); [email protected] (Z.W.) 2 Key Laboratory of Symbolic Computation and Knowledge Engineering, Jilin University, Changchun 130012, China * Correspondence: [email protected] † Current address: Zhuhai Laboratory of Key Laboratory of Symbol Computation and Knowledge Engineering of Ministry of Education, Department of Computer Science and Technology, Zhuhai College of Jilin University, Zhuhai 519041, China. ‡ These authors contributed equally to this work. Abstract: FPGA has recently played an increasingly important role in heterogeneous computing, but Register Transfer Level design flows are not only inefficient in design, but also require designers to be familiar with the circuit architecture. High-level synthesis (HLS) allows developers to design FPGA circuits more efficiently with a more familiar programming language, a higher level of abstraction, and automatic adaptation of timing constraints. When using HLS tools, such as Xilinx Vivado HLS, specific design patterns and techniques are required in order to create high-performance circuits. Moreover, designing efficient concurrency and data flow structures requires a deep understanding of the hardware, imposing more learning costs on programmers. In this paper, we propose a set of functional patterns libraries based on the MapReduce model, implemented by C++ templates, Citation: Huang, L.; Gao,T.; Li, D.; which can quickly implement high-performance parallel pipelined computing models on FPGA with Wang, Z.; Wang, K.
  • MATLAB Creating Graphical User Interfaces  COPYRIGHT 2000 - 2004 by the Mathworks, Inc

    MATLAB Creating Graphical User Interfaces  COPYRIGHT 2000 - 2004 by the Mathworks, Inc

    MATLAB® The Language of Technical Computing Creating Graphical User Interfaces Version 7 How to Contact The MathWorks: www.mathworks.com Web comp.soft-sys.matlab Newsgroup [email protected] Technical support [email protected] Product enhancement suggestions [email protected] Bug reports [email protected] Documentation error reports [email protected] Order status, license renewals, passcodes [email protected] Sales, pricing, and general information 508-647-7000 Phone 508-647-7001 Fax The MathWorks, Inc. Mail 3 Apple Hill Drive Natick, MA 01760-2098 For contact information about worldwide offices, see the MathWorks Web site. MATLAB Creating Graphical User Interfaces COPYRIGHT 2000 - 2004 by The MathWorks, Inc. The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. No part of this manual may be photocopied or repro- duced in any form without prior written consent from The MathWorks, Inc. FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for, or through the federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees that this software or documentation qualifies as commercial computer software or commercial computer software documentation as such terms are used or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern the use, modification, reproduction, release, performance, display, and disclosure of the Program and Documentation by the federal government (or other entity acquiring for or through the federal government) and shall supersede any conflicting contractual terms or conditions.
  • Bash Guide for Beginners

    Bash Guide for Beginners

    Bash Guide for Beginners Machtelt Garrels Garrels BVBA <tille wants no spam _at_ garrels dot be> Version 1.11 Last updated 20081227 Edition Bash Guide for Beginners Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions, translations and availability.........................................................................................2 4. Revision History..................................................................................................................................2 5. Contributions.......................................................................................................................................3 6. Feedback..............................................................................................................................................3 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................4 9. Conventions used in this
  • PJM Command Line Interface

    PJM Command Line Interface

    PJM Command Line Interface PJM Interconnection LLC Version 1.5.1 11-18-2020 PJM Command Line Interface Table of Contents Purpose ..................................................................................................................................................................................... 4 System Requirements ............................................................................................................................................................... 4 Release History ......................................................................................................................................................................... 4 Usage ........................................................................................................................................................................................ 5 Standalone Application ......................................................................................................................................................... 5 Example Standalone Execution ....................................................................................................................................... 5 Parameter Details ............................................................................................................................................................. 7 Password Encryption .......................................................................................................................................................
  • TASSEL 3.0 / 4.0 Pipeline Command Line Interface: Guide to Using Tassel Pipeline

    TASSEL 3.0 / 4.0 Pipeline Command Line Interface: Guide to Using Tassel Pipeline

    TASSEL 3.0 / 4.0 Pipeline Command Line Interface: Guide to using Tassel Pipeline Terry Casstevens ([email protected]) Institute for Genomic Diversity, Cornell University, Ithaca, NY 14853-2703 March 28, 2014 Prerequisites ............................................................................................................................................................ 1 Source Code ............................................................................................................................................................ 1 Install ....................................................................................................................................................................... 1 Execute .................................................................................................................................................................... 1 Increasing Heap Size ............................................................................................................................................... 2 Examples ................................................................................................................................................................. 2 Examples (XML Configuration Files) .................................................................................................................... 2 Usage ......................................................................................................................................................................
  • Reference Manual

    Reference Manual

    Reference Manual Command Line Interface (CLI) HiLCOS Rel. 9.12 RM CLI HiLCOS Technical Support Release 9.12 05/16 https://hirschmann-support.belden.eu.com The naming of copyrighted trademarks in this manual, even when not specially indicated, should not be taken to mean that these names may be considered as free in the sense of the trademark and tradename protection law and hence that they may be freely used by anyone. © 2016 Hirschmann Automation and Control GmbH Manuals and software are protected by copyright. All rights reserved. The copying, reproduction, translation, conversion into any electronic medium or machine scannable form is not permitted, either in whole or in part. An exception is the preparation of a backup copy of the software for your own use. The performance features described here are binding only if they have been expressly agreed when the contract was made. This document was produced by Hirschmann Automation and Control GmbH according to the best of the company's knowledge. Hirschmann reserves the right to change the contents of this document without prior notice. Hirschmann can give no guarantee in respect of the correctness or accuracy of the information in this document. Hirschmann can accept no responsibility for damages, resulting from the use of the network components or the associated operating software. In addition, we refer to the conditions of use specified in the license contract. You can get the latest version of this manual on the Internet at the Hirschmann product site (www.hirschmann.com.) Hirschmann Automation and Control GmbH Stuttgarter Str. 45-51 Germany 72654 Neckartenzlingen Tel.: +49 1805 141538 Rel.
  • Great Lakes Cheat Sheet Less File Prints Content of File Page by Page Guide to General L Inux (Bash) a Nd S Lurm C Ommands Head File Print First 10 Lines of File

    Great Lakes Cheat Sheet Less File Prints Content of File Page by Page Guide to General L Inux (Bash) a Nd S Lurm C Ommands Head File Print First 10 Lines of File

    Viewing and editing text files cat file Print entire content of file Great Lakes Cheat Sheet less file Prints content of file page by page Guide to general L inux (Bash) and S lurm c ommands head file Print first 10 lines of file tail file Print last 10 lines of file Accessing Great Lakes nano Simple, easy to use text editor Logging in from a terminal (Duo required) vim Minimalist yet powerful text editor ssh uniqname @greatlakes.arc-ts.umich.edu emacs Extensible and customizable text editor Transferring files between Great Lakes and your system scp input uniqname@ greatlakes-xfer.arc-ts.umich.edu: output Advanced file management scp -r i nput uniqname@ greatlakes-xfer.arc-ts.umich.edu:o utput scp uniqname@ greatlakes-xfer.arc-ts.umich.edu:i nput output chmod Change read/write/execute permissions which cmd List the full file path of a command GUI Clients PuTTY SSH client for Windows whereis cmd List all related file paths (binary, source, manual, etc.) of a command WinSCP SCP client for Windows du dir List size of directory and its subdirectories FileZilla FTP client for Windows, Mac, and Linux find Find file in a directory Basic Linux file management Aliases and system variables man command Display the manual page for command alias Create shortcut to command pwd Print out the present working directory env Lists all environment variables ls List the files in the current directory export var = val Create environment variable $ var with value ls -lh Show long, human-readable listing val ls dir List files inside directory dir echo $var Print the value of variable $var rm file Delete file .bashrc File that defines user aliases and variables mkdir dir Create empty directory called dir Input and output redirection rmdir dir Remove empty directory dir $( command) Runs command first, then inserts output to the rm -r dir Remove directory dir and all contents rest of the overall command cd dir Change working directory to dir < Standard input redirection cd .
  • Fast Cache for Your Text: Accelerating Exact Pattern Matching with Feed-Forward Bloom Filters Iulian Moraru and David G

    Fast Cache for Your Text: Accelerating Exact Pattern Matching with Feed-Forward Bloom Filters Iulian Moraru and David G

    Fast Cache for Your Text: Accelerating Exact Pattern Matching with Feed-Forward Bloom Filters Iulian Moraru and David G. Andersen September 2009 CMU-CS-09-159 School of Computer Science Carnegie Mellon University Pittsburgh, PA 15213 Abstract This paper presents an algorithm for exact pattern matching based on a new type of Bloom filter that we call a feed-forward Bloom filter. Besides filtering the input corpus, a feed-forward Bloom filter is also able to reduce the set of patterns needed for the exact matching phase. We show that this technique, along with a CPU architecture aware design of the Bloom filter, can provide speedups between 2 and 30 , and memory consumption reductions as large as 50 when compared with × × × grep, while the filtering speed can be as much as 5 higher than that of a normal Bloom filters. × This research was supported by grants from the National Science Foundation, Google, Network Appliance, Intel Corporation and Carnegie Mellon Cylab. Keywords: feed-forward Bloom filter, text scanning, cache efficient 1 Introduction Matching a large corpus of data against a database of thousands or millions of patterns is an im- portant component of virus scanning [18], data mining and machine learning [1] and bioinfor- matics [19], to name a few problem domains. Today, it is not uncommon to match terabyte or petabyte-sized corpuses or gigabit-rate streams against tens to hundreds of megabytes of patterns. Conventional solutions to this problem build an exact-match trie-like structure using an algo- rithm such as Aho-Corasick [3]. These algorithms are in one sense optimal: matching n elements against m patterns requires only O(m + n) time.
  • Standard TECO (Text Editor and Corrector)

    Standard TECO (Text Editor and Corrector)

    Standard TECO TextEditor and Corrector for the VAX, PDP-11, PDP-10, and PDP-8 May 1990 This manual was updated for the online version only in May 1990. User’s Guide and Language Reference Manual TECO-32 Version 40 TECO-11 Version 40 TECO-10 Version 3 TECO-8 Version 7 This manual describes the TECO Text Editor and COrrector. It includes a description for the novice user and an in-depth discussion of all available commands for more advanced users. General permission to copy or modify, but not for profit, is hereby granted, provided that the copyright notice is included and reference made to the fact that reproduction privileges were granted by the TECO SIG. © Digital Equipment Corporation 1979, 1985, 1990 TECO SIG. All Rights Reserved. This document was prepared using DECdocument, Version 3.3-1b. Contents Preface ............................................................ xvii Introduction ........................................................ xix Preface to the May 1985 edition ...................................... xxiii Preface to the May 1990 edition ...................................... xxv 1 Basics of TECO 1.1 Using TECO ................................................ 1–1 1.2 Data Structure Fundamentals . ................................ 1–2 1.3 File Selection Commands ...................................... 1–3 1.3.1 Simplified File Selection .................................... 1–3 1.3.2 Input File Specification (ER command) . ....................... 1–4 1.3.3 Output File Specification (EW command) ...................... 1–4 1.3.4 Closing Files (EX command) ................................ 1–5 1.4 Input and Output Commands . ................................ 1–5 1.5 Pointer Positioning Commands . ................................ 1–5 1.6 Type-Out Commands . ........................................ 1–6 1.6.1 Immediate Inspection Commands [not in TECO-10] .............. 1–7 1.7 Text Modification Commands . ................................ 1–7 1.8 Search Commands .