DOCSLIB.ORG

Introduction Part 1 Learning Turbo Vision Chapter 1 Inheriting the Wheel Chapter 2 Writing Turbo Vision Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction Part 1 Learning Turbo Vision Chapter 1 Inheriting the Wheel Chapter 2 Writing Turbo Vision Applications c o N T E N T s Introduction 1 Chapter 2 Writing Turbo Vision Why Turbo Vision? ...... ..... ...... 1 applications 23 What is Turbo Vision? ....... ..... 1 Your first Turbo Vision application .. .. 2S What you need to know . .. ... ... 2 The desktop, menu bar, and status line . 25 What's in this book? . .. ... .. ... .. .. 2 The desktop ..... ... .... .. .. " 26 ll1e status line ... .. .. ..... .... , 26 Part 1 Learning Turbo Vision Creating new commands . .. .. .... 27 Chapter 1 Inheriting the wheel 7 ll1e menu bar . ... .. .. ...... .. 28 The framework of a windowing A note on structure . .. 30 application. .. 7 Opening a window . .. 31 A new Vision of application development. 8 Standard window equipment. .. 31 The elements of a Turbo Vision Window initialization . .. .. 33 application . .. 9 The Insert method . ... .......... 33 Naming of parts ... .. .. : .... 9 Closing a window . .. 34 Views .......... .. .... .. 9 Window behavior . .. 34 Events .. .... .. .. .. .. .. 9 Look through any window . 35 Mute objects . .. 10 What do you see? ........ .. .... 37 A common "look and feel" .. ....... 10 A better way to Write .. ..... .. 38 "Hello, World!" Turbo Vision style ... 12 A simple file viewer . 38 Running HELLO.PAS . ....... .. 13 Reading a text file ... ....... .. 39 Pulling down a menu ... ..... ... 14 Buffered drawing . .. 40 A dialog box . .... ... ... ... 15 The draw buffer ...... ... ...... 40 Buttons . ..... .. ...... .. .. ..... 15 Moving text into a buffer ........ 41 Getting out . 16 Writing buffer contents ... .. .... 41 Inside HELLO.PAS .. .. .... ... ... .. 16 Knowing how much to write . ... 42 ll1e application object . .. .... ... .. 17 Scrolling up and down . ......... .. 42 ll1e dialog box object . .. .. .. .... 18 Multiple views in a window . .. 45 Flow of execution and debugging .... 19 Where to put the functionality ' " . 46 HELLO's main program. 19 Making a dialog box .... .. .. , . .. 47 ll1e lnit method .. ........... .. 20 Executing a modal dialog box . .. .. 49 TI1e Run method . .. 20 Taking control . 50 ll1e Done method ..... ... .. 21 Button, button... .. 50 Summary . .. .. .. .... ........ .. 21 Nonnal and default buttons " .. .. 52 Focused controls ..... ....... .. ' . 52 Take your pick ....... ........ 53 Creating a duster 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 53 Frames. 0 0 0 • •• 0 0 0 0.' 0 . 0 •• 0 0 0 o. 0 0 75 Check box values 00 0 000 0 000000000 53 Buttons 0 •• • 0 0 • • 0 0 • o • • 0 • 0 • 0 00 •• 0 0 75 One more cluster 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 54 Clusters o. 0 • • 0 0 0 0 • • 0 0 0 0 0 • o. 0 • • 0 0 75 Labeling the controls 0 0 0 0 0 0 0 0 0 0 0 00 0 0 55 Menus 0 ••• 00 • • 0. 0. o. 0 " 0 0 •• • 0. 0 0 75 TI1e input line object 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 55 Histories 0 0 • 0 •• 0 • • • • 0 • 0 • • 0 • 0 0 • 0 0 0 76 Setting and getting data 0 0 0 0 0 0 0 0 0 •• 00 56 Input lines o. 0 •• 0 •• • 0 •• 0 • •• 0 0 0 0 0 0 76 Shortcut keys and conflicts o. 0 0 • • 0 0 0 0 59 List viewers 0 0 • • • 0 • 0 • 0 • • • 0 0 0 • 0 • 0 0 76 Ending the dialog box 0 0 0 0 0 0 0 •• 0 • 0 0 0 61 Scrolling objects 0 0 • 0 0 0 0 • 0 0 0 0 0 • 0 0 0 76 Other dialog box controls o. 0 • 0 0 0 • • 0 0 • • 61 Text devices 0 • • • 0 • 0 ••• • • • 0 0 • • • • •• 77 Static text .. 0 0 0 • ••••• o. 0 • • 0 •• 0 • • • • • 61 Static text ... 0 •• 0 •••••• 0 0 •• • • o. 77 List viewer 0 0 • • • 0 • 0 •• 0 0 0 • • • 0 0 • • 0 •• 0 61 Status lines 0 • 0 0 • •• •• • 0 0 • • 0 0 • 0 • • • 0 78 List box .. 0 • 000 0 00 .0 00 • • • • ••• 0 o •• 0 62 Non-visible elements 0 0 •• • 0 •• 0 • •• 0 0 • o. 78 fiistory . 0 0 0 0 0 • 0 0 0 0 0 0 0 0 0 0 0 0 • • 0 0 • 0 0 0 62 Streams 0 0 0 0 •• • 00 ••• 0.00 0. o. o. 0 • ••• 78 Standard dialog boxes 0 0 0 0 0 0 0 • 0 • • 0 0 • •• 62 DOS streams . 0 0 0 0 0 • • • 0 0 0 0 0 • 0 0 • 0 0 79 Buffered streams 0 0 • 0 0 • • • • • 0 0 •• 0 0 0 79 Part 2 Programming Turbo Vision EMS streams 0 0 0 0 0 0 0 • 0 0 0 0 0 0 0 0 • 0 0 0 79 Chapter 3 The object hierarchy 65 Resources .. 0 • 0 0 0 0 0 0 0 • • •• 0 • 0 • 0 0 • 0 •• 79 Collections 0 0 0 • 0 0 0 0 0 0 0 0 0 • 0 • 0 •• 0 • • o. 79 Object typology 0 • 0 0 0 0 0 0 0 • 0 0 0 0 0 0 0 0 0 0 0 0 67 Sorted collections .. .. 0 •• • • 0 80 Abstract objects 0 0 • 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 67 String collections 0 0 0 0 • ••• 0 0 • • • • 0 0 0 80 Abstractmetl10ds 0 • • • • o. 0 0 0 0 o. 0 0. 00 68 Resource collections 0 • 0 ••• 0 0 •• 0 •• 0 80 Object instantiations and derivations 0 0 0 68 String lists 0 0 0 0 0 • 0 0 •• 0 0 • 0 0 • 0 0 0 0 • • o. 80 Instantiation 0 0 0 0 0 0 0 0 0 0 0 • 0 • • 0 0 0 0 0 • • 68 Derivation 0 0 0 0 0 0 0 0 0 0 •• 0 0 0 0 0 0 •• 0 0 0 0 69 Chapter 4 Views 81 Turbo Vision methods 0 0 0 0 0 •• • 0 0 0 0 ••• 0 69 "We have taken cantrol of your TV .. 0" 81 Abstract methods . 0 0 0 0 0 0 •• •• 0 0 0 • •• 69 Simple view objects ... 0 0 • 0 •• 0 0 0 0 • 0 0 0 0 82 Pseudo-abstract methods 0 0 0 • 0 • 0 0 0 • 0 70 Setting your sigh ts . .. 0 0 0 •••• 0 0 0 0 • 0 0 82 Virtual methods . 0 0 • 0 0 ••• • 0 • • • • • • •• 70 Getting the TPoint 000 • • • • 00 • • 000 • • 83 Static methods 0 • • 0 • 0 • 0 0 •••• 0 • 0 • • ••• 70 Getting into a TRect 0 • 0 • • o. 0 • •• 0 o. 83 Turbo Vision fields 0 0 • 0 0 0 •• 0 •• 0 • 0 • • 0 •• 70 Turbo Vision coordinates . o ••• 000 0 84 Primitive object types. 0 •• ••• 0 0 • • • 0 • • • • 71 Making an appearance .. 0 0 0 0 0 • 0 0 0 0 0 0 84 TPoint 00 •• 0 0 0 . 000 .0 00 .0 0 .0 . 0 •• 0 . 00 72 Territoriality .. 0 0 0 0 • 0 0 0 •• 0 • •• • 0 0 0 85 TRect. 0 0.00 ••• : •• • 00 •• 0 o. o. o. 0 •• • •• 72 Drawing on demand 0 0 0 0 0 0 • 0 0 • •• 0 85 TObject .. 0 • 0 • • , 0 •• •• 0 0 ••• 0 0 0 • 0 0 • 0 0 72 Putting on your best behavior . 0 • 0 • • • 85 Views .. 0 0 o. 0.0 ••• 000 • • 0 ••• • 0 •• 0 ••• 0 72 Complex views 0 0 0 •• 0 0 0 0 0 •• 0 0 0 0 0 0 0 0 0 0 86 Views overview .. 0 • 0 0 0 • •••••••• " 73 Groups and subviews 0000000 . 0 • 0 00 0 86 Groups. 0 •• 0 . 0. 00 •• • 0000 •••• • 000 . 0 73 Getting into a group . 0 0 0 0 • 0 • 0 • 0 •• 0 • • 87 The abstract group . 0 0 0 • • 0 • 0 : 0 0 , 0 0 73 Another angle on Z-order 0 0 • •• • 0 0 0 88 Desktops .0 . 0 •• 0 00 0 000 0 .0 0 ' : • 0 • 0 74 Group portraits 0 • 0 0 • 0 0 0 0 • 0 0 0 0 • • 0 • • 0 89 Programs . ... .. 0 • ••••• 0 •• • • • 0 74 Relationships between views . 0 0 0 • • ,0 90 Applications . .. 0 0 0 0 •• •• • 0 0 • 0 •• • 74 The object hierarchy . 0 • •• 0 0 0 0 •• 0 • 0 91 Windows .. 0 0 0 • • • 0 0 • • 00 0 •• • o. 0 0 , 74 Ownership 0 • 0 0 0 • 0 • 0 0 • 0 • 0 • 0 • 0 0 0 0 0 91 Dialog boxes . 0 0 0 0 0 0 •• • 0 • 0 0 • 0 • o. 74 Subviews and view trees 0 0 • 0 • • 0 0 0 0 0 0 92 Terminal views 0 ••• • 0 0 0 0 0 •• 0 • 0 0 • 0 o. 75 75 SeJected and focused views . .. 95 Chapter 5 Event-driven 75 Finding the focused view .. .... .. 96 programming 109 75 How does a view get the focus? .. .. 96 Bringing Turbo Vision to life ... .. .. 109 75 The focus chain . .. 97 Reading the user's input . .......... 109 76 Modal views . .. ... ......... ...... 97 The nature of events .. ... ... ......... 1111 76 Modifying default behavior . .......... 98 Kinds of events .... .. 111 76 TIle Options flag word . 98 Mouse events .................. 112 7 ofSelectabJe . .. ............... 99 Keyboard events . .. 112 n ofTopSelect ... ... ...... .... 99 Message events . ............... 112 77 ofFirstGick . .... ... .. ........... 99 "Nothing" events ............... 112/ 78 ofFramed .. ... ... ............ 99 Events and commands. .. 113 78 ofPreProcess ... ... ... .... ..... 99 Rou ting of events ........... .. ... 113 7 ofPostProcess . 99 Where do events come from? ....... 113 79 ofBuffered ... .. ... .. .... .. 100 Where d o events go? ..... .. ... .... 114 79 ofTileable . .. 100 Positional events. .. 114 79 ofCenterX ..... .. ... .... , 100 Focused events ..... .. ...... .. 115 79 ofCenterY . ......... .. .. ... ... 100 Broadcast events . .. 115 79 ofCentered . .. 101 User-defined events ... ..... .. 116 TIle GrowMode flag byte . ...... 101 Masking events . ................. 116 o gfGrow LoX ......... .. ... ... 101 Phase . .. ... ..... ............ ... 116 o gfG rowLoY .............. .. ... 101 The Phase field . ...... .. ....... 118 o gfGrow HiX ... .. .............. 101 Commands ..... ........... ...... 119 gfGrowHiY . .. ...... ... 101 Defining commands . .. 119 gfGrow All . .. ... .. ... .. .. .. 101 Binding commands .. .. ....... .. 120 gfGrowRel ..... ..... .. .. .. 101 Enabling and disabling commands .. 120 TIle DragMode flag byte ..... .. ... 102 Handling events ... .. 121 dmDragMove ....... ... :... ... 102 The event record.
Load more

