<div dir="ltr">It's also hard for a user to find all preferences if every tiny widget have one. <div><br></div><div>Karl<br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 3, 2015 at 8:48 AM, Marcel Taeumel <span dir="ltr"><<a href="mailto:marcel.taeumel@student.hpi.uni-potsdam.de" target="_blank">marcel.taeumel@student.hpi.uni-potsdam.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">...but if we want to let Morphs access those preferences, we probably still<br>
need such a class-side abstraction in Morphs. Otherwise Morphic would be<br>
dependent on Tools, which should not be.<br>
<br>
Such preference access happens in Morphs in many places right now. Even<br>
outside initialization code, which is not good because a single morph cannot<br>
behave differently to the system's preferences easily.<br>
<br>
Best,<br>
Marcel<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://forum.world.st/The-Trunk-Morphic-kfr-958-mcz-tp4823778p4823904.html" target="_blank">http://forum.world.st/The-Trunk-Morphic-kfr-958-mcz-tp4823778p4823904.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the Squeak - Dev mailing list archive at Nabble.com.<br>
<br>
</div></div></blockquote></div><br></div>