isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-27 05:12:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
849607316a
mutter/examples
History
Emmanuele Bassi df15f04fc0 build: Use libtool macros to find libm 
Instead of using `-lm` everywhere, use LT_LIB_M inside configure.ac, and
$(LIBM) inside Makefile.am.
2015-03-03 17:23:37 +00:00
..
basic-actor.c examples/basic: Use the event type and not a flag 2012-07-30 10:54:18 +01:00
bin-layout.c Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
box-layout.c examples/box: Allow toggling animations 2012-08-20 17:58:30 +01: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: Remove a stray restore_easing_state() 2013-06-15 12:12:43 +01:00
easing-modes.c examples/easing-modes: Use newly added modes 2012-07-19 22:13:28 -04:00
flow-layout.c flow-layout: Add :snap-to-grid property 2013-05-11 10:54:38 -04:00
grid-layout.c Remove usage of ClutterLayoutManager easing API 2012-07-11 13:22:21 +01:00
image-content.c Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
layout-manager.c examples/layout-manager: Toggle between states 2015-01-11 17:00:02 +00:00
Makefile.am build: Use libtool macros to find libm 2015-03-03 17:23:37 +00:00
pan-action.c Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
README Move examples from tests/interactive to a new top-level 2012-05-01 19:00:35 +01:00
redhand.png Fully rework the conformance test suite 2013-12-12 18:51:11 +00:00
rounded-rectangle.c examples/rounded: Use CLUTTER_REQUEST_CONTENT_SIZE 2015-01-12 13:38:07 +00:00
scroll-actor.c Move scroll actor test to the examples 2012-05-17 10:57:15 +01:00
threads.c examples: Use pivot point, not anchor point 2012-07-11 13:22:20 +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.