DOCSLIB.ORG

Iphone Programming

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Iphone Programming Mobile Applications and Services FALL 2013 - iOS basics Navid Nikaein Mobile Communication Department This work is licensed under a CC attribution Share-Alike 3.0 Unported license. What do you need? . Mac OS X 10.5 or above . Notions on OO programming (Objective C) . iOS SDK (Free, registration required) . iOS Dev License (Optional) Student Program: Free Individual Program: $99 Enterprise Program: $399 . An iPhone/iPod Touch/iPad (Optional) ©Navid Nikaein 2013 2 iOS Smart Mobile Devices . iOS 7 . Multi Touch Display (1.136x640) . Storage 8-64 GB . Processor M7 /A7 64 bits, A6, A5 . Graphics Power VR . Memory 1GB DDR2 . Connectivity Secondary USB 2.0 Applications GSM/GPRS/EDGE/UMTS/HSDPA/LTE Wifi 802.11 b/g/n BT Assisted GPS . Double Camera: 8 MP & 1.2MP Primary . HD Audio/VIDEO Applications . Power 3.8 V . Weight 112g ©Navid Nikaein 2013 3 Platform Components . iOS SDK / Tools . Language . Frameworks . Design Strategies ©Navid Nikaein 2013 4 Platform Component - iOS SDK . Tools: .m, .h .nib Xcode Text editor, Debugger & Compiler Interface Builder (UI) storyborad .xib Creates user interface (xml) Instruments (profiler ) Optimize the application Dash Code Create web applications for Safari iOS Simulator (Code-Build-Debug) Dtrace, NSZombies, Guard Mallloc Reference Library ©Navid Nikaein 2013 5 Xcode ©Navid Nikaein 2013 6 App Development Process . Who are your audience ? . What is the purpose of your app? . What problem your app trying to solve? . What content your app incorporate? ©Navid Nikaein 2013 7 Next step . After you have a concept for your app, designing a good user interface is the next step to creating a successful app Storyboard, views ,… Define the interaction Implementing the behaviours ©Navid Nikaein 2013 8 Platform Component - iOS Language . Objective-C / C Extension to (superset of) standard ANSI C with Smalltalk-style messaging designed to give C full OO programming capabilities Primary language for Apple’s Cocoa API C & GCC can be used for low-level programming ©Navid Nikaein 2013 9 A big Picture ©Navid Nikaein 2013 10 Platform Component - iOS Frameworks Name Prefixes Name Prefixes Accelerate.framework cblas, vDSP EventKitUI.framework EK AddressBook.framework AB ExternalAccessory.framework EA AddressBookUI.framework AB Foundation.framework NS AssetsLibrary.framework AL GameKit.framework GK AudioToolbox.framework AU,Audio iAd.framework AD AudioUnit.framework AU ImageIO.framework CG AVFoundation.framework AV IOKit.framework N/A CFNetwork.framework CF MapKit.framework MK CoreAudio.framework Audio MediaPlayer.framework MP CoreData.framework NS MessageUI.framework MF CoreFoundation.framework CF MobileCoreServices.framework UT CoreGraphics.framework CG OpenAL.framework AL CoreLocation.framework CL OpenGLES.framework EAGL, GL CoreMedia.framework CM QuartzCore.framework CA CoreMotion.framework CM QuickLook.framework QL CoreTelephony.framework CT Security.framework CSSM, Sec CoreText.framework CT StoreKit.framework SK CoreVideo.framework CV SystemConfiguration.framework SC EventKit.framework EK UIKit.framework UI ©Navid Nikaein 2013 11 iOS Frameworks: New Name Prefixes Account.framework AC CoreBluetooth.framework CB CoreImage.framework CI Core.MIDI.framework MIDI GLKit.framework GLK GSS.framework gss Twiter.framework TW See appendix B of iOS Technology Overview ©Navid Nikaein 2013 12 frameworks ©Navid Nikaein 2013 13 iOS Design Patterns and Techniques . Model-view-controller design pattern that governs the overall structure of your app . Delegation Transfer information and data from one object to another . Target-Action Translates user interactions with buttons and controls into code that your app can execute . Block-Objects Implement callbacks and asynchronous code . Sandboxing Protect the system and other apps ©Navid Nikaein 2013 14 Platform Component - iOS Design Strategy . Cocoa version of Model-View-Controller (MVC) Assigns objects in an application one of three roles: model, view, or controller Defines the way objects communicate with each other Separate and allow generic view and models Controllers acts as a glue between view and model . MVC allows reusability and flexibility to your application How your model is presented/viewed to the user (UI logic) knows how to draw itself and Encapsulate, manipulate, and process can respond to user actions the data specific to an application ©Navid Nikaein 2013 15 MVC . All about managing the communication between objects ©Navid Nikaein 2013 16 MVCs working together ©Navid Nikaein 2013 17 MVC . Model = manipulate and process data / algorithm / networking Not aware of controller and view To-one and to-many relationship with other model objects Communicate generically using broadcast channel Key-value observing (listen to changes) Notification (NSNotificationCenter) Communication example User actions in the view layer that create or modify data are communicated through a controller object and result in the creation or updating of a model object. When a model object changes (for example, new data is received over a network connection), it notifies a controller object, which updates the appropriate view objects ©Navid Nikaein 2013 18 MVC . View = Display / Event capture / Visual interaction Not aware of controller and model Know how to draw itself and user can interact with it Generic and provides consistency between applications Communicate generically using Target – Action Delegate (Will, did, should) Communication example View objects learn about changes in model data through the application’s controller objects User-initiated changes—for example, text entered in a text field— through controller objects to an application’s model objects. ©Navid Nikaein 2013 19 MVC . Controller = coordination / delegation / dirty job Know about view and model objects Manage views, datas, and application logic and lifecycle App –specific code Communication: A controller object interprets user actions made in view objects and communicates new or changed data to the model layer. When model objects change, a controller object communicates that new model data to the view objects so that they can display it. ©Navid Nikaein 2013 20 Application Object and Delegation . Application template comes with a few existing source code files that set up the app environment. UIApplicationMain function creates the app object to work with iOS create a run loop to deliver events to your app coordinates other high-level app behaviors Called by main.m . UIApplicationMain creates two components Application object: an instance of UIApplication App Delegate Window: creates and keep track of the window where your app’s content is drawn Lifecycle: provides a place to respond to state transitions within the app: ©Navid Nikaein 2013 21 Target-Action . Action Piece of code that’s linked to some kind of event that can occur in your app creating and implementing a method with an IBAction return type and a sender parameter - (IBAction)restoreDefaults:(id)sender; Sender points to the object that triggers the action . Outlet provide a way to reference objects from your interface @property (weak, nonatomic) IBOutlet UITextField *textField; . Control Event provide a way for your code to receive messages from the user interface Touch and drag events Editing events Value-changed events . Navigation controller Manage the transition between the views Navigation stack is LIFO, and the first item is always root view controller ©Navid Nikaein 2013 22 Sandbox . Fine-grained controls that limit the app’s access Hone of the app . App and its preferences and data are placed in sandbox at the install time ©Navid Nikaein 2013 23 Core Objects of an App Image View Text View Button ©Navid Nikaein 2013 24 App States . Not running app has not been launched or was running but was terminated by the system . Inactive running in the foreground but is currently not receiving events . Active running in the foreground and is receiving events . Background Background and executing code Before being suspended Background directly . Suspended Background and not executing code ©Navid Nikaein 2013 25 State Transitions . application:willFinishLaunchingWithOptions first chance to execute code at launch time. application:didFinishLaunchingWithOptions perform any final initialization before your app is displayed to the user. applicationDidBecomeActive Lets your app know that it is about to become the foreground app. Use this method for any last minute preparation. applicationWillResignActive Lets you know that your app is transitioning away from being the foreground app. Use this method to put your app into a quiescent state. applicationDidEnterBackground: Lets you know that your app is now running in the background and may be suspended at any time. applicationWillEnterForeground Lets you know that your app is moving out of the background and back into the foreground, but that it is not yet active. applicationWillTerminate Lets you know that your app is being terminated. This method is not called if your app is suspended. ©Navid Nikaein 2013 26 App Launch Cycle ©Navid Nikaein 2013 27 iOS Architecture . iOS can be viewed as a set of layers HW ©Navid Nikaein 2013 28 iOS Features . Media Graphics . Cocoa touch Audio UIkit Camera & photo lib Multitouch gestures iPod media lib Storyborad Document , printing . Core services iOS simulator . Networking Services Inter-app messaging Store Kit (in-app) Messaging Push notification In-app SMS Game Kit Cut, copy, paste iAd Gyro +
Load more

