> The two ideas that jump out at me from your code are that the
> Form handling can be organized as submit-driven callbacks,
> and that a Page class can coordinate handling of a page
> of forms.  Both of these are appealing.  I guess the open question
> is whether code that follows this pattern is easier to understand.

I think it might be a familiar pattern for those with experience with a
typical GUI toolkit but maybe not for others.

Maybe that's an inevitable trade-off against the hoped for benefits of
refactoring things this way: greater consistency in behavior/appearance
and less overall coding.

What's really nice about QP is it's so flexible you can use both
approaches in a mix and match fashion.

Dave