isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-26 01:50:42 -05:00
Code Issues Packages Projects Releases Wiki Activity
093aa086af
mutter/clutter/clutter/clutter-paint-node.h

102 lines
4.6 KiB
C
Raw Normal View History

Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
/*
* Clutter.
*
* An OpenGL based 'interactive canvas' library.
*
* Copyright (C) 2011 Intel Corporation.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2 of the License, or (at your option) any later version.
*
* This library 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
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library. If not, see <http://www.gnu.org/licenses/>.
*
* Author:
* Emmanuele Bassi <ebassi@linux.intel.com>
*/
Move header inclusion guard at the top GCC has some optimization for the inclusion guard, but they only work if the check is the outermost one. We're fairly inconsistent because of historical reasons, so we should ensure that we follow the same pattern in every public header.
2015-07-07 10:51:13 -04:00
#ifndef __CLUTTER_PAINT_NODE_H__
#define __CLUTTER_PAINT_NODE_H__
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
#if !defined(__CLUTTER_H_INSIDE__) && !defined(CLUTTER_COMPILATION)
#error "Only <clutter/clutter.h> can be included directly."
#endif
#include <cogl/cogl.h>
#include <clutter/clutter-types.h>
G_BEGIN_DECLS
#define CLUTTER_TYPE_PAINT_NODE (clutter_paint_node_get_type ())
#define CLUTTER_PAINT_NODE(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), CLUTTER_TYPE_PAINT_NODE, ClutterPaintNode))
#define CLUTTER_IS_PAINT_NODE(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), CLUTTER_TYPE_PAINT_NODE))
typedef struct _ClutterPaintNodePrivate ClutterPaintNodePrivate;
typedef struct _ClutterPaintNodeClass ClutterPaintNodeClass;
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
GType clutter_paint_node_get_type (void) G_GNUC_CONST;
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
ClutterPaintNode * clutter_paint_node_ref (ClutterPaintNode *node);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_unref (ClutterPaintNode *node);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_set_name (ClutterPaintNode *node,
const char *name);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_add_child (ClutterPaintNode *node,
ClutterPaintNode *child);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_add_rectangle (ClutterPaintNode *node,
const ClutterActorBox *rect);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_add_texture_rectangle (ClutterPaintNode *node,
const ClutterActorBox *rect,
float x_1,
float y_1,
float x_2,
float y_2);
Remove cogl-1.0 vs cogl-2.0 vs cogl experimental API split Mutter (and libmutter users) are the only users of this version of cogl, and will more or less only use the cogl-1.0, cogl-2.0 and cogl experimental API variants, and having the possibility of having different API versions of the same API depending on what file includes it is error prone and confusing. Lets just remove the possibility of having different versions of the same API. https://bugzilla.gnome.org/show_bug.cgi?id=768977
2016-06-16 15:04:40 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_add_path (ClutterPaintNode *node,
CoglPath *path);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_paint_node_add_primitive (ClutterPaintNode *node,
CoglPrimitive *primitive);
Fixes for the API reference Typos, missing symbols, and missing documentation.
2012-04-19 11:00:23 -04:00
/**
* CLUTTER_VALUE_HOLDS_PAINT_NODE:
* @value: a #GValue
*
* Evaluates to %TRUE if the @value has been initialized to hold
* a #ClutterPaintNode.
*
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
* Since: 1.10
Fixes for the API reference Typos, missing symbols, and missing documentation.
2012-04-19 11:00:23 -04:00
*/
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
#define CLUTTER_VALUE_HOLDS_PAINT_NODE(value) (G_VALUE_HOLDS (value, CLUTTER_TYPE_PAINT_NODE))
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_value_set_paint_node (GValue *value,
gpointer node);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
void clutter_value_take_paint_node (GValue *value,
gpointer node);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
gpointer clutter_value_get_paint_node (const GValue *value);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
CLUTTER_AVAILABLE_IN_1_10
Add PaintNode, an element on the render object tree Now that we have a proper scene graph API, we should split out the rendering part from the logical and event handling part. ClutterPaintNode is a lightweight fundamental type that encodes only the paint operations: pipeline state and geometry. At its most simple, is a way to structure setting up the programmable pipeline using a CoglPipeline, and submitting Cogl primitives. The important take away from this API is that you are not allowed to call Cogl API like cogl_set_source() or cogl_primitive_draw() directly. The interesting approach to this is that, in the future, we should be able to move to a purely retained mode: we will decide which actors need to be painted, they will update their own branch of the render graph, and we'll take the render graph and build all the rendering commands from that. For the 1.x API, we will have to maintain invariants and the existing behaviour, but as soon as we can break API, the old paint signal will just go away, and Actors will only be allowed to manipulate the render tree.
2012-02-01 10:51:27 -05:00
gpointer clutter_value_dup_paint_node (const GValue *value);
G_END_DECLS
#endif /* __CLUTTER_PAINT_NODE_H__ */
Reference in New Issue Copy Permalink