- Mark Dalgleish - Angular Delegator
- Casey Butler - Life as a Angular noob
macro (->) { | |
rule infix { $assign:expr = ($arg (,) ...) | {$body ...} } => { | |
function($arg (,) ...) { | |
$body ... | |
} | |
} | |
rule infix { $assign:expr = ($arg (,) ...) | $value:expr } => { | |
function($arg (,) ...) { | |
return $value; | |
} |
- Alex B - How Ebay use Angular
- Rob Kerr - Breaking apart words & web services
(if there's time)
<link rel="import" href="https://raw.githubusercontent.com/geelen/x-gif/gh-pages/dist/x-gif.html"> |
It feels like I'm facing the same thing the same problems writing the API of these components. In particular:
- A component might have several distinct modes. As in, an
<x-gif speed="1.0">
has a very different playback mode from<x-gif bpm="120">
, so you shouldn't be allowed to have bothspeed
andbpm
. But it doesn't seem right to break them into separate components, so either one takes precedence or having both present causes an explosion. - A component might require more than one attribute to be valid. As in,
. Until you have both the `channel` and `note` you can't make connection to the midi signal. But if you're driving the component with a framework like angular, it will first render incompletely (as
), then after a$digest
will insert the right values. So a component may need to permit being in an invalid state temporarily, then when all attributes are set go and get
After the previous attempt and raising an issue, I am trying to install again with a fresh rootfs as described here
First attempt failed with missing dependencies, so I reran a command from last time:
sudo apt-get install build-essential autoconf automake autopoint libtool intltool bison flex libgnutls28-dev libxml2-dev libsqlite3-dev
Stuck on installing Weston — it's missing a dependency on libinput
which I can't find in the repo and the build instructions for Weston reference as needing to be built from source. Seems like this should be part of the dependency tree for Webkit, then?
The idea is to combine the best bit of global styling (reuse, small payload) and local styling (total isolation, first-class React syntax)
This is combined with the concept of traits: you can think of them as permitted property/value pairs. Instead of every component being able to have every CSS property available to it, you can reduce your permitted set to X font families, Y font-size + line-height pairs, Z foreground/background colour pairs, W padding amounts. This is based off my work using amcss on real projects — traits were the single key feature that kept me using AM.
The one-sentence explanation: A site defines a set of permitted visual features, all components are simply a combination of those features
/* equivalent to postcss-local-scope. INPUT: */ | |
.outer { | |
color: papayawhip; | |
box-shadow: 0 0 10px; | |
} | |
/* OUTPUT: */ | |
@export .outer ".outer-abcs12r3adudas"; |