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

Tony Garnock-Jones tonyg at leastfixedpoint.com
Fri Jun 17 14:35:09 UTC 2022


OK, I think that makes two in favour. Any against?

Presumably I should wait until after the release to do it... or????

Cheers,
   Tony


On 6/17/22 13:13, Taeumel, Marcel wrote:
> +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
> 
> 
> 


More information about the Squeak-dev mailing list