<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto">+1</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best,</div>
<div dir="auto">Marcel </div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> on behalf of Tony Garnock-Jones <tonyg@leastfixedpoint.com><br>
<b>Sent:</b> Friday, June 17, 2022 12:34:52 PM<br>
<b>To:</b> The general-purpose Squeak developers list <squeak-dev@lists.squeakfoundation.org><br>
<b>Subject:</b> [squeak-dev] Traits tooling: as simple as a one-line change to Browser?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi all,<br>
<br>
I've been using Traits (!).<br>
<br>
It's a lovely way to program.<br>
<br>
I needed to make a small change to Browser to reenable some <br>
apparently-previously-exposed functionality:<br>
<br>
addSpecialMenu: aMenu<br>
<classListMenu><br>
aMenu addList: #( ...<br>
<br>
I added `<classListMenu>` to Browser>>addSpecialMenu:, which otherwise <br>
was not mentioned anywhere, and then some new trait UI was available.<br>
<br>
Should we do this by default? If not, what needs doing before we can <br>
make trait tooling more accessible?<br>
<br>
Cheers,<br>
Tony<br>
<br>
</div>
</span></font></div>
</body>
</html>