Re: Rev e2cd63: curses gui ready for *careful* testing

Maybe Leo Textual User Interface (as opposed to "Graphical"). Consonle seems kind of "tekkie". Cheers, Offray On 17/06/17 08:00, Chris George wrote: > A small nit. > > gui = Graphical User Interface > > Using the acronym in reference to a console application is a bit of > stretch given its

Re: Rev e2cd63: curses gui ready for *careful* testing

An updated console-gui guide is on the web. An important code improvement: the Ctrl-Q dialog now presents the options as Yes/No rather than Yes/Cancel. The documentation makes clear that there is no way to cancel Ctrl-Q. Edward -- You received this message because you are subscribed to the

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sun, Jun 18, 2017 at 8:59 AM, lewis wrote: > Here is the Leo-Console alpha User Guide. > ​It's now on the web: http://leoeditor.com/console-gui.html Thanks again, Lewis, for your excellent work. Edward -- You received this message because you are subscribed to

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sun, Jun 18, 2017 at 8:59 AM, lewis wrote: > Here is the Leo-Console alpha User Guide. > ​... You need to specify the Console gui with the command-line option: --gui=console ​Rev 1624092 supports --gui=console, exactly equivalent to --gui=curses. --gui=curses won't

Re: Rev e2cd63: curses gui ready for *careful* testing

> ​(Lewis): ​ ​Warning: If you Tab to the [Quit Leo] button, and press Enter, Leo will quit completely with no dialog box asking if you want to save your changes.​ Fixed at a733586. 4 Lines of code to subclass the Quit button, well over an hour to discover how. The npyscreen class structure is

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sun, Jun 18, 2017 at 8:59 AM, lewis wrote: > Here is the Leo-Console alpha User Guide. > ​Great job. I'll put this on the web today. ​> ​ Warning: If you Tab to the [Quit Leo] button, and press Enter, Leo will quit completely with no dialog box asking if you want

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sat, Jun 17, 2017 at 8:00 AM, Chris George wrote: > A small nit. > > gui = Graphical User Interface > > Using the acronym in reference to a console application is a bit of > stretch given its historical meaning. A gui is everything BUT. > ​Heh. I think we can live with

Re: Rev e2cd63: curses gui ready for *careful* testing

Here is the Leo-Console alpha User Guide. I hope it encourages all the eager users to test out Leo-Console. Feel free to edit and update as required; I am not attached in any way to the structure. Initially I started writing it to help me compare it with Leo and deal with the somewhat clunky

Re: Rev e2cd63: curses gui ready for *careful* testing

A small nit. gui = Graphical User Interface Using the acronym in reference to a console application is a bit of stretch given its historical meaning. A gui is everything BUT. Chris On Sat, Jun 17, 2017 at 3:43 AM, Edward K. Ream wrote: > On Sat, Jun 17, 2017 at 1:30 AM,

Re: Rev e2cd63: curses gui ready for *careful* testing

I've prepared a User Guide for Leo when running the curses gui. It is based upon your comments about the pre-alpha code and some alpha testing :) A few questions: How do you want to refer to Leo running the curses gui? To be honest I don't really like 'Leo curses gui' and think a name which

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sat, Jun 10, 2017 at 7:57 PM, lewis wrote: > Can you confirm which commands you have seen working in the minibuffer? > I'm not sure that the minibuffer is active. > I tried a few without success: > File-Open-by-name > scroll-outline-down-line > ​Those are not likely

Re: Rev e2cd63: curses gui ready for *careful* testing

Can you confirm which commands you have seen working in the minibuffer? I'm not sure that the minibuffer is active. I tried a few without success: File-Open-by-name scroll-outline-down-line Lewis On Thursday, June 8, 2017 at 2:06:23 AM UTC+10, Edward K. Ream wrote: > > > 5. Some commands can

Re: Rev e2cd63: curses gui ready for *careful* testing

Yes, using the mouse I can now select windows without any lock-up. Lewis > -- 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

