summaryrefslogtreecommitdiff
path: root/gsk/gskprivate.c
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@gnome.org>2016-03-17 13:48:19 +0000
committerEmmanuele Bassi <ebassi@gnome.org>2016-10-18 11:29:34 +0100
commit7afdd3fdb5c5fda9da87555b40a61e6a321c2414 (patch)
treedf0af389900df9bf676695f95925dce9e8239d9d /gsk/gskprivate.c
parentd519e4aafe325106f6a5f2139921bf246cb4848d (diff)
downloadgtk+-7afdd3fdb5c5fda9da87555b40a61e6a321c2414.tar.gz
Initial implementation of GSK rendering pipeline
GSK is conceptually split into two scene graphs: * a simple rendering tree of operations * a complex set of logical layers The latter is built on the former, and adds convenience and high level API for application developers. The lower layer, though, is what gets transformed into the rendering pipeline, as it's simple and thus can be transformed into appropriate rendering commands with minimal state changes. The lower layer is also suitable for reuse from more complex higher layers, like the CSS machinery in GTK, without necessarily port those layers to the GSK high level API. This lower layer is based on GskRenderNode instances, which represent the tree of rendering operations; and a GskRenderer instance, which takes the render nodes and submits them (after potentially reordering and transforming them to a more appropriate representation) to the underlying graphic system.
Diffstat (limited to 'gsk/gskprivate.c')
-rw-r--r--gsk/gskprivate.c16
1 files changed, 16 insertions, 0 deletions
diff --git a/gsk/gskprivate.c b/gsk/gskprivate.c
new file mode 100644
index 0000000000..9e82502da5
--- /dev/null
+++ b/gsk/gskprivate.c
@@ -0,0 +1,16 @@
+#include "gskresources.h"
+
+static gpointer
+register_resources (gpointer data)
+{
+ _gsk_register_resource ();
+ return NULL;
+}
+
+void
+gsk_ensure_resources (void)
+{
+ static GOnce register_resources_once = G_ONCE_INIT;
+
+ g_once (&register_resources_once, register_resources, NULL);
+}