Timeline for Best practice for generating jQuery dynamical content
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2014 at 9:38 | vote | accept | DanielTheRocketMan | ||
| Feb 19, 2014 at 9:24 | comment | added | Fge | Don't worry about this "transfering", this won't impose any performance problems as PHP optimizes this on it's own. Furthermore don't let your architecture be driven by premature optimization. You can optimize later on if this really turns out to be a bottleneck (which I highly doubt it will ever be). The author of the post is right. And in my opinion what you use is a model is a mixture of a model, repository and mapper (violating the single responsibility principle of course). On the View accessing model discussion: I don't like the view depending on the model. ViewModels come to mind here. | |
| Feb 19, 2014 at 2:05 | comment | added | DanielTheRocketMan | Thank you for your answer. I expected this kind of answer. The point is that as you assume the data may have lots of results and I would have to transfer this to the view. On other hand, I also was influenced by stackoverflow.com/questions/13813046/…. What do you think about this? Thank you for the other suggestions, but most of them are related to CodeIgniter style: "Welcome", "MSearchModel". In fact, this is just a part of a large application and there are several "search" situations. | |
| Feb 18, 2014 at 23:36 | history | answered | Fge | CC BY-SA 3.0 |