Recommended publications
  • A Java Implementation of a Portable Desktop Manager Scott .J Griswold University of North Florida
    UNF Digital Commons UNF Graduate Theses and Dissertations Student Scholarship 1998 A Java Implementation of a Portable Desktop Manager Scott .J Griswold University of North Florida Suggested Citation Griswold, Scott .,J "A Java Implementation of a Portable Desktop Manager" (1998). UNF Graduate Theses and Dissertations. 95. https://digitalcommons.unf.edu/etd/95 This Master's Thesis is brought to you for free and open access by the Student Scholarship at UNF Digital Commons. It has been accepted for inclusion in UNF Graduate Theses and Dissertations by an authorized administrator of UNF Digital Commons. For more information, please contact Digital Projects. © 1998 All Rights Reserved A JAVA IMPLEMENTATION OF A PORTABLE DESKTOP MANAGER by Scott J. Griswold A thesis submitted to the Department of Computer and Information Sciences in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences UNIVERSITY OF NORTH FLORIDA DEPARTMENT OF COMPUTER AND INFORMATION SCIENCES April, 1998 The thesis "A Java Implementation of a Portable Desktop Manager" submitted by Scott J. Griswold in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences has been ee Date APpr Signature Deleted Dr. Ralph Butler Thesis Advisor and Committee Chairperson Signature Deleted Dr. Yap S. Chua Signature Deleted Accepted for the Department of Computer and Information Sciences Signature Deleted i/2-{/1~ Dr. Charles N. Winton Chairperson of the Department Accepted for the College of Computing Sciences and E Signature Deleted Dr. Charles N. Winton Acting Dean of the College Accepted for the University: Signature Deleted Dr.
    [Show full text]
  • LWUIT Developer's Guide
    Lightweight UI Toolkit Developer’s Guide Part No. 07-08-10 July 2010 Copyright © 2008, 2010 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • UI Manager Properties
    APPENDIX A UI Manager Properties THROUGHOUT THIS BOOK YOU'LL FIND TABLES that list the property names and data types for all the UIResource elements of specific Swing components. Although these tables serve to list all the information about a specific component, I fig­ ured it would be handy to also group all the information about property names in one place. With that in mind, Table A-1 provides a complete list of properties used by the predefined look and feel classes-Motif, Macintosh, Metal, and Windows­ provided with the Swing 1.1.1 release. The table indicates with an "X" which of the four look and feel classes uses a particular property. To change the default setting for any one of these properties, you need to notify the UIManager by storing a new setting in the lookup table of the UIManager. For instance, to change the default text for the "Yes" button on a JOptionPane, 11 you'd replace the 0ptionPane. yesButtonText II property with the new setting 11 11 UIManager. put ( 0ptionPane. yesButtonTextll, Si II);. Then, any component cre­ ated after the setting change will get the new value: 11 5i 11 .1fyou want a displayed component to get the new setting, you must call its updateUI () method. When you change the current look and feel, any custom settings you install may be lost. If the class of the property value setting implements the UIResource interface (an empty marker interface such as Serializable), then the setting will be replaced by the default setting of the look and feel.
    [Show full text]
  • Translate's Localization Guide
    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
    [Show full text]
  • Appendix 1 the Borland Pascal Package
    Section 1. Installation 555 Appendix 1 The Borland Pascal Package Section 1. Installation When you open your carton of Borland Pascal, you may be frightened by the tens of kilos of books and mountain of disks. This Appendix will get you started on installation and use of the system to write your Pascal programs. Even if you have already installed Borland Pascal and are using it, you may find some useful tips here, so please thumb through these pages. (There is much useful information in the Borland Pascal User's Guide, which is in your package.) For starters, your computer should have a goodly chunk of free disk space in one hard disk partition. If you install the complete Borland Pascal system, that will take about 30M. The programs with this book will fill about 2M, and when you start writing programs, who knows? Before you start installation, decide which partition to use, and note how much free disk space is available. Don't push a partition to its absolute limit. Start the "Install" program by inserting Disk 1 into the A: drive and typing A:INSTALL <Enter> (By the time this book appears you will probably be able to acquire BP on CD­ ROM and install it that way.) The "Install" program gives you lots of options, and explains what it is doing as it runs. If you have adequate disk space, the easiest course is to install everything. If you want to install only what you need for using this book, when the "Install" program prompts you for what to install/omit, you can omit the Windows version, the Assembler, the Profiler, the Debugger, the Turbo Vision package, and the On-line compilers.
    [Show full text]
  • BORLAND Turbo Pascafbj Version 6.0
    BORLAND Turbo PascafBJ Version 6.0 Turbo Vision Guide BORLAND INTERNATIONAL INC. 1800 GREEN HILLS ROAD P.O. BOX 660001, scons VALLEY, CA 95067-0001 Copyright © 1990 by Borland International. All rights reserved. All Borland products are trademarks or registered trademarks of Borland International, Inc. Other brand and product names are trademarks or registered trademarks of their respective holders. PRINTED IN THE USA. R2 10 9 8 7 6 5 4 3 2 1 c o N T E N T s Introduction 1 Chapter 2 Writing Turbo Vision Why Turbo Vision? ................... 1 applications 23 What is Turbo Vision? ................. 1 Your first Turbo Vision application . .. 23 What you need to know ............... 2 The desktop, menu bar, and status line .. 25 What's in this book? ................... 2 The desktop . .. 26 The status line . .. 26 Part 1 Learning Turbo Vision Creating new commands. .. 27 Chapter 1 Inheriting the wheel 7 The menu bar ..................... 28 The framework of a windowing A note on structure . .. 30 application . .. 7 Opening a window. .. 31 A new Vision of application development. 8 Standard window equipment . .. 31 The elements of a Turbo Vision Window initialization .............. 33 application . .. 9 The Insert method ............... 33 Naming of parts .................... 9 Closing a window. .. 34 Views ........................... 9 Window behavior . .. 34 Events ........................... 9 Look through any window . .. 35 Mute objects. .. 10 What do you see? .................. 37 A common "look and feel" .......... 10 A better way to Write. .. 38 "Hello, World!" Turbo Vision style ..... 12 A simple file viewer .. .. 38 Running HELLO.PAS .............. 13 Reading a text file .. .. 39 Pulling down a menu. .. 14 Buffered drawing .................
    [Show full text]
  • Mohsen Aghajani Professional Curriculum Vitae
    Mohsen Aghajani Professional Curriculum Vitae Objective Programming, Project Management, Analysis, Network, Network Security and Application Security Other interests: Model making for various kind of software projects, Database Programming, Web Programming, Virtual Intelligence Programming, Operating Systems (Design and implementation), Integrated management systems (MIS). Interested in network planning, implementation and management, staff instruction and teaching, user management, security planning, find security holes to stop intruders and security planning in remote environments. Experience 1994 – 1998 ● Design and implementation of various customer based software ● Programming of a Persian library system for DOS ● Producing a mathematic learning program for high school students in BASIC ● Programming a Persian editor in Pascal Turbo Vision environment ● Experimental Virtual Intelligence programming ● Programming of a graphical API for Persian language in Pascal ● Programming of a Derive (n level) program in assembly ● Producing API for a text based GUI library in Pascal ● Producing resident applications in Pascal under DOS 1998 – 2002 ● Reprogramming of library system under Windows ● Implementing a note taking application under Windows ● Producing Aseman (A multimedia astronomy application) ● Producing Components World (A toolbox for Delphi developers) ● Programming in Saraye Honar project (A multimedia project for NikRayan Institute) ● Producing ArmVector (A graphic toolbox for NikRayan Institute) ● Producing lottery application
    [Show full text]
  • The Law of Look and Feel
    THE LAW OF LOOK AND FEEL * † PETER LEE & MADHAVI SUNDER ABSTRACT Design—which encompasses everything from shape, color, and packaging to user interface, consumer experience, and brand aura—is the currency of modern consumer culture and increasingly the subject of intellectual property claims. But the law of design is confused and confusing, splintered among various doctrines in copyright, trademark, and patent law. Indeed, while nearly every area of IP law protects design, the law has taken a siloed approach, with separate disciplines developing ad hoc rules and exceptions. To address this lack of coherence, this Article provides the first comprehensive assessment of the regulation of consumers’ aesthetic experiences in copyright, trademark, and patent law—what we call “the law of look and feel.” We canvas the diverse ways that parties have utilized (and stretched) intellectual property law to protect design in a broad range of products and services, from Pac-Man to Louboutin shoes to the iPhone. In so doing, we identify existing doctrines and principles that inform a normatively desirable law of look and feel that courts and Congress should extend throughout IP law’s protection of design. We argue that design law should protect elements of look and feel but remain sensitive to eliminating or mitigating exclusive rights in response to evolving standardization, consumer expectations, and context. Notably, our normative conception of design protection sometimes departs quite starkly from how courts have expansively conceptualized look and feel as protectable subject matter. Going further, we argue that the new * Professor of Law and Chancellor’s Fellow, University of California, Davis.
    [Show full text]
  • Modifying Your Navigation Menu
    Modifying your Navigation Menu The left side navigation pane is configured differently than your regular web site pages. You can add and remove links to your site pages, change how the menu is ordered and how the menu itself is displayed. By default, when you create a page it will show in the navigation menu. Automatically created links have icons that look like this. Manually created links have icons that look like this. note: Keep in mind that the navigation pane is designed to streamline your site and guide traffic to your web pages. If you will exceed 10 links in the left side pane, then it would be a good idea to speak with the Office of Institutional advancement and request assistance with developing the content and structure of your web site. Navigation Menu Default Settings 1.) If your navigation menu is not displaying your site links correctly, confirm it is configured correctly. Login to SharePoint, navigate to your site and click on Settings->Site settings 2.) At the next page, click on Navigation under the Look and Feel menu. 3.) In the Navigation menu, confirm that the Global Navigation and Current Navigation are set as follows. a.) Global Navigation - Select "Display the same navigation items as the parent site". b.) Current Navigation - Select "Structural Navigation: Display the navigation items below the current site". Leave the "Show Subsites" check box empty, but fill in the "Show Pages" check box. 4.) Scroll down to the "Structural Navigation" configuration. a.) Confirm the Structural Navigation: Sorting is configured to Sort manually. 5.) Scroll further down to view the actual navigation links in the Editing and Sorting window Editing Your Navigation Links New pages will automatically add themselves to the navigation menu, but you must organize the links manually.
    [Show full text]
  • COPYRIGHTING "LOOK and FEEL": MANUFACTURERS TECHNOLOGIES V
    Volume 3, Spring Issue, 1990 COPYRIGHTING "LOOK AND FEEL": MANUFACTURERS TECHNOLOGIES v. CAMS Brett N. Dorny* and Michael K. Friedland* INTRODUCTION Some new technologies fit easily into the preexisting legal frame- work. Immediately upon development, attorneys and courts comfortably place the technology into a familiar category. Rights are certain, trans- actions efficient, and technological progress continues unhindered. Such has not been the case with computer software,~ which, from the first, has resisted neat categorization. A programmer creates software by writing source code, a series of steps, logically arranged, containing commands similar to English words and phrases. Program source code, while distantly resembling free- flowing verse, is devoid of literary--or functional--value. In most common applications, program source code is translated into object code by a program known as a compiler. It is the object code that a computer understands. The object code, an uninterrupted series of zeros and ones, is not only uninteresting to humans, but virtually unintelligible as well. Only in the confluence of unintelligible software (object code) and com- puter hardware is a program given life, making it usable, and therefore appreciable in the marketplace. 2 Nevertheless, both source code and object code are protected by copyright, the body of law traditionally reserved for the protection of literary, cinematic, musical, and other artistic compositions. The marketability of a program depends in large part on its user inter- face. 3 In determining what software to purchase people rarely, if ever, consider the code the computer runs. Typical users are unsophisticated, and easy-to-use programs are in great demand.
    [Show full text]
  • Borland C++ Power Programming
    Borland C++ Power Programming Borland C++ Power Programming Clayton Walnum PROGRAMMING SERIES i SAMS/q3 Borland C++ Power Prog Paula 2-17-93 FM lp7 Borland C++ Power Programming Borland C++ Power Programming 1993 by Que Corporation All rights reserved. Printed in the United States of America. No part of this book may be used or reproduced in any form or by any means, or stored in a database or retrieval system, without prior written permission of the publisher except in the case of brief quotations embodied in critical articles and reviews. Making copies of any part of this book for any purpose other than your own personal use is a violation of United States copyright laws. For information, address Que Corporation, 11711 N. College Ave., Carmel, IN 46032. Library of Congress Catalog No.: 93-83382 ISBN: 1-56529-172-7 This book is sold as is, without warranty of any kind, either express or implied, respecting the contents of this book, including but not limited to implied warranties for the book’s quality, performance, merchantability, or fitness for any particular purpose. Neither Que Corporation nor its dealers or distributors shall be liable to the purchaser or any other person or entity with respect to any liability, loss, or damage caused or alleged to be caused directly or indirectly by this book. 96 95 94 93 8 7 6 5 4 3 2 1 Interpretation of the printing code: the rightmost double-digit number is the year of the book’s printing; the rightmost single-digit number, the number of the book’s printing.
    [Show full text]
  • Interrai Software System – New Look and Feel Guide Interrai New User Interface – Update 2019
    interRAI Software System – New Look and Feel Guide interRAI new user interface – Update 2019 This guide provides interRAI assessors and users an overview of the visual changes of the new user interface introduced to the interRAI Software System. These visual changes are permanent. All functionality remains the same. Please note that the pink screen-shots have been taken from a test environment and will be blue on the live site. We are confident that you will enjoy the modern and fresh new look. If you have any questions or feedback, please contact [email protected]. Home page When you log in, you will immediately notice that the Home, Help and Logout icons which were words, are now picture representations and are situated in the top right-hand corner. Old: New: The panel icons on the Home page remain unchanged. When you click on Client Management, you see visual differences. Old: New: Menu items are now highlighted to indicate where you are (solid dark blue highlight on the left-hand side menu) and an orange highlight will follow your mouse up and down the menu. An upper dark blue line borders the entry fields and highlights your current screen tab orange. A fine blue line displays around the field in which your cursor is sitting. The lower data field labels are also dark blue. A dark blue highlight shows when you hover your mouse over the Search and Clear Search Criteria buttons. Navigation When you enter a client record, you see visual differences on the Client Overview. The field labels are .
    [Show full text]