Hi Nancy ---

Sounds like the little known Nancy_Folsom_Search_and_Replace_Wizard pattern. :-)

Seriously, I wouldn't sweat it. What you are trying to do is refactor existing code into design patterns when it may not be possible. You may not be able to reconcile objects=patterns. It could be that a composite of objects sortof equals a pattern or a single object embraces multiple patterns.

You can go nuts with stuff like this.


>I have a search and replace wizard class library that comprises several classes and subclasses. It's an old (and working) routine. Now, I'm trying to model it (yeah, yeah, I know :), and am driving myself nuts trying to identify what patterns things *might* be.
>
>For example: I have a container superclass that I subclass into containers for each wizard step. I add the controls for each step to the container subclass. (I then have a pageframe class that subclasses the step containers.) In this case the container superclass just sets the layout information. I don't add any custom properties or methods. Is this an example (even if a bad one) of a Facade structural pattern? I looked at Template, but to me it's not a behavioral pattern.
>
>Another example: I have a listbox subclass that adds a custom property called "PopulateList". This subclass calls PopulateList in the Init, but it doesn't code the Populate list. I let subclasses control that. Is this an example of a Template Method design pattern?
>
>TIA for comments (and patience :)