-- Christof Coetzee <[email protected]> wrote
(on Wednesday, 28 September 2011, 01:55 PM -0700):
> Matt thanks for the reply,
> 
> I have used the methods as per this tutorial as well - I guess my point with
> over-engineer is just that, a lot of classes, options etc. etc. to
> accomplish something really trivial, maybe I'm just lazy 
> 
> Anyway sometimes true genius lies in simplicity, I consider myself very
> proficient with ZF and I struggle with decorators and every single ZF
> developer I've worked with feels the same... I'm not referring to simple
> form layouts as you'll find in 80% of all the tutorials - then there is also
> the obvious potholes as well, file fields and belongsTo array issues etc.
> 
> bottom line is most of the time front-end developers/designers design the
> form layouts, which in a counter argument makes the decorators sort of
> redundant anyway, unless we use view scripts and hand code the render() of
> 1000 fields.
> 
> long story short, the decorators does not help us with RAD, its frustrating
> and makes us miss deadlines...history has proven that the more complex
> something gets, the more prone to error, the trend these days are anyway
> "simpler is better"

The problem we have is that we're trying to accommodate too many use
cases -- which is why the decorators were developed in the first place.
Yes, "simpler is better" is a good mantra, but at the complexity level
of forms, it falls apart. There are few if any good approaches that will
meet that criteria.

I totally understand your frustrations, and we're hoping to address them
with a new forms implementation in ZF2. If you'd be willing to step up
and test those against your criteria for ease of use and flexibility
when we have a ZF2 release ready with the forms, I'd appreciate it.

-- 
Matthew Weier O'Phinney
Project Lead            | [email protected]
Zend Framework          | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc

-- 
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]


Reply via email to