| // flow-typed signature: ba132c96664f1a05288f3eb2272a3c35 | |
| // flow-typed version: c4bbd91cfc/redux_v3.x.x/flow_>=v0.33.x | |
| declare module 'redux' { | |
| /* | |
| S = State | |
| A = Action |
| // flow-typed signature: ba132c96664f1a05288f3eb2272a3c35 | |
| // flow-typed version: c4bbd91cfc/redux_v3.x.x/flow_>=v0.33.x | |
| declare module 'redux' { | |
| /* | |
| S = State | |
| A = Action |
Picking the right architecture = Picking the right battles + Managing trade-offs
When I heard about Brad Frost's Patternlab for the first time at beyond tellerrand I was intrigued. The idea of splitting your design work for a website into simple modules or patterns isn't new and starts to become more and more of a standard. But organizing this into a very visual styleguide/patternlab seemed to make so much sense. Brad also introduced a very interesting approach with his separation of modules into categories, such as atoms, molecules and organisms.
I started porting Brad's patternlab app to Kirby, but it never really made it to something polished and it turned out for me after using it for Kirby's panel UI, that it's actually a pain in the ass to maintain such a pattern collection.
The problem with such a styleguide or patternlab is that it exists next to the real thing. When you change something in your code base you also have to update the particular code for the pattern in patternlab. To be honest I went very quickly from being
| const I = x => x | |
| const K = x => y => x | |
| const A = f => x => f (x) | |
| const T = x => f => f (x) | |
| const W = f => x => f (x) (x) | |
| const C = f => y => x => f (x) (y) | |
| const B = f => g => x => f (g (x)) | |
| const S = f => g => x => f (x) (g (x)) | |
| const S_ = f => g => x => f (g (x)) (x) | |
| const S2 = f => g => h => x => f (g (x)) (h (x)) |
If you disable mobile access on Android, you can still use an unprepared offline network. If you have mobile networks enabled and connect to a not prepared offline network, the smartphone will fall back to mobile wifi. Sometimes, there is a message, that gives you some chance to use it, but the Samsung phone I had for test purposes denied to work with LibraryBox (which is not prepared yet).
iOS5 or iOS6 introduced a call-home function, that checks for the internet. If it does not receive a specific answer (see below), it opens up a lightweight browser, where you usually can login in hotels (the captive portal). If you don't solve the connection issue with logging in, I think < iOS9 does not fall back to mobile network. I read, that iOS9 will partialle use mobile internet, when the wifi connection is bad. As vague this statement is, so low my knowledge is. Fact is, my prepared PirateBox does not bring my iOS9 iPhone back into mobile n
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| Fluxxor | |
| Tuxedo | |
| nexus-flux | |
| Marty | |
| Reflux | |
| Fluxy |