Viewrendered3 is finally close to preliminary release, after I got diverted by a few red herrings. As I clean up the anomalies I know about, please look over the attached set of goals for the project. I don't want to seriously enlarge the scope at this time, but if anyone thinks that something should be added or changed, or that one of my goals isn't thought out correctly, this would be a good time to let me know.
One thing that is still up in the air for me is the relationship between *viewrendered *and *vr3* with regard to displaying Leo information like the docstrings of other plugins. Should *vr3* simply replace *vr* for this purpose? If yes, I don't know how this communication is accomplished, but right now, the two interfere. And I see that *vr *gets loaded somehow even if it's not called for in an *enabled-plugins* setting. I'm going to need to understand how this all works, and any guidance will be very helpful. TomP -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/cac893cf-f064-4f96-a092-e206124103ba%40googlegroups.com.Title: <string>
Goals for VR3
Enhancements
The primary intent of Viewrendered3 is to enhance the Viewrendered plugin to able to:
- view an entire sub-tree at once;
- mix text and code while still being able to execute the code.
Enhancements to ViewRendered for @rst and @md nodes:
- Render an entire subtree.
- Code Blocks
- Optionally render only code blocks.
- Colorize code blocks.
- Optionally execute Python code in code blocks.
- Display print() output below code blocks.
- Delineate code blocks started by @language markers in addition to md or RsT code block formatting.
- Preserve Python decorators in code blocks.
- Correctly treat RsT or md when they are in a Python docstring. That is, render the docstring correctly as text.
- Ability to export rendered results to system browser.
- Omit lines between @ and @c markers, except in docstrings.
- Render math content using MathJax rendering.
Non-goals
At this time, the following are not goals:
- Render math with css or any other method besides MathJax.
- Nodes with mixed @rst and @md sections.
- Executing other languages besides Python.
- Understanding @others directives or <<named sections>>.
- Inserting graphical or other non-print() execution output into the tree.
- Saving a code-only file from any node or subtree.
Note that a code-only file can be gotten by exporting the code-only rendering, then highlighting the page in the browser, copying it, and pasting into a file.
