yes it does break the mvc model. The one example that could be considered okay is the creation of a select form element as it does require quite a bit of logic and could be considered as something that clutters the template with logic that is outside the expertise of the template engineer. But then again the logic is not that difficult and does not require that much extra Velocity code, so it may not be worth breaking the MVC separation. John McNally Ethan Adams wrote: > > Does it break the MVC model to have your screen class pre-build HTML and stuff it >into a context value for the template to display????? > > I know this probably isn't appropriate for this group....but I figured I would try. > > ------------------------------------------------------------ > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] > Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> > Problems?: [EMAIL PROTECTED] ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
