> On 11 Feb 2019, at 09:20, Nicolas Cellier > <[email protected]> wrote: > > > > Le lun. 11 févr. 2019 à 08:45, Norbert Hartl <[email protected] > <mailto:[email protected]>> a écrit : > > > > Am 11.02.2019 um 08:00 schrieb [email protected] > > <mailto:[email protected]>: > > > > Hello! > > > > This is my weekly ChangeLog, from 4 February 2019 to 10 February 2019. > > You can see it in a better format by going here: > > http://log.smallworks.eu/web/search?from=4/2/2019&to=10/2/2019 > > <http://log.smallworks.eu/web/search?from=4/2/2019&to=10/2/2019> > > > > ChangeLog > > ========= > > > > 9 February 2019: > > ---------------- > > > > * === On layouts > > As you know, I've been working on layouts for Spec 2. The basic > > layouts I want to have available next week(s) are four: > > > > * +SpecBoxLayout+ : A simple way to place components horizontally or > > vertically > > * +SpecPanedLayout+ : Same as box layout, but with a resizable splitter > > (and it will allow just two... if you want more you will need to compose). > > * +SpecGridLayout+ : To place components in a grid (x,y coordinates and > > spans) > > * +SpecXYLayout+ : This could be renamed as +SpecAbsoluteLayout+ and > > it's name says all, it will allow absolute location of components > > (obviously, in relation with its parent). > > > > For a second phase there will be a couple more +SpecFlowLayout+ and a > > kasowari layout (without name yet :P). > > > Apple and others call it auto layout. I don‘t like that name as it isn‘t > really clear. It could be called ConstraintLayout. > > +1 for ConstraintLayout
Ok, Constraint will be :) (But it will not arrive until half part of P8 development :P) Esteban > > Norbert > > The ones on first phase are the most important ones. In particular, we > > have detected that with > > first three (Box, Paned, Grid) we can reproduce everything we have > > currently in Pharo. The second phase > > will add possibilities for the future. > > > > Anyway, I have "kind-of-working" the first three, but I have problems > > when applying layouts here and there, because > > morphic time to time wants to behave differently than asked. > > > > One of the problems is that for this layouts, to make them behave > > correctly (and without a lot of work from users), > > I will need to add the concept of "minimum, preferred and maximum" > > extent. Reason why I'm playing with a small > > implementation of styling... which most probably will go away once I > > find the best way to handle this constraints. > > > > So, this week I have nothing finished, just a pointer to my current > > work: > > [https://github.com/estebanlm/Spec/tree/dev-2.0](https://github.com/estebanlm/Spec/tree/dev-2.0) > > > > <https://github.com/estebanlm/Spec/tree/dev-2.0%5D(https://github.com/estebanlm/Spec/tree/dev-2.0)> > > > > > > 7 February 2019: > > ---------------- > > > > * Small fix-a-day: > > [https://github.com/pharo-project/pharo/pull/2452](https://github.com/pharo-project/pharo/pull/2452) > > > > <https://github.com/pharo-project/pharo/pull/2452%5D(https://github.com/pharo-project/pharo/pull/2452)> > > > > > > cheers! > > Esteban > >
