On Monday, March 21, 2022 at 10:56:08 AM UTC-4 [email protected] wrote: > Definitely, and I appreciate your (and Edward's) responsiveness and > openness. I don't grasp everything in your message (yet), I only installed > leo on one computer yesterday and was a bit surprised to see it (pip > actually) download PyQt5 just after I had manually installed PyQt6, and ... > not installing leo6.6 but an older version.
Version 6.6 hasn't been released yet, that's why you got 6.5 using pip. Those of us using non-release versions of 6.6 are getting them from the Github repository. They change pretty often, and could have bugs that will (we hope) be fixed). As of 6.5, IIRC, Leo didn't officially support Qt6. That's because Qt6 didn't include certain parts that Leo might use. Also, there were some API changes with Qt6. By Qt 6.23, and current development versions of Leo, both of these issues have been resolved and Leo can use either Qt5 or Qt6, whichever is available. > I expected Qt would be used for some visualization, but I have no > experience with it either. Leo uses Qt for all the UI (User Interface) elements - the trees, text editor, menus, etc. Internally, Leo is written so that it can be adapted to other graphics rendering systems, but I doubt that Qt will be replaced anytime soon. For display of graphical material, not one of Leo's strong points so far, there are several possibilities. These include: 1. Reference the image in a Markdown or Restructured text node, then display it in the Viewrendered or Viewrendered3 plugin. 2. Compute the SVG that describes a graphic, and display that with the VR or VR3 plugins, or send it to your web browser. 3. Write a script that produces a graph description - for example, the Graphviz description language - and use a batch file to send it to graphviz and then display it in your web browser. Your command could launch the batch file. This is not hard to do, though it will take a little learning to get up to speed on how. Here, by "script" I mean a small Python program that runs inside of Leo and (usually) uses Leo features. > I'm still out on the priority to cover my "information bowls" in leo > (between my Python logfile mill, long-term food reserve management, Belgium > addresses with fibers, home climate control, etc.) Most imply some future > Python code, but I actually hope that leo would help me see more clearly > where I should put my efforts first, by evaluating the "RoI" of everything > I put in. Leo is *really good* for developing Python code. It may take some time to fully appreciate just how good since there isn't any tutorial-type document that walks you through all of it. (There are tutorials, though). And Leo's abilities can be extended by Python scripts (programs) that add new commands. For example, I wrote a script that generates and displays a mind map of the selected Leo subtree. It gets launched like most other Leo commands. -- 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/44e8c67c-9132-4ff2-bfe9-805cb2f58452n%40googlegroups.com.
