Breaking changes

[ImJimmi]

@mjokipii

because it doesn’t comply with some web standard - which it has nothing to do with

Flex-box is a web concept though, that’s where it came from. The intention was always for juce::FlexBox to copy the CSS flex-box. @jules made a lot of comments about grid and flex-box around the time it was added to the web, and just before it was added in JUCE, for example:

@jules

(However, I am interested in the new HTML flexbox stuff - that seems like it might be worth copying now that a lot of smart people seem to have finally agreed on it being the best way to structure box-style layouts)

I totally understand that it’s frustrating for something to have changed to ‘fix’ something that’s not risk, but changes like this put the framework in a better place for the future.

For the record, I asked for these changes to be made here:

BR: FlexBox::AlignItems not behaving as expected

Using the following CSS, I can get the pictures result: #main { width: 200px; height: 200px; border: 1px solid black; display: flex; align-items: flex-end; } #main div { width:50px; height:50px; } [Screenshot 2021-10-20 at 21.48.58] However, doing the equivalent in JUCE, doesn’t give the expected result: juce::FlexBox flex; flex.alignItems = juce::FlexBox::AlignItems::flexEnd; flex.items = { juce::FlexItem{ b1 }.withWidth(50.f).withH…

I wanted the correct behaviour because I’ve been writing a module that simplifies UI development and discovered these issues when I was comparing CSS layouts to the equivalent JUCE ones.