so we're using this for co-ordinating nodeschools all over
so I reckon it'll work nice for this international gang
but it's as useful as the good peeps who idle in it
so don't be afraid drop a note whenever your thinking velocity things
etc
message ends
must sleep now
will poke the PR button tomorrow.
I've got a preliminary comparison of CSS isolation techniques begun: http://css-isolation.meteor.com/
At this point, I can't see how to recommend the webcomponents method. Anything we do to isolate the CSS will require separate LESS processing. Pre-compiling the LESS to CSS in the package seems like the best option to me.
See the demos: http://css-isolation.meteor.com/
Thinking I'll see about making an X-tag meteor package to automatically turn a template into a WebComponent
awesome
i'm probably missing something obvious, but why does the LESS have to be compiled separately?
just merging in the changing from
devel
there's more to be done, but it's useable, and I could use some help & sleep.
the transition rocks
maybe add some more padding on the bottom. This is scrolled all the way down: http://i.imgur.com/JHpEe7X.png
The 4 fail in the red box and the 4 failed tests below is kind of redundant: http://i.imgur.com/q9o2agX.png
We will not have to compile less separately
Should be quite seamless changeover
good work!
active class is a known issue, will take a look when I get some time.
The redundancy is deliberate, I wanted a graphic / icon representation and a plain english representation for maximum accessibility / quick parsing for tired brains.