My Experience is what Benoit outlined. Direct interaction between Commands and Views objects causes heavy coupling that limits the reuse off your view. Granted coupling is needed in a design, but this is where the ViewHelper comes in. Define your API/Features for your View in the mind set that its generic enough that any Command could call it then create that specific API method in ViewHelper.
Renaun --- In [email protected], "Benoit Hediard" <[EMAIL PROTECTED]> wrote: > > I'll second this approach : > 1. use as much as possible the Model Locator and bindings to avoid > commands<>views dependencies, > 2. when not sufficient or not elegant, use a viewhelper. > > Benoit Hediard (which was using too much viewhelpers at the begining ;) ) > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
