[squeak-dev] Changeset: ShoutAttribute & semi-styling
marcel.taeumel at hpi.de
Mon Nov 11 12:53:03 UTC 2019
> Styling, on the other hand, should be dynamic if we simply always use a PluggableCodePaneSpec?
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]+ then "style it". ;-) Then save it.
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...
Am 11.11.2019 12:20:10 schrieb Thiede, Christoph <christoph.thiede at student.hpi.uni-potsdam.de>:
Thanks for the overview.
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 :-)
Styling, on the other hand, should be dynamic if we simply always use a PluggableCodePaneSpec?
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel
Gesendet: Montag, 11. November 2019 11:07:00
An: John Pfersich via Squeak-dev
Betreff: Re: [squeak-dev] Changeset: ShoutAttribute & semi-styling
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:
- styling on/off
- fixed (monospaced) font?
- horizontal scrolling on/off (or text wrapping on/off)
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]):
- A new event for changed/update would make sense?
- What are the default values of properties if no further values are specified?
- 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?
Further code readings:
HelpBrowser >> #buildWith:
HelpBrowser >> #buildCodeContentsWith:
HelpBrowser >> #aboutToStyle:
(senders of) #usesCodeStyling
(implementors of) #usesCodeStyling
Am 10.11.2019 20:50:13 schrieb Thiede, Christoph <christoph.thiede at student.hpi.uni-potsdam.de>:
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 :-)
On Sun, Nov 10, 2019 at 8:27 PM +0100, "tim Rowledge" <tim at rowledge.org [mailto:tim at rowledge.org]> wrote:
> On 2019-11-10, at 10:28 AM, Christoph Thiede 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 at rowledge.org; http://www.rowledge.org/tim Useful random insult:- Thinks everyone else is entitled to his opinion, like it or not.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev