So in essence you would create additional classes that are basically ParameterHandlers (maybe "Catalogs" would be an analogy that would fit here?), is that correct? Directors and Builders would then only need to use the same Catalog to determine what they can and should know about the object to be created.
If I understand you correctly then this is something I also thought about. The advantage would be that it would be clearer where to find these parameters and not be surprised if an object of a class has lots of attributes that come from its various mixed-in roles.
Maybe this isn't at all what you meant but I think I'm warming up to the idea anyway.... :-)
In reply to Re^2: Builder design pattern with lots of parameters - trying to declutter design
by tospo
in thread Builder design pattern with lots of parameters - trying to declutter design
by tospo
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |