<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>I have been piddling around with this to see what I can see to generate a starting point for thinking about this.<br></div><div><br></div><div><br></div><div>An obvious first step would be to show all the preferences associated with a "thing"</div><div><br></div><div>TextEditor<br></div><div>Workspace<br></div><div>TheWorldMainDockingBar <br></div><div><br></div><div>are just a few of the things that have preferences on them:<br></div><div><br></div><div><blockquote style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245);"><div>Transcript clear.<br></div><div>(SystemNavigation allMethodsSelect:[:mds | <br></div><div> #(preference:category:description:type: preference:categoryList:description:type:)<br></div><div> anySatisfy:[:s| (mds pragmaAt: s) notNil]])<br></div><div> do:[:m |<br></div><div> Transcript show: (m methodSymbol) ; cr.<br></div><div> m compiledMethod pragmas do:[:pragma |<br></div><div> Transcript show: ((pragma methodClass name)copyReplaceAll:'class' with:' '); cr;cr.<br></div><div> Transcript show: (pragma);cr;cr;cr;cr.]]<br></div></blockquote><br></div><div><br></div><div>Per what Tim writes below...<br></div><div><br></div><div>We should be able to automate that task by modifying "something" programatically.<br></div><div><br></div><div>Also....<br></div><div><br></div><div>Would it make sense to add the preferences toggling directly to the menus for specific things?<br></div><div><br></div><div>fileOutFilePath and fileOutOnAccept strike me as useful things to be viewed and modified in any Workspace.<br></div><div><br></div><div>cordially,<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div class="zmail_extra_hr" style="border-top: 1px solid rgb(204, 204, 204); height: 0px; margin-top: 10px; margin-bottom: 10px; line-height: 0px;"><br></div><div class="zmail_extra" data-zbluepencil-ignore="true"><br><div id="Zm-_Id_-Sgn1">---- On Sat, 27 Nov 2021 23:29:47 -0500 <b>tim Rowledge <tim@rowledge.org></b> wrote ----<br></div><br><blockquote style="margin: 0px;"><div><br><br>> On 2021-11-27, at 2:56 PM, Thiede, Christoph <<a href="mailto:Christoph.Thiede@student.hpi.uni-potsdam.de" target="_blank">Christoph.Thiede@student.hpi.uni-potsdam.de</a>> wrote:<br>> <br>> But IMHO separate help documents should be used with caution - in my experience, they are looked up significantly rarer than help content that is integrated right into the domain (method comments, class comments, tooltips, maybe help buttons).<br><br>Something that would probably help here is making sure that when a class (or group of classes etc) has a HelpBrowser section, we reference that Help stuff from the class(es) & method comments. We have the ability to link a bit of text to class comments, definitions, methods and so on, so maybe we could add one to a HelpBrowser section? <br><br>Hmm, a few minutes whacking suggests that a simple subclass of TextAction would do the job, along with a bit more understanding of the right way to open a help browser on a suitable topic. Maybe tomorrow.<br><br><br>tim<br>--<br>tim Rowledge; <a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>Objects are closer than they appear.<br><br><br><br></div></blockquote></div><div><br></div></div><br></body></html>