(06-03-2015, 12:40 AM)RogerMore Wrote: Ok, so it's better to load the news model and news library from my page controller.
Then model retrieves the data and I give it to the library to process it into data for a view?
In most cases this is true. You generally want each class to be as simple as possible, especially since this often makes them more reusable.
For a simplified example, I could build a library which calls my model to retrieve some data, then creates a select element (drop-down), using one column for the values and another for the content/displayed value. However, this would tie the library to the model (and possibly even to the columns), and the library would know far more about the data than is really necessary for this functionality.
If I instead built my library to expect the data and column names to be supplied as needed, the library could be used to transform any dataset into a select element. If the library contains a series of methods for performing transformations on data, you may decide that the data to be transformed should be passed to the constructor, while any additional information required for the transforms (like the column names for the drop-down) could be passed to the methods.
Of course, this example is simple enough that much of the required functionality is built into many base models, but I hope it helps to illustrate the point.
