Pills: A simple responsive CSS grid for humans

Post by YngwieMalware » Thu, Jun 02, 2016, 5:54 PM UTC

calinet6 wrote: post #47

have_faith wrote: post #39

The problem with all of these responsive grid systems is that they are opinionated about how a component responds. Responsiveness is not a document level problem, it's a component level problem and each component has it's own concerns. One component might keep the 2up grid from desktop to mobile, another might collapse to single column half way, and so on. Having generic desktop and mobile class names ala bootstrap d…

The problem with all of these responsive grid systems is that it's so easy to do a grid in plain CSS with flexbox and media queries that they're close to zero added value in almost all cases.

Post by nilliams » Thu, Jun 02, 2016, 6:48 PM UTC

jacobr wrote: post #70

nilliams wrote: post #63

Earlier quoted context omitted.

Flexbox doesn't work in IE. It also doesn't solve the need for conventions around grid breakpoints, when e.g. working in a team. Doesn't come close to replacing Bootstrap 3 (and similar) grid systems IMO.

You are incorrect, flexbox works in IE10 and up. Works fine in Edge without any prefixes even.

Post by Raphmedia » Thu, Jun 02, 2016, 7:57 PM UTC

plq wrote: post #35

Please explain to me: What happened to the philosophy behind http://csszengarden.com ? Back when CSS needed evangelizing, the main selling point was "never touch the DOM for styling". What went wrong?

Post by mikewhy » Thu, Jun 02, 2016, 8:53 PM UTC

have_faith wrote: post #66

JustSomeNobody wrote: post #43

Earlier quoted context omitted.

> Components are very dumb right now, we need smart components that understand their surroundings beyond the window. Then we will have truly portable components! This is the iceberg problem. Component based programming has been around since probably the 60's. The easy part is making components. The hard part is making them (and this is the Holy Grail), portable. Pipes and Filters in the Unix OS is a simple example of…

This is what I feel is missing from web components. Some sort of generic api for components to reason about their immediate environment. Similar to the Unix OS pipes and filter api that means every program understands how to get some information about the context that it is being run in. It's not difficult to imagine a calendar component that needs to visually display vastly differently depending on how much space it…

Post by donatj » Thu, Jun 02, 2016, 9:54 PM UTC

    .content {
        @include box-size(3/4);
    }

    .sidebar {
        @include box-size(1/4);
    }