The Anandtech AMD Radeon R9 R290X Review
anandtech.com1 pointsby ssafejava0 comments
.widget
$padding: 3px
$activeColor: $color1
$inactiveColor: $color2
padding: $padding
/* ... etc. */
.subWidget
$padding: 6px
.subWidget2
$inactiveColor: $color3
/* ... and so on */
With preprocessors, this doesn't work - you're better off defining a mixin that you feed variables into, which isn't the most intuitive approach. I hope this is adopted quickly by the major browser vendors. Unfortunately, writing your styles in this way will completely break in browsers that don't support it, in the absence of some sort of polyfilling JS or build tool. var MyRouter = Backbone.ExtendedRouter.extend({
routeEvents: {
'var1' : {'change' : onChange},
'var2' : {'change add remove' : onVar2Event},
'' : {'all': onRoute}
},
// ...
});
And so on. App.Router.setState(publicState, privateState, triggerOptions)
App.Router.replaceState(publicState, privateState, triggerOptions)
App.Router.addState(publicState, privateState, triggerOptions)
That way, we can trigger routes exactly when we want them (with or without an actual url change), store private state using the History API, and support microstates. The best part (IMO) is that different routers can listen to separate parts of the url, allowing a URL change to trigger multiple routes on completely separate routers. This would go a long way toward true separation of concerns in larger apps. Have you ever kissed a girl?
- Bryan
is incredibly tasteless.