DOCSLIB.ORG

Package 'Gwidgetswww'

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Package 'Gwidgetswww' Package ‘gWidgetsWWW’ July 2, 2014 Version 0.0-23 Title Toolkit implementation of the gWidgets API for use with web pages Author John Verzani Maintainer John Verzani <[email protected]> Depends R (>= 2.11.0), methods, proto, filehash, digest, rjson Suggests Extends canvas, RSVGTipsDevice, SVGAnnotation, webvis Description Port of the gWidgets API to program dynamic websites. Can be used with R's dynamic help web server to serve local files. This provides a convenient means to make local GUIs for users without concern for external GUI toolkits. Also, in combination with RApache,http://biostat.mc.vanderbilt.edu/rapache/index.html, this framework can be used to make public websites powered by R. The Ext JavaScript libararies (www.extjs.com) are used to create and manipulate the widgets dynamically. License GPL (>= 3) URL http://gwidgets.r-forge.r-project.org/ LazyLoad FALSE Repository CRAN Date/Publication 2012-06-09 10:18:19 NeedsCompilation no 1 2 gWidgetsWWW-package R topics documented: gWidgetsWWW-package . .2 gcanvas . 11 ggooglemaps . 13 gprocessingjs . 15 gsvg............................................. 18 gwebvis . 20 gWidgetsWWW-helpers . 21 gWidgetsWWW-undocumented . 22 gw_browseEnv . 22 gw_package . 22 localServerStart . 23 Index 25 gWidgetsWWW-package Toolkit implementation of gWidgets for WWW Description Port of gWidgets API to WWW using RApache and the ExtJS javascript libraries. Details This package ports the gWidgets API to WWW, allowing the authoring of interactive webpages within R commands. The webpages can be seen locally through a local server or viewed through the internet:The local version is installed with the package and uses R’s internal web server for serving help pages. The server version requires the RApache module for Apache to be installed and configured. (More later.) The webpages themselves use the excellent Extjs toolkit (www.sencha.com) to render the widgets. This toolkit is installed with the package. The gWidgets API is meant to be multi-toolkit. For its other implementations (gWidgetsRGtk2, gWidgetsQt, gWidgetstcltk) the main methods are defined in the gWidgets package, with toolkit packages providing the link between the graphical widget library and R. The gWidgetsWWW is different, it is a more-or-less faithful implementation of the API, but this is not enforced by using the gWidgets pacakge. This was chosen, as there are some significant differences between an in- teractive desktop GUI and a webpage. As the differences are not great, this file documents differences from the API. We defer to the gWid- gets documentation for more detail. (However, this package is not compatible with the gWidgets package so reading that documentation is best done with a separate R process.) gWidgetsWWW-package 3 Overview: The gWidgetsWWW package at one level maps R\/ commands to javascript commands. Basically it just pastes together a bunch of javascript commands to send to the browser. A more sophisticated treatment (like pyjamas for python) would compile the R code into javascript, but that does not happen here. This package is a simple mapping. The communication between R\/ and the browser works as follows. Before a page is rendered, it can be constructed using the gWidget constructors and methods. When the top-level window is shown (via its print method), the javascript code to produce the page is created. This javascript code takes advantage of the freely available Ext libraries which greatly enhance the base javascript language. This code should be contained in or sourced into a web page so that it can be rendered in a browser. The gWidgetsWWW package provides several examples of how this works. The interactivity of a GUI is created through httpxmlrequests back to the RApache server. Each page load creates a unique session to store the state. This allows data to be passed from the web page back to an R process and back without needed to reload an entire page. In fact, reloading a page creates a new session. What is missing is a way to initiate a request from R\/ to the web page and then back to R. As such, the state of the web page is constantly passed back to the R\/ session. That is, when a control is updated, such as when a radio button is clicked, there is a call back into R\/ to set that value. This allows handlers in R to be aware of the state of the web page. On the downside, this may cause a lag in performance. Installation: To run the local version of gWidgetsWWW no installation is necessary beyond installing the pack- age. The command localServerStart can be used to load a script. Installation for the server requires several steps: a) installing RApache, b) installing gWidgetsWWW c) configuring RApache for gWidgetsWWW, and d) creating some webpages Installing RApache is documented at the RApache website. Installing gWidgetsWWW is straight- forward. To configure RApache for gWidgetsWWW, a sample configuration is included in the templates di- rectory. There are several variables to configure. The defaults work with a recent version of Ubuntu, so it can be as easy as simply copying the file into the appropriate place for the web server to read it. The Ext libraries are included in the basehtml/ext directory. Ext has a dual-license model, of- fering an open source LGPL license along with a per-developer, royalty-free commercial license. The standard configuration reads these files from where the R package is installed. (This may need adjustment), so no installation is necessary. To complete the installation, the gWidgetsWWW package provides some stock icons in the basehtml/images directory.. As with the extjs libraries, these can be installed whereever, but the default configuration finds them where R installs the package. The author would very much appreciate that a coherent set 4 gWidgetsWWW-package of icons be contributed. Web pages can be made in two ways. Once can use a brew template and call back into R to generate the page. However, it is much easier to write a standalone R script and call that. For local installs, the function localServerOpen is used to open a file. For server installs, the script need only be put into the proper directory. (This is /var/www/gWidgetsWWW in the default configura- tion.) The script is loaded by calling the proper URL, which takes the form: servername/gWidgetsWWWrun/scriptname, where servername is the http:///www.yourhost.com bit, gWidgetsWWWrun is the default name for the invocation and scriptname the file in the directory (or directories) specified to search through. The scripts themselves have a pretty standard structure: there must be a global gwindow instance (corresponding to the main web page, or which there can only be on), gWidgetsWWW commands for layout, and finally a call to the visible<- method of gwindow to print out the javascript com- mands generated by the package. The Examples directory has many examples. (Try localServerOpen("Examples/ex-index.R", pacakge="gWidgetsWWW") to see.) Sessions: gWidgetsWWW uses sessions to store data when a web page is loaded. Sessions are simply R environments. HTML itself is stateless, so some means is necessary to keep track of data between interactions. The use of AJAX allows pieces of a page to be updated without the entire page, mak- ing pages appear much more responsive. This involves callbacks into a R process that are executed within the environment stored for the session. The environments do not remember which packages are loaded, so if your callback requires a pack- age beyond the base and gWidgetsWWW you will need to include the appropriate require com- mand in the callback. Sometimes the database driver will complain. Likely this is due to the database not being locked while a transaction is being completed. The sessions are stored by default in files under a directory using filehash. This has the advantage of being easy to remove using regular cron jobs, but may be slower than other forms of storage. This is all a bit of a hack, so any report of bugs is appreciated. Containers: We now describe implementation of the basic widgets in gWidgetsWWW beginning with the con- tainers. A primary difference in gWidgetsWWW over gWidgets for other toolkits is the restriction to only one top-level window, which maps to the webpage. Subwindows are possible though. These are constructed with the same constructor, but one passes in the top-level window to the parent argu- ment. The window object is a bit different than other gWidgets implementations, as the object is not rendered until the web page is ready to display. This rendering is done through the visible<- gWidgetsWWW-package 5 method. (In particular, the constructor’s visible argument is ignored.) After rendering, new wid- gets can be added but it doesn’t happen by the same process and may not work as desired. To be on the safe side, you can add child widgets and make them not visible to begin. The default handler is assigned to the unload signal which is called when a page is left. One thing to remember, is that web pages in gWidgetsWWW will lose state when reloaded. For windows, only the svalue<- method, for adjusting the title, is defined. There are a few proto properties to adjust the page. The property doLoadingText can be set to FALSE to suppress the "loading" message whenever a handler is being called. The default means of each window being a webpage can be overridden by specifying a value of ..renderTo, as in w = gwindow(); w$..renderTo = "someId" for some HTML object with appropriate id. The ggroup container accepts the horizontal and spacing arguments, but does not use the use.scrollwindow argument (spacing can not be done after rendering with the svalue<- method though). When adding a child component (which is done when a ggroup instance is used as a parent container) the expand argument is not used, nor is the anchor argument of gWidgets.
Load more

