<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p><i>> ... Terse Guide ...</i></p>
<p><br>
</p>
<p>I would still propose to reformat it about this way:</p>
<p><img size="25563" contenttype="image/png" id="img651388" style="max-width: 99.9%; user-select: none;" contextid="img817413" tabindex="0" src="cid:28d0935b-bb15-4e11-ae66-7d6476e04fea"><br>
</p>
<p>And also in your second screenshot, I think text wrapping would improve the readability. :)</p>
<p><br>
</p>
<p>> <span style="font-size: 12pt;">> Styling, on the other hand, should be dynamic if we simply always use a PluggableCodePaneSpec?</span></p>
<div><i>> <span style="font-size: 12pt;">Hmm... I wouldn't do that in the help browser by default. Those little "wiki-like" pages in the help browser are text documents that can contain code -- not the other way round. You can always style a piece of text with
[cmd]+[6] then "style it". ;-) Then save it.</span></i></div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div><span style="font-size: 12pt;">What is the difference between a pluggable code pane that is not "okToStyle", and a pluggable text spec? As far as I see, at least the Morphic implementation does not make any difference here ...</span></div>
<div><span style="font-size: 12pt;">Moreover, "style it" is exactly where my changeset comes :-) Referring to the current Trunk implementation, I do not think we should store the hard-coded result of a #styleIt operation at any place. Please note that at the
moment, the ShoutAttribute only works for PluggableTextMorphPlus and enforces styling even if it is not "okToStyle".</span></div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div><i><span style="font-size: 12pt;">> </span><span style="font-size: 12pt;">Well, actual mark-down with dynamic styling of selected text portions would also be nice. Yet, then we would need an extra "edit mode" for those pages in the help browser to "see"
the mark down, which we do not need at the moment. And that's a good thing. It feels more direct. ;-) Not sure how long we can keep it that way...</span></i><span style="font-size: 12pt;">
<div><br>
</div>
<div>The old question about WYSIWYG vs WYSIWYM :-) Well, inspecting or manipulating a TextAction after creation is not very easy for now (okay, I don't know all details about TextAction>>analyze). We could need a hotkey for something like "change attribute"
here, maybe.</div>
<div>But if we could develop a *simple* WYSWIWYM language, I think a switch in the PluggableTextMorph (yellow-button or halo) menu could be a compromise; and it would be also a nice way to store the text, as Text>>readStream is quite cryptical. However, pure
Markdown does neither support colors nor links, while on the other hand, HTML is not the simplest language to read, in my humble opinion. GitHub-flavored Markdown? BBCode? ;-)</div>
</span></div>
<p></p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div><font size="2" color="#808080"></font></div>
</div>
</div>
</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>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel<br>
<b>Gesendet:</b> Montag, 11. November 2019 13:53:03<br>
<b>An:</b> John Pfersich via Squeak-dev<br>
<b>Betreff:</b> Re: [squeak-dev] Changeset: ShoutAttribute & semi-styling</font>
<div> </div>
</div>
<div>
<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
> <span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Styling, on the other hand, should be dynamic if we simply always use a PluggableCodePaneSpec?</span>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px"><br>
</span></div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Hmm... I wouldn't do that in the help browser by default. Those little "wiki-like" pages in the help browser are text documents that can contain code -- not the other way round.
You can always style a piece of text with [cmd]+[6] then "style it". ;-) Then save it.</span></div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px"><br>
</span></div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Well, actual mark-down with dynamic styling of selected text portions would also be nice. Yet, then we would need an extra "edit mode" for those pages in the help browser to "see"
the mark down, which we do not need at the moment. And that's a good thing. It feels more direct. ;-) Not sure how long we can keep it that way...</span></div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px"><br>
</span></div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Best,</span></div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Marcel</span></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;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 11.11.2019 12:20:10 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:</p>
<div style="font-family:Arial,Helvetica,sans-serif">
<div id="divtagdefaultwrapper" style="font-size: 12pt;color: #000000;font-family: Calibri,Helvetica,sans-serif" dir="ltr">
<p>Hi Marcel,</p>
<p><br>
</p>
<p>Thanks for the overview.</p>
<p>However, I'd be curious why and when we should ever want font to be monospaced or text wrapping to be disabled for text or Smalltalk code? From my point of view, monospacing is a relic of programming languages that provide bad readability due to a complicated or counter-intuitive
syntax, and horizontal scroll bars are inconvenient at all, as exceedingly few mouses support 2D scrolling (I don't even know whether Squeak supports them :D) and you cannot read the whole line at once. Just my two cents :-)</p>
<p><br>
</p>
<p>Styling, on the other hand, should be dynamic if we simply always use a PluggableCodePaneSpec?</p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family: Calibri,Arial,Helvetica,sans-serif;font-size: ;margin: 0">
<div><span style="font-size: 10pt;color: #808080"></span></div>
</div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif;color: #000000"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel<br>
<b>Gesendet:</b> Montag, 11. November 2019 11:07:00<br>
<b>An:</b> John Pfersich via Squeak-dev<br>
<b>Betreff:</b> Re: [squeak-dev] Changeset: ShoutAttribute & semi-styling</span>
<div> </div>
</div>
<div>
<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi, there.
<div><br>
</div>
<div>Styling in HelpTopic is "under construction" because of how tool builder works. There is usually a lot of "initialization code" which is challenging to toggle at a tool's run-time:</div>
<div><br>
</div>
<div>- styling on/off</div>
<div>- fixed (monospaced) font?</div>
<div>- horizontal scrolling on/off (or text wrapping on/off)</div>
<div><br>
</div>
<div>Consequently, things that seem to be "under construction" in Squeak's Help Browser might actually be "under construction" in the tool builder (and all it's specs and relationships to pluggable morphs [Morphic] or pluggable views [ST80/MVC]):</div>
<div><br>
</div>
<div>- A new event for changed/update would make sense?</div>
<div>- What are the default values of properties if no further values are specified?</div>
<div>- Is a default value coded in a widgets #initialize or in a tool's (or model's) #buildWith: or in the spec's #ifNil: or in the (tool) builder's #buildPluggable*:? Or at all places together? What are the override priorities then?</div>
<div><br>
</div>
<div>Further code readings:</div>
<div><br>
</div>
<div>HelpBrowser >> #buildWith:</div>
<div>
<div style="font-size: 13.3333px">HelpBrowser >> #buildCodeContentsWith:</div>
</div>
<div>HelpBrowser >> #aboutToStyle:</div>
<div>(senders of) #usesCodeStyling</div>
<div>(implementors of) #usesCodeStyling</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;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 10.11.2019 20:50:13 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:</p>
<div style="font-family:Arial,Helvetica,sans-serif">
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255); text-align: left;" dir="auto">
Yeah, I already saw styling in the help topics is a bit under construction, I will be happy to work at this after this change set will have been approved :-)</div>
<div id="ms-outlook-mobile-signature" dir="auto" style="text-align: left;">
<div><br>
</div>
Best,</div>
<div id="ms-outlook-mobile-signature" dir="auto" style="text-align: left;">Christoph</div>
<br>
<br>
<br>
<div class="gmail_quote">On Sun, Nov 10, 2019 at 8:27 PM +0100, "tim Rowledge" <span dir="ltr">
<<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex;border-left: 1px #ccc solid;padding-left: 1ex;min-width: 500px">
<div dir="3D"ltr"">
<pre>> On 2019-11-10, at 10:28 AM, Christoph Thiede <christoph.thiede@student.hpi.uni-potsdam.de> wrote:
>
> ShoutAttribute.cs
That looks pretty damn good. This could help a great deal in making Help stuff clearer, so thank you!
tim
--
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim
Useful random insult:- Thinks everyone else is entitled to his opinion, like it or not.
</christoph.thiede@student.hpi.uni-potsdam.de></pre>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>