Re: [Catalyst] An MVC logic separation conundrum

Thank you all very much for your help, it's given me some real food for thought. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive:

Re: [Catalyst] An MVC logic separation conundrum

Chris, Related to this, I've a scheduled job that sends email that include URLs back to my catalyst app, so... can't really use a callback here. URL details such as hostname and path are configuration info. It would be nice to have a light-weight method for accessing the app's routing, but

Re: [Catalyst] An MVC logic separation conundrum

* Chris Welch [2016-03-10 15:45]: > My original question was not about passing the method call in per se, > but the return value from that method call You could do that of course. The question I’d ask is, does the caller have to know which values from the match object it

Re: [Catalyst] An MVC logic separation conundrum

On 10 March 2016 at 12:42, Aristotle Pagaltzis wrote: > * Chris Welch [2016-03-09 20:10]: > > All of this brings up a quandary: there are only two ways around this > > that I can see: > > There’s plenty more. E.g. you could have generate_ical_data expect

Re: [Catalyst] An MVC logic separation conundrum

* Chris Welch [2016-03-09 20:10]: > All of this brings up a quandary: there are only two ways around this > that I can see: There’s plenty more. E.g. you could have generate_ical_data expect one or several callbacks to generate those values for it, something like

Re: [Catalyst] An MVC logic separation conundrum

Thank you for the validation - I thought that was the case. On 9 March 2016 at 22:11, Darren Duncan wrote: > The best option is to keep the concerns separated. Models should always > take their inputs via explicit arguments for a Model-specific API, and they > should

Re: [Catalyst] An MVC logic separation conundrum

The best option is to keep the concerns separated. Models should always take their inputs via explicit arguments for a Model-specific API, and they should not have any knowledge of or direct access to a Controller. If this means you have to bundle up a larger amount of data in the Controller