Discuss Term and Fingerprint class structure

[thiemowmde]

Personally I'm not absolutely happy with how the Term and Fingerprint class structure is build currently. Examples:

$entity->getFingerprint()->setAliasGroup(
    new AliasGroup( 'en', array( 'ohi' ) )
);
// vs.
$entity->getFingerprint()->setAliasGroup(
    'en', array( 'ohi' )
);

$entity->getFingerprint()->setAliasGroups(
    new AliasGroupList( array( /* ... */ ) )
);
// vs.
$entity->getFingerprint()->setAliasGroups(
    array( /* ... */ )
);

Similar for most of the new ...List classes (I hope you don't misunderstood me when I said that these classes feel to me like "reimplementing PHP arrays"). I'm aware this is a very vague discussion at this point. I think we all need to actually work with this code to form personal opinions if it's good as it is or should be simpler.

This ticket is a reminder for that later discussion.

[JeroenDeDauw]

I've been thinking that adding shortcut methods as follows might be nice:

$fingerprint->setDescriptionText( 'en', 'some english stuff' );
$fingerprint->setAliasGroupTexts( 'en', array( ... ) );

Do keep in mind that patterns such as this should happen rarely, since they "reach through objects":

$entity->getFingerprint()->stuff()

In almost all cases, code doing things with labels and such should just get a Fingerprint rather than a whole Entity.

[thiemowmde]

Here is an other example I found in #62:

$this->fingerprint->setDescriptions( new TermList( array() ) );