<!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>Hi Folks,<br></div><div><br></div><div>I just noticed that HelpBrowser does not respect the page order, but rather, places subclasses at the bottom and methods at the top.<br></div><div><br></div><div>given...</div><blockquote style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245);"><div>pages ^ #( todo LevelTwoHelp bibliography )<br></div></blockquote><div><br></div><div>I am hoping to see <br></div><div><br></div><div>page: todo.<br></div><div>book: LevelTwoHelp<br></div><div>page: bibliography.<br></div><div><br></div><div><br></div><div>instead I see<br></div><div><br></div><div>page:todo<br></div><div>page bibliography<br></div><div>book: LevelTwoHelp<br></div><div><br></div><div><br></div><div><br></div><div>Can this be overridden? Is there a reason I am not aware of?<br></div><div><br></div><div>The reason, is that I would like the HelpBrowser to respect the ordering in the Org (soon to be Markdown) files so that round-trip import-exports are consistent.<br></div><div><br></div><div>Here is the .org snippet in question: (You can see Bibliography page is after Level Two Help<br></div><div><br></div><div><blockquote style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245);"><div>* Doc Test Document Help<br></div><div><br></div><div>I need to get this text to show up. put it in a comment and store retrieve it?<br></div><div>yes, this is how SqueakCorePackagesHelp does it.<br></div><div><br></div><div>** Todo<br></div><div> [[My Bibliography][Bibliography]]<br></div><div><br></div><div>#+BEGIN_EXAMPLE<br></div><div><br></div><div> 1. [ ] get level one headlines content showing up<br></div><div> 2. [ ] add org links to the parser grammar.<br></div><div> 3. [ ] figure out and document a heuristic on handling headline levels<br></div><div> 4. [ ] figure out a heuristic (factory next-page-name ) for page names and Help class names<br></div><div> 5. [ ]ditch the bracket convention for pages and classes. use heuristics<br></div><div> 6. [ ] uncomplete todo item<br></div><div> 7. [X] complete todo item<br></div><div> <br></div><div><br></div><div> links<br></div><div> + [[link][description] or [[link]<br></div><div> + use Org->Hyperlinks->literal to see links as they are while still preserving the linkyness of em.<br></div><div> + C-c C-o to follow<br></div><div> + C-c & to return<br></div><div> + C-c C-l with the cursor on the links prompts for editing<br></div><div> + <BACKSPACE> after a bracket will remove the bracket exposing the links structure<br></div><div><br></div><div> + [[Bibliography][Bibliography]]<br></div><div><br></div><div> <br></div><div>#+END_EXAMPLE<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>** Level Two<br></div><div>level 2 headlines can be a page or a class<br></div><div>*** Level Three<br></div><div>level 3 headlines can be a page or a class<br></div><div><br></div><div>** Bibliography<br></div><div> <<Bibliography>><br></div><div> [[<a target="_blank" href="https://orgmode.org/manual/Internal-Links.html">https://orgmode.org/manual/Internal-Links.html</a>]]<br></div></blockquote><div><br></div></div><div><br></div><div>In the above, Level Two resolves into its own HelpClass because it has sub-pages (which resolve into either methods or subclasses...which...)</div></div><br></body></html>