>I'm getting into this discussion late...
>
>Our "mainform" class uses a form with a pageframe. Works well and is extensible. We've also used invisible containers -- making them visible when needed. Works well, but lacks the features of forms -- user can't automatically drag, resize, etc... It sounds like formsets, forms, and pageframes each offer unique capabilities that may be useful to just about any application as the application grows. For this reason, I'm considering using a "mainformset" class for just about everything. This would be my own subclass that includes a formset, and a single form with a pageframe. This would give me the option to add more forms or to add more pages without any redesign. If I do not use additional forms or pages the overhead should be small. Do you see any problems with this strategy?

Seems like there is no easy answer. We are going to try to see what the overhead is. One would think that the only overhead would be at instanciation, and destroy, but maybe formset events processing has a cost associated. Some of our automated processes are very real time intensive, so a small overhead in event processing may affect the long term results.