DOCSLIB.ORG

Getting and Installing GIMP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Getting and Installing GIMP APPENDIX A Getting and Installing GIMP You’ve decided to learn to edit images with GIMP! But if it’s not already on your computer, first you have to install it. You may have Windows, Linux, a Mac, or another UNIX system such as FreeBSD. All of them can run GIMP, but each has a different installation method. Of course, if you can, you’d certainly prefer to run the most recent 2.4 version. Most computers can, but some OS variants are too old. If that’s the case, you may have to run an older version. We’ll explain those options in Appendix B. If you wish, you can also build GIMP from source, which is covered in Appendix C. Here, you’ll learn • Requirements • Where to find GIMP Then skip to the appropriate section: • Installing on Windows • Installing on Mac • Installing on Linux or UNIX Requirements GIMP doesn’t require an especially fast machine. However, if you want to work with large images, you’ll find that more memory will help a lot. A faster processor won’t hurt, of course. On Windows, GIMP 2.4 should work on NT4, Windows 2000, XP, or Vista. If you have an older version of Windows, skip to Appendix B. You can download GIMP 2.4 for Mac OS X Tiger (10.4) or Leopard (10.5). The more adventurous Panther (10.3) users can also build GIMP 2.4 using the MacPorts system, but it’s probably easier to just download GIMP 2.2 as Gimp.app from http://gimp-app.sourceforge.net. OS X systems older than Panther face other problems (see Appendix B). If you have OS 9.2 or earlier, you cannot run GIMP at all; it was never supported and never will be. Recent Linux and other UNIX-based systems will have GIMP 2.4 in their packaging system, and it may very well have been part of your initial installation; you probably already have it. 521 522 APPENDIX A ■ GETTING AND INSTALLING GIMP On UNIX-based systems (including Mac OS X and Linux), GIMP is also an “X” application: it’s built on top of a toolkit called GTK+ that uses the X Window System (sometimes called X11 since most systems use version 11) for drawing to the screen, creating windows, and other low-level operations. X doesn’t stand for anything except “the next letter after W.” (Seriously! X was the successor to a window system called W, which was in use at MIT in 1984 when X was being designed.) So you’ll need X in order to run GIMP. This is only likely to be an issue on Macs, since most Linux and UNIX systems are already running X. (There’s a version of GTK+ in the works that will run on OS X without requiring X, but it’s still experimental. If you want to try a GIMP built on the Mac-native GTK, you may be able to find builds at http://gimp-app.sourceforge.net.) One thing you shouldn’t need is money. GIMP is free software: free because you can get it without paying, and also because you’re free to redistribute it or modify it. You can buy GIMP from various sources, and sometimes these versions include extra goodies like an installer or a collection of cool brushes. But most of the time, you’ll do just as well starting with the free version. IF GIMP IS FREE SOFTWARE, IS IT LEGAL FOR PEOPLE TO SELL IT? Yes. GIMP is licensed under the GNU General Public License (GPL), which allows anyone to distribute the soft- ware, and even to charge money for it. However, the GPL does insist that further redistribution be allowed (the seller can’t prevent you from making copies and giving them out to your friends). Also, the source code for the program (the human-readable programming instructions that make the program work) must be included, or at least be made available. The GPL also requires that you receive a copy of the license itself along with the program, so you can learn about your rights to share the program, modify it, or contribute to the project. Where to Find GIMP The GIMP project lives at http://gimp.org. There, you can find links to downloadable versions for several operating systems along with instructions on how to get GIMP for even more sys- tems. You can also find out how to build it yourself if you want to try the latest cutting-edge version. At gimp.org, you’ll also find a substantial collection of documentation. There’s a complete user’s manual, a large collection of tutorials, and information on GIMP’s programming inter- faces for anyone interested in writing scripts or plug-ins. You can sample a collection of mailing lists and IRC channels where you can ask questions, volunteer to help, or just trade tips. Please remember that any URLs listed here may change. The web is beyond our control! APPENDIX A ■ GETTING AND INSTALLING GIMP 523 Installing on Windows Unlike previous versions, installing GIMP 2.4 on Windows is very much like installing any other software (except you don’t have to pay for it). The only tricky part is Python. If you want GIMP to be able to run Python scripts, you’ll need PyGTK (from http://pygtk.org) plus all its dependencies. Getting them all to work can be somewhat challenging on Windows (it might be easier to install Linux!). The Quick Start Version 1. First, point your browser to http://gimp.org and download GIMP. 2. Unzip and run the installation program. The (Slightly) Longer Version First, navigate your browser to http://gimp.org. The opening page will have a Download button right in the title bar. Click that and you’ll probably be taken to the Windows Download Page automatically (gimp.org tries to figure out what system you’re using). The first link should be the Installer, which you download. When the download is finished, double-click the EXE file to expand it and get to the installation window. First you’ll see a typical Welcome screen. Click Next to get going. You’ll then be given an opportunity to read the GNU General Public License—the GPL you may have heard about. When you’ve had enough, just click Next again and you’re at the Install page. Your options are Install now (which is fine) or Customize. If you choose the latter, you can indicate an installation folder that’s different from the default, choose which components to install, indicate which file types should launch GIMP, choose your Start Menu folder, and indi- cate if you should have a desktop icon and/or a Quick Launch icon. Generally, you won’t want to change any of this, but if you do, then Customize is your best option. Either way, you’ll end up clicking an Install button and eventually get a screen that tells you the installation is complete and offers the option to launch GIMP (the default has a check- mark beside it). You can delete the installation EXE now if you wish. You’re done! Installing on Macintosh Before downloading GIMP 2.4, make sure you have X11 installed (or optionally XQuartz on 10.5 Leopard). If it’s already on your system, it should be in the Utilities subdirectory of your Applications folder. If it’s not already there, you can install it from your System Install disc. Can’t find your old discs? Download the appropriate version from Apple using your Mac OS X Software… finder menu option. X11 will be in the Unix & Open Source section. (Leopard users may be able to get GIMP 2.4 there too!) 524 APPENDIX A ■ GETTING AND INSTALLING GIMP The Quick Start Version 1. Point your browser to http://gimp.org, click on Mac OS X to go to the Wilber Loves Apple site, and get the proper version for your machine. 2. Double-click the DMG to mount it, then copy GIMP 2.4 to your Applications folder. Start it as you would any other application (it will automagically start X11 for you if it’s not already running). The (Slightly) Longer Version The GIMP project doesn’t provide Mac builds (or, indeed, builds for any system), but works with another organization: the Wilber Loves Apple community. If you start at gimp.org and click on Mac OS X, it takes you to their site: http://darwingimp.sourceforge.net. You’ll be faced with four possibilities: OS X 10.5 (Leopard) or OS X 10.4 (Tiger), Intel, or PowerPC? Surely you know! But if you don’t, both questions are easily answered by going to the first item in your Apple menu, About This Mac. The Version line will say 10.4.something (Tiger) or 10.5.something (Leopard). The Processor line will list either a PowerPC or an Intel chip. ■Note If About This Mac says 10.3.something (that’s Panther) or earlier, you’re out of luck in this section and should proceed to Appendix B. Or you can upgrade your system. Your call. Download the correct version. Go to your usual download destination and double-click the Gimp2.4.blah.blah.dmg as you normally would. This will mount a virtual disk and open a window with the GIMP application in it…and one other thing: the GNU Public License. What you do with the latter is up to you, but the former should be copied to your Applications folder.
Load more

