<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
In general, I like having SystemNavigation to navigate code objects.<div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 05.07.2019 00:50:11 schrieb tim Rowledge <tim@rowledge.org>:</p><div style="font-family:Arial,Helvetica,sans-serif"><br><br>> On 2019-07-04, at 3:43 PM, Eliot Miranda <eliot.miranda@gmail.com> wrote:<br>> <br>> Hi Marcel,<br>> <br>> On Jul 4, 2019, at 2:24 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br>> <br>>> Hi, there.<br>>> <br>>> I just got really confused by the differences of<br>>> <br>>> [SystemNavigation allCallsOn: #drawOn:] bench.<br>>> <br>>> and<br>>> <br>>> [SystemNavigation default allCallsOn: #drawOn:] bench.<br>>> <br>>> because I expected that MNU fallback to kick in to insert "default" automatically.<br>>> <br>>> However, #allCallsOn: is actually implemented in Behavior and not just in SystemNavigation.<br>>> <br>>> Can we remove SystemNavigation class >> #doesNotUnderstand: so nobody starts relying on that?<br>> <br>> Tangentally, my feeling, and I know it was Andreas’ feeling too, is that all of<br>> <br>> SystemNavigation default ...<br>> SystemNavigation ...<br>> self systemNavigation ...<br>> <br>> are a real mouthful. Any abbreviation would be appreciated. “Smalltalk ...” was much nicer and arguably more comprehensible.<br><br>Mine too. I really don't understand the splitting up into near-incomprehensible boxes. So I'd say "can we remove SystemNavigation" or at least "can we provide Smalltalk>>allCalsOn: even if it just delegates"<br><br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>Useful Latin Phrases:- Quo signo nata es? = What's your sign?<br><br><br><br></marcel.taeumel@hpi.de></eliot.miranda@gmail.com></div></blockquote>
</div></body>