Juergen

> What are your plans? Well, it's still that “one type to rule them all, one click to find them, to crop, resize, align them, to parallax and focuspoint, to...

Thinking process initialized … UPDATED LIST: #### Section Dimensions ○ default (defined by context) ○ custom width [      ] ( dropdown, opts: % of parent width ** | px | rem...

> If the image is scaled from Full HD to 300px, resizing might be very useful. > UPD: > This might be the rule for TS, not just for the...

maybe Image Size ○ use as background of the current wrapper section but this only makes sense with certain settings. e.g. 'cover' and/or 'parallax'

and of course Section Display ○ default (block/flex, defined by context) ○ inline the latter is ideal if you e.g. want to build a row of logos with different aspect...

> … gallery might become after the similar tuning Gallery will definitely continue to use gd thumbs but its css needs to be 'flexboxed'. Will spare us some 20 KB...

> UPD > Or, will the assets be loaded depending on the selected features? Runtime JS footprint for parallax and focuspoint is neglible, alltogether ~7 KB (minified)

> Do you mean, I inserted a section of one type, and after changing the option it can become a section of another type? If it was a Responsive Image...

> From then you can switch/mix the behavior on the fly. The problem is not mixing the functionality. It's the editor UI that must communicate meaningful combinations. Basically there is...

I remember when I initially made Parallax Image, folks asked why they cannot set more parameters. My answer then was: Trust me, you do not want to :)