Also, whenever you are able to isolate a cohesive set of properties and methods from your view, you can extract it into a separate class which represents something real (what a pity that flexbuilder isn't capable to do this automatically).
Tim, can you provide a code example, which necessarily needs a ViewHelper (or can benefit from it substantially)? Cheers, Ralf. On 7/3/06, JesterXL <[EMAIL PROTECTED]> wrote: > Speaking for Steven, but the reason they espoused using ModelLocator over > ViewHelpers was a few reasons. First off, many people felt the need to > create ViewHelpers for every View. This was ridicolous; no View could ever > do anything useful but instantiate GUI components, and register for events. > You had no clue WHAT that View could do. Suddenly you're code base > basically doubled for extremely little gain. -- 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/
