On Wed, May 25, 2005 at 03:51:19PM -0400, mental@...3... wrote:
Quoting Bryce Harrington <bryce@...260...>:
I haven't looked very deeply at that, but I suspect it may impose requirements that may make it inconvenient to just have a showDialog() routine. It may be necessary to have a getDialog() routine, to allow the verb handler a chance to make those customizations. However, I think a preferable solution would be to push that custom stuff down into the dialog's code itself, so all dialogs can be handled the same way.
Probably what you are reaching for is the Template Method pattern (http://www.dofactory.com/Patterns/PatternTemplate.aspx), where showDialog() would act as the template method [not to be confused with C++ templates].
It could be. Like I said, I haven't really analyzed the more complex dialogs to see why they have the custom behavior. It may even be possible to solve it just with the virtual functions.
I don't think this has to be sorted out for the 0.42 release. Possibly as people convert more dialogs it'll get solved dialog by dialog without any trouble.
Bryce