Re^5: Understanding Catalyst

Replies are listed 'Best First'.
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
via model glue like Catalyst::Model::Adaptor. I don't understand why that would be necessary ... it seems gratuitous	[reply]
Re^8: Understanding Catalyst by Your Mother (Archbishop) on Oct 05, 2015 at 21:54 UTC
It beats the crap out of 100 undecorated function calls and `use\|require` statements sprinked all over the place and even embedded in the templates with contorted logic to surface instead of just being in `[% c.model("WhatWhat").call %]` and then something impossible to repurpose, let alone trivially change, with a simple back end swap. `c.uri_for()` might seem gratuitous too if you’ve never grown an app that needed testing, flexible deployment, or midstream changes that could otherwise be trivial. :P	[reply] [d/l] [select]
Re^9: Understanding Catalyst by Anonymous Monk on Oct 05, 2015 at 22:08 UTC
Re^10: Understanding Catalyst by Your Mother (Archbishop) on Oct 05, 2015 at 22:57 UTC
Some notes below your chosen depth have not been shown here