On Tuesday, June 18, 2019 at 1:28:51 AM UTC-5, Edward K. Ream wrote: I have revised several conclusions. As usual, making a strong, pithy statement helps the mind engage and critique it. This reply contains quotes from this thread and "Leo's past and future".
> [Integrating pyzo features into Leo] would be foolish and unnecessary. This is now debatable, as discussed below. > I have done extensive code-level prototyping of pyzo integration without [considering] the *basics*, covered in the pyzo intro <https://pyzo.org/pyzo_intro.html>, configuring shells <https://pyzo.org/shellconfig.html> and interactive vs script mode <https://pyzo.org/interactive_vs_script.html>. That was being way too hard on myself. I probably *did* read these pages, without realizing their significance at the time. That's hardly a crime. In all likelihood, I could not have truly understood their significance without having done the prototyping I did. > Doh: Pyzo can run alongside Leo True, but not conclusive. John Lunzer said: "I'm not optimistic that users would see this as a "good" or "clean" solution to having shell and file browser features available to them." Debaters take note: a pithy comment is way more effective than windy ones. > Would I embed pyzo's docks into Leo if I could just wave a magic wand? Yes, probably. Alas, actually doing so would take a lot of work. So what? The goal matters more than programming difficulties, provided that no heroic measures are needed. > There are *only *two ways forward: > 1. *Import *pyzo code and bend it to Leo's will. > 2. *Copy* pyzo code into Leo and suffer all the ill effects of cut and paste. > Each is ugly in its own way. These are not necessarily gotchas. Any "ugliness" would be confined to a plugin. It's too early to say. There might be a third way: some kind of client/server interaction between Leo and pyzo/yoton. Yoton, pyzo's communication infrastructure, is worth learning and playing with on its own. Communication between Leo and other programs will likely be a big part of Leo's future. > Scripts run in an external environment can't be Leonine. They could be given access to c, g and p, but they could not control Leo without heroic measures. Not a gotcha. Most people use scripts for purposes unrelated to Leo! Pyzo allows scripts to run in the background. Leo could (and should) do this too. Such *Leonine background scripts* would not be able to control Leo either. Finally, pyzo's debugger and shell would replace Leo's python_console and xdb plugins. If this can be done (a big question) it would be a major improvement to Leo. *Summary* > I shall not add pyzo's major features to Leo. Not in 6.1. Not ever. I was way too harsh on myself and hasty in my conclusions. I am now officially dithering regarding pyzo :-) Time for more prototyping. This is progress. The prototyping will happen in a wider context: interaction with other programs. 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 https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/0764c742-24fb-49ec-9b44-9b0586175fe0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
