Hi, there.
I use traits to describe the expected view interface in Vivide (github.com/hpi-swa/vivide): https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag...
There are other traits in Vivide to make protocols explicit: https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag... https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag... https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag... https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag... https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag... https://github.com/hpi-swa/vivide/tree/master-squot/repository/Vivide.packag...
Best, Marcel Am 31.03.2019 04:54:26 schrieb David T. Lewis lewis@mail.msen.com: Changing the subject line to focus on Levente's question.
On Thu, Mar 28, 2019 at 06:43:11PM +0100, Levente Uzonyi wrote:
What are the current use cases for traits?
In order to experiment with Git based repositories, I have loaded the Tonel package from the github repositories of Jakob Reschke.
Installer ensureRecentMetacello. (Smalltalk classNamed: #Metacello) new repository: 'github://j4yk/tonel:squeak'; baseline: 'Tonel'; load.
This brings in the FS-AnsiStreams package, which uses traits.
Having traits in Squeak allows me to load this package.
Dave