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

java - Run a .jar on Heroku -

-
i trying run .jar file on heroku, , can't find instructions anywhere on how this. have read wants me compile uploading heroku. possible, , if is, how this? if helps, trying run minecraft craftbukkit server, , don't have pom.xml file yet. you didn't provide details i'll try give , people reaches question way it. first of all, create heroku account , create heroku application (assumed have done that). second, need generate application jar , upload heroku. so, open terminal , install heroku cli (assuming unix terminal): $ sudo npm install -g heroku-cli you need have npm , nodejs installed, can check link: https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-ubuntu-16-04 once done that, can use npm update node version acceptable heroku-cli: $ sudo npm install -g n $ sudo n 7.10.0 and run: $ sudo npm install -g heroku-cli in order deploy jars, need install deploy plugin: $ sudo heroku plugins:install heroku-cli-deploy ...
Read more

java - Jtable duplicate Rows -

-
Image
when add new rows in jtable duplicate rows many times this method update jtable public final void tableaucomande(){ ((defaulttablemodel)tabcommande.getmodel()).getdatavector().clear(); session s=hibernateutil.getsessionfactory().opensession(); criteria cr1= s.createcriteria(commande.class); list <commande> lcs=cr1.list() ; criteria cr2= s.createcriteria(lignecommande.class); list <lignecommande> lck=cr2.list() ; if(lcs.size()!=0 && lck.size()!=0) { (commande lc:lcs) { for(lignecommande lig:lck){ ((defaulttablemodel)tabcommande.getmodel()).addrow(new object[]{ lc.getid_cmd(),lc.getnumcmd(),lc.getdate_cmd(),lc.getclient().getnomprenom(), lig.getproduit().getlib_prd(),lig.getquantite(),lig.getproduit().getid_prd() }); } } // tabcommande.setrowselectioninterval(tabcommande.getrowcount()-1,tabcommande.getrowcount()-1); } } this code add add data rows displaye...
Read more

validation - How to pass paramaters like unix into windows batch file -

-
i need pass various parameters .cmd file unix format file.cmd -configuration=value -source=value -flag but, try this: startlocal @echo off cls setlocal set cmdline=%* set configuration= set source= set badargs= set validation= goto main :splitargs echo splitargs(%*) if "%*" neq "" ( /f "tokens=1,2,* delims== " %%i in ("%*") call :assignkeyvalue %%i %%j & call :splitargs %%k ) goto :eof :assignkeyvalue echo assignkeyvalue(%1, %2) if /i %1==-configuration ( set configuration=%2 ) else if /i %1==-source ( set source=%2 ) else ( rem append unrecognised [key,value] badargs echo unknown key %1 set badargs=%badargs%[%1, %2] ) goto :eof :validate echo validating set validation=fail if defined configuration ( echo -configuration ok if defined source ( echo -source ok if not defined badargs ( set validation=success ) ) ) goto :eof :main cl...
Read more