Recommended publications
  • Practice Tips for Open Source Licensing Adam Kubelka
    Santa Clara High Technology Law Journal Volume 22 | Issue 4 Article 4 2006 No Free Beer - Practice Tips for Open Source Licensing Adam Kubelka Matthew aF wcett Follow this and additional works at: http://digitalcommons.law.scu.edu/chtlj Part of the Law Commons Recommended Citation Adam Kubelka and Matthew Fawcett, No Free Beer - Practice Tips for Open Source Licensing, 22 Santa Clara High Tech. L.J. 797 (2005). Available at: http://digitalcommons.law.scu.edu/chtlj/vol22/iss4/4 This Article is brought to you for free and open access by the Journals at Santa Clara Law Digital Commons. It has been accepted for inclusion in Santa Clara High Technology Law Journal by an authorized administrator of Santa Clara Law Digital Commons. For more information, please contact [email protected]. ARTICLE NO FREE BEER - PRACTICE TIPS FOR OPEN SOURCE LICENSING Adam Kubelkat Matthew Fawcetttt I. INTRODUCTION Open source software is big business. According to research conducted by Optaros, Inc., and InformationWeek magazine, 87 percent of the 512 companies surveyed use open source software, with companies earning over $1 billion in annual revenue saving an average of $3.3 million by using open source software in 2004.1 Open source is not just staying in computer rooms either-it is increasingly grabbing intellectual property headlines and entering mainstream news on issues like the following: i. A $5 billion dollar legal dispute between SCO Group Inc. (SCO) and International Business Machines Corp. t Adam Kubelka is Corporate Counsel at JDS Uniphase Corporation, where he advises the company on matters related to the commercialization of its products.
    [Show full text]
  • Copyrighted Material
    33_754935 bindex.qxp 11/7/05 10:09 PM Page 345 Index Applications Menu, 42–43, 68–71 • Symbols • Applixware Office package, 15 appointments, tracking, 210 * (asterisk), 249, 251 archives, packing and unpacking (tar), 20, \ (backslash), 248 337–338 - (dash), 94 arguments, command line, 247 . (dot), 92 asterisk (*), 249, 251 ! (exclamation point), 252–253 Asymmetric DSL (ADSL), 108–109 / (forward slash), 79, 81 attachments, e-mail, 154 > (greater-than sign), 249 audio CDs, playing, 221–223 - (hyphen), 95 authentication, 292 < (less-than sign), 249 automatic command completion, 250 . (period), 96 automatic login, 40, 318–319, 325 | (pipe), 248 ? (question mark), 251 " (quotation marks), 247 ; (semicolon), 248 • B • [] (square brackets), 252 backdoor, 292 .. (two dots or dot-dot), 92 background, desktop, 73–74, 75–76 backing up files, 20 backslash (\), 248 • A • base station, 129 bash (Bourne Again Shell) access point, wireless LAN, 129, 131 automatic command completion, 250 Adobe Portable Document Format. See PDF combining commands, 248 ADSL (Asymmetric DSL), 108–109 described, 47–48, 246 AES (Advanced Encryption Standard), 129 error messages, saving to file, 249–250 aggregator, RSS, 185 file, command input from, 249 AIM (America Online instant messaging output, saving to file, 249 service), 54, 161–162 repeating previously typed commands, Akregator news reader, 54, 185–186 252–253 amaroK music player, 224 syntax, 247–248 Apache Web server, 16 wildcards, 251–252 applets, 68, 75 bastion host, 293 application gateway, 292 bit bucket, 250 applications Blam RSS reader, 54 controlling, 18–19 block device, 94 development, 17 Bluetooth wireless, 20, 271 e-mail, 152–153 bookmark field, 200 GNOME Desktop, illustrated,COPYRIGHTED 64 boot menu MATERIAL items, installing, 27–28 GNU, 343 boot process, starting and stopping services, installing at setup, 32 263–264 KDE Desktop, illustrated, 64 booting, 26–27, 39–40 Linux packages, 11 Bourne Again Shell.
    [Show full text]
  • Source Code Trees in the VALLEY of THE
    PROGRAMMING GNOME Source code trees IN THE VALLEY OF THE CODETHORSTEN FISCHER So you’ve just like the one in Listing 1. Not too complex, eh? written yet another Unfortunately, creating a Makefile isn’t always the terrific GNOME best solution, as assumptions on programs program. Great! But locations, path names and others things may not be does it, like so many true in all cases, forcing the user to edit the file in other great programs, order to get it to work properly. lack something in terms of ease of installation? Even the Listing 1: A simple Makefile for a GNOME 1: CC=/usr/bin/gcc best and easiest to use programs 2: CFLAGS=`gnome-config —cflags gnome gnomeui` will cause headaches if you have to 3: LDFLAGS=`gnome-config —libs gnome gnomeui` type in lines like this, 4: OBJ=example.o one.o two.o 5: BINARIES=example With the help of gcc -c sourcee.c gnome-config —libs —cflags 6: gnome gnomeui gnomecanvaspixbuf -o sourcee.o 7: all: $(BINARIES) Automake and Autoconf, 8: you can create easily perhaps repeated for each of the files, and maybe 9: example: $(OBJ) with additional compiler flags too, only to then 10: $(CC) $(LDFLAGS) -o $@ $(OBJ) installed source code demand that everything is linked. And at the end, 11: do you then also have to copy the finished binary 12: .c.o: text trees. Read on to 13: $(CC) $(CFLAGS) -c $< manually into the destination directory? Instead, 14: find out how. wouldn’t you rather have an easy, portable and 15: clean: quick installation process? Well, you can – if you 16: rm -rf $(OBJ) $(BINARIES) know how.
    [Show full text]
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • Linux on the Road
    Linux on the Road Linux with Laptops, Notebooks, PDAs, Mobile Phones and Other Portable Devices Werner Heuser <wehe[AT]tuxmobil.org> Linux Mobile Edition Edition Version 3.22 TuxMobil Berlin Copyright © 2000-2011 Werner Heuser 2011-12-12 Revision History Revision 3.22 2011-12-12 Revised by: wh The address of the opensuse-mobile mailing list has been added, a section power management for graphics cards has been added, a short description of Intel's LinuxPowerTop project has been added, all references to Suspend2 have been changed to TuxOnIce, links to OpenSync and Funambol syncronization packages have been added, some notes about SSDs have been added, many URLs have been checked and some minor improvements have been made. Revision 3.21 2005-11-14 Revised by: wh Some more typos have been fixed. Revision 3.20 2005-11-14 Revised by: wh Some typos have been fixed. Revision 3.19 2005-11-14 Revised by: wh A link to keytouch has been added, minor changes have been made. Revision 3.18 2005-10-10 Revised by: wh Some URLs have been updated, spelling has been corrected, minor changes have been made. Revision 3.17.1 2005-09-28 Revised by: sh A technical and a language review have been performed by Sebastian Henschel. Numerous bugs have been fixed and many URLs have been updated. Revision 3.17 2005-08-28 Revised by: wh Some more tools added to external monitor/projector section, link to Zaurus Development with Damn Small Linux added to cross-compile section, some additions about acoustic management for hard disks added, references to X.org added to X11 sections, link to laptop-mode-tools added, some URLs updated, spelling cleaned, minor changes.
    [Show full text]
  • Darktable 1.2 Darktable 1.2 Copyright © 2010-2012 P.H
    darktable 1.2 darktable 1.2 Copyright © 2010-2012 P.H. Andersson Copyright © 2010-2011 Olivier Tribout Copyright © 2012-2013 Ulrich Pegelow The owner of the darktable project is Johannes Hanika. Main developers are Johannes Hanika, Henrik Andersson, Tobias Ellinghaus, Pascal de Bruijn and Ulrich Pegelow. darktable is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. darktable is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with darktable. If not, see http://www.gnu.org/ licenses/. The present user manual is under license cc by-sa , meaning Attribution Share Alike . You can visit http://creativecommons.org/ about/licenses/ to get more information. Table of Contents Preface to this manual ............................................................................................... v 1. Overview ............................................................................................................... 1 1.1. User interface ............................................................................................. 3 1.1.1. Views ..............................................................................................
    [Show full text]
  • ACS – the Archival Cytometry Standard
    http://flowcyt.sf.net/acs/latest.pdf ACS – the Archival Cytometry Standard Archival Cytometry Standard ACS International Society for Advancement of Cytometry Candidate Recommendation DRAFT Document Status The Archival Cytometry Standard (ACS) has undergone several revisions since its initial development in June 2007. The current proposal is an ISAC Candidate Recommendation Draft. It is assumed, however not guaranteed, that significant features and design aspects will remain unchanged for the final version of the Recommendation. This specification has been formally tested to comply with the W3C XML schema version 1.0 specification but no position is taken with respect to whether a particular software implementing this specification performs according to medical or other valid regulations. The work may be used under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license. You are free to share (copy, distribute and transmit), and adapt the work under the conditions specified at http://creativecommons.org/licenses/by-sa/3.0/legalcode. Disclaimer of Liability The International Society for Advancement of Cytometry (ISAC) disclaims liability for any injury, harm, or other damage of any nature whatsoever, to persons or property, whether direct, indirect, consequential or compensatory, directly or indirectly resulting from publication, use of, or reliance on this Specification, and users of this Specification, as a condition of use, forever release ISAC from such liability and waive all claims against ISAC that may in any manner arise out of such liability. ISAC further disclaims all warranties, whether express, implied or statutory, and makes no assurances as to the accuracy or completeness of any information published in the Specification.
    [Show full text]
  • Press Release: New and Revised Extensions for Accessible
    Press release Leuven, Belgium, 8 November 2011 New and Revised Extensions for Accessible Document Creation with OpenOffice.org and LibreOffice The Katholieke Universiteit Leuven (K.U.Leuven) today released an extension for OpenOffice.org Writer and LibreOffice Writer that enables users to evaluate and repair accessibility issues in word processing documents. “AccessODF” (http://sourceforge.net/p/accessodf/wiki/) is a freeware extension for OpenOffice.org and LibreOffice, two office suites that are freely available for Microsoft Windows, Mac OS X, Linux/Unix and Solaris. At the same time, K.U.Leuven also releases new versions of two other extensions: odt2daisy (http://odt2daisy.sourceforge.net/) and odt2braille (http://odt2braille.sourceforge.net/). The former enables users to export word processing documents to digital talking books in the DAISY format; the latter enables exporting to Braille and printing on a Braille embosser. AccessODF, odt2daisy and odt2braille are being developed in the framework of the AEGIS project, an R&D project funded by the European Commission. The three extensions will be demonstrated at the AEGIS project’s Workshop and Conference, which take place in Brussels on 28-30 November 2011 (http://aegis-conference.eu/). AccessODF AccessODF is an extension that can be used in OpenOffice.org Writer and in LibreOffice Writer. It enables authors to find and repair accessibility issues in their documents, i.e. issues that make their documents difficult or even impossible to read for people with disabilities. This includes
    [Show full text]
  • Beginning Portable Shell Scripting from Novice to Professional
    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • Gutenprint 5.0 User's Manual and Release Notes
    Gutenprint 5.0 User's Manual Robert Krawitz March 4, 2007 Gutenprint 5.0 User's Manual Copyright © 2000-2007 Robert Krawitz Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation with no invariant sections, no Front-Cover texts, and no Back-Cover texts. Gutenprint 5.0 is licensed in its entirety under the terms of the GNU General Public License. The CUPS code (in src/cups) is licensed under the terms of the GNU General Public License version 2; the balance of the code is licensed under the terms of the GNU General Public License version 2 or any later version published by the Free Software Foundation. EPSON, ESC/P, and Stylus are registered trademarks of Seiko Epson Corp. ESC/P2 is a trademark of Seiko Epson Corp. All other product names are trademarks and/or registered trademarks of their vendors. 2 Gutenprint 5.0 User's Manual 03/04/2007 Table of Contents 1) Introduction............................................................................................................................................5 1.1) What is Gutenprint?.......................................................................................................................5 1.2) History of Gutenprint.....................................................................................................................5 1.2.1) The early years: Gimp-Print 3.x and 4.0................................................................................5
    [Show full text]
  • The Glib/GTK+ Development Platform
    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
    [Show full text]