Re: Understanding Catalyst

Methinks that you have “Model” and “View” confused in your mind . . .

(See Catalyst::Manual::Intro.) The MVC view-of-the-world basically goes like this:

Model: Access to data, manipulating data, allowing the rest of the application to functionally-ignore where the data comes from and how it is stored.
View: The presentation layer. Templating and output-preparation goes here. (Not in the Model.)
Controller: Everything else.

And, while the MVC paradigm is a useful way to look at some things, it really only works really-well with CRUD (Create, Read, Update, Delete) applications, where the user’s conceptual model of what he is doing is fairly close to “I am manipulating records in a database, and I can do anything I want with anything that I see.” When the application becomes more complex than that, the MVC model starts to be a bit simple-minded and application logic starts showing-up in places other than where MVC says it “ought” to be. (Even given that the role, scope and bounds of “Controller” is already quite vague.) Therefore, understand how the MVC abstraction is put together, but consider it to be an abstraction of what any given application may in fact require.

Catalyst is a good framework. Dancer is another.

Replies are listed 'Best First'.
Re^2: Understanding Catalyst by QuillMeantTen (Friar) on Oct 03, 2015 at 16:22 UTC
In this application I did not use a database, I used cookies and the $c->session hash to manage everything, would it be more appropriate to put all the manipulations inside the Model instead of the controller?	[reply]
Re^3: Understanding Catalyst by locked_user sundialsvc4 (Abbot) on Oct 04, 2015 at 00:45 UTC
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.
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
Re^6: Understanding Catalyst by Your Mother (Archbishop) on Oct 05, 2015 at 11:32 UTC
Some notes below your chosen depth have not been shown here