Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
GDK
open-in-new
<h2 id="software-architecture">Software architecture</h2> <p>GTK is implemented on top of an abstraction layer called GDK, freeing GTK from low-level concerns like input gathering, <a href="/facts/Drag_and_drop/7Xd8vXfn">drag and drop</a>, and pixel format conversion. GDK is an intermediate layer which separates GTK from the details of the windowing system. </p><p>GDK is an important part of GTK's portability. Since low-level cross-platform functionality is already provided by <a href="/facts/GLib/s3a6avhy">GLib</a>, all that is needed to make GTK run on other platforms is to port GDK to the underlying <a href="/facts/Operating_system/8XTuvMh2">operating system</a>'s graphics layer. Hence, the GDK ports to the <a href="/facts/Windows_API/RRw4RtTu">Windows API</a> and <a href="/facts/Quartz_(graphics_layer)/FLvFwpYt">Quartz</a> are what enable GTK applications to run on <a href="/facts/Microsoft_Windows/bwhAhuSL">Windows</a> and <a href="/facts/MacOS/Y93vVpTm">macOS</a>, respectively. </p><p>Starting with GTK+ 2.8, GDK supports <a href="/facts/Cairo_(graphics)/FuAWHozI">Cairo</a>, which is recommended for use with GTK+ 3 instead of GDK's drawing functions.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> </p><p>GDK is an intermediate layer which isolates <a href="/facts/GTK/oLpVm9pp">GTK</a> from the details of the <a href="/facts/Windowing_system/nKYmkjP6">windowing system</a>. GDK is a thin wrapper around <a href="/facts/Xlib/2fKMo9BF">Xlib</a>. The X Window System comes with a low-level library called <a href="/facts/Xlib/2fKMo9BF">Xlib</a>. Almost every function in GDK is a very thin wrapper around a corresponding Xlib function; but some of the complexity (and functionality) of Xlib is hidden, to simplify programming and to make GDK easier to port to other windowing systems, such as <a href="/facts/Wayland_(display_server_protocol)/I9I1TbEG">Wayland</a> or Microsoft Windows. The Xlib functionality provided is mostly that targeted toward applications; for example, many features used solely by <a href="/facts/Window_manager/WFRnDBz7">window managers</a> are not exposed in GDK. </p><p>GDK supports <a href="/facts/OpenGL/xQoMWePr">OpenGL</a> (or <a href="/facts/OpenGL_ES/DRkjxUFb">OpenGL ES</a>) for better control of the <a href="/facts/Graphics_pipeline/XnF55m31">graphics pipeline</a>. </p> <h3>GdkFrameClock</h3> <p>GdkFrameClock was added in GTK 3.8<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>While GTK applications remain mainloop driven (cf. <a href="/facts/Event_loop/NNcN8Auy">Glib event loop</a>), meaning the application is idle inside this main loop most of the time waiting for an event and then calls the appropriate subroutine when one occurs, GdkFrameClock adds an additional mechanism, which tells the application when to update and repaint a window.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> The update rate can be synchronized with the monitor refresh rate. </p> <h3>GTK Scene Graph Kit</h3> <p class="note">Main article: <a href="/facts/GTK_Scene_Graph_Kit/awvXl29R">GTK Scene Graph Kit</a></p> <p>In its history GDK contained and linked with a couple of different <a href="/facts/Canvas_(GUI)/Wk1G3BLX">Canvases</a>. </p> <ul><li><a href="https://wiki.gnome.org/Attic/ProjectRidley/CanvasOverview">https://wiki.gnome.org/Attic/ProjectRidley/CanvasOverview</a> <ul><li><a href="https://wiki.gnome.org/Attic/ProjectRidley/CanvasOverview/Canvases">https://wiki.gnome.org/Attic/ProjectRidley/CanvasOverview/Canvases</a></li></ul></li> <li><a href="https://wiki.gnome.org/Projects/GooCanvas">https://wiki.gnome.org/Projects/GooCanvas</a></li></ul> <p>Developers were also considering new directions for the library, including removing deprecated <a href="/facts/Application_programming_interface/GMlN4vUr">API</a> components and adding an integrated <a href="/facts/Canvas_(GUI)/Wk1G3BLX">scene graph (canvas)</a> system, similar to the Clutter graphics library, effectively integrating GTK with <a href="/facts/OpenGL/xQoMWePr">OpenGL</a> and <a href="/facts/Vulkan_(API)/e188Vdpc">Vulkan</a>.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a><a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p> <ul><li><a href="/facts/GTK_Scene_Graph_Kit/awvXl29R">GTK Scene Graph Kit</a> (GSK)<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a><a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a></li></ul> <p>GTK+ Scene Graph Kit (GSK) was released as part of GTK+ 3.90 in March 2017. It is the scene graph and rendering API for GTK. GSK has not been further integrated with GDK (which is also part of GTK) but is kept in its own directory. </p> <h3>Windowing systems</h3> <p>GDK contains back-ends to a couple of <a href="/facts/Windowing_system/nKYmkjP6">windowing systems</a>, namely to the <a href="/facts/X11/ac2vRIQL">X11</a> and <a href="/facts/Wayland_(display_server_protocol)/I9I1TbEG">Wayland</a> protocols, to <a href="/facts/Quartz_Compositor/etoHysmD">Quartz</a> and <a href="/facts/Graphics_Device_Interface/C8yuXxtL">GDI</a>, and even to the <a href="/facts/Hypertext_Transfer_Protocol/TWtvf7JD">Hypertext Transfer Protocol</a> (HTTP) engine Broadway. </p><p>With the release of GNOME 3.16 in March 2015, GDK obtained an experimental back-end for the <a href="/facts/Mir_(software)/ocQNVYbU">Mir</a> display server protocol.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> The Mir display server protocol is a product by <a href="/facts/Canonical_(company)/76WPw1uW">Canonical</a> for their <a href="/facts/Ubuntu_(operating_system)/0WDd7hkb">Ubuntu</a> distribution of Linux, which they intend to compete with the Wayland display server protocol; so far, it is implemented only in Ubuntu. </p><p>At present, no back-end exists for <a href="/facts/Direct_Rendering_Manager/AjCBBvrU">KMS</a>. </p><p>The environment variable <i>GDK_BACKEND</i> can be used to start an application and force this instance of it to use a certain windowing system: GDK_BACKEND=wayland gnome-calculator GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese </p> <h2 id="gdk-pixbuf">gdk-pixbuf</h2> <p>gdk-pixbuf is a toolkit for image loading and pixel buffer manipulation. The library provides image loading and saving facilities, fast scaling and compositing of pixbufs, simple animation loading (i.e. animated GIFs), and rendering the libart image buffer to a GdkDrawable instance. </p><p>gdk-pixbuf has a fairly large API. </p><p>The fundamental structure in the gdk-pixbuf library is GdkPixbuf, a private, opaque data structure that mirrors many of the same concepts that ArtPixBuf supports. In fact, most of GdkPixbuf's private data fields have the same names and data types as the corresponding ones in ArtPixBuf. This similarity dates back to the earlier days when gdk-pixbuf was a wrapper around <a href="/facts/Libart/qe3EhptL">libart</a>. Since that time, the libart dependency has been stripped out, and gdk-pixbuf was merged into the GTK+ 2.0 code base. As such, gdk-pixbuf's days as a standalone library are limited to the <a href="/facts/GNOME_1/njT57VQI">GNOME 1</a> release. </p><p>With the release of GTK+ 2.22 on 2010-09-23, gdk-pixbuf has been turned back into a standalone library, after being shipped as part of GTK+ since gtk+ 2.0. This was done in preparation for the transition to GTK+ 3. </p> <ul><li><a href="https://git.gnome.org/browse/gdk-pixbuf/">https://git.gnome.org/browse/gdk-pixbuf/</a></li></ul> <p>The first stand-alone release was <a href="https://mail.gnome.org/archives/ftp-release-list/2010-September/msg00119.html">2.22</a> on 2010-Sep-21, its development started with <a href="https://mail.gnome.org/archives/ftp-release-list/2010-June/msg00171.html">2.21.3</a> on 2010-06-23. </p> <h2 id="history">History</h2> <p>GDK was originally developed on the <a href="/facts/Display_server/nKYmkjP6">X Window System</a> for the GIMP <a href="/facts/Raster_graphics_editor/rP4c280y">raster graphics editor</a>.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p> <h2 id="see-also">See also</h2> <ul> <li>Free and open-source software portal</li></ul> <ul><li>Clutter</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="https://git.gnome.org/browse/gtk+/tree/gdk?h=gtk-3-18">GDK code from release GTK+ 3.19.0</a></li> <li><a href="https://blogs.gnome.org/alexl/2013/11/04/the-modern-gtk-drawing-model/">The modern Gtk drawing model</a> – Alexander Larsson, 2013/11/04</li> <li><a href="https://www.gtk.org/overview.php">Overview of GTK and its Libraries</a> <a href="https://web.archive.org/web/20190312022548/https://www.gtk.org/overview.php">Archived</a> 2019-03-12 at the <a href="/facts/Wayback_Machine/nmQ3a6JC">Wayback Machine</a> - The GTK Project</li> <li><a href="https://git.gnome.org/browse/gtk-web/plain/images/architecture.svg">https://git.gnome.org/browse/gtk-web/plain/images/architecture.svg</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Migrating from GTK+ 2.x to GTK+ 3 - Use cairo for drawing <a href="https://docs.gtk.org/gtk3/migrating-2to3.html#use-cairo-for-drawing" target="_blank">https://docs.gtk.org/gtk3/migrating-2to3.html#use-cairo-for-drawing</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"GdkFrameClock". <a href="https://developer.gnome.org/gdk3/stable/GdkFrameClock.html" target="_blank">https://developer.gnome.org/gdk3/stable/GdkFrameClock.html</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Larsson, Alexander (2013-11-04). "The modern Gtk drawing model". <a href="https://blogs.gnome.org/alexl/2013/11/04/the-modern-gtk-drawing-model/" target="_blank">https://blogs.gnome.org/alexl/2013/11/04/the-modern-gtk-drawing-model/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Alberto Ruiz's Blog <a href="https://aruiz.typepad.com/siliconisland/2008/03/gtk-hackfest-20.html" target="_blank">https://aruiz.typepad.com/siliconisland/2008/03/gtk-hackfest-20.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Havoc Pennington's scene graph proposal <a href="https://mail.gnome.org/archives/gtk-devel-list/2008-March/msg00017.html" target="_blank">https://mail.gnome.org/archives/gtk-devel-list/2008-March/msg00017.html</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"The GTK+ Scene Graph Kit". 2014-07-29. <a href="https://www.bassi.io/articles/2014/07/29/guadec-2014-gsk/" target="_blank">https://www.bassi.io/articles/2014/07/29/guadec-2014-gsk/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Graphene". 2014-05-02. <a href="https://blogs.gnome.org/ebassi/2014/05/02/graphene/" target="_blank">https://blogs.gnome.org/ebassi/2014/05/02/graphene/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"add an experimental backend for mir". <a href="https://git.gnome.org/browse/gtk+/commit/?id=0f26b26f1d93f002ccd5fe6b6fd636172bfbb24b" target="_blank">https://git.gnome.org/browse/gtk+/commit/?id=0f26b26f1d93f002ccd5fe6b6fd636172bfbb24b</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>GIMP - A Brief (and Ancient) History of GIMP <a href="https://www.gimp.org/about/ancient_history.html" target="_blank">https://www.gimp.org/about/ancient_history.html</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> </ol>