Mixins may contain state, (traditional) traits don’t. Mixins use “implicit conflict resolution”, traits use “explicit conflict resolution” Mixins depends on linearization, traits are flattened. Lecture about traits ad 1. In mixins you can define instance variables. Traits do not allow this. The state must be provided by the composing class (=class using the traits) ad … Read more
So that [some code] makes the myMixin methods available within myModule by just calling mixinMethod1() and have correct scope That’s impossible. You cannot modify a scope by calling a function, especially not from outside. See also Is it possible to import variables in JavaScript? for the design reasons of that. So, what can you do? … Read more
New Answer (requires LESS 1.4.0) What you actually desire is something known as extending in LESS and SASS terminology. For example, you want an HTML element (just an example)… <div class=”myclass”></div> …to fully behave as if it had a span3 class from bootstrap added to it, but without actually adding that class in the HTML. … Read more
A mixin is typically used with multiple inheritance. So, in that sense, there’s “no difference”. The detail is that a mixin is rarely useful as a standalone object. For example, say you have a mixin named “ColorAndDimension”, which adds a color property and width and height. Now, you could add ColorAndDimension to a, say, Shape … Read more
Variable interpolation in @mixins does not appear to be supported currently. The SASS documentation calls this #{} interpolation and describes it like this: Interpolation: #{} You can also use SassScript variables in selectors and property names using #{} interpolation syntax: $name: foo; $attr: border; p.#{$name} { #{$attr}-color: blue; } Per the documentation, interpolation of variable … Read more
If you want to use variables as property names you need to use string interpolation – #{$var}. So this should work: [class*=”shift”] { $sft-o: 10px; @mixin shift_stp($val) { &[class*=”_sml”]{ #{$val}: $sft-o; } &[class*=”_mid”]{ #{$val}: $sft-o * 2; } &[class*=”_big”]{ #{$val}: $sft-o * 3; } } &[class*=”_m”]{ @include shift_stp(margin); } &[class*=”_p”]{ @include shift_stp(padding); } } DEMO … Read more
A mixin is just a different conceptual idea, of how to organize code and inheritance. You can of course combine it with using classical or prototypal inheritance, but it also works stand-alone, so to speak. For instance, instead of creating “delegated” object properties/lookups (like prototypal inheritance), we would truly “form” new stand-alone objects, from multiple … Read more
I just read about this topic in The Well-Grounded Rubyist (great book, by the way). The author does a better job of explaining than I would so I’ll quote him: No single rule or formula always results in the right design. But it’s useful to keep a couple of considerations in mind when you’re making … Read more
Starting from SASS 3.1 you can pass named arguments to do that: @include linear-gradient($from: #7a7a7a, $to: #1a1a1a, $ie-filters: true); The rest will be default.
You could use CGLIB for that. The class Mixin is able to generate a dynamic class from several interfaces / object delegates: static Mixin create(java.lang.Class[] interfaces, java.lang.Object[] delegates) static Mixin create(java.lang.Object[] delegates) static Mixin createBean(java.lang.Object[] beans)