2007-08-04 04:59:18 -04:00
|
|
|
#include <stdlib.h>
|
2008-11-07 14:32:28 -05:00
|
|
|
#include <gmodule.h>
|
2007-08-04 04:59:18 -04:00
|
|
|
#include <clutter/clutter.h>
|
|
|
|
|
2008-01-31 09:42:49 -05:00
|
|
|
/* each time the timeline animating the label completes, swap the direction */
|
2007-08-04 04:59:18 -04:00
|
|
|
static void
|
|
|
|
timeline_completed (ClutterTimeline *timeline,
|
|
|
|
gpointer user_data)
|
|
|
|
{
|
2008-01-31 09:42:49 -05:00
|
|
|
clutter_timeline_set_direction (timeline,
|
|
|
|
!clutter_timeline_get_direction (timeline));
|
2007-08-04 04:59:18 -04:00
|
|
|
clutter_timeline_start (timeline);
|
|
|
|
}
|
|
|
|
|
2008-10-08 15:50:22 -04:00
|
|
|
static ClutterActor *raise_actor[2];
|
2008-01-31 09:42:49 -05:00
|
|
|
static gboolean raise_no = 0;
|
|
|
|
|
|
|
|
static gboolean
|
|
|
|
raise_top (gpointer ignored)
|
|
|
|
{
|
2008-10-08 15:50:22 -04:00
|
|
|
clutter_actor_raise_top (raise_actor[raise_no]);
|
2008-01-31 09:42:49 -05:00
|
|
|
raise_no = !raise_no;
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
2008-01-31 11:55:34 -05:00
|
|
|
static ClutterActor *
|
2009-01-27 10:18:45 -05:00
|
|
|
clone_box (ClutterActor *original)
|
2008-01-31 11:55:34 -05:00
|
|
|
{
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
gfloat width, height;
|
2008-01-31 11:55:34 -05:00
|
|
|
ClutterActor *group;
|
|
|
|
ClutterActor *clone;
|
|
|
|
|
2009-01-27 10:18:45 -05:00
|
|
|
clutter_actor_get_size (original, &width, &height);
|
2008-01-31 11:55:34 -05:00
|
|
|
|
|
|
|
group = clutter_group_new ();
|
2009-01-27 10:18:45 -05:00
|
|
|
clone = clutter_clone_new (original);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (group), clone);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_depth (clone, width / 2);
|
2008-01-31 11:55:34 -05:00
|
|
|
|
2009-01-27 10:18:45 -05:00
|
|
|
clone = clutter_clone_new (original);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (group), clone);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_rotation (clone, CLUTTER_Y_AXIS, 180, width / 2, 0, 0);
|
|
|
|
clutter_actor_set_depth (clone, -width / 2);
|
2008-01-31 11:55:34 -05:00
|
|
|
|
2009-01-27 10:18:45 -05:00
|
|
|
clone = clutter_clone_new (original);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (group), clone);
|
|
|
|
clutter_actor_set_rotation (clone, CLUTTER_Y_AXIS, 90, 0, 0, 0);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_depth (clone, width / 2);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (clone, 0, 0);
|
|
|
|
|
2009-01-27 10:18:45 -05:00
|
|
|
clone = clutter_clone_new (original);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (group), clone);
|
|
|
|
clutter_actor_set_rotation (clone, CLUTTER_Y_AXIS, 90, 0, 0, 0);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_depth (clone, width / 2);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (clone, width, 0);
|
|
|
|
|
2009-01-27 10:18:45 -05:00
|
|
|
clone = clutter_clone_new (original);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (group), clone);
|
|
|
|
clutter_actor_set_rotation (clone, CLUTTER_X_AXIS, 90, 0, 0, 0);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_depth (clone, -width / 2);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (clone, 0, height);
|
|
|
|
|
2009-01-27 10:18:45 -05:00
|
|
|
clone = clutter_clone_new (original);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (group), clone);
|
|
|
|
clutter_actor_set_rotation (clone, CLUTTER_X_AXIS, 90, 0, 0, 0);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_depth (clone, -width / 2);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (clone, 0, 0);
|
|
|
|
|
|
|
|
clutter_actor_show_all (group);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
|
2008-01-31 11:55:34 -05:00
|
|
|
return group;
|
|
|
|
}
|
|
|
|
|
2008-01-31 09:42:49 -05:00
|
|
|
static ClutterActor *
|
|
|
|
janus_group (const gchar *front_text,
|
|
|
|
const gchar *back_text)
|
|
|
|
{
|
2008-01-31 11:55:34 -05:00
|
|
|
ClutterColor slide_color = {0x00, 0x00, 0x00, 0xff};
|
2008-01-31 09:42:49 -05:00
|
|
|
ClutterColor red = {0xff, 0x00, 0x00, 0xff};
|
|
|
|
ClutterColor green = {0x00, 0xff, 0x00, 0xff};
|
|
|
|
ClutterActor *group, *rectangle, *front, *back;
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
gfloat width, height;
|
|
|
|
gfloat width2, height2;
|
2008-01-31 09:42:49 -05:00
|
|
|
|
|
|
|
group = clutter_group_new ();
|
|
|
|
rectangle = clutter_rectangle_new_with_color (&slide_color);
|
2008-12-11 08:48:01 -05:00
|
|
|
front = clutter_text_new_with_text ("Sans 50px", front_text);
|
|
|
|
back = clutter_text_new_with_text ("Sans 50px", back_text);
|
|
|
|
clutter_text_set_color (CLUTTER_TEXT (front), &red);
|
|
|
|
clutter_text_set_color (CLUTTER_TEXT (back), &green);
|
2008-01-31 09:42:49 -05:00
|
|
|
|
|
|
|
clutter_actor_get_size (front, &width, &height);
|
|
|
|
clutter_actor_get_size (back, &width2, &height2);
|
|
|
|
|
|
|
|
if (width2 > width)
|
|
|
|
width = width2;
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
|
2008-06-10 02:37:46 -04:00
|
|
|
if (height2 > height)
|
2008-01-31 09:42:49 -05:00
|
|
|
height = height2;
|
|
|
|
|
|
|
|
clutter_actor_set_size (rectangle, width, height);
|
Remove Units from the public API
With the recent change to internal floating point values, ClutterUnit
has become a redundant type, defined to be a float. All integer entry
points are being internally converted to floating point values to be
passed to the GL pipeline with the least amount of conversion.
ClutterUnit is thus exposed as just a "pixel with fractionary bits",
and not -- as users might think -- as generic, resolution and device
independent units. not that it was the case, but a definitive amount
of people was convinced it did provide this "feature", and was flummoxed
about the mere existence of this type.
So, having ClutterUnit exposed in the public API doubles the entry
points and has the following disadvantages:
- we have to maintain twice the amount of entry points in ClutterActor
- we still do an integer-to-float implicit conversion
- we introduce a weird impedance between pixels and "pixels with
fractionary bits"
- language bindings will have to choose what to bind, and resort
to manually overriding the API
+ *except* for language bindings based on GObject-Introspection, as
they cannot do manual overrides, thus will replicate the entire
set of entry points
For these reason, we should coalesces every Actor entry point for
pixels and for ClutterUnit into a single entry point taking a float,
like:
void clutter_actor_set_x (ClutterActor *self,
gfloat x);
void clutter_actor_get_size (ClutterActor *self,
gfloat *width,
gfloat *height);
gfloat clutter_actor_get_height (ClutterActor *self);
etc.
The issues I have identified are:
- we'll have a two cases of compiler warnings:
- printf() format of the return values from %d to %f
- clutter_actor_get_size() taking floats instead of unsigned ints
- we'll have a problem with varargs when passing an integer instead
of a floating point value, except on 64bit platforms where the
size of a float is the same as the size of an int
To be clear: the *intent* of the API should not change -- we still use
pixels everywhere -- but:
- we remove ambiguity in the API with regard to pixels and units
- we remove entry points we get to maintain for the whole 1.0
version of the API
- we make things simpler to bind for both manual language bindings
and automatic (gobject-introspection based) ones
- we have the simplest API possible while still exposing the
capabilities of the underlying GL implementation
2009-05-06 11:44:47 -04:00
|
|
|
clutter_actor_set_rotation (back, CLUTTER_Y_AXIS, 180, width / 2, 0, 0);
|
2008-01-31 09:42:49 -05:00
|
|
|
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add (CLUTTER_CONTAINER (group),
|
|
|
|
back, rectangle, front, NULL);
|
2008-01-31 09:42:49 -05:00
|
|
|
|
|
|
|
clutter_actor_show_all (group);
|
|
|
|
return group;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2008-11-07 14:32:28 -05:00
|
|
|
G_MODULE_EXPORT gint
|
|
|
|
test_depth_main (int argc, char *argv[])
|
2007-08-04 04:59:18 -04:00
|
|
|
{
|
2008-01-31 09:42:49 -05:00
|
|
|
ClutterTimeline *timeline;
|
|
|
|
ClutterBehaviour *d_behave;
|
|
|
|
ClutterBehaviour *r_behave;
|
|
|
|
ClutterActor *stage;
|
2008-01-31 11:55:34 -05:00
|
|
|
ClutterActor *group, *hand, *label, *rect, *janus, *box;
|
2008-01-31 09:42:49 -05:00
|
|
|
ClutterColor stage_color = { 0xcc, 0xcc, 0xcc, 0xff };
|
|
|
|
ClutterColor rect_color = { 0, 0, 0, 0x88 };
|
[stage] Coalesce fog and perspective API
The fog and perspective API is currently split in two parts:
- the floating point version, using values
- the fixed point version, using structures
The relative properties are using the structure types, since they
are meant to set multiple values at the same time. Instead of
using bare values, the whole API should be coalesced into two
simple calls using structures to match the GObject properties.
Thus:
clutter_stage_set_fog (ClutterStage*, const ClutterFog*)
clutter_stage_get_fog (ClutterStage*, ClutterFog*)
clutter_stage_set_perspective (ClutterStage*, const ClutterPerspective*)
clutter_stage_get_perspective (ClutterStage*, ClutterPerspective*)
Which supercedes the fixed point and floating point variants.
More importantly, both ClutterFog and ClutterPerspective should
using floating point values, since that's what get passed to
COGL anyway.
ClutterFog should also drop the "density" member, since ClutterStage
only allows linear fog; non-linear fog distribution can be achieved
using a signal handler and calling cogl_set_fog() directly; this keeps
the API compact yet extensible.
Finally, there is no ClutterStage:fog so it should be added.
2009-03-09 13:24:44 -04:00
|
|
|
ClutterFog stage_fog = { 10.0, -50.0 };
|
2008-01-31 09:42:49 -05:00
|
|
|
GError *error;
|
2007-08-04 04:59:18 -04:00
|
|
|
|
|
|
|
clutter_init (&argc, &argv);
|
|
|
|
|
|
|
|
stage = clutter_stage_get_default ();
|
|
|
|
clutter_stage_set_color (CLUTTER_STAGE (stage), &stage_color);
|
[stage] Coalesce fog and perspective API
The fog and perspective API is currently split in two parts:
- the floating point version, using values
- the fixed point version, using structures
The relative properties are using the structure types, since they
are meant to set multiple values at the same time. Instead of
using bare values, the whole API should be coalesced into two
simple calls using structures to match the GObject properties.
Thus:
clutter_stage_set_fog (ClutterStage*, const ClutterFog*)
clutter_stage_get_fog (ClutterStage*, ClutterFog*)
clutter_stage_set_perspective (ClutterStage*, const ClutterPerspective*)
clutter_stage_get_perspective (ClutterStage*, ClutterPerspective*)
Which supercedes the fixed point and floating point variants.
More importantly, both ClutterFog and ClutterPerspective should
using floating point values, since that's what get passed to
COGL anyway.
ClutterFog should also drop the "density" member, since ClutterStage
only allows linear fog; non-linear fog distribution can be achieved
using a signal handler and calling cogl_set_fog() directly; this keeps
the API compact yet extensible.
Finally, there is no ClutterStage:fog so it should be added.
2009-03-09 13:24:44 -04:00
|
|
|
clutter_stage_set_fog (CLUTTER_STAGE (stage), &stage_fog);
|
2007-11-21 06:55:26 -05:00
|
|
|
clutter_stage_set_use_fog (CLUTTER_STAGE (stage), TRUE);
|
|
|
|
|
2007-08-04 04:59:18 -04:00
|
|
|
g_signal_connect (stage,
|
|
|
|
"button-press-event", G_CALLBACK (clutter_main_quit),
|
|
|
|
NULL);
|
|
|
|
|
2008-01-27 18:39:23 -05:00
|
|
|
group = clutter_group_new ();
|
|
|
|
clutter_stage_add (stage, group);
|
|
|
|
clutter_actor_show (group);
|
|
|
|
|
2008-12-11 08:48:01 -05:00
|
|
|
label = clutter_text_new_with_text ("Mono 26", "Clutter");
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (label, 120, 200);
|
2007-11-21 06:55:26 -05:00
|
|
|
clutter_actor_show (label);
|
|
|
|
|
2008-04-25 09:37:36 -04:00
|
|
|
error = NULL;
|
|
|
|
hand = clutter_texture_new_from_file ("redhand.png", &error);
|
|
|
|
if (error)
|
|
|
|
g_error ("Unable to load redhand.png: %s", error->message);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (hand, 240, 100);
|
2007-08-04 04:59:18 -04:00
|
|
|
clutter_actor_show (hand);
|
|
|
|
|
2007-11-21 06:55:26 -05:00
|
|
|
rect = clutter_rectangle_new_with_color (&rect_color);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_actor_set_position (rect, 340, 100);
|
2007-11-21 06:55:26 -05:00
|
|
|
clutter_actor_set_size (rect, 200, 200);
|
|
|
|
clutter_actor_show (rect);
|
2007-08-04 04:59:18 -04:00
|
|
|
|
2008-01-31 09:42:49 -05:00
|
|
|
clutter_container_add (CLUTTER_CONTAINER (group), hand, rect, NULL);
|
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (stage), label);
|
2007-08-04 04:59:18 -04:00
|
|
|
|
2007-11-21 06:55:26 -05:00
|
|
|
/* 3 seconds, at 60 fps */
|
|
|
|
timeline = clutter_timeline_new (180, 60);
|
2007-08-04 04:59:18 -04:00
|
|
|
g_signal_connect (timeline,
|
|
|
|
"completed", G_CALLBACK (timeline_completed),
|
|
|
|
NULL);
|
|
|
|
|
2009-01-16 08:42:06 -05:00
|
|
|
d_behave =
|
|
|
|
clutter_behaviour_depth_new (clutter_alpha_new_full (timeline,
|
|
|
|
CLUTTER_LINEAR),
|
|
|
|
-100, 100);
|
2008-01-31 09:42:49 -05:00
|
|
|
clutter_behaviour_apply (d_behave, label);
|
|
|
|
|
|
|
|
/* add two faced actor */
|
|
|
|
janus = janus_group ("GREEN", "RED");
|
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (stage), janus);
|
|
|
|
clutter_actor_set_position (janus, 300, 350);
|
|
|
|
|
2009-01-16 08:42:06 -05:00
|
|
|
r_behave =
|
|
|
|
clutter_behaviour_rotate_new (clutter_alpha_new_full (timeline,
|
|
|
|
CLUTTER_LINEAR),
|
|
|
|
CLUTTER_Y_AXIS,
|
|
|
|
CLUTTER_ROTATE_CW,
|
|
|
|
0, 360);
|
2008-01-31 09:42:49 -05:00
|
|
|
clutter_behaviour_apply (r_behave, janus);
|
2007-08-04 04:59:18 -04:00
|
|
|
|
2008-01-31 11:55:34 -05:00
|
|
|
/* add hand box */
|
2009-01-27 10:18:45 -05:00
|
|
|
box = clone_box (hand);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_container_add_actor (CLUTTER_CONTAINER (stage), box);
|
|
|
|
clutter_actor_set_position (box, 200, 250);
|
|
|
|
clutter_actor_set_scale (box, 0.5, 0.5);
|
|
|
|
clutter_actor_set_rotation (box, CLUTTER_X_AXIS, 45, 0, 0, 0);
|
|
|
|
clutter_actor_set_opacity (box, 0x44);
|
|
|
|
|
2009-01-16 08:42:06 -05:00
|
|
|
r_behave =
|
|
|
|
clutter_behaviour_rotate_new (clutter_alpha_new_full (timeline,
|
|
|
|
CLUTTER_LINEAR),
|
|
|
|
CLUTTER_Y_AXIS,
|
|
|
|
CLUTTER_ROTATE_CW,
|
|
|
|
0, 360);
|
2008-01-31 11:55:34 -05:00
|
|
|
clutter_behaviour_apply (r_behave, box);
|
|
|
|
|
|
|
|
|
2007-08-04 04:59:18 -04:00
|
|
|
clutter_actor_show (stage);
|
|
|
|
|
|
|
|
clutter_timeline_start (timeline);
|
|
|
|
|
2008-10-08 15:50:22 -04:00
|
|
|
raise_actor[0] = rect;
|
|
|
|
raise_actor[1] = hand;
|
2008-01-31 09:42:49 -05:00
|
|
|
g_timeout_add (2000, raise_top, NULL);
|
|
|
|
|
2007-08-04 04:59:18 -04:00
|
|
|
clutter_main ();
|
|
|
|
|
|
|
|
g_object_unref (d_behave);
|
|
|
|
g_object_unref (timeline);
|
|
|
|
|
|
|
|
return EXIT_SUCCESS;
|
|
|
|
}
|