DOCSLIB.ORG

GTK+ Brochure

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GTK+ Brochure GIO – Input/Output on Steroids The GTK+ Widget Toolkit GIO is striving to provide a modern, easy-to-use Vir- On top of GLib/GObject/GIO sits GTK+, a library tual File System (VFS) API that sits at the right level containing a wide range of widgets. A widget is a basic in the library stack. GIO also contains other generally component of a graphical user interface, for instance a The GLib/GTK+ Development useful APIs for desktop applications (such as network- button, some text, a menu, etc. A container is a spe- ing and D-Bus support). It was created to provide cial widget that can contain other widgets. All these Platform an API that is so good that developers prefer it over widgets are (indirect) subclasses of the GObject base raw POSIX calls. Among other things that means us- class. ing GObject. It also means not cloning the POSIX Although widgets can be created, configured and as- API, but providing higher-level, document-centric in- sembled programmatically, the Glade interface builder terfaces. can be used to create the user interface graphically. GTK+ is a multi-platform toolkit for creating graphi- The abstract file system model of GIO consists of a The Glade application creates an XML file that can be cal user interfaces. Offering a complete set of widgets, number of interfaces and base classes for I/O and files. loaded with GTK+. GTK+ is suitable for projects ranging from small one- Then there is a number of stream classes, similar to the Among other things, GTK+ provides a flexible them- off tools to complete application suites. input and output stream hierarchies that can be found ing system with a CSS-like language, as well as an GTK+ is written in C but has been designed from the in frameworks like Java. There is a framework for stor- interactive inspector. ing and retrieving application settings. There is sup- ground up to support a wide range of languages, not port for network programming, including connectivity only C/C++. Using GTK+ from languages such as monitoring, name resolution, lowlevel socket APIs and Long-Term Support GTK+ Versions Python and JavaScript (especially in combination with highlevel client and server helper classes. There is sup- the Glade GUI builder) provides an effective method port for connecting to the D-Bus inter-process com- During the GTK+ 3 development, a new minor version of application development. munication system: sending and receiving messages, was released every six months. GTK+ 3.22 – released GTK+ is free/libre software and part of the GNU owning and watching bus names, and making objects in September 2016 – is and will be the last minor ver- Project. The licensing terms for GTK+, the GNU available on the bus. Beyond these, GIO provides: file sion of the 3.x series. Moving forward, the GTK+ LGPL, allow it to be used by all developers without monitoring; utility classes to implement asynchronous project has adopted a new versioning scheme with a any license fees or royalties. and/or cancellable operations; an easy-to-use API to new Long-Term Support (LTS) version released every GTK+ has been created in 1996 for the GIMP — launch and interact with child processes; and more. two to three years. GTK+ 3.22 is an LTS version, the next LTS version will be GTK+ 4.0, then 5.0, etc. the GNU Image Manipulation Program — but quickly By using the same GIO API, an application can sup- Intermediary versions will continue to be released ev- evolved into a general-purpose library used by a large port remote files in addition to local files. The local ery six months; for GTK+ 4, those intermediary ver- number of applications including the GNU project’s case is implemented by GIO, while implementations for sions are numbered 3.90, 3.92, 3.94 and so on. Those GNOME desktop. various network file systems are provided by the GVFS non-LTS versions have less stability guarantees. Devel- package as loadable modules. Another design choice is opers preferring a stable foundation should choose an to move backends out-of-process, which minimizes the LTS version of GTK+. An LTS version is supported dependency bloat and makes the whole system more at least three years. robust. The backends are not included in GIO, but in the separate GVFS package. GVFS also contains a daemon which spawn further mount daemons for each More Information individual connection. TM https://www.gtk.org/ https://blog.gtk.org/ Architecture Overview GLib – the Core Library Over time GTK+ has been built up to be based on Firstly, GLib provides common data structures: other libraries, also developed by the GTK+ team: • Single and doubly linked lists. • GLib, a low-level core library that forms the ba- • Hash tables. sis of GTK+. It provides data structure handling for C, portability wrappers and interfaces for such • Balanced binary trees. A main event loop. run-time functionality as an event loop, threads, • N-ary trees: trees of data with any number of dynamic loading, an object system (GObject) and branches. GObject – an Object System high-level input/output APIs (GIO). • Strings with text buffers which grow automatically • Pango, a library for layout and rendering of text as text is added. Most modern programming languages come with their with an emphasis on internationalization. It forms own native object systems and additional fundamen- • Arrays of arbitrary elements which grow automat- the core of text and font handling for GTK+. tal algorithmic language constructs. Just as GLib ically as elements are added. serves as an implementation of such fundamental types • ATK, a library for a set of interfaces providing • GVariant, a generic data type that stores a value and algorithms (linked lists, hash tables and so forth), accessibility. By supporting the ATK interfaces, an along with information about the type of that GObject provides an implementation of a flexible, ex- application or toolkit can be used with tools such value. tensible, and intentionally easy to map (into other lan- as screen readers, magnifiers, and alternative input guages) object-oriented framework for C. devices. • And a few other data structures. All common object-oriented concepts are present: in- • GDK is the abstraction layer that allows GTK+ heritance, interfaces, virtual/overridable methods, ab- to support multiple windowing systems. GDK pro- GLib also contains loads of utilities: stract classes, constructors, destructors, and so on. vides backends for X11, Windows, Mac OS X, Way- • String and Unicode manipulation. Memory management is handled by reference count- land, Mir, and a web browser. • Date and time functions. ing: when the reference count decreases to 0 the object Another library used heavily by GTK+, but which • A command-line option parser. is destroyed. GObject also provides a powerful signal system: you can create your own signals and connect is external to the GTK+ project, is Cairo, a library • Perl-compatible regular expressions. for 2D graphics with support for multiple output de- callback functions to it. It is a great way to decou- vices (including the X Window System, Win32 and • An XML parser. ple classes since the object sending the signal doesn’t know who receive it. Another peculiarity of GObject Quartz) while producing a consistent output on all me- • A unit-test framework. dia while taking advantage of display hardware accel- is a property, which is basically an object attribute sur- • And many other utilities. eration when available. mounted by a notify signal that is sent when its value changes. Last, but not least, GLib provides some core event- Alongside a GLib event loop, the GObject signal sys- driven programming features, with a main event loop, tem forms a foundation for event-driven programming. Your GTK+ Application support for threads and asynchronous communication The event-driven paradigm is not only useful for graph- between threads. An event loop listens some sources of GTK+ ical user interfaces (with user events such as key presses events, that can come from file descriptors (plain files, and mouse clicks), but also for daemons that respond Pango GDK ATK GIO pipes or sockets), timeouts, or other custom sources. A to hardware changes (a USB stick inserted, a second priority is associated with each source of events. When monitor connected, a printer low on paper), or soft- Cairo GLib an event arrives, the event loop dispatches it to the ware that listen to network connections or messages application. The event can then be taken into account, from other processes, among other examples. either in the same thread or another thread..
Load more

