continue development where we left before the release effort
introduce typedef for Frame numbers (see #882)
settle and implement some long standing concerns regarding #920

- what the dispatch operation actally is
- where the deadlines are established
TiddlyWiki: fix some orphaned pages

...caused by image names starting with upper case letter
explain the term 'subsystem'
fix error in test fixture

random offset should always be != zero
Ticket #925: remove LUID from interface/plugin specifications

In the November developer meeting, Christian and I agreed that
it's best to remove that offending LUID specifications altogether.

Those embedded LUIDs where one of the issues blocking the transition to C++11
Switch compilation to C++11 standard with GNU extensions

Why GNU extensions? They where on by default previously,
so we're changing nothing besides the C++ standard level.

AFAIK, we're using a GNU extension at one place, and this
could be replaced by 'decltype' now.
Switch from TR1 preveiw to the new standard headers

- functional
- memory
- unordered collections
unsuccessful attempt to bridge between std::hash and boost::hash_value  (Ticket #722)
minor improvement to the GUI-model Sequence

including a LUID based hash identity
C++11 transition fixes

- comparison of weak-pointers
Ticket #940: solution for binding GUI signals

 * use a development snapshot of lib SigC including the recent C++11 adaptations
 * never include whole namespaces. Here we got a clash between std::bind and sigc::bind
 * use lambdas
   * to make the binding code more readable
   * to take the nested invocations apart, which resolves the return type ambiguity
Ticket #942: introduce move semantics for our custom shared-ptr-wrapper lib::P
C++11 transition: get compilation to pass again

...but we have still 12 test failures
Scons: check for C++11 specific headers. Be more explicit w/r boost

we still don't check for the precise boost version number in the
SCons configuration. We might do so in future, but for now our
policy is that precise version dependency checking is the business
of the packager (i.e. the debian package). The SCons build just
has to ensure the absolute necessary baseline
DOC: Tighten the build requirements to C++11 and Boost-1.55
testrunner: handle help request properly

don't actually execute the tests when there was a --help
fix long standing error in testsuite runner

...uncovered by switching to c++11
When invoking an individual test, we used to erase
the 0-th cmdline argument, which happens to be allways
the name of the test being invoked. Yet none of our
tests actually complied to that contract. Rather,
all tests taking arguments access them by 1-based
argument index. Previously, the argument values just
happened to be still in memory at the original location
after erasing the 0st element.

"Fixed" that by changing the contract. Now, the 0th argument
remains in place, but when there are no additional arguments,
the whole cmdline is cleared.
This is messy, but the test runer needs to be rewritten
entirely, the whole API is clumsy and dangerous. Ticket #289
C++ uses a more precise meaning of 'convertiblity' now

Conversion means automatic conversion. In our case,
what we need ist the ability to *construct* a bool from
our (function) object -- while functors aren't automatically
convertible to bool. Thus we use one of the new predicates
from <type_traits>