Adrian.

One comment – I disagree with you on this point :

“Adding boolean properties for ruling out in what state the component should be is a good practice.”

Using this approach it’s possible (though not valid) for your component to have both inInput == true & isFinal == true.

Instead, I’d suggest that it’s the job of the getCurrentSkinState() method to calculate the current state (without the use of external booleans). If you did want to store the calculated value, you should use a single state var ( string / int ) and a set of constants to avoid multiple states being active.

You could always retain the isInput / isFinal, (to improve readibility) but write them as getters :

private function get isInput() : Boolean
{
return getCurrentSkinState() == MySkinState.INPUT
}

Just my $0.02
That aside, I found the write up on states very informative. Thanks!

Marty