domfarr98 / java-objects-as-components Goto Github PK

Having the selector have the ability to change cases at run-time allows for dynamic decision making inside of composite components, meaning that composed components that aren't selected aren't lost (allowing for greater applicability and re-use of a single component). However, this is only present in the selector mechanism, which means that half of all composites have this feature. By allowing for sequences to be changed during run-time, this feature will be present in all composites.

Most component models feature a loop mechanism as well as a selector and a sequencer to be Turing complete. This was simply a missed feature when this was first created and implementing such a functionality wouldn't be especially difficult.