Forum Posts Feed
RightNote Question
< Next Topic | Back to topic list | Previous Topic >
Posted by Marbux
Sep 3, 2015 at 12:59 AM
Jon Polish wrote:
Also consider Ultra Recall for this purpose. Its search capabilities are
>excellent. Neither UR or NoteCase have the kind of web export
>incorporated into RightNote.
While it is accurate that NoteCase Pro’s *default* HTML export does not match Rightnote’s export, NoteCase Pro’s HTML export is near-infinitely variable thanks to its embedded Lua v. 5.3 script interpreter and API methods for modifying the output HTML content during export. In the NoteCase Pro Help file, see
Automation, Scripts and Plugins > Scripting NoteCase Pro > Scriptable Program Commands > Document Commands > HTML Export Commands
Automation, Scripts and Plugins > Scripting NoteCase Pro > Scriptable Program Commands > Document Commands > Nc_Doc_Export (including CSS templating options).
Via event triggers, scripts can also automatically perform such alterations on every HTML export:
Automation, Scripts and Plugins > Scripting NoteCase Pro > Script Event Triggers > Before Header HTML Exported
Automation, Scripts and Plugins > Scripting NoteCase Pro > Script Event Triggers > Before Note HTML Exported
For example, I run with a script enabled via the Before Note HTML exported trigger that adds support for 12 HTML elements that NoteCase Pro does not support by default, converting escaped tags into unescaped tags: BLOCKQUOTE, CITE, CODE, DD, DL, DT, HR, LI, OL, P, PRE, and UL. Since the conversion is accomplished working from a Lua table of unescaped tags and their escaped equivalents, it’s trivial to add support for still more elements or attributes.
Post-export modification of web pages is also enabled via an event trigger and an API method that returns the path of the last exported file. See
Automation, Scripts and Plugins > Scripting NoteCase Pro > Script Event Triggers > After Document Exported
Automation, Scripts and Plugins > Scripting NoteCase Pro > Scriptable Program Commands > Application Commands > Get Previous Values > Nc_App_ExportPath_Get.
Along with an extremely rich selection of node states and properties (including tags and custom properties) that can be acted upon and manipulated by scripts, there are few limitations (beyond conformance with web standards) on the form that exported web pages can take. See Automation, Scripts and Plugins > Scripting NoteCase Pro > Scriptable Program Commands > Note Commands > Note Property Commands (listing 32 node states and properties that be acted upon by scripts).
In summary, it’s erroneous to assume that NoteCase Pro’s web export capabilities are limited to the default user options. The web page export options are nearly unlimited.
Posted by Jon Polish
Sep 3, 2015 at 11:59 AM
Thank you for elaborating on NoteCase’s capabilities. I was aware of some of what you wrote and the possibilities I was ignorant of are intriguing. With variations on how and where the tweaking occurs, similar things may be said of almost any other program that converts content to html.
However what I wrote was in answer to Ken’s inquiry and (as I have gathered across his posts) the level of technical involvement to which he is willing to commit. Of course I could be wrong (sorry Ken), but that is my take.
Jon
Posted by Ken
Sep 3, 2015 at 03:04 PM
Jon Polish wrote:
>However what I wrote was in answer to Ken’s inquiry and (as I have
>gathered across his posts) the level of technical involvement to which
>he is willing to commit. Of course I could be wrong (sorry Ken), but
>that is my take.
>
>Jon
Hi Jon,
While I do find the potential of a little bit of programming to be interesting, you were correct that the level of technical involvement to which I am willing to commit is limited.
—Ken
Posted by Jon Polish
Sep 3, 2015 at 03:07 PM
Thanks Ken. Glad I was reading you correctly.
Jon
Posted by Marbux
Sep 3, 2015 at 07:52 PM
Jon Polish wrote:
> With variations on how and where the tweaking occurs,
>similar things may be said of almost any other program that converts
>content to html.
Agreed, although in nearly all cases you’ll be limited to working with external scripts, e.g., shell scripts, which are not operating system-independent, or with a file converter capable of formatting output, e.g., Pandoc. One big advantage of having Lua embedded is that its interpreter runs in a virtual machine so scripts are (if written correctly) portable across operating systems. For example, I’ve written somewhere in the neighborhood of 700 scripts for NoteCase Pro, keep them synced with ownCloud, and use any of them on both Linux Mint 17 and Win7. Portable scripts earn lots of extra points on my scorecard. :-)
Having 34 program event triggers defined for launching scripts, and 341 program API methods exported to Lua also helps a lot, with one of those methods alone able to activate 159 different user actions. Plus three embedded Lua libraries, one for UTF-8 support that replaces the Lua string library functions that act on or return character counts, one for handling TCP/IP connections, and one the Lua File System library, which makes the file and directory handling portable too.
Of course I’m biased. Did I mention that I *really* like NoteCase Pro? :-) That’s why I’ve assisted in its development as a volunteer for the last four or five years.