[Pharo-dev] Layout for placing widgets

Pavel Krivanek pavel.krivanek at gmail.com
Sat Oct 28 16:29:15 EDT 2017


Hi Thierry,

your repository mentions the MIT license but the original license of the
Cassowary package was LGPL. Is is a different code?

Cheers,
-- Pavel

2017-10-28 21:43 GMT+02:00 Thierry Goubier <thierry.goubier at gmail.com>:

> Le 28/10/2017 à 16:26, Stephane Ducasse a écrit :
>
>> I was reading ...
>> I will see if I can load cassowary in Pharo.
>>
>
> https://github.com/ThierryGoubier/Cassowary
>
> Done two years ago.
>
> Thierry
>
>
>
>> On Sat, Oct 28, 2017 at 4:21 PM, Stephane Ducasse
>> <stepharo.self at gmail.com> wrote:
>>
>>> Ok then may be we should give a try to use. Tx for the links.
>>>
>>> Stef
>>>
>>> On Sat, Oct 28, 2017 at 4:18 PM, Ben Coman <btc at openinworld.com> wrote:
>>>
>>>> 2017-10-27 19:13 GMT+02:00 Stephane Ducasse <stepharo.self at gmail.com>:
>>>>>
>>>>>>
>>>>>> I was wondering if there is a layout that we can use to propose
>>>>>> alternate placing layout for widgets in spec?
>>>>>>
>>>>>> Like...
>>>>>> attached to  the left 10pixels rubber band box or fixed size box
>>>>>> 10pixels attached to the right.
>>>>>>
>>>>>
>>>>
>>>> On Oct 27, 2017, at 12:59 PM, Pavel Krivanek <pavel.krivanek at gmail.com>
>>>>> wrote:
>>>>>
>>>>> Maybe we should check cassowary
>>>>>
>>>>> https://croisant.net/blog/2016-02-24-ui-layout-constraints-
>>>>> part-1/#ui-constraints
>>>>>
>>>>
>>>>
>>>> On Sat, Oct 28, 2017 at 4:48 PM, Stephane Ducasse <
>>>> stepharo.self at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Pavel I do not think that cassowary is good for us.
>>>>>
>>>>
>>>>
>>>> Do you mean Cassowary in particular, or constraint based UI in general?
>>>>
>>>> My naive first impression is, if Cassowary is good enough for Apple...
>>>> https://news.ycombinator.com/item?id=9846992
>>>> https://www.quora.com/Should-I-use-Auto-Layout
>>>>
>>>> and Google (search here for "solver")...
>>>> https://academy.realm.io/posts/cool-constraintlayout-droidco
>>>> n-boston-2017/
>>>>
>>>> such that "in 2016, both iOS and Android have first-party layout systems
>>>> based on Cassowary."
>>>> https://www.bignerdranch.com/blog/constraintlayout-vs-auto-l
>>>> ayout-how-do-they-compare/
>>>>
>>>> then it seems worth some analysis, and discussion of better
>>>> alternatives.
>>>>
>>>>
>>>> Coincidentally, I see a Smalltalk implementation is available...
>>>> http://www.squeaksource.com/Cassowary.html
>>>> https://constraints.cs.washington.edu/solvers/cassowary-tochi.pdf
>>>>
>>>>
>>>> For balance, some points against AutoLayout, but some alternatives also
>>>> seem
>>>> to use Cassowary solver...
>>>> https://www.reddit.com/r/iOSProgramming/comments/4t6kd5/why_
>>>> i_dont_use_autolayout/
>>>> https://www.bignerdranch.com/blog/constraintlayout-vs-auto-l
>>>> ayout-how-do-they-compare/
>>>> https://makeapppie.com/2015/10/28/why-stack-views-are-your-
>>>> best-friend-if-you-hate-auto-layout/
>>>> https://cocoacasts.com/working-with-stack-views/
>>>>
>>>>
>>>> cheers -ben
>>>>
>>>>
>>>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171028/39ccba97/attachment-0002.html>


More information about the Pharo-dev mailing list