brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
mutter/examples/Makefile.am

47 lines
894 B
Makefile
Raw Normal View History

Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 18:30:10 +01:00
include $(top_srcdir)/build/autotools/Makefile.am.silent
all_examples = \
basic-actor \
examples: Updated box-layout example Updated test-box-layout to use modern API and move it to examples. https://bugzilla.gnome.org/show_bug.cgi?id=677283
2012-06-02 15:01:11 +02:00
box-layout \
Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 18:30:10 +01:00
canvas \
constraints \
drag-action \
drop-action \
Move the easing modes test into the examples It's a pretty simple, self-contained example of how to use different easing modes, as well as the implicit animations API.
2012-05-02 18:37:36 +01:00
easing-modes \
Move FlowLayout test into examples There's nothing really test-worthy in the ClutterFlowLayout interactive test; it can be lifted pretty much as is, and placed into the examples.
2012-05-02 12:14:45 +01:00
flow-layout \
examples: Add a grid-layout example A fairly complete example for ClutterGridLayout https://bugzilla.gnome.org/show_bug.cgi?id=677372
2012-06-03 12:18:37 +02:00
grid-layout \
examples: Add an example of layout manager The MultiLayout shows how to write a layout manager with two policies, and to use the easing state of a child to interpolate the allocation.
2012-05-04 17:43:30 +01:00
layout-manager \
pan-action: add PanAction, to handle panning in scrollable actors PanAction is a GestureAction-subclass that implements the panning concept for scrollable actors, with the ability to emit interpolated signals to emulate the kinetic inertia of the panning. PanAction provides: • pan signal, notifying users of the panning gesture status; • pan-stopped signal, emitted at the end of the interpolated phase of the panning gesture, if enabled; • pan-axis property, to allow constraining the dragging to a specific axis; • interpolated property, to enable or disable the inertial behaviour; • deceleration property, to customize the rate at which the momentum of the panning will be slowed down; • acceleration-factor property, applied to the inertial momentum when starting the interpolated sequence. An interactive test is also provided. https://bugzilla.gnome.org/show_bug.cgi?id=681648
2012-08-25 16:23:23 +02:00
pan-action \
Add rounded corners rectangle example using Canvas An old request: how to create a rectangle with rounded corners with Clutter; we use ClutterCanvas and Cairo because we want anti-aliased edges.
2012-05-03 13:53:29 +01:00
rounded-rectangle \
Move scroll actor test to the examples Nothing specific to test, and the code is idiomatic enough to be used as an example.
2012-05-16 16:12:20 +01:00
scroll-actor \
Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 18:30:10 +01:00
threads
if PIXBUF_TESTS
all_examples += \
bin-layout \
image-content
endif
INCLUDES = \
-I$(top_srcdir) \
build: Fix out of tree builds
2012-07-30 12:33:24 +01:00
-I$(top_builddir) \
Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 18:30:10 +01:00
-I$(top_srcdir)/clutter \
-I$(top_builddir)/clutter
LDADD = \
$(top_builddir)/clutter/libclutter-@CLUTTER_API_VERSION@.la \
$(CLUTTER_LIBS) \
$(GDK_PIXBUF_LIBS) \
-lm
examples: Enable maintainer compiler flags Another step in keeping the example code up to date and correct.
2012-06-06 13:39:50 +01:00
AM_CFLAGS = $(CLUTTER_CFLAGS) $(GDK_PIXBUF_CFLAGS) $(MAINTAINER_CFLAGS)
Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 18:30:10 +01:00
AM_CPPFLAGS = \
-DTESTS_DATADIR=\""$(abs_top_srcdir)/tests/data"\" \
-DG_DISABLE_SINGLE_INCLUDES \
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
-DGLIB_DISABLE_DEPRECATION_WARNINGS
Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 18:30:10 +01:00
noinst_PROGRAMS = $(all_examples)
-include $(top_srcdir)/build/autotools/Makefile.am.gitignore
Reference in New Issue Copy Permalink