Till Bovermann

Can't this be done with a (Control)`Spec`? This seems to be similar to the String specs used in the OSC implementation, or?

@sensestage: > I have to admit that I am not uptodate enough with the code base to know how much of the work on Collectives that I put in is...

Speaking of `MKtlElementCollective`, it is missing documentation... And I have no diea whatsoever what it is intended for.

related to #140

if all the accessors are implemented, this could be starting as a cookbook example. If popular, can be made into a separate class.

wit the new MKtlDesc implementation, we could have a method `serialise` which returns `MKtl:fullDesc` including all `MKtlElement:value` (and lastValue etc.) serialised into a state dictionary...

:100:

Sounds good to me. I was wondering how much we need to follow the geometry of the H/W devices... maybe it is just enough to give hints on available real-estate...

An alternative would be to show only mas 2 ocatves (more are really difficult to handle screen-real-estate-wise). IMHO, there's no point of showing 80 keys, even if that master keyboard...

in the cookbook?