Re^3: Understanding Catalyst

I’m not sure that the MVC paradigm really addresses that concept very well. If the application has no persistent storage, I’m not sure if one would say that it has a Model.

However ... “there are no absolutes.” MVC, like everything else, is a guideline not a mantra. If you have developed something that works cleanly for you, I would not redesign it for the sake of philosophy. :-) Others may weigh-in with differing opinions.

Replies are listed 'Best First'.
Re^4: Understanding Catalyst by Your Mother (Archbishop) on Oct 04, 2015 at 18:42 UTC
Model != Storage. Model == Data. Google search API is a model, for example. A weather service is a model. `sub d10 { 1+int(rand(10)) }` is a model.	[reply] [d/l]
Re^5: Understanding Catalyst by QuillMeantTen (Friar) on Oct 05, 2015 at 06:31 UTC
In your example, shouldn't the sub d10 live in another file than the Controller/(Root\|whatever).pm?	[reply]
Re^6: Understanding Catalyst by Your Mother (Archbishop) on Oct 05, 2015 at 11:32 UTC
Yes. It would either be in MyApp::Model::Dice or much better in a Games::Dice module that has nothing to do with MyApp and is used via model glue like Catalyst::Model::Adaptor. I am trying to write a reply to your original post but it’s pretty long and I might not get it done.	[reply]
Re^7: Understanding Catalyst by Anonymous Monk on Oct 05, 2015 at 21:49 UTC
Re^8: Understanding Catalyst by Your Mother (Archbishop) on Oct 05, 2015 at 21:54 UTC
Some notes below your chosen depth have not been shown here