DOCSLIB.ORG

User Interface Software Technology BRAD A

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. Examples of toolkits ductivity gains for programmers and include Motif for X/11 and the widgets have become important commercial in the Windows and Macintosh tool- products. Although most commercial boxes. There are also many research tools concentrate on building the sur- toolkits [Myers 1995], such as Garnet face look of the interface (the placement [Baecker et al. 1995], Amulet, Inter- of the menus and buttons and the choice Views, and tcl/tk. Virtual toolkits allow of colors), some systems have addressed an application to be written once and how the interface behaves (what hap- then to execute on Windows, Macintosh, pens when the buttons are pressed and or Motif (and others) by providing a objects are moved around). single programming interface and many There are many different kinds of different “looks and feels.” Another user interface software [Myers 1995]. name for these tools is “cross-platform The windowing system supports the development systems.” Examples of separation of the screen into different commercial virtual toolkits include Gal- (usually rectangular) regions, called axy, Open Interface, and XVT. “windows.” The X/11 window system for On top of the toolkit might be higher- Unix divides the window functionality level tools that help the designer use the into two layers: the window system, toolkit widgets, which include the fol- which is the functional or programming lowing: interface, and the window manager, which is the user interface. The window Prototyping tools, which allow the de- system provides procedures that allow signer to quickly mock up some exam- Copyright © 1996, CRC Press. ACM Computing Surveys, Vol. 28, No. 1, March 1996 190 • Brad A. Myers ples of what the screens in the pro- generation languages (4GLs) that gram will look like. Often these tools support defining the interactive forms cannot be used to create the real user for accessing and entering data also interface of the program because they fall into this category. only simulate the widgets. The first Screen scrapers or front-enders, which prototyping tool was probably Dan provide a graphical user interface to Bricklin’s Demo. Apple’s HyperCard old programs without changing the and MacroMedia’s Director are often existing application code by providing used as prototypers. A research sys- an in-memory buffer that pretends to tem is SILK, which allows free-hand be the screen of an old character ter- gestures and storyboards for sketch- minal. A leading program of this type ing the initial designs [Landay and is Easel. Myers 1995]. User interface management systems Card-based tools, which support inter- (UIMSs) [Olsen 1992], which usually faces that can be presented as a se- provide a new language in which the quence of mostly static pages, some- user interface is programmed. Exam- times called “frames,” “cards,” or ples include HP/Apollo’s Open-Dia- “forms.” The most famous example is logue, VAPS from Virtual Prototypes, Apple’s HyperCard. and many research systems. UIMSs Interface builders, also called Interface have used state-transition networks, Development Tools, which allow the context-free grammars, event lan- designer to create dialog boxes, guages, declarative languages, and menus, and windows by laying out constraint languages to specify the widgets interactively with the mouse. behavior of the interface. Other properties of the widgets can be Automatic generation tools, which cre- set using property sheets. The behav- ate parts of the user interface such as ior (what happens when widgets are the dialog boxes from a list of the operated) must usually be pro- contents. A research system that pro- grammed separately by writing con- vides this is ITS from IBM Research ventional code. An early research ex- [Baecker et al. 1995]. ample is Steamer, and there are literally hundreds of commercial tools Demonstrational tools [Cypher et al. in this category today, including 1993], which allow parts of the inter- UIM/X for Motif and Novell’s App- face other than the widgets to be spec- Ware for PCs. Microsoft’s Visual Ba- ified interactively without program- sic is essentially an Interface Builder ming. For example, Lapidary and coupled with an interpreted program- Marquise allow the dynamic creation ming language. and behavior of objects to be demon- Application frameworks, which gener- strated. ally provide an object-oriented archi- A comprehensive list of commercial and tecture that guides programmers and research tools for general use is avail- helps define how the software should able at http://www.cs.cmu.edu/;bam/ be designed. Examples include Ap- toolnames.html. ple’s MacApp [Wilson 1990] and Mi- crosoft’s OLE [Brockschmidt 1995]. Database interfaces, which support REFERENCES form-based or GUI-based access to da- tabases. Major database vendors such BAECKER,R.M.,GRUDIN, J., BUXTON,W.A.S.,AND GREENBERG, S. 1995. Readings in Human- as Oracle provide tools that allow the Computer Interaction: Toward the Year 2000. user interface to be designed using Morgan Kaufmann, San Francisco, CA. interactive form editors (which are es- BROCKSCHMIDT, K. 1995. Inside OLE, 2nd ed. sentially interface builders). Fourth- Microsoft Press, Redmond, WA. ACM Computing Surveys, Vol. 28, No. 1, March 1996 User Interface Software Technology • 191 CYPHER, A., HALBERT,D.C.,KURLANDER, D., tools. ACM Trans. Comput. Human Interac- LIEBERMAN, H., MAULSBY, D., MYERS,B.A., tion 2, 1 (March), 64–103. AND TURRANSKY, A., EDS. 1993. Watch What MYERS,B.A.AND ROSSON, M. B. 1992. Survey I Do: Programming by Demonstration. MIT on user interface programming. Human fac- Press, Cambridge, MA. tors in computing systems. In: Proceedings LANDAY,J.AND MYERS, B. A. 1995. Interactive SIGCHI’92, (Monterey, CA, May), 195–202. sketching for the early stages of user interface OLSEN,D.R.,JR., 1992. User Interface Manage- design. Human factors in computing systems. ment Systems: Models and Algorithms. Mor- In: Proceedings SIGCHI’95. (Denver, CO, gan Kaufmann, San Mateo, CA. May), 43–50. WILSON, D. 1990. Programming with MacApp. MYERS, B. A. 1995. User interface software Addison-Wesley, Reading, MA. ACM Computing Surveys, Vol. 28, No. 1, March 1996.
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]
  • 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]
  • 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]
  • 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]
  • 302 Using Interface Builder in Xcode 4 Final DDF
    Using Interface Builder in Xcode 4 Joey Hagedorn Interface Builder Engineer These are confidential sessions—please refrain from streaming, blogging, or taking pictures 1 What Is Interface Builder? 2 Agenda 1 Tour of Interface Builder in Xcode 2 Building a basic application 3 Integrating new Mac OS X Lion features X 3 1 Tour of Interface Builder in Xcode 4 5 6 7 8 9 10 11 Agenda 1 Tour of Interface Builder in Xcode 2 Building a basic application 3 Integrating new Mac OS X Lion features X 12 2 Building a basic application 13 Demo Building a basic application using Interface Builder 14 Agenda 1 Tour of Interface Builder in Xcode 2 Building a basic application 3 Integrating new Mac OS X Lion features X 15 3 Integrating new Mac OS X Lion features X 16 17 18 19 Integrating New Mac OS X Lion Features Demo 20 Using Interface Builder in Xcode 4 Kevin Cathey Interface Builder Engineer 21 Demo Creating Popovers in Interface Builder 22 Autolayout What is Autolayout? Button {{20, 64}, {70, 20}} Aqua guides are one-time visual helpers to produce the frame of a view 23 Autolayout What is Autolayout? {{20, 64}, {70, 20}} Autolayout reverses this: guides kept as constraints which is input, frame is output 24 What Is Autolayout? • Persist the aqua guides as objects called constraints • Constraints are relationships that must hold • Constraints involve one or two views • Constraints are objects you interact with in your document 25 Why Autolayout? • Dynamism: Improved responsiveness to changes in the application • Simplicity: Creation of basic interfaces
    [Show full text]
  • CERN Computer Newsletter Has Become a Sort of Historical Institution by Itself
    CERN COMPUTER CERN - IT Division CH-1211 Geneve 23 NEWSLETTER SWITZERLAND CERN-CNL-2000-001 January – April 2000 Vol. XXXIV, issue no 1 Contents If you need Help i Editorial iv 1 Physics Computing 1 1.1 ALICE Data Challenge 2000 . .......................................... 1 2 Desktop Computing 3 2.1 Central Computing Helpdesk - Outlines and Strategy ............................... 3 2.2 Service Handbook for the Desktop Support Contract with IT Division . ................ 4 2.3 Backing up Data on your Unix Desktop Machine . ............................... 5 2.4 Linux Red Hat 6.1 now Certified .......................................... 5 2.5 Operating System Certification - Present List . ............................... 5 2.6 Range of UNIX platforms served by ASIS . ............................... 6 3 Internet Services and Network 7 3.1 Improvement of CERN Connectivity to the Global Internet . ........................... 7 3.2 Rationalisation of Support for Network Protocols . ............................... 7 3.3 Connecting Computing Equipment onto the CERN Network ........................... 8 4 Scientific Applications and Software Engineering 9 4.1 Garfield Version 7.02 . .............................................. 9 4.2 Magboltz 2 . .................................................. 10 4.3 News from the Software Development Tools Service ............................... 10 5 Desktop Publishing 12 5.1 XML-related Developments . .......................................... 12 6 The Learning Zone 14 6.1 X11 Desktop Environments (KDE and GNOME)
    [Show full text]
  • MAD Week 1 App Intro.Pptx
    Mobile Applicaon Development Aileen Pierce STARTING IOS APPLICATION DEVELOPMENT iOS Development Differences • Limited screen size • Each app has one window • Limited system resources – Apps need to start and quit quickly • Might not always have Internet access • Uses Objecve-C – Flavor of C based on NeXTSTEP • No physical keyboard and mouse for interac,on iOS Device Tour • iPhone 5 – 4 inches diagonally – 1136 x 640 resoluon • iPhone 4/4S – 3.5 inches diagonally – 480 x 320 resolu,on, 960 x 640 re,na • iPad mini – 7.9 inches diagonally – 1024 x 768 resoluon • iPad – 9.7 inches diagonally – 1024 x 768 resolu,on, 2048 x 1536 re,na • Mul,-touch operaons • Landscape or portrait mode SDK Components • Xcode – Integrated Development Environment (IDE) to create and manage development projects – Interface Builder • Tool to build your applicaon user interfaces • Frameworks – So_ware libraries that provide specific func,onality • Simulator – Simulates running your apps on your Mac • Instruments – Gather and analyze data on your apps behavior Developing apps • Start with an Xcode template • Design the user interface (UI) • Hook up the UI and the code • Write the code using the frameworks • Build and run your app (iteravely) – Compiles your files creang a single library • Test and debug un,l you’re done Geng Started with Xcode • Integrated Development Environment (IDE) • Projects • iOS Applicaon • Templates – Enables you to easily create different types of apps • Product – iPhone, iPad, or universal Single View Applicaon • Good for apps with a single view
    [Show full text]
  • BLAISE PASCAL MAGAZINE ALL ABOUT DELPHI and DELPHI PRISM(.Net) , LAZARUS & PASCAL and RELATED LANGUAGES Pascal8
    BLAISE PASCAL MAGAZINE ALL ABOUT DELPHI AND DELPHI PRISM(.Net) , LAZARUS & PASCAL AND RELATED LANGUAGES Pascal8 Delphi 2010 – what a feeling! - Bob Swart page 7 Gestures could be the new ’must’ in our computers future Counters - David Dirkse page 11 Learning counting again, - could wel be a hobby... Virus in Delphi? - Nick Hodges page 14 Nick explains how to get rid of the virus and block it. Dezign for databases - Marco Roessen page 16 A fantastic alternative for its expensive competitors, and it’s even cheaper. Customizing the T-Field data display - Henk Schreij page 18 Diving deeper into the possibility’s Using Free Pascal and Lazarus to create applications for OSX - Jeremy North page 20 Working on the Mac is hot Writing Delphi Components II: Custom Properties and Windows Controls - Marco Cantù page 22 In the new Delphi versions it looks all different. My Top Five Delphi 2010 New Features - Pawel Glowacki page 24 Except for guestures ther is a lot of news... Fast Graphic deformation by using Scanlines - Peter Bijlsma page 28 Control your own image or blow it up! Berlusconi on the edge Wide Information Bus (Introduction) - Fikret Hasovic page 33 What is it and what the use for it? Freehand Drawing (Introduction) - David Dirkse page 36 shows how to create your own paint program October 2009 Publisher: Foundation for Supporting the Pascal Programming Language in collaboration with the Dutch Pascal User Group (Pascal Gebruikers Groep) © Stichting Ondersteuning Programeertaal Pascal Cover price Europe: € 10.00 / UK £ 10.00 / US $ 10.00 BLAISE PASCAL MAGAZINE 8 ALL ABOUT DELPHI AND DELPHI PRISM(.Net) ,LAZARUS & PASCAL AND RELATED LANGUAGES CONTENTS Volume 8, ISSN 1876-0589 Editor in chief Articles Detlef D.
    [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]
  • Carbon: an Essential Element of Mac OS X
    ADC March 2001 2/6/01 1:44 PM Page 1 Apple Developer Connection Direct Carbon: An Essential Element of Mac OS X ne of the things that makes Mac OS X unique is its integra- developers, while at the same time delivering tion of five separate application runtime environments: all the performance, features, and reliability OCarbon, Cocoa, Classic, Java, and BSD. Never before has an that Mac OS X has to offer. About 70 percent operating system offered developers so many options. This series of of the classic Mac OS APIs are fully support- articles will give you the information you need to make an informed ed, and Carbon adds many new APIs specifi- decision as to which of these environments is right for your applica- cally to take advantage of Mac OS X. tion on Mac OS X. This month, I’m going to talk about Carbon and what it offers you as a Macintosh developer. What Diamonds Are Made Of A Brief History of Carbon Carbon offers a wealth of features to support and accelerate your Carbon represents the evolution of the Mac OS API, from a single- Mac OS X development efforts. Whether you’re new to the platform, user, cooperatively scheduled system, to a modern multi-user system or an old-timer, here are some of the reasons why you’ll find Carbon with memory protection and preemptive multitasking. Carbon a solid foundation for your software product: sprang from Apple’s desire to provide a gentle migration path for • Broad Language Support Apple provides interfaces, compilers, and tools for Carbon programming in C and C++, while other languages such as BASIC and FORTRAN are offered by other tool vendors.
    [Show full text]