On Tue, Apr 21, 2015 at 9:39 AM, Jacob Peck <[email protected]> wrote:
Thanks for promoting my plugin! I pushed some minor fixes and introduced > some new commands at rev 4b98c93. > > The new commands are: > [*-expanded-*] > Ah. I see. You want g.getScript. I had forgotten about the p.script property. > The way Qt handles printing is to send an HTML document to the print > dialog. The non *-html commands wrap whatever you've chosen in some HTML > wrapper code, and make it monospaced. The *-html commands assume whatever > you are printing is a valid, complete HTML document, without the wrapper > code from the other commands -- this allows you to stylize your output. It > should work well with @rich bodies from Terry's richtext.py plugin. It > seems to work without <html>, <body>, etc. tags, but otherwise needs to be > valid html. > > Attached is a .leo file with a few test cases. Rea > > d the <!-- comments --> at the end of the first node, and the differences > should become clear. > Thanks. That was helpful. Everything now works as expected. Rev fe751c6 improves the docstrings, imo, so that the workings of html-related print commands is clearer. By luck I discovered that neither the plugin nor leoPrinting.py worked with PyQt 5. This appears to be a severe packaging fail in PyQt5. Fixed at rev 0eaa984. the printing.py plugin can be removed. > Done at rev d4fa3f4. > It is important to keep c.printingController available > It is always inited during Leo's startup. The print commands will do nothing for null guis. 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.
