On Thu, Aug 8, 2019 at 9:41 AM Edward K. Ream <[email protected]> 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 would seem to be, "all the docks are optional, so what's the
problem?"  Some replies:

1. The new pyzo code will bloat Leo and increase the difficulty of
maintaining Leo.  Do I really want to saddle my successors with that?
Integrating pyzo with Leo will take real work, and somebody is going to
understand that work in detail.

2. A day or two ago I started out just wanting to see if the Pyzo File
Browser (pfb) could be integrated into Leo.  Clearly, this should not have
to drag huge amounts of pyzo code into Leo.  It turned out to be easy to
load *all* the docks with very little work, so that's where I went.
Perhaps instead I should copy the minimal code needed into the (properly
named) pyzo_file_browser plugin.  That should sidestep the *big question*.

3. There are aspects of pyzo's editors that I admire.  Perhaps I should
start another prototype project that would integrate the good parts of
pyzo's editors directly into Leo, without actually using much (or any) of
pyzo's code.

*Summary*

I'll probably go ahead and get the remaining docks working, that is
visually.  I might as well finish this phase of the project.

The *big question* (how to integrate pyzo and Leo) can not be ignored.
Using huge amounts of pyzo code promises difficulties for future devs.
Instead, using just a bit of pyzo code in a few places may make more sense.

All questions and comments welcome.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS3%2BHvi4acnFXh6rcetZf7-C%3D72X%2B1Ui61F96cNGpkxA_g%40mail.gmail.com.

Reply via email to