This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Joined: Feb 19, 2013
Sorry for not being precise enough.
I know I could do something like creating a new composite and inside the composite I could list several components/composites and only ONE component is rendered based on some incoming attribute.
But this way the composite will grow and grow. The component selector I am thinking about might serve as a selector for maybe more than 100 components.
So I think it's necessary or better to have some kind of "registry" for the component and select it via some "key".
Background: Imagine some generic UI for defining jobs. Each job has its specific parameters and after selecting a job I would like to offer some input component(s) specially designed for that job.