Re: New Leo edit control

2017-01-24 Thread Edward K. Ream
On Tue, Jan 24, 2017 at 10:34 AM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > > > -- > *From:* Edward K. Ream > ​Good marketing. And great work, Terry. Not sure how this will fit in > with the pyzo widgets. Eventually I

Re: New Leo edit control

2017-01-24 Thread 'Terry Brown' via leo-editor
From: Edward K. Ream ​Good marketing.  And great work, Terry. Not sure how this will fit in with the pyzo widgets. Eventually I would like to use pyzo widgets so that we can have a border for use by the debugger.  Hmm. Iirc, pyzo uses scintilla, so maybe this is

Re: New Leo edit control

2017-01-24 Thread Edward K. Ream
On Tue, Jan 24, 2017 at 9:21 AM, Edward K. Ream wrote: Start with k.makeMasterGuiBinding. After you are through retching, you > should be able to continue. > ​The essence of the code is that everything should work if the the new widget has a wrapper. So in that sense the

Re: New Leo edit control

2017-01-24 Thread Edward K. Ream
​​ On Mon, Jan 23, 2017 at 7:54 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: Attached is a screen shot, which looks odd because the screen shot > software's omitting the window border. > ​I'm glad you included this. It provides good context for the discussion.​ > >

Re: New Leo edit control

2017-01-24 Thread john lunzer
Really nice work Terry. The most obvious feature that stood out was the "recurse" option. I've long wanted a way to view a node in what I call "edit mode" without creating a separate @edit node and reloading from disk constantly. The downside to an @edit node is that it pollutes the tree and

New Leo edit control

2017-01-23 Thread 'Terry Brown' via leo-editor
On Mon, 23 Jan 2017 13:40:48 -0600 "Edward K. Ream" wrote: > On Mon, Jan 23, 2017 at 11:42 AM, john lunzer > wrote: > > > Of the code editor's I've used code comparison is encouraged within > > a single running application, this allows for fancier things