Thanks for explaining that. I think it was a mistake for me to call this class a "widget" based on that notion, since it's already reusing a view (TalkDetailsWidget). I'd say it actually performs more as a controller in that it takes the input from its TalkDetailsWidget instance and sends it over to the model.