1. 18 Jun, 2018 1 commit
  2. 17 Jun, 2018 4 commits
  3. 05 May, 2017 1 commit
  4. 23 Aug, 2016 1 commit
  5. 11 Dec, 2015 1 commit
  6. 06 Dec, 2015 2 commits
  7. 19 Aug, 2015 1 commit
  8. 11 Jul, 2015 2 commits
  9. 07 Jul, 2015 1 commit
  10. 18 Jun, 2015 1 commit
  11. 23 Apr, 2015 1 commit
  12. 03 Mar, 2015 2 commits
    • Emmanuele Bassi's avatar
      Drop the UProf dependency · 25329280
      Emmanuele Bassi authored
      Nobody has been compiling Clutter with profiling enabled in a long time.
      UProf itself hasn't been updated in 5 years, and it still depends on
      deprecated components like dbus-glib, with no port to GDBus in sight.
      The profiling code was moderately useful in the past, but these days
      it's probably better to profile Cogl than Clutter itself; timing
      information can be extracted by the timestamp on each diagnostic message
      that is now available by default in the CLUTTER_NOTE macro, and we can
      add ad hoc counters where needed.
    • Emmanuele Bassi's avatar
      build: Use libtool macros to find libm · df15f04f
      Emmanuele Bassi authored
      Instead of using `-lm` everywhere, use LT_LIB_M inside configure.ac, and
      $(LIBM) inside Makefile.am.
  13. 03 Jan, 2015 1 commit
    • Emmanuele Bassi's avatar
      WARNING: Massive revert commit · 77ec8774
      Emmanuele Bassi authored
      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
      89a2862b commit. The history is too long
      to be reverted commit by commit without being extremely messy.
  14. 01 Jan, 2015 1 commit
  15. 14 Dec, 2014 1 commit
  16. 23 Jul, 2014 1 commit
  17. 27 Jun, 2014 1 commit
  18. 25 Jun, 2014 1 commit
  19. 10 Feb, 2014 1 commit
  20. 24 Jan, 2014 2 commits
  21. 23 Jan, 2014 2 commits
  22. 20 Jan, 2014 1 commit
  23. 12 Dec, 2013 4 commits
    • Emmanuele Bassi's avatar
      build: Ignore *.test files · b4044292
      Emmanuele Bassi authored
      Generated when enabling installed tests.
    • Emmanuele Bassi's avatar
      conformance: Add more tests · 526d0ea8
      Emmanuele Bassi authored
      Add back some deprecated and general purpose API tests. These are the
      ones that were written already pretty much conforming to the GTest API
      and style, and thus require minimal porting.
    • Emmanuele Bassi's avatar
      conformance: Add actor tests · 7ec337f2
      Emmanuele Bassi authored
      Port the ClutterActor tests to the test API, and ensure they run under
      the new TAP harness.
    • Emmanuele Bassi's avatar
      Fully rework the conformance test suite · 2a660fa2
      Emmanuele Bassi authored
      The current conformance test suite is suboptimal in many ways.
      All tests are built into the same binary, which makes adding new tests,
      builting tests, and running groups of tests much more awkward than it
      needs to be. The first issue, especially, raises the bar of contribution
      in a significant way, while the other two take their toll on the
      maintainer. All of these changes were introduced back when we had both
      Clutter and Cogl tests in tree, and because we were building the test
      suite for every single change; since then, Cogl moved out of tree with
      all its tests, and we build the conformance test suite only when running
      the `check` make target.
      This admittedly large-ish commit changes the way the conformance test
      suite works, taking advantage of the changes in the GTest API and test
      First of all, all tests are now built separately, using their own test
      suite as defined by each separate file. All tests run under the TAP
      harness provided by GTest and Automake, to gather a proper report using
      the Test Anything Protocol without using the `gtester` harness and the
      `gtester-report` script. We also use the Makefile rules provided by GLib
      to vastly simplify the build environment for the conformance test suite.
      On top of the changes for the build and harness, we also provide new API
      for creating and running test suites for Clutter. The API is public,
      because the test suite has to use it, but it's minimal and mostly
      provides convenience wrappers around GTest that make writing test units
      for Clutter easier.
      This commit disables all tests in the conformance test suite, as well as
      moving the data files outside of the tests/data directory; the next few
      commits will re-establish the conformance test suite separately so we
      can check that everything works in a reliable way.
  24. 04 Dec, 2013 2 commits
  25. 14 Nov, 2013 1 commit
    • Bastian Winkler's avatar
      interval: Implement ClutterScriptable interface · e5678550
      Bastian Winkler authored
      This allows the creation of ClutterTransition objects in ClutterScript:
         "id" : "scripted-transition",
         "type" : "ClutterPropertyTransition",
         "property-name" : "background-color",
         "interval" : {
           "type" : "ClutterInterval",
           "value-type" : "ClutterColor",
           "initial" : "red",
           "final" : "blue"
  26. 27 Aug, 2013 1 commit
  27. 19 Aug, 2013 2 commits