Goals for Viewrendered3

[Thomas Passin]

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

[Edward K. Ream]

On Fri, Feb 7, 2020 at 1:56 PM Thomas Passin <tbp1...@gmail.com> wrote:

One thing that is still up in the air for me is the relationship between viewrendered and vr3

I would prefer that the user choose either VR or VR3. That way the VR pane can be used as is.

Edward

[Thomas Passin]

I would too.  How does Leo send the docstring information to VR?  It isn't getting to VR3 at present.  Note that I changed all the command names from "vr-xxx" to "vr3-xxx" (only in VR3;  I didn't change a thing in VR).  Is there one "vr-" command that Leo is using?

[Edward K. Ream]

On Sat, Feb 8, 2020 at 7:48 AM Thomas Passin <tbp1...@gmail.com> wrote:

How does Leo send the docstring information to VR? 

Iirc, it's the other way around. The plugin sends its docstring to Leo's core. The top-level init function contains:

g.registerHandler('scrolledMessage', show_scrolled_message)

Edward