I'd like to contribute to ZfcUser by normalizing some of the form handling behavior and propose some specific changes to the location and sequencing of Form construction. Before I do that, I want to make sure I'm clear on the go-forward strategy for Form extension.
As ZfcUser is split into many optional modules, I assume we'll badly need -- and therefore adopt -- a consistent Form extension strategy. This will make it possible for arbitrarily many modules to enhance a single Form. Is the preferred Form extension strategy still in flux or is there a specific strategy that's been decided?
An obvious choice is an event-based system -- a convention used (somewhat inconsistently) in the current code base. However, I'd hate to invest time standardizing and tweaking this strategy if it is instead a legacy that's going away.
I'd like to contribute to ZfcUser by normalizing some of the form handling behavior and propose some specific changes to the location and sequencing of Form construction. Before I do that, I want to make sure I'm clear on the go-forward strategy for Form extension.
As ZfcUser is split into many optional modules, I assume we'll badly need -- and therefore adopt -- a consistent Form extension strategy. This will make it possible for arbitrarily many modules to enhance a single Form. Is the preferred Form extension strategy still in flux or is there a specific strategy that's been decided?
An obvious choice is an event-based system -- a convention used (somewhat inconsistently) in the current code base. However, I'd hate to invest time standardizing and tweaking this strategy if it is instead a legacy that's going away.