<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Tim,<div><br></div><div>that's a good idea. Yet, such a mechanism would be decoupled from the automatic styling pluggable text morphs can provide.</div><div><br></div><div>Best,</div><div>Marcel</div><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 06.08.2019 20:45:48 schrieb tim Rowledge <tim@rowledge.org>:</p><div style="font-family:Arial,Helvetica,sans-serif">Assuming we're still talking about styling in the Workspaces, I'd like to suggest investigating having a Shout style that you can apply to any text within a workspace; then plain old notes can be left alone, code can be selected and marked as 'shoutable'. If that can be done, then one might imagine that style simply being the default style in code related text views.<br><br>> On 2019-08-06, at 11:39 AM, Levente Uzonyi <leves@caesar.elte.hu> wrote:<br>> <br>> Wouldn't it be better if there were only a single method:<br>> <br>> updateStyle: inTheBackground<br>> <br>> ...<br>> <br>> instead of duplicating the logic?<br>> <br>> <br>> Levente<br><br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>Useful random insult:- Not much to show for four billion years of evolution.<br><br><br><br></leves@caesar.elte.hu></div></blockquote>
</div></body>