Advertisement
Guest User

Untitled

a guest
Apr 17th, 2013
37
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.96 KB | None | 0 0
  1. <terryapodaca> so in general, site specific can use Requirements:: and that's perfectly fine.
  2. <FrozenFire> In my opinion, no.
  3. <FrozenFire> Your presentation should be completely decoupled from your controller.
  4. <FrozenFire> When you want to change the design of your site, you're going to have to rewrite half of your code.
  5. <FrozenFire> These guys are suggesting making the theme completely dependent upon the project code.
  6. <FrozenFire> So whenever you want to add some styles to a template, you have to modify the project code.
  7. <FrozenFire> That's utterly ridiculous, and would be laughed at by just about every experienced developer not in the SS community.
  8. <FrozenFire> Your controller should make zero considerations about the type of content it's outputting.
  9. <FrozenFire> It should render the type of view, and return that
  10. <FrozenFire> The view should define its presentational dependencies
  11. <FrozenFire> Requirements is part of the view - it's a presentational helper.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement