syntax - LESS namespaces: "#namespace > .mixin()" vs. ".namespace.mixin()" -

-

all less documentation , tutorials use #namespace > .mixin() syntax when takes namespaces. find myself more comfortable .namespace.mixin() syntax, i.e.:

.namespace() {     .mixin() {         foo: bar;     } }  #usage {.namespace.mixin()}

am missing something? there difference between these 2 variants (in partucular, way mixins/variables affect scope , vice versa)? or kind of historically rooted tradition?

you're right, ".namespace > .mixin", ".namespace.mixin" , ".namespace .mixin" different beasts when used selectors. things seem dissimilar when goes mixin invoke/expansion. cannot craft example where:

"#usage {#namespace > .mixing}" "#usage {#namespace.mixing}" "#usage {#namespace .mixing}"

etc. produce non equal output, assuming .mixin defined parametric ruleset. same ".namespace". e.g.:

/* */ #namespace {     .mixin1() {         foo1: bar;         .mixin1() {             foo2: bar;         }     }      .someruleset {         foo3: bar;         .mixin1 {             foo4: bar;         }     } }  /* 1 */ #u1 {#namespace > .mixin1()} /* 2 */ #u2 {#namespace .mixin1()} /* 3 */ #u3 {#namespace.mixin1} /* 4 */ #u4 {#namespace .mixin1} /* 5 */ #u5 {#namespace.mixin1.mixin1()} /* 6 */ #u6 {#namespace.someruleset.mixin1()}  /* b */ .namespace {     .mixin1() {         foo1: bar;         .mixin1() {             foo2: bar;         }     }      .someruleset {         foo3: bar;         .mixin1 {             foo4: bar;         }     } }  /* 1 */ #u1 {.namespace > .mixin1()} /* 2 */ #u2 {.namespace .mixin1()} /* 3 */ #u3 {.namespace.mixin1} /* 4 */ #u4 {.namespace .mixin1} /* 5 */ #u5 {#namespace.mixin1.mixin1()} /* 6 */ #u6 {#namespace.someruleset.mixin1()}

all 1-6 results seems equal.

i don't know if it's intended less behaviour, "language dark corners" or ... here's why prefer use ".namespace.mixin()" syntax , not "#namespace > .mixin()" (if understand correctly , if way works intended behaviour - assuming "less.js 1.4.x"): strictly speaking, there's no such things "namespace" or "mixin" in less, no more "logical abstractions". there're rulesets can parametric , non-parametric. ruleset can serve namespace, mixin or both depending on way define , invoke it.

so original question two:

  1. use of ">" (this main concern): if it's redundand when invoking/"calling" mixin (unlike ">" in selectors) - drop it.
  2. "#" vs. ".": if nested "mixin" can serve namespace (and that's possible if it's defined "dot ruleset") why want declare top-level namespace "#"? in other words, if can use ".ruleset1.ruleset2.ruleset3.ruleset4.etc()" can't "#ruleset1 > #ruleset2 >. etc()" why use latter syntax two-level expansion? (except cases when need mixin inside of id selector).

while writing above, thought better correct original example adding empty parens ".namespace" definition stress fact it's explicitly invokable entity , not selector in way.

.namespace.mixin refers element both classes while .namespace .mixin find .mixins in .namespace, or typo?


Comments

Post a Comment

Popular posts from this blog

ruby on rails - Is it the correct way to implement belongs_to relation with factory girl? -

-
i have realy easy model. user have role_id depends of role table (id, name) role reference. i want create users of types on rspec test, factory girl. my first idea factory :role name "guest" factory :role_admin name "admin" end factory :role_supervisor name "supervisor" end etc... have lot different roles end factory :user email password '123456' password_confirmation '123456' association :role, factory: :role factory :admin association :role, factory: :role_admin end factory :supervisor association :role, factory: :role_supervisor end etc... have lot different roles end in model have simple method : def is(role_name) return self.role.name == role_name end it's correct way to? realy need create factory role? can make stub function in factory girl each role? i realy new test stuff, thanks. factories should reflect models. class user has_many :products en
Read more

geolocation - Windows Phone 8 - Keeping background location tracking active beyond four hours -

-
i'm in process of developing wp8 app makes use of background location tracking abilities provided os. idea monitor users position , notify them when near types of places. so far seems work fine , when running location tracking works expect. the problem is, seems phone times out background apps after around 4 hours, stopping location tracking. i can understand why microsoft did it, preserve battery life etc. there's not point having background location tracking app has manually restarted every 4 hours! if user chooses run app , made aware of potential battery hit, surely should able run indefinitely - point of course, if system runs out of resources or similar that's fair enough. does have experience this? there must hundreds of others apps in store have run issue have thought? , presumably there must way of keeping location tracking running? i've tried periodically updating live tile (using dispatchertimer) while tracking running doesn't seem enough ke
Read more

Uncaught TypeError: Cannot read property 'parentNode' of null javascript -

-
this code should make element disappear list when dropped on element (called cookiemonster) addevent(cookiemonster, 'drop', function (e) { if (e.stoppropagation) e.stoppropagation(); var el = document.getelementbyid(e.datatransfer.getdata('text')); el.parentnode.removechild(el); return false; }); create auxiliar variable this addevent(cookiemonster, 'drop', function (e) { if (e.stoppropagation) e.stoppropagation(); var el = document.getelementbyid(e.datatransfer.getdata('text')); var aux = el.parentnode; aux.removechild(el); return false; });
Read more