Enforcing CLAM's framework good practices.

Another change related with the Processing infrastructure 3.2.2 is the clarification of a single way of doing things, removing accessory behavior that has not proven as useful as expected. In the first phases of the framework design, there were obvious problems of ``over-design'', which resulted in offering different ways of doing similar things. This flexibility promotes misuse and unnecessary complexity. There are now many Processing classes and in some cases some of them do similar things such as type checking or default initialization in different ways. A clear guideline in how all Processing objects should behave has been issued but now needs to be promoted into the whole repository.