Recommended publications
  • User Interface Software Tools
    User Interface Software Tools Brad A. Myers August 1994 CMU-CS-94-182 School of Computer Science Carnegie Mellon University Pittsburgh, PA 15213 Also appears as Human-Computer Interaction Institute Technical Report CMU-HCII-94-107 This report supersedes CMU-CS-92-114 from February, 1992, published as: Brad A. Myers. ‘‘State of the Art in User Interface Software Tools,’’ Advances in Human- Computer Interaction, Volume 4. Edited by H. Rex Hartson and Deborah Hix. Norwood, NJ: Ablex Publishing, 1993. pp. 110-150. Abstract Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. This article discusses the different kinds of user interface software tools, and investigates why some approaches have worked and others have not. Many examples of commercial and research systems are included. Finally, current research directions and open issues in the field are discussed. This research was sponsored by NCCOSC under Contract No. N66001-94-C-6037, ARPA Order No. B326. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the official policies, either expressed or implied, of NCCOSC or the U.S. Government. CR CATEGORIES AND SUBJECT DESCRIPTORS: D.2.2 [Software Engineering]: Tools and Techniques-User Interfaces; H.1.2 [Models and Principles]: User/Machine Systems-Human Factors; H.5.2 [Information Interfaces and Presentation]: User Interfaces-User Interface Management Systems; I.2.2 [Artificial Intelligence]: Automatic Programming-Program Synthesis; ADDITIONAL KEYWORDS AND PHRASES: User Interface Software, Toolkits, Interface Builders, User Interface Development Environments.
    [Show full text]
  • An Introduction to Qt 4
    AnAn IntroductionIntroduction toto QtQt 44 Jason Trent [email protected] OOuutltliinnee . Why Trolltech? . Why Qt? . Qt 4 Widgets, Datatypes, and Structures . Qt Designer . qmake . Qt without C++ . Demo WWhhyy TTrroolllltetecchh?? .. QQtt aanndd QQttooppiiaa CCoorree aarree OOppeenn SSoouurrccee .. SSuuppppoorrtteedd bbyy mmuullttii--mmiilllliioonn ddoollllaarr ccoommppaannyy WWhhyy QQt?t? .. MMuullttii--ppllaattffoorrmm – No “virtual machines” or emulation layers – Native compilation for Windows, X11, and Mac • Utilizes core OS technologies (Core, Aero, …) – Extensions - ActiveQt, Motif Migration WWhhyy QQt?t? Over 400 C++ Classes . Not just a GUI toolkit – File handling – Networking – Process handling – Threading – Database access – Event loop processing – XML processing – OpenGL integration – and beyond WWhhyy QQt?t? .. IInntteerrnnaattiioonnaalliizzaattiioonn – Built in support for Unicode and Translation • Language and font aware layouts • Bidirectional font support • Mixed-international interface .. SSeeee QQtt LLiinngguuiisstt ffoorr mmoorree WWhhyy QQt?t? .. NNoott jjuusstt mmuuttllii--ppllaattiiffoorrmm,, mmuullttii--aarrcchhiitteeccttuurree .. QQttooppiiaa CCoorree 44 SSeerriieess – Support for embedded devices • Cell phones, PDAs, etc… – Supports Qt4 widgets with little to no code change QQWWiiddggeett TThhee mmeeeekk mmaayy iinnhheerriitt tthhee eeaarrtthh…… ……bbuutt tthhee eeaarrtthh sshhaallll iinnhheerriitt QQWWiiddggeett QWidget QQtt 44 WWiiddggeetsts .. IInnhheerriitt tthhee aallll--ppoowweerrffuull QQWWiiddggeett .. IInncclluuddee::
    [Show full text]
  • 1 More on Type Checking Type Checking Done at Compile Time Is
    More on Type Checking Type Checking done at compile time is said to be static type checking. Type Checking done at run time is said to be dynamic type checking. Dynamic type checking is usually performed immediately before the execution of a particular operation. Dynamic type checking is usually implemented by storing a type tag in each data object that indicates the data type of the object. Dynamic type checking languages include SNOBOL4, LISP, APL, PERL, Visual BASIC, Ruby, and Python. Dynamic type checking is more often used in interpreted languages, whereas static type checking is used in compiled languages. Static type checking languages include C, Java, ML, FORTRAN, PL/I and Haskell. Static and Dynamic Type Checking The choice between static and dynamic typing requires some trade-offs. Many programmers strongly favor one over the other; some to the point of considering languages following the disfavored system to be unusable or crippled. Static typing finds type errors reliably and at compile time. This should increase the reliability of delivered program. However, programmers disagree over how common type errors are, and thus what proportion of those bugs which are written would be caught by static typing. Static typing advocates believe programs are more reliable when they have been type-checked, while dynamic typing advocates point to distributed code that has proven reliable and to small bug databases. The value of static typing, then, presumably increases as the strength of the type system is inc reased. Advocates of languages such as ML and Haskell have suggested that almost all bugs can be considered type errors, if the types used in a program are sufficiently well declared by the programmer or inferred by the compiler.
    [Show full text]
  • Programming Java for OS X
    Programming Java for OS X hat’s so different about Java on a Mac? Pure Java applica- tions run on any operating system that supports Java. W Popular Java tools run on OS X. From the developer’s point of view, Java is Java, no matter where it runs. Users do not agree. To an OS X user, pure Java applications that ignore the feel and features of OS X are less desirable, meaning the customers will take their money elsewhere. Fewer sales translates into unhappy managers and all the awkwardness that follows. In this book, I show how to build GUIs that feel and behave like OS X users expect them to behave. I explain development tools and libraries found on the Mac. I explore bundling of Java applications for deployment on OS X. I also discuss interfacing Java with other languages commonly used on the Mac. This chapter is about the background and basics of Java develop- ment on OS X. I explain the history of Java development. I show you around Apple’s developer Web site. Finally, I go over the IDEs commonly used for Java development on the Mac. In This Chapter Reviewing Apple Java History Exploring the history of Apple embraced Java technologies long before the first version of Java on Apple computers OS X graced a blue and white Mac tower. Refugees from the old Installing developer tan Macs of the 1990s may vaguely remember using what was tools on OS X called the MRJ when their PC counterparts were busy using JVMs. Looking at the MRJ stands for Mac OS Runtime for Java.
    [Show full text]
  • User Interface Software Technology BRAD A
    User Interface Software Technology BRAD A. MYERS Human Computer Interaction Institute, Carnegie Mellon University ^[email protected]& The user interface of an application is the application to draw pictures on the the part that the person using the soft- screen and get input from the user, and ware sees and interacts with. The part the window manager allows the end of the software that makes the user user to move windows around, and is interface work is often large, complex, responsible for displaying the title lines, and difficult to implement, debug, and borders, and icons around the windows. modify. Today direct manipulation in- However, many people and systems use terfaces (also called graphical user in- the name “window manager” to refer to terface (GUI’s)) are almost universal, both layers, since systems such as the and the part of the software that han- Macintosh and Microsoft Windows do dles the user interface generally takes a not separate them. significant percentage of the total sys- On top of the windowing system is the tem design and implementation time toolkit, which contains many commonly [Myers and Rosson 1992]. Therefore, used widgets such as menus, buttons, specialized software tools have been cre- scroll bars, and text-input fields. Tool- ated to ease the programmer’s burden, kits usually connect to application pro- and today virtually all new user inter- grams through call-back procedures de- face software uses tools that make the fined by the application programmer implementation easier. Many of these that are used when a widget is operated tools have demonstrated significant pro- by the end user.
    [Show full text]
  • Concepts in Programming Languages Supervision 1 – 18/19 V1 Supervisor: Joe Isaacs (Josi2)
    Concepts in Programming Languages Supervision 1 { 18/19 v1 Supervisor: Joe Isaacs (josi2). All work should be submitted in PDF form 24 hours before the supervision to the email [email protected], ideally written in LATEX. If you have any questions on the course please include these at the top of the supervision work and we can talk about them in the supervision. Note: there is a revision guide http://www.cl.cam.ac.uk/teaching/1718/ConceptsPL/RG. pdf for this course. 1. What is the different between a static and dynamic typing. Give with justification which languages and static or dynamic. 2. What is the different between strong and weak typing. 3. What is type safety. How are type safety and type soundness distinct? 4. What type system does LISP have what are the basic types?, where have you seen a similar type system before. 5. What is a abstract machine, why are they useful? Where have you seen or used them before? 6. Name at least six different function calling schemes and which languages use each of them. 7. Give an overview of block-structured languages, include which ideas were first introduced in a programming language and how they influenced each other. Making sure to list the main characteristics of each language. You should talk about three distinct languages, then for each language make sure to make distinctions between different version of each language. Make a timeline using pen and paper or a diagram tool. 8. Using the type inference algorithm given in the notes (a typing checker with constraints) find the most general type for fn x ) fn y ) y x 9.
    [Show full text]
  • From Perl to Python
    From Perl to Python Fernando Pineda 140.636 Oct. 11, 2017 version 0.1 3. Strong/Weak Dynamic typing The notion of strong and weak typing is a little murky, but I will provide some examples that provide insight most. Strong vs Weak typing To be strongly typed means that the type of data that a variable can hold is fixed and cannot be changed. To be weakly typed means that a variable can hold different types of data, e.g. at one point in the code it might hold an int at another point in the code it might hold a float . Static vs Dynamic typing To be statically typed means that the type of a variable is determined at compile time . Type checking is done by the compiler prior to execution of any code. To be dynamically typed means that the type of variable is determined at run-time. Type checking (if there is any) is done when the statement is executed. C is a strongly and statically language. float x; int y; # you can define your own types with the typedef statement typedef mytype int; mytype z; typedef struct Books { int book_id; char book_name[256] } Perl is a weakly and dynamically typed language. The type of a variable is set when it's value is first set Type checking is performed at run-time. Here is an example from stackoverflow.com that shows how the type of a variable is set to 'integer' at run-time (hence dynamically typed). $value is subsequently cast back and forth between string and a numeric types (hence weakly typed).
    [Show full text]
  • Principles of Programming Languages
    David Liu Principles of Programming Languages Lecture Notes for CSC324 (Version 2.1) Department of Computer Science University of Toronto principles of programming languages 3 Many thanks to Alexander Biggs, Peter Chen, Rohan Das, Ozan Erdem, Itai David Hass, Hengwei Guo, Kasra Kyanzadeh, Jasmin Lantos, Jason Mai, Sina Rezaeizadeh, Ian Stewart-Binks, Ivan Topolcic, Anthony Vandikas, Lisa Zhang, and many anonymous students for their helpful comments and error-spotting in earlier versions of these notes. Dan Zingaro made substantial contributions to this version of the notes. Contents Prelude: The Study of Programming Languages 7 Programs and programming languages 7 Models of computation 11 A paradigm shift in you 14 Course overview 15 1 Functional Programming: Theory and Practice 17 The baseline: “universal” built-ins 18 Function expressions 18 Function application 19 Function purity 21 Name bindings 22 Lists and structural recursion 26 Pattern-matching 28 Higher-order functions 35 Programming with abstract syntax trees 42 Undefined programs and evaluation order 44 Lexical closures 50 Summary 56 6 david liu 2 Macros, Objects, and Backtracking 57 Object-oriented programming: a re-introduction 58 Pattern-based macros 61 Objects revisited 74 The problem of self 78 Manipulating control flow I: streams 83 Manipulating control flow II: the ambiguous operator -< 87 Continuations 90 Using continuations in -< 93 Using choices as subexpressions 94 Branching choices 98 Towards declarative programming 101 3 Type systems 109 Describing type systems 110
    [Show full text]
  • Using Xmlfor User Interface Documentation And
    Journal of Theoretical and Applied Information Technology © 2005 - 2010 JATIT & LLS. All rights reserved. www.jatit.org USING XML FOR USER INTERFACE DOCUMENTATION AND DIFFERENTIAL EVALUATION 1MOHAMMAD TUBISHAT, 2IZZAT ALSMADI, AND 3MOHAMMED AL-KABI 1Lecturer, Computer Science Department, Yarmouk University, Irbid, Jordan 2Asstt. Prof., Computer Information Systems Department, Yarmouk University, Irbid, Jordan 3Asstt. Prof., Computer Information Systems Department, Yarmouk University, Irbid, Jordan E-mail: [email protected] , [email protected] , [email protected] ABSTRACT In any software product, the user interface is one of the most important parts that defines the communication between the user and the system. One of the challenges in user interfaces is in the ability to save its state at any time as in many cases, especially in problems such as power interruptions; there is a need to save the last “good” state. In some other cases, there is a need to see if the user interface state is changed or to compare the current state with a previous one. This is required for several possible cases such as: evaluation, and changes in requirements, design and implementation. The format used for storing the state of the Graphical User Interface (GUI) should be global and can be easily used by different types of applications (such as the XML format). A GUI state is usually defined as the overall combination of properties of all the components or widgets of the GUI. In this paper an alternative back end representation is proposed for user interfaces and their state from their original format within the applications. In this approach the user interface is converted to an XML file.
    [Show full text]
  • CS442 Module 4: Types
    CS442 Module 4: Types University of Waterloo Winter 2021 1 Getting Stuck In Module 2, we studied the λ-calculus as a model for programming. We showed how many of the elements of “real-world” programming languages can be built from λ-expressions. But, because these “real-world” constructs were all modelled as λ-expressions, we can combine them in any way we like without regard for “what makes sense”. When we added semantics, in Module 3, we also added direct (“primitive”) semantic implementations of particular patterns, such as booleans, rather than expressing them directly as λ-expressions. That change introduces a similar problem: what happens when you try to use a primitive in a way that makes no sense? For instance, what happens if we try to add two lists as if they were numbers? Well, let’s work out an example that tries to do that, using the semantics of AOE, plus numbers and lists, from Module 3, and the expression (+ (cons 1 (cons 2 empty)) (cons 3 (cons 4 empty))): • The only semantic rule for + that matches is to reduce the first argument. After several steps, it reduces to [1, 2], so our expression is now (+ [1, 2] (cons 3 (cons 4 empty))). • The rule for + to reduce the first argument no longer matches, because the first argument is not reducible. But, the rule to reduce the second argument doesn’t match, because the first argument is not a number1. No rules match, so we can reduce no further. What happens next? The answer is that nothing happens next! There’s no semantic rule that matches the current state of our program, so we can’t take another step.
    [Show full text]
  • Ultimate++ Forum
    Subject: Porting (Mac OS X) and "reference application" idea Posted by mirek on Thu, 17 May 2007 15:35:21 GMT View Forum Message <> Reply to Message I have an idea how to speed-up the porting (MacOS X now, be it is general). The most time consuming part of problem is to find out all the information about implementing required things on target platform, something that developer that knows the platform would find primitive. OTOH, target platform guru's are unlikely to know about U++ implementation details. So my idea is to create "reference application" that will contain all the function for minimal (and perhaps later, advanced) target platform support. Target platform guru will reimplement this application (using the most straighforward way) and submit the code, which will serve as great boost to development speed (sort of U++ oriented knowledge base). Thoughts? Mirek Subject: Re: Porting (Mac OS X) and "reference application" idea Posted by captainc on Sun, 14 Sep 2008 13:08:14 GMT View Forum Message <> Reply to Message luzr wrote on Thu, 17 May 2007 11:35I have an idea how to speed-up the porting (MacOS X now, be it is general). The most time consuming part of problem is to find out all the information about implementing required things on target platform, something that developer that knows the platform would find primitive. OTOH, target platform guru's are unlikely to know about U++ implementation details. So my idea is to create "reference application" that will contain all the function for minimal (and perhaps later, advanced) target platform support.
    [Show full text]
  • 51. Graphical User Interface Programming
    Brad A. Myers Graphical User Interface Programming - 1 51. Graphical User Interface Programming Brad A. Myers* Human Computer Interaction Institute Carnegie Mellon University 5000 Forbes Avenue Pittsburgh, PA 15213 [email protected] http://www.cs.cmu.edu/~bam (412) 268-5150 FAX: (412) 268-1266 *This paper is revised from an earlier version that appeared as: Brad A. Myers. “User Interface Software Tools,” ACM Transactions on Computer-Human Interaction. vol. 2, no. 1, March, 1995. pp. 64-103. Draft of: January 27, 2003 To appear in: CRC HANDBOOK OF COMPUTER SCIENCE AND ENGINEERING – 2nd Edition, 2003. Allen B. Tucker, Editor-in-chief Brad A. Myers Graphical User Interface Programming - 2 51.1. Introduction Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. Virtually all applications today are built using some form of user interface tool [Myers 2000]. User interface (UI) software is often large, complex and difficult to implement, debug, and modify. As interfaces become easier to use, they become harder to create [Myers 1994]. Today, direct manipulation interfaces (also called “GUIs” for Graphical User Interfaces) are almost universal. These interfaces require that the programmer deal with elaborate graphics, multiple ways for giving the same command, multiple asynchronous input devices (usually a keyboard and a pointing device such as a mouse), a “mode free” interface where the user can give any command at virtually any time, and rapid “semantic feedback” where determining the appropriate response to user actions requires specialized information about the objects in the program.
    [Show full text]