[squeak-dev] Traits tooling: as simple as a one-line change to Browser?

Taeumel, Marcel Marcel.Taeumel at hpi.de
Fri Jun 17 11:13:47 UTC 2022


+1

Best,
Marcel
________________________________
From: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> on behalf of Tony Garnock-Jones <tonyg at leastfixedpoint.com>
Sent: Friday, June 17, 2022 12:34:52 PM
To: The general-purpose Squeak developers list <squeak-dev at lists.squeakfoundation.org>
Subject: [squeak-dev] Traits tooling: as simple as a one-line change to Browser?

Hi all,

I've been using Traits (!).

It's a lovely way to program.

I needed to make a small change to Browser to reenable some
apparently-previously-exposed functionality:

        addSpecialMenu: aMenu
                <classListMenu>
                aMenu addList: #( ...

I added `<classListMenu>` to Browser>>addSpecialMenu:, which otherwise
was not mentioned anywhere, and then some new trait UI was available.

Should we do this by default? If not, what needs doing before we can
make trait tooling more accessible?

Cheers,
   Tony

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220617/172331b8/attachment.html>


More information about the Squeak-dev mailing list