mutter

isa/mutter

mirror of https://github.com/brl/mutter.git synced 2025-02-26 09:44:10 +00:00

History

Emmanuele Bassi 75ef676b15 examples: Build with deprecation warnings turned on

We want to ensure that the examples stay valid and idiomatic; thus, we
should build them with deprecation warnings turned on.

2012-06-06 13:37:05 +01:00

basic-actor.c

timeline: Add a new "stopped" signal

2012-05-31 09:54:23 +01:00

bin-layout.c

Move examples from tests/interactive to a new top-level

2012-05-01 19:00:35 +01:00

box-layout.c

examples: Updated box-layout example

2012-06-04 16:16:39 +02:00

canvas.c

examples/canvas: Resize the canvas on allocation changes

2012-05-11 17:38:53 +01:00

constraints.c

examples/constraints: Do not use deprecated API

2012-06-06 13:37:02 +01:00

drag-action.c

examples: Update drag and drop action code

2012-05-24 13:58:31 +01:00

drop-action.c

examples: Update drag and drop action code

2012-05-24 13:58:31 +01:00

easing-modes.c

Move the easing modes test into the examples

2012-05-02 18:37:36 +01:00

flow-layout.c

examples/flow: Do not use deprecated API

2012-06-06 13:36:46 +01:00

grid-layout.c

examples: Add a grid-layout example

2012-06-05 12:28:40 +02:00

image-content.c

Move examples from tests/interactive to a new top-level

2012-05-01 19:00:35 +01:00

layout-manager.c

examples: Update layout-manager example to use the animations API

2012-05-28 19:37:19 +02:00

Makefile.am

examples: Build with deprecation warnings turned on

2012-06-06 13:37:05 +01:00

README

Move examples from tests/interactive to a new top-level

2012-05-01 19:00:35 +01:00

rounded-rectangle.c

Add rounded corners rectangle example using Canvas

2012-05-04 17:54:51 +01:00

scroll-actor.c

Move scroll actor test to the examples

2012-05-17 10:57:15 +01:00

threads.c

examples/threads: Modernize code

2012-06-05 18:47:44 +01:00

README

The code in this directory is meant to be XIncluded into the Clutter API
reference, and thus is to be considered part of the Clutter documentation.

As such, the code MUST be:

  - correct;
  - idiomatic, i.e. show how a task is meant to be achieved using the
    best possible practices given the current API;
  - well documented;
  - ready for copy and paste.