![]() ![]() Markdown is generally more use for generating HTML from plain text using inline mark-up. If you don’t know what Markdown is, I’d genuinely suggest ignoring it for now as it won’t help you at this point. ![]() In terms of your questions here and in other current threads, I’d suggest that Markdown is a distraction to your goal. Noting Tinderbox’s text area is an RTF writing space, Markdown is a form of plain-text mark-up basically helps those who like to write in plain text to generate HTML (sung a Markdown. If the ultimate goal is to produce a web page, what’s the advantage of going via Markdown rather than just generating HTML directly from Tinderbox? Preview mode $HTMLExportTemplate("/System/Prototypes/Note") = "/System/Templates/Processed markdown" Įxport mode $HTMLExportTemplate("/System/Prototypes/Note") = "/System/Templates/Markdown page" Ĭopy markdown runCommand("pbcopy", exportedString(current, "/System/Templates/Markdown page")) Processed markdown template ^value(runCommand($HTMLPreviewCommand("/System/Prototypes/Markdown"), exportedString(current, "/System/Templates/Markdown page")))^ I have a third stamp that copies the markdown source to the clipboard, regardless of the mode. Then I have stamps to switch between Preview and Export modes - Preview mode sets the HTMLExportTemplate to Processed markdown, and Export mode sets it to Markdown page. But here’s my current solution that’s a few more steps.īasically it involves creating a separate template, which renders the note using the Markdown page template, and passes the result through to the Markdown prototype’s HTMLPreviewCommand. I would love it if anyone could share a way to have the preview and HTML work the way I want. I haven’t quite cracked it (and I don’t even know if it’s possible), but I have come up with something workable for the time being. Is that possible? I’ve attached a demo file if that’s helpful. I want the Preview pane to show the above text, but piped through the HTMLPreviewCommand. ![]() I want the HTML pane to show the result of the note run through the template - not processed by the HTMLPreviewCommand. So my preview is a mixture of unprocessed template code, and the processed note:ĭisabling HTMLPreviewCommand correctly constructs the HTML that I want, but of course it doesn’t run it through a processor for the preview pane. The problem seems to be that when HTMLExportCommand is enabled, Tinderbox processes ^text^ through the preview command before passing the text off to the template. Basically I can have either 3 or 4, but not both. I can’t seem to figure out the right combination of HTML* attributes. I am trying to create a document that will let me: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |