I'm not a huge fan of the factory - I think we'd lose a lot of the
graceful class extension by forcing a factory class upon it and then
supply user paths, prefixes, etc. that could be avoided by inheritance.
The logic behind this is that with a factory, you may fetch a persisted form
(session, cache) which contains some data (like previous post info or error
messages).
I am still a big fan of the Zend_Db_Table approach, whereby methods such
as 'init()', 'preDispatch', 'postDispatch' etc could be leveraged to
allow a self-contained 'static' class (i.e. the logic is hardcoded into
the Form Model) or to build a dynamic form from a config file.
This pushes things like redirection into the model. Conventional thought on
MVC is that the controller layer handles things like redirection and user
input whereas models handle computation.
K
Hi all,
A few days ago I posted a new Zend_Form proposal. It takes a somewhat
different approach than Simon & Ralf's proposal.
It has been discussed a few times on #zftalk, but I feel that it could
really use some community input.
Please read it and comment on it at:
http://framework.zend.com/wiki/pages/viewpage.action?pageId=36061
Thanks!
Jurriën
--
Simon Mundy | Director | PEPTOLAB
""" " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654
4124
http://www.peptolab.com
