Re: Embedding Leo into pyzo?

Hi Edward. I meant this -> http://leoeditor.com/leoBridge.html I have not had time to try this inside pyzo, but testing leoBridge within pyzo would be a good test. On Wednesday, January 11, 2017 at 7:32:58 PM UTC+8, Edward K. Ream wrote: > > > > On Mon, Jan 9, 2017 at 5:31 AM, Satish Goda

Re: Improving Leo using pyzo code

I installed Flexx yesterday and it is brilliant! On Wednesday, January 11, 2017 at 7:43:44 PM UTC+8, Edward K. Ream wrote: > > > > On Sun, Jan 8, 2017 at 3:17 PM, john lunzer > wrote: > >> So awesome that you made this discovery, I've wanted to try Pyzo out for >> some time

Re: Leo's real weaknesses

​​ ​​On Wed, Jan 11, 2017 at 3:57 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: ​> ​ I'm not sure if that can be a blanket statement. I guess Leo doesn't have a defined boundary between declared API and internals subject to change - perhaps by default we've assumed the

Re: Leo's real weaknesses

From: Edward K. Ream To: leo-editor Sent: Wednesday, January 11, 2017 1:33 PM Subject: Re: Leo's real weaknesses On Wed, Jan 11, 2017 at 12:31 PM, 'Terry Brown' via leo-editor wrote:> I wouldn't be

Re: Leo's real weaknesses

On Wed, Jan 11, 2017 at 12:31 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: ​> I wouldn't be in a huge rush to eliminate wrappers. No worries. They can't be eliminated now, because doing so could break existing code. EKR -- You received this message because you are

Re: Leo's real weaknesses

1. Using wrapper classes for text editing The present Qt gui is, iirc, Leo's fourth gui.  Two preceded Leo in python.  Previously, the python version of Leo used the much weaker Tk gui. The pyzo code shows just how big a price Leo has paid for the wrapper text abstraction layer.  Otoh,

Leo's real weaknesses

Recent criticisms of Leo and its architecture have been wildly off the mark. The most ludicrous was the statement that 'c', 'g' and 'p' should have longer names. Here, I'd like to discuss Leo's *real *weaknesses. Some have recently been exposed as I study pyzo's operation and code. I'll also

Re: The design of Leo+Ipython+Jupyter+Lit-computing

On Tuesday, January 10, 2017 at 12:14:44 PM UTC-5, Offray Vladimir Luna Cárdenas wrote: I would give priority to @cell directive and interaction with (I)python > kernels (maybe via yoton), even if other @-directives for the notebook are > not supported at the beginning. > I agree. >

Re: Improving Leo using pyzo code

On Sun, Jan 8, 2017 at 3:17 PM, john lunzer wrote: > So awesome that you made this discovery, I've wanted to try Pyzo out for > some time now. You may be aware that the author of Pyzo is also the author > of Flexx. ​No I didn't know that. Almar Klein is a busy guy

Re: Leo + PlantUML workflow

On Mon, Jan 9, 2017 at 5:22 AM, Satish Goda wrote: > I am exclusively using Leo since two months (not even Pyzo/PyCharm) as I > am able to document my thoughts and move things around easily (non > destructively via clone nodes). > ​Glad to hear it! ​ > The executing of

Re: Embedding Leo into pyzo?

On Mon, Jan 9, 2017 at 5:31 AM, Satish Goda wrote: > I think in today's world of disparate software components, It would be > really nice to see how Leo's integration component would integrate with > Pyzo. > ​What do mean by "Leo's integration component"?​ > I really