Recommended publications
  • R&S®BBA100 Broadband Amplifier Open
    R&S®BBA100 Broadband Amplifier Open Source Acknowledgment 5353.8300.00 – 01 /RL/1/EN 01.00 / Broadcasting 3575.4620.02 M: - T - PAD Open Source Acknowledgment R&S BBA100 Introduction Contents 1 Introduction ......................................................................................... 3 1.1 Disclaimer ..................................................................................................................... 3 1.2 How to obtain the source code .................................................................................. 3 2 Software packages ............................................................................. 4 3 Verbatim license texts ........................................................................ 7 3.1 Apache License 2.0 ..................................................................................................... 7 3.2 GNU Library General Public License, Version 2.0 (LGPL 2.0) ..............................10 3.3 Boost Software License ............................................................................................18 3.4 GNU General Public License, Version 2.0 (GPL 2.0) ..............................................18 3.5 GNU Lesser General Public License, Version 2.1 (LGPL 2.1) ...............................24 3.6 Mozilla Public License, Version 1.1 (MPL 1.1) ........................................................32 3.7 MIT ...............................................................................................................................40 3.8 JDOM License
    [Show full text]
  • A Practical UNIX Capability System
    A Practical UNIX Capability System Adam Langley <[email protected]> 22nd June 2005 ii Abstract This report seeks to document the development of a capability security system based on a Linux kernel and to follow through the implications of such a system. After defining terms, several other capability systems are discussed and found to be excellent, but to have too high a barrier to entry. This motivates the development of the above system. The capability system decomposes traditionally monolithic applications into a number of communicating actors, each of which is a separate process. Actors may only communicate using the capabilities given to them and so the impact of a vulnerability in a given actor can be reasoned about. This design pattern is demonstrated to be advantageous in terms of security, comprehensibility and mod- ularity and with an acceptable performance penality. From this, following through a few of the further avenues which present themselves is the two hours traffic of our stage. Acknowledgments I would like to thank my supervisor, Dr Kelly, for all the time he has put into cajoling and persuading me that the rest of the world might have a trick or two worth learning. Also, I’d like to thank Bryce Wilcox-O’Hearn for introducing me to capabilities many years ago. Contents 1 Introduction 1 2 Terms 3 2.1 POSIX ‘Capabilities’ . 3 2.2 Password Capabilities . 4 3 Motivations 7 3.1 Ambient Authority . 7 3.2 Confused Deputy . 8 3.3 Pervasive Testing . 8 3.4 Clear Auditing of Vulnerabilities . 9 3.5 Easy Configurability .
    [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]
  • 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]
  • 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]
  • Ultimate++ Forum Probably with These Two Variables You Could Try to Integrate D-BUS
    Subject: DBus integration -- need help Posted by jlfranks on Thu, 20 Jul 2017 15:30:07 GMT View Forum Message <> Reply to Message We are trying to add a DBus server to existing large U++ application that runs only on Linux. I've converted from X11 to GTK for Upp project config to be compatible with GIO dbus library. I've created a separate thread for the DBus server and ran into problems with event loop. I've gutted my DBus server code of everything except what is causing an issue. DBus GIO examples use GMainLoop in order for DBus to service asynchronous events. Everything compiles and runs except the main UI is not longer visible. There must be a GTK main loop already running and I've stepped on it with this code. Is there a way for me to obtain a pointer to the UI main loop and use it with my DBus server? How/where can I do that? Code snipped example as follows: ---- code snippet ---- myDBusServerMainThread() { //========================================================== ===== // // Enter main service loop for this thread // while (not needsExit ()) { // colaborate with join() GMainLoop *loop; loop = g_main_loop_new(NULL, FALSE); g_main_loop_run(loop); } } Subject: Re: DBus integration -- need help Posted by Klugier on Thu, 20 Jul 2017 22:30:17 GMT View Forum Message <> Reply to Message Hello, You could try use following methods of Ctrl to obtain gtk & gdk handlers: GdkWindow *gdk() const { return top ? top->window->window : NULL; } GtkWindow *gtk() const { return top ? (GtkWindow *)top->window : NULL; } Page 1 of 3 ---- Generated from Ultimate++ forum Probably with these two variables you could try to integrate D-BUS.
    [Show full text]
  • Fundamentals of Xlib Programming by Examples
    Fundamentals of Xlib Programming by Examples by Ross Maloney Contents 1 Introduction 1 1.1 Critic of the available literature . 1 1.2 The Place of the X Protocol . 1 1.3 X Window Programming gotchas . 2 2 Getting started 4 2.1 Basic Xlib programming steps . 5 2.2 Creating a single window . 5 2.2.1 Open connection to the server . 6 2.2.2 Top-level window . 7 2.2.3 Exercises . 10 2.3 Smallest Xlib program to produce a window . 10 2.3.1 Exercises . 10 2.4 A simple but useful X Window program . 11 2.4.1 Exercises . 12 2.5 A moving window . 12 2.5.1 Exercises . 15 2.6 Parts of windows can disappear from view . 16 2.6.1 Testing overlay services available from an X server . 17 2.6.2 Consequences of no server overlay services . 17 2.6.3 Exercises . 23 2.7 Changing a window’s properties . 23 2.8 Content summary . 25 3 Windows and events produce menus 26 3.1 Colour . 26 3.1.1 Exercises . 27 i CONTENTS 3.2 A button to click . 29 3.3 Events . 33 3.3.1 Exercises . 37 3.4 Menus . 37 3.4.1 Text labelled menu buttons . 38 3.4.2 Exercises . 43 3.5 Some events of the mouse . 44 3.6 A mouse behaviour application . 55 3.6.1 Exercises . 58 3.7 Implementing hierarchical menus . 58 3.7.1 Exercises . 67 3.8 Content summary . 67 4 Pixmaps 68 4.1 The pixmap resource .
    [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]
  • Decwindows Motif Guide to Application Programming
    DECwindows Motif Guide to Application Programming Order Number: AA–PGZEB–TE January 1994 This document describes the programming interface for widgets provided by Digital in the DECwindows Motif Version 1.2 Toolkit. This document also includes tutorial programming information for the DECwindows Motif Version 1.2 Toolkit. Revision/Update Information: This is a revised manual. Operating System: OpenVMS AXP Version 1.5 VMS Version 5.5–2 Software Version: DECwindows Motif Version 1.2 for OpenVMS AXP DECwindows Motif Version 1.2 for OpenVMS VAX Digital Equipment Corporation Maynard, Massachusetts January 1994 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1994. All Rights Reserved. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, Bookreader, DEC, DECpaint, DECterm, DECwindows, DECwrite, Digital, eXcursion, OpenVMS, VAX, VAX DOCUMENT, VMS, XUI, and the DIGITAL logo.
    [Show full text]
  • A Successor to the X Window System
    Y: A Successor to the X Window System Mark Thomas <[email protected]> Project Supervisor: D. R¨uckert <[email protected]> Second Marker: E. Lupu <[email protected]> June 18, 2003 ii Abstract UNIX desktop environments are a mess. The proliferation of incompatible and inconsistent user interface toolkits is now the primary factor in the failure of enterprises to adopt UNIX as a desktop solution. This report documents the creation of a comprehensive, elegant framework for a complete windowing system, including a standardised graphical user interface toolkit. ‘Y’ addresses many of the problems associated with current systems, whilst keeping and improving on their best features. An initial implementation, which supports simple applications like a terminal emulator, a clock and a calculator, is provided. iii iv Acknowledgements Thanks to Daniel R¨uckert for supervising the project and for his help and advice regarding it. Thanks to David McBride for his assistance with setting up my project machine and providing me with an ATI Radeon for it. Thanks to Philip Willoughby for his knowledge of the POSIX standard and help with the GNU Autotools and some of the more obscure libc functions. Thanks to Andrew Suffield for his help with the GNU Autotools and Arch. Thanks to Nick Maynard and Karl O’Keeffe for discussions on window system and GUI design. Thanks to Tim Southerwood for discussions about possible features of Y. Thanks to Duncan White for discussions about the virtues of X. All company and product names are trademarks and/or registered trademarks of their respective owners.
    [Show full text]
  • Clutter Version 1.10.0, Updated 9 May 2012
    Guile-GNOME: Clutter version 1.10.0, updated 9 May 2012 Matthew Allum and OpenedHand LTD Intel Corporation This manual is for (gnome clutter) (version 1.10.0, updated 9 May 2012) Copyright 2006,2007,2008 OpenedHand LTD Copyright 2009,2010,2011,2012 Intel Corporation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You may obtain a copy of the GNU Free Documentation License from the Free Software Foundation by visiting their Web site or by writing to: The Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA i Short Contents 1 Overview :::::::::::::::::::::::::::::::::::::::::::: 1 2 ClutterAction :::::::::::::::::::::::::::::::::::::::: 2 3 ClutterActorMeta ::::::::::::::::::::::::::::::::::::: 3 4 ClutterActor ::::::::::::::::::::::::::::::::::::::::: 5 5 ClutterAlignConstraint:::::::::::::::::::::::::::::::: 63 6 ClutterAlpha :::::::::::::::::::::::::::::::::::::::: 65 7 ClutterAnimatable ::::::::::::::::::::::::::::::::::: 68 8 Implicit Animations :::::::::::::::::::::::::::::::::: 69 9 ClutterAnimator ::::::::::::::::::::::::::::::::::::: 76 10 ClutterBackend :::::::::::::::::::::::::::::::::::::: 82 11 ClutterBinLayout :::::::::::::::::::::::::::::::::::: 84 12 ClutterBindConstraint :::::::::::::::::::::::::::::::: 87 13 Key Bindings:::::::::::::::::::::::::::::::::::::::: 90
    [Show full text]