Re: [Plone Mosaic Sprint Barcelona discussion] Re: Plone Mosaic Sprint Barcelona June 10 - 13
Guido Stevens <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Organization | Cosent -:- social knowledge technology |
| Message-ID | <[email protected]> |
On 15/05/14 16:24, Asko Soukka wrote:
> Hi Guido,
>
> thanks for the inspiring details.
>
> Guido Stevens wrote:
>> That can only work if we have a smart page composition controller who
>> does the rendering and decides which tile should render left, right,
>> middle; and how large; and how the responsive reflow should work. = who
>
> So this "smart controller" should be more than just a customizable grid
> with assigned tiles? E.g. an add-on tile could request a "large centrish
> slot somewhere above the body text" and controlled would find a proper
> slot from the grid? Can you give an example story how would it work?
>
> With "responsive reflow", do you mean just good and responsive HTML +
> CSS, or something more magical?
The core problem in managing a responsive grid is that you cannot just
naively assign a tile to a specific grid cell, without considering how
the grid should morph along css breakpoints. I'm using Bootstrap3 as a
reference, and any specific css defined layout there results in four
different visual results: desktop, tablet landscape, tablet portrait and
smartphone.
So, at base I do mean just plain ol' responsive HTML/CSS at the actual
rendering implementation. But I think configuration at that level does
not really make sense. If you take the gridlets prototype as a
reference, that would mean you'd need to train your layout editors to
define four media variants for each layout. And then it wouldn't be
responsive anymore, you'd have four different css structures instead of
a single smart one that uses responsive reflow ("col-lg-4 col-md-6
hidden-sm" etc).
Rather I envision some abstraction layer (the "smart controller") that
turns policy statements like "foo would like to be rendered big in the
middle, top priority" and "bar should be small, can go anywhere, has
medium priority, but has a light preference for the right edge of the
screen" and is then able to reason across the complete set of these tile
policies and choose an optimal solution that renders acceptably across
the four device breakpoints.
Yes I'm crazy, I know ;-)
>> I hope that's enough to turn your "95%" into a "100%"? ;-)
>
> The 5% is about me to organize my work here and book the trip :)
Of course, I was teasing you... Look forward to collaborate on this in
Barcelona.
:*CU#
--
Guido Stevens | +31.43.3618933 | http://cosent.nl
s o c i a l k n o w l e d g e t e c h n o l o g y
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs