Re: Status report: using pyzo features in Leo

On Wednesday, August 14, 2019 at 4:51:15 AM UTC-5, Edward K. Ream wrote: > the pyzo_in_leo plugin now loads *all* of pyzo's docks. I have retired the pyzo_file_browser plugin. The pyzo_in_leo plugin now does everything that the pyzo_file_browser plugin did. As a result, there is no longer any

Re: Status report: using pyzo features in Leo

On Monday, August 12, 2019 at 9:24:43 AM UTC-5, Edward K. Ream wrote: > Today marks a huge milestone. The pyzo_file_browser plugin has collapsed in complexity! And today marks another huge milestone: the pyzo_in_leo plugin now loads *all* of pyzo's docks. The code is ridiculously simple:

Re: Status report: using pyzo features in Leo

On Mon, Aug 12, 2019 at 4:22 PM Brian Theado wrote: 1. IMO, at a bare minimum, you should always first check in the pyzo code without any of your changes and only then add your changes. > IMO, at a bare minimum, you should always first check in the pyzo code without any of your changes

Re: Status report: using pyzo features in Leo

Edward, On Mon, Aug 12, 2019 at 11:13 AM Edward K. Ream wrote: > On Monday, August 12, 2019 at 9:59:05 AM UTC-5, Edward K. Ream wrote: > [...] > 1. We can now see clearly we must import *all* of pyzo's code into Leo. > Exactly where doesn't matter. We can't adapt pyzo to Leo in any other way.

Re: Status report: using pyzo features in Leo

On Monday, August 12, 2019 at 9:59:05 AM UTC-5, Edward K. Ream wrote: > The new scheme is the *only* way that has any realistic chance of working. *Implications* 1. We can now see clearly we must import *all* of pyzo's code into Leo. Exactly where doesn't matter. We can't adapt pyzo to Leo in

Re: Status report: using pyzo features in Leo

On Mon, Aug 12, 2019 at 9:24 AM Edward K. Ream wrote: > At long last there is an *easy* path for using any part of pyzo's code, modified as we like, without monkey-patches. In retrospect, it's now clear that: 1. The new scheme combines the best features of use-by-copy and use-by-import: -

Re: Status report: using pyzo features in Leo

On Monday, August 12, 2019 at 5:55:08 AM UTC-5, Edward K. Ream wrote: > leo/plugins/pyzo will allow me to experiment safely with significant changes to pyzo's code, especially pyzo's startup code. Done. > Side effects of "import pyzo" must be eliminated. Done. Today marks a huge

Re: Status report: using pyzo features in Leo

On Sunday, August 11, 2019 at 7:11:31 AM UTC-5, Edward K. Ream wrote: > I plan to put all needed support files in a new leo/plugins/*pyzo_support* directory. Did that yesterday. It worked. > Generalizing [the code] is always in my mind. When I awoke I saw that yesterday's code must indeed be

Re: Status report: using pyzo features in Leo

On Sunday, August 11, 2019 at 7:11:31 AM UTC-5, Edward K. Ream wrote: *Incremental packaging* > > ...I plan to put all needed support files in a new leo/plugins/ > *pyzo_support* directory. *Functions *from...pyzo's startup code will go > into pyzo_support/*pyzo_functions.py*. *Modules...*will

Re: Status report: using pyzo features in Leo

On Saturday, August 10, 2019 at 3:08:54 PM UTC-5, Edward K. Ream wrote: > Rev 75d917 in the pyzo branch adds icons to the pyzo_file_browser plugin, completely vindicating an incremental approach: Last night's rev 77004da makes more of the dock functional. The plugin now contains an interim

Re: Status report: using pyzo features in Leo

On Saturday, August 10, 2019 at 11:12:45 AM UTC-5, Edward K. Ream wrote: > During development, having a separate plugin for each pyzo dock...will be the simplest way. Imo, incremental development is a must. Rev 75d917 in the pyzo branch adds icons to the pyzo_file_browser plugin, completely

Re: Status report: using pyzo features in Leo

On Sat, Aug 10, 2019 at 8:33 AM Edward K. Ream wrote: > If this grand strategy succeeds, it will allow each pyzo dock to be defined in a separate Leo plugin. Each such plugin will contain nothing but imports, calls to do-something functions, and a few lines of code in each plugin's onCreate

Re: Status report: using pyzo features in Leo

On Monday, August 5, 2019 at 1:27:12 PM UTC-5, Edward K. Ream wrote: > This time around everything things much easier. *Status* Recent revs in the pyzo branch put the code that used to be in pyzo_file_browser.py into the pyzo_in_leo.py plugin. The pyzo_file_browser.py now contains a *copy* of

Re: Status report: using pyzo features in Leo

> > *Show whole files in the body pane* > > This is how pyzo works. Kent has requested this once or twice. I have > just created #1279 > > > for this. >

Re: Status report: using pyzo features in Leo

On Friday, August 9, 2019 at 7:08:56 AM UTC-5, Edward K. Ream wrote: > I'll rename [pyzo_file_browser.py] to pyzo_in_leo.py. Done at 82e2bd8 in the pyzo branch. I'm thinking of taking a break from the pyzo projects for awhile while I fix bugs :-) Edward -- You received this message because

Re: Status report: using pyzo features in Leo

On Friday, August 9, 2019 at 2:41:39 AM UTC-5, Edward K. Ream wrote: And now my subconscious is screaming at me...The *big question* (how to > integrate pyzo and Leo) can not be ignored. > After a bit more sleep I see that this project is still experimental, no matter how much apparent

Re: Status report: using pyzo features in Leo

On Thu, Aug 8, 2019 at 9:41 AM Edward K. Ream wrote: > Progress has been so fast that I'm a bit dizzy. And now my subconscious is screaming at me. This isn't the critic. It would be unwise to tell it to buzz off. The visual image is that with all the new docks Leo won't be Leo. The response

Re: Status report: using pyzo features in Leo

On Thu, Aug 8, 2019 at 11:41 AM Chris George wrote: > Pyzo docks are floaters. > > Pyzo docks do not nest. > > Using the X in the titlebar to close a Pyzo dock is a one way trip. The > title is removed from the pop-up menu. > > Clicking the diamond in a titlebar removes the titlebar of the Pyzo

Re: Status report: using pyzo features in Leo

Pyzo docks are floaters. Pyzo docks do not nest. Using the X in the titlebar to close a Pyzo dock is a one way trip. The title is removed from the pop-up menu. Clicking the diamond in a titlebar removes the titlebar of the Pyzo dock widget below it. It also turns off the ability to access the

Re: Status report: using pyzo features in Leo

On Monday, August 5, 2019 at 1:27:12 PM UTC-5, Edward K. Ream wrote: This time around everything things much easier. > This post describes recent progress in the pyzo branch. As usual, the summary contains the gist. The pyzo_file_browser plugin now can embed *all* of pyzo's docks (except the

Re: Status report: using pyzo features in Leo

On Wednesday, August 7, 2019 at 10:05:48 AM Edward K. Ream wrote: *> Leo's pyzo_file_browser plugin now puts pyzo's standard file browser​ in a Leo dock!* Recent revs prevent crashes in Leo's pyzo code, both in general and specifically when using the file browser. Double-clicking a file in

Re: Status report: using pyzo features in Leo

​​On Mon, Aug 5, 2019 at 1:27 PM Edward K. Ream wrote: > There is no need for the "let's pretend it's easy principle", because everything is easy :-) *Leo's pyzo_file_browser plugin now puts pyzo's standard file browser​ in a Leo dock!* This is a big milestone. You can show/hide this dock

Re: Status report: using pyzo features in Leo

On Monday, August 5, 2019 at 1:29:10 PM UTC-5, Edward K. Ream wrote: Oops, I meant so say, "I expect that completing *#1149* will take a matter > of days." > Maybe :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Re: Status report: using pyzo features in Leo

On Monday, August 5, 2019 at 1:27:12 PM UTC-5, Edward K. Ream wrote: > > This time around everything things much easier. There is no need for the > "let's pretend it's easy principle", because everything *is* easy :-) > Problems with imports are appearing. They are similar, but not the same,

Re: Status report: using pyzo features in Leo

On Monday, August 5, 2019 at 1:27:12 PM UTC-5, Edward K. Ream wrote: *Summary* > > All the old problems seem to have disappeared. I expect that completing > will take a matter of days. > Oops, I meant so say, "I expect that completing *#1149* will take a matter of days." Edward -- You