Recommended publications
  • ES520) and Mesh Dynamic's (4000 SERIES) Networking Capabilities During COASTS 2007 Field Experiments
    Calhoun: The NPS Institutional Archive Theses and Dissertations Thesis Collection 2008-03 A comparative analysis of Fortress (ES520) and Mesh Dynamic's (4000 SERIES) networking capabilities during COASTS 2007 field experiments Tyler, Brian Keith. Monterey, California. Naval Postgraduate School http://hdl.handle.net/10945/4160 NAVAL POSTGRADUATE SCHOOL MONTEREY, CALIFORNIA THESIS A COMPARATIVE ANALYSIS OF FORTRESS (ES520) AND MESH DYNAMICS’ (4000 SERIES) NETWORKING CAPABILITIES DURING COASTS 2007 FIELD EXPERIMENTS by Brian Keith Tyler March 2008 Thesis Advisor: Rex Buddenberg Co Advisor: Tom Hoivik Approved for public release; distribution is unlimited THIS PAGE INTENTIONALLY LEFT BLANK REPORT DOCUMENTATION PAGE Form Approved OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instruction, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188) Washington DC 20503. 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED March 2008 Master’s Thesis 4. TITLE AND SUBTITLE A Comparative Analysis of Fortress (ES520) and 5. FUNDING NUMBERS Mesh Dynamics’ (4000 Series) Networking Capabilities During Coasts 2007 Field Experiments 6. AUTHOR(S) Brian Keith Tyler 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8.
    [Show full text]
  • Using VAPS XT 661 Course Syllabus
    Using VAPS XT 661 Course Syllabus Session duration: Classroom 1.5 days Main Objective In this course, you will learn the basics of VAPS XT and leverage the 661 module to build ARINC 661 applications including how to create and add new widgets or objects with the tool. The course also covers how to build the VAPS XT 661 definition files, UA layers and widget sets. Upon completion of the course, the participant should be able to create formats and objects and be able to generate executables from these formats. You will understand how to use the major predefined objects in VAPS XT and will be able to create your own. Target Audience This is an ideal course for individuals to use the VAPS XT 661 module to design graphic applications. Prerequisites This course assumes basic PC knowledge and basic knowledge of VAPS XT regular mode. Format This Instructor-led course is taught through a series of lectures and hands-on exercises in which you learn how to use the ARINC 661 components of the tool. Topics Covered Explanation of the ARINC 661 Standard Using VAPS XT in the A661 mode Using the displays and windows Creating a graphical widget Creating a coded widget 1 Daily Outline for Classroom “Using VAPS XT 661” Course Day 1 Lesson 1: Explanation of the ARINC 661 Standard Lesson 2: Using VAPS XT in the A661 mode Lesson 3: Using the displays and windows Lesson 4: Creating a graphical widget Day 2 Lesson 5: Creating a coded widget Recap of the 5 lessons Questions and Answers specific from trainees Closing the course 2 Detailed Description
    [Show full text]
  • Leveraging Abstract User Interfaces
    Non-visual access to GUIs: Leveraging abstract user interfaces Kris Van Hees and Jan Engelen Katholieke Universiteit Leuven Department of Electrical Engineering ESAT - SCD - DocArch Kasteelpark Arenberg 10 B-3001 Heverlee, Belgium [email protected], [email protected] Abstract. Various approaches to providing blind users with access to graphi- cal user interfaces have been researched extensively in the past 15 years, and yet accessibility is still facing many obstacles. Graphical environments such as X Windows offer a high degree of freedom to both the developer and the user, complicating the accessibility problem even more. Existing technology is largely based on either a combination of graphical toolkit hooks, queries to the applica- tion and scripting, or model-driven user interface development. Both approaches have limitations that the proposed research addresses. This paper builds upon past and current research into accessibility, and promotes the use of abstract user interfaces to providing non-visual access to GUIs. 1 Introduction Ever since graphical user interfaces (GUIs) emerged, the community of blind users has been concerned about its effects on computer accessibility [1]. Until then, screen readers were able to truly read the contents of the screen and render it in tactile and/or audio format. GUIs introduced an inherently visual interaction model with a wider variety of interface objects. MS Windows rapidly became the de facto graphical environment of choice at home and in the workplace because of its largely consistent presentation, and the availability of commercial screen readers created somewhat of a comfort zone for blind users who were otherwise excluded from accessing GUIs.
    [Show full text]
  • Fakultät Informatik
    Fakultät Informatik TUD-FI08-09 September 2008 Uwe Aßmann, Jendrik Johannes, Technische Berichte Albert Z¨undorf (Eds.) Technical Reports Institut f¨ur Software- und Multimediatechnik ISSN 1430-211X Proceedings of 6th International Fujaba Days Technische Universität Dresden Fakultät Informatik D−01062 Dresden Germany URL: http://www.inf.tu−dresden.de/ Uwe Aßmann, Jendrik Johannes, Albert Zündorf (Eds.) 6th International Fujaba Days Technische Universität Dresden, Germany September 18-19, 2008 Proceedings Volume Editors Prof. Dr. Uwe Aßmann Technische Universität Dresden Departement of Computer Science Institute for Software and Multimedia Technologie Software Technologie Group Nöthnitzer Str. 46, 01187 Dresden, Germany [email protected] DIpl. Medieninf. Jendrik Johannes Technische Universität Dresden Departement of Computer Science Institute for Software and Multimedia Technologie Software Technologie Group Nöthnitzer Str. 46, 01187 Dresden, Germany [email protected] Prof. Dr. Albert Zündorf University of Kassel Chair of Research Group Software Engineering Department of Computer Science and Electrical Engineering Wilhelmshöher Allee 73, 34121 Kassel, Germany [email protected] Program Committee Program Committee Chairs Uwe Aßmann (TU Dresden, Germany) Albert Zündorf (University of Kassel, Germany) Program Commitee Members Uwe Aßmann (TU Dresden, Germany) Jürgen Börstler (University of Umea, Sweden) Gregor Engels (University of Paderborn, Germany) Holger Giese (University of Paderborn, Germany) Pieter van Gorp (University of Antwerp, Belgium) Jens Jahnke (University of Victoria, Canada) Mark Minas (University of the Federal Armed Forces, Germany) Manfred Nagl (RWTH Aachen, Germany) Andy Schürr (TU Darrmstadt, Germany) Wilhelm Schäfer (University of Paderborn, Germany) Gerd Wagner (University of Cottbus, Germany) Bernhard Westfechtel (University of Bayreuth, Germany) Albert Zündorf (University of Kassel, Germany) Editor’s preface For more than ten years, Fujaba attracts a growing community of researchers in the field of software modelling.
    [Show full text]
  • Graphical User Interfaces As Updatable Views
    Portland State University PDXScholar Dissertations and Theses Dissertations and Theses 2009 Graphical User Interfaces as Updatable Views James Felger Terwilliger Portland State University Follow this and additional works at: https://pdxscholar.library.pdx.edu/open_access_etds Part of the Computer Engineering Commons, and the Computer Sciences Commons Let us know how access to this document benefits ou.y Recommended Citation Terwilliger, James Felger, "Graphical User Interfaces as Updatable Views" (2009). Dissertations and Theses. Paper 2671. https://doi.org/10.15760/etd.2672 This Dissertation is brought to you for free and open access. It has been accepted for inclusion in Dissertations and Theses by an authorized administrator of PDXScholar. Please contact us if we can make this document more accessible: [email protected]. DISSERTATION APPROVAL The abstract and dissertation of James Felger Terwilliger for the Doctor of Philosophy in Computer Science were presented on November 26, 2008, and accepted by the dis- sertation committee and the doctoral program. COMMITTEE APPROVALS: Lois Delcambre, Chair David Maier Leonard Shapiro Andrew Black Robert Bertini Representative of the Office of Graduate Studies DOCTORAL PROGRAM APPROVAL: Wu-Chi Feng, Director Computer Science Ph.D. Program ABSTRACT An abstract of the dissertation of James Felger Terwilliger for the Doctor of Philosophy in Computer Science presented November 26, 2008. Title: Graphical User Interfaces as Updatable Views In contrast to a traditional setting where users express queries against the database schema, we assert that the semantics of data can often be understood by viewing the data in the context of the user interface (UI) of the software tool used to enter the data.
    [Show full text]
  • The Design of a GUI Paradigm Based on Tablets, Two-Hands, and Transparency
    The Design of a GUI Paradigm based on Tablets, Two-hands, and Transparency Gordon Kurtenbach, George Fitzmaurice, Thomas Baudel, and Bill Buxton Alias | Wavefront 110 Richmond Street East Toronto, Canada, M5C 1P1 <gordo, gf, tbaudel, buxton>@aw.sgi.com 1+ 416 362-9181 ABSTRACT between UI widgets and the artwork where a large majority An experimental GUI paradigm is presented which is based of the UI widgets exist around the edge of the artwork. The on the design goals of maximizing the amount of screen first design tension could be addressed by a larger screen used for application data, reducing the amount that the UI with the cost being the expense of a larger display. How- diverts visual attentions from the application data, and ever, as screen size increases the second design tension increasing the quality of input. In pursuit of these goals, we becomes a problem. As the screen and artwork become integrated the non-standard UI technologies of multi-sensor larger the distance a user must travel to/from a tool palette tablets, toolglass, transparent UI components, and marking or menu increases. This results in longer task times. Fur- menus. We describe a working prototype of our new para- thermore, a user's focus of attention must constantly change digm, the rationale behind it and our experiences introduc- from some point on the artwork to a UI widget at the edge ing it into an existing application. Finally, we presents some of the screen and then refocus on the artwork again. Divid- of the lessons learned: prototypes are useful to break the ing attention in this manner requires additional time to barriers imposed by conventional GUI design and some of reacquire the context and can also result in users missing their ideas can still be retrofitted seamlessly into products.
    [Show full text]
  • Computer Basics Handout
    Computer Basics Handout To register for computer training at Kitsap Regional Library please call your local branch: Bainbridge: 206-842-4162 Downtown Bremerton: 360-377-3955 Kingston Library: 360-297-3330 Little Boston: 360-297-2670 Manchester: 360-871-3921 Port Orchard: 360-876-2224 Poulsbo: 360-779-2915 Silverdale Library: 360-692-2779 Sylvan Way: 360-405-9100 or Toll-Free 1-877-883-9900 Visit the KRL website www.krl.org for class dates and times. Welcome to Computer Basics at Kitsap Regional Library. This ninety-minute lesson offers an introduction to computers, their associated hardware and software, and provides hands-on training to help you acquire the basic computer skills necessary to begin using a computer comfortably. Students enrolled in this Computer Basics class will learn: • to identify the various components of a computer • how to use the Mouse and scroll bar • how to log-on and off the library computers • the basics of the Internet browser and KRL home page • how to use the library’s online catalog (KitCat) Computers can be used for many different purposes: locate information, communicate, manage finances, purchase goods and services, or simply be entertained by music and movies. The full capabilities of a computer are dependent upon the technology included or added to its core structure. There are many tasks you can accomplish using the computers here at the Kitsap Regional library, for example a library user can: Locate Information: Access the Internet Search the library’s print and media collection using the KitCat Catalog
    [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]
  • Mixing Board Vs. Mouse Interaction in Parameter Adjustment Tasks
    Mixing Board Versus Mouse Interaction In Value Adjustment Tasks Steven Bergner, Matthew Crider, Arthur E. Kirkpatrick, Torsten Moller¨ School of Computing Science, Simon Fraser University, Burnaby, BC, Canada We present a controlled, quantitative study with 12 participants comparing interaction with a haptically enhanced mixing board against interaction with a mouse in an abstract task that is motivated by several practical parameter space exploration settings. The study participants received 24 sets of one to eight integer values between 0 and 127, which they had to match by making adjustments with physical or graphical sliders, starting from a default position of 64. Based on recorded slider motion path data, we developed an analysis algorithm that identifies and measures different types of activity intervals, including error time moving irrelevant sliders and end time in breaks after completing each trial item. This decomposition facilitates data cleaning and more selective outlier removal, which is adequate for the small sample size. Our results showed a significant increase in speed of the mixing board interaction accompanied by reduced perceived cognitive load when compared with the traditional mouse-based GUI interaction. We noticed that the gains in speed are largely due to the improved times required for the hand to reach for the first slider (acquisition time) and also when moving between different ones, while the actual time spent manipulating task-relevant sliders is very similar for either input device. These results agree strongly with qualitative predictions from Fitts’ Law that the larger targets afforded by the mixer handles contributed to its faster performance. Our study confirmed that the advantage of the mixing board acquisition times and between times increases, as more sliders need to be manipulated in parallel.
    [Show full text]
  • Chapter Five Multiple Choice Questions 1. Which of the Following
    Chapter Five Multiple Choice Questions 1. Which of the following is not a characteristic of direct manipulation interfaces? a. Visibility of the objects and actions of interest. b. Menu selection and form fill-in. c. Rapid, reversible, incremental actions. d. Replacement of typed commands by a pointing action on the object of interest. 2. Augmented reality is _______________. a. The same thing as virtual reality b. A type of dashboard displaying a large volume of information at one time. c. An innovation in which users see the real world with an overlay of additional information. d. The use of haptic interaction skills to manipulate objects and convert the physical form to a digital form. 3. Drawbacks of direct manipulation include all of the following except _____________. a. Designs may consume valuable screen space. b. Users must learn the meanings of visual representations. c. Visual representation may be misleading d. The gulf of execution is increased 4. Remote environments are complicated by ______________. a. The gulf of execution, the gulf of evaluation, and time delays. b. Time delays, incomplete feedback, and unanticipated interferences. c. Supervisory control, lack of multiple coordinated views, and time delays d. Lack of precision, supervisory control, time delays, and gulf of execution. 5. All of the following are good guidelines for use of icons except _________________. a. Represent the object or action in a familiar and recognizable manner. b. Carefully consider three-dimensional icons; they are eye-catching but also can be distracting. c. Limit the number of different icons. d. Make the icon blend in with its background.
    [Show full text]
  • Graphical Widgets for Helvar IP Driver Installation and User Guide
    Graphical Widgets for Helvar IP Driver Installation and User Guide Doc. No. D005608 Iss. 1 Graphical Widgets for Helvar IP Driver Table of Contents 1 Revision History ....................................................................................................................... 3 2 Document Outline .................................................................................................................... 3 3 Scope ....................................................................................................................................... 3 4 Safety Precautions .................................................................................................................. 3 5 General Description ................................................................................................................. 3 6 System Requirements ............................................................................................................. 4 7 Disclaimer ................................................................................................................................ 4 8 Installation ................................................................................................................................ 4 9 Widget Overview ..................................................................................................................... 5 10 Adding a Widget onto a PX file ............................................................................................... 5 10.1 Adding a widget
    [Show full text]
  • Prismtm Graphics Toolkit
    PrismTM Graphics Toolkit Create Stunning User Interfaces in Record Time Prism™ is a complete family of leading edge graphical interface development tools and libraries created by Blue Water Embedded, Inc. Prism is a complete framework and toolset for designing and deploying advanced graphical interfaces on embedded systems, providing everything a developer needs to make your UI visions a reality. The Prism family includes the following components. PRISM RUNTIME FRAMEWORK™ Prism Runtime Framework is our runtime framework incorporating a complete high-performance graphical drawing library and GUI widget set. This framework provides all of the necessary nuts and bolts to enable you to display professional quality graphics on nearly any target system capable of graphical output. Prism Runtime Framework allows you to incorporate any number of fonts, images, strings and other assets seamlessly on your embedded target, with or without a file system. The widget set includes a wide variety of buttons, panels, scroll bars, text display and rich text editing controls, sliders, charts, graphs, animations, icons, and other graphical widget types. Developers can easily add their own custom widgets to the framework. Any combination of input devices including keypad, keyboard, touch screen, mouse, and multi-touch capable input devices can be utilized within this framework. Variations of Prism Runtime Framework are available for all color depths, screen resolutions, and hardware capabilities. Color depths ranging from monochrome to full 32-bit-per-pixel drawing with alpha channel are fully supported. Prism Runtime Framework is provided ready to run on your embedded target without requiring any underlying support. Prism Runtime Framework is also provided in convenient desktop configurations, meaning that you can build and execute your complete UI design in a Microsoft Windows or Linux/X11 environment well before the availability of your target hardware.
    [Show full text]