A recent rev fixed bug 136: Viewrendered2 chokes on displaying @html nodes. However, the bug fix was an unsatisfying half measure.
That work highlighted the strengths and weaknesses of the vr2 plugin. +1's: - It uses QWebView for rendering. - It allows export of html. - It allows optional rendering of entire trees, not just a single node. - And maybe other useful features. -1's: 1. It duplicates difficult infrastructure code from the vr plugin. 2. The user must choose either vr or vr2, not both. I propose to merge both plugins, calling the result viewrendered.py. This should be *relatively *straightforward. New settings will specify only the *default *actions where vr and vr2 differ. The user will be able to choose desired actions at any time using the vr2 menu in the rendering pane. I see no real downsides to the merger. YMMV. Your comments, please, Amigos. Edward -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