Re: Rev e2cd63: curses gui ready for *careful* testing

Leo 5.5, Git repo info: branch = master, commit = 3c8f2b9f8ecb Python 3.6.1, PyQt version 5.8.0 Windows 10 AMD64 On Saturday, June 10, 2017 at 11:54:49 PM UTC+10, Edward K. Ream wrote: > > > ​No. I never noticed that. What platform are you using? > -- You received this message because you are

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sat, Jun 10, 2017 at 8:43 AM, lewis wrote: > > Have you noticed that you can navigate between panes using a mouse-click, > but it only works for a maximum of 2, or sometimes 3 clicks? After that you > have to clear the blockage with a Tab, then the mouse-click works

Re: Rev e2cd63: curses gui ready for *careful* testing

Thanks for the Tab tip. Have you noticed that you can navigate between panes using a mouse-click, but it only works for a maximum of 2, or sometimes 3 clicks? After that you have to clear the blockage with a Tab, then the mouse-click works again. Strange! Regards Lewis On Saturday, June 10,

Re: Rev e2cd63: curses gui ready for *careful* testing

On Sat, Jun 10, 2017 at 3:09 AM, lewis wrote: ​> ​ I'm able to edit and add new headlines, but I can't seem to activate a body pane or edit body text. I tried typing 'B', clicking on the body pane. ​ ​ Can you run the instructions by again? You should see the prompts in

Re: Rev e2cd63: curses gui ready for *careful* testing

I'm able to edit and add new headlines, but I can't seem to activate a body pane or edit body text. I tried typing 'B', clicking on the body pane. Can you run the instructions by again? I can confirm if you haven't saved your file, pressing Ctrl-Q displays a Dialog box, with the option to save.

Re: Rev e2cd63: curses gui ready for *careful* testing

On Thu, Jun 8, 2017 at 10:49 PM, Terry Brown wrote: I'm seeing very high CPU usage down arrowing through the tree pane - > fan kicking in and rate of advance of the selected line quite slow - do > you see anything like that? > ​My pc doesn't have a fan ;-)​ You might

Re: Rev e2cd63: curses gui ready for *careful* testing

On Thu, 8 Jun 2017 10:23:06 -0700 (PDT) "Edward K. Ream" wrote: > On Thursday, June 8, 2017 at 7:53:50 AM UTC-5, Edward K. Ream wrote: > > *Warning*: no prompt is made if you quit (Ctrl-Q, etc.) with unsaved > > changes. I'll fix this today. It involves getting npyscreen >

Re: Rev e2cd63: curses gui ready for *careful* testing

Congratulations Edward! It's been a huge work from your side and a pleasure from our side to have you sharing with us the technical challenges and decisions made during the journey! Thanks for sharing! Xavier El 07/06/2017 a las 13:06, Edward K. Ream escribió: Recent work makes the

Re: Rev e2cd63: curses gui ready for *careful* testing

On Thursday, June 8, 2017 at 7:53:50 AM UTC-5, Edward K. Ream wrote: *Warning*: no prompt is made if you quit (Ctrl-Q, etc.) with unsaved > changes. I'll fix this today. It involves getting npyscreen "dialogs" to > work properly. > Recent revs fix this and make other dialogs functional. I

Re: Rev e2cd63: curses gui ready for *careful* testing

On Wednesday, June 7, 2017 at 11:06:23 AM UTC-5, Edward K. Ream wrote: > Recent work makes the cursesGui2 code minimally functional. *Warning*: no prompt is made if you quit (Ctrl-Q, etc.) with unsaved changes. I'll fix this today. It involves getting npyscreen "dialogs" to work properly.

Rev e2cd63: curses gui ready for *careful* testing

Recent work makes the cursesGui2 code minimally functional. Enable with --gui=curses on the command line. All unit tests pass when run using the curses gui, but quite a few tests have been disabled. *Do not assume that the code is safe.* Instead, I recommend testing on files under git