About: Text-based user interface is a research topic. Over the lifetime, 9 publications have been published within this topic receiving 83 citations. The topic is also known as: textual user interface & terminal user interface.
TL;DR: A visualization system for a tracer may include a processing pipeline that may generate tracing data, preprocess the data, and visualize the data as mentioned in this paper, which may perform various functions including mathematical, statistical, aggregation with other data and others.
Abstract: A visualization system for a tracer may include a processing pipeline that may generate tracing data, preprocess the data, and visualize the data. The preprocessing step may include a mechanism to process user-defined expressions or other executable code. The executable code may perform various functions including mathematical, statistical, aggregation with other data, and others. The preprocessor may perform malware analysis, test the functionality, then implement the executable code. A user may be presented with an editor or other text based user interface component to enter and edit the executable code. The executable code may be saved and later recalled as a selectable transformation for use with other data streams.
TL;DR: XVERSA facilitates the use of the Algebra of Communicating Shared Resources, a real-time process algebra with explicit notions of resources and priority, which supports syntax checking, analysis based on equivalence checking, state space exploration, and algebraic rewriting.
Abstract: We present XVERSA, a set of tools for the specification and analysis of resource-bound real-time systems. XVERSA facilitates the use of the Algebra of Communicating Shared Resources (ACSR), a real-time process algebra with explicit notions of resources and priority. A text based user interface supports syntax checking, analysis based on equivalence checking, state space exploration, and algebraic rewriting. A graphical user interface allows systems to be described and analyzed using intuitive pictorial representations of ACSR language elements.
TL;DR: A system that parses International Society for Analytical Cytology, ISAC, Flow Cytometry Standard 2.0 files and stores the data in AdaSAGE tables, which is employed to analyze and plot the data from multiple experiments.
Abstract: Two existing Ada tools AdaSAGE and AYACC were combined to produce a system that parses International Society for Analytical Cytology, ISAC, Flow Cytometry Standard 2.0 files and stores the data in AdaSAGE tables. There are significant differences in the way manufacturers interpret and conform to Flow Cytometry Standard 2.0. AdaSAGE is employed to analyze and plot the data from multiple experiments. This data is used to assess the stability of flow cytometers. The initial release will be for DOS. The utilization of AdaSAGE, which is a flexible database tool, will facilitate subsequent development of other products. The software engineer, whose previous professional experience was with C and C++, had very few problems with Ada syntax. The interface to the compiler and other tools was immature compared to those available for C++. The DOS text based user interface environment provided by AdaSAGE limited the functionality of the user interface. However, the present DOS 386 program can be directly ported to the newly released version of AdaSAGE for Microsoft Windows 95. Ada’s strong type checking and package structure have significantly facilitated the development of the product.
TL;DR: Results of a case study in maintenance of an object oriented software application are presented, where a software engineer replaced a text based user interface with a graphical user interface based on the Microsoft Foundation Classes, adapted the application for the Win32 environment, and corrected faults in the original application.
Abstract: Results of a case study in maintenance of an object oriented software application are presented. A software engineer replaced a text based user interface with a graphical user interface (GUI) based on the Microsoft Foundation Classes, adapted the application for the Win32 environment, and corrected faults in the original application. About 94.8% of the maintenance effort was perfective (development of the GUI), 3.2% adaptive and 2.0% corrective. Comparisons are drawn to similar maintenance activities in the literature.
TL;DR: This work aimed to build-up a full-scale 2D graphics module on a small embedded system with an LCD panel, which shows a TUI (text user interface) model, which is similar to the Unix Curses library and/or primitive graphics system used on earlier PC user interfaces.
Abstract: In these days, smaller devices are possible to show graphics output, through attaching customized LCD panel displays. Our target system is a small embedded system with an LCD panel. As a typical low-tier embedded system, it has a low-end CPU and restricted memories. We aimed to build-up a full-scale 2D graphics module on it. After analyzing system requirements, we found that the most hardiest restriction is the size of available memory. As an alternative to the full-scale modules, our design shows a TUI (text user interface) model, which is similar to the Unix Curses library and/or primitive graphics system used on earlier PC user interfaces. Our design has a drawback of restricted controllability of 2020 character resolutions on the screen, rather than 240x320 pixel resolutions, while it enables pop-up menus and screen back buffering, with less than 7K extra memory usage. User Interface features including pop-up menus, push buttons, and customizable windows are also provided.