Re: ENB: Curses prototype: phase 2 design and process

On Fri, Apr 21, 2017 at 6:51 AM, john lunzer wrote: > Ahh, I'm sorry to have suggested urwid. I totally forgot about the Linux > only limitation. > ​Not a problem. Getting up to speed with winpdb/rpdb2 makes everything worthwhile. Edward -- You received this message

Re: ENB: Curses prototype: phase 2 design and process

On Friday, April 21, 2017 at 6:24:11 AM UTC-5, Edward K. Ream wrote: In short, urwid doesn't seem to work on Windows, but npyscreen runs > anywhere and can be debugged on Linux with rpdb2 and winpdb. I'd say this > is a good enough resolution to the problem of what curses widgets to use. > At

Re: ENB: Curses prototype: phase 2 design and process

Blasphemy! Haha, jk. I too probably would have recommended pycharm if I were going to go with anything "pro". As much as I try not to give commercial software kudos they've got a good piece of software. It's a shame the debugging experience on Windows isn't more fluid. I'm not sure how long

Re: ENB: Curses prototype: phase 2 design and process

or https://www.jetbrains.com/pycharm/ On Fri, Apr 21, 2017 at 7:11 AM, Kent Tenney wrote: > It might be worth biting the bullet, buying a commercial IDE like > https://wingware.com/ > > > On Fri, Apr 21, 2017 at 6:51 AM, john lunzer wrote: > >> Ahh, I'm

Re: ENB: Curses prototype: phase 2 design and process

It might be worth biting the bullet, buying a commercial IDE like https://wingware.com/ On Fri, Apr 21, 2017 at 6:51 AM, john lunzer wrote: > Ahh, I'm sorry to have suggested urwid. I totally forgot about the Linux > only limitation. > > > On Friday, April 21, 2017 at 7:24:11

Re: ENB: Curses prototype: phase 2 design and process

Ahh, I'm sorry to have suggested urwid. I totally forgot about the Linux only limitation. On Friday, April 21, 2017 at 7:24:11 AM UTC-4, Edward K. Ream wrote: > > On Friday, April 21, 2017 at 5:56:29 AM UTC-5, Edward K. Ream wrote: >> >> >> Ok. Misleading 'help attach' and error message

Re: ENB: Curses prototype: phase 2 design and process

On Friday, April 21, 2017 at 5:56:29 AM UTC-5, Edward K. Ream wrote: > > > Ok. Misleading 'help attach' and error message confused me for awhile. > Sorry, I mis-remembered what I had just done! In the second console, first do: password Then do: attach to get a list of pid's. Then

Re: ENB: Curses prototype: phase 2 design and process

On Friday, April 21, 2017 at 5:47:56 AM UTC-5, Edward K. Ream wrote: This is pretty cool. I actually would prefer not to use the winpdb gui. > At present, I haven't figured out how I might use rpdb2 in the *second* > console. > Ok. Misleading 'help attach' and error message confused me

Re: ENB: Curses prototype: phase 2 design and process

On Friday, April 21, 2017 at 4:19:43 AM UTC-5, Edward K. Ream wrote: So I would like to try urwid on Windows, but neither pudb nor winpdb seem > to work on Windows, due to problems with fctrl on Windows. > Alright. Some real progress. winpdb works well on Leo as follows: 1. In a console,

Re: ENB: Curses prototype: phase 2 design and process

On Friday, April 21, 2017 at 4:19:43 AM UTC-5, Edward K. Ream wrote: > For now, the way forward will be to duplicate the npyscreen code in urwid on Windows. The following code fails with both Python 2 and 3 on Windows: import urwid txt = urwid.Text(u"Hello World") fill =

Re: ENB: Curses prototype: phase 2 design and process

On Friday, April 21, 2017 at 3:58:49 AM UTC-5, Edward K. Ream wrote: Yesterday was, mostly, a long digression into portability, installation and > debugging issues. Not fun. These diversions are a great way to kill > enthusiasm. > Importing urwid works in windows with 2/3. On Linux, urwid is

Re: ENB: Curses prototype: phase 2 design and process

On Thursday, April 20, 2017 at 6:38:33 AM UTC-5, Edward K. Ream wrote: > > On Thursday, April 20, 2017 at 6:21:05 AM UTC-5, Edward K. Ream wrote: >> >> >> Rev e1e4e48 completes part A using an npyscreen.NPSApp class and >> associated MultiLineEditableBoxed widget. It looks like npyscreen has

Re: ENB: Curses prototype: phase 2 design and process

On Thursday, April 20, 2017 at 6:09:19 PM UTC-5, Terry Brown wrote: In linux at least there are plenty of ways of separating the trace > output from the screen output. Yes, I know that. On Linux, but not windows, the console is restored after curses exits, so any traces are available later,

Re: ENB: Curses prototype: phase 2 design and process

On Thu, 20 Apr 2017 17:24:19 -0500 "Edward K. Ream" wrote: > On Thu, Apr 20, 2017 at 11:31 AM, Kent Tenney > wrote: > > > possibly logging would help? > > https://pypi.python.org/pypi/devpy > > > > ​I doubt it. The solution, imo, is to use pudb (linux)

Re: ENB: Curses prototype: phase 2 design and process

On Thu, Apr 20, 2017 at 11:31 AM, Kent Tenney wrote: > possibly logging would help? > https://pypi.python.org/pypi/devpy > ​I doubt it. The solution, imo, is to use pudb (linux) or winpdb (windows). I got sidetracked with other issues. I'll attempt one or the other working

Re: ENB: Curses prototype: phase 2 design and process

possibly logging would help? https://pypi.python.org/pypi/devpy provides logging with one line of code, maybe the useful message gets logged before the terminal is lost ... On Thu, Apr 20, 2017 at 10:38 AM, Edward K. Ream wrote: > On Thu, Apr 20, 2017 at 8:12 AM, john

Re: ENB: Curses prototype: phase 2 design and process

On Thu, Apr 20, 2017 at 8:12 AM, john lunzer wrote: I realize you're doing this as an exercise but if you're getting frustrated > with npyscreen (I also think the docs are a little sparse) there is always > urwid, which I think has much better documentation. It's also got all

Re: ENB: Curses prototype: phase 2 design and process

I realize you're doing this as an exercise but if you're getting frustrated with npyscreen (I also think the docs are a little sparse) there is always urwid, which I think has much better documentation. It's also got all the widgets necessary for Leo. Also, again, a good example of a full

Re: ENB: Curses prototype: phase 2 design and process

On Thursday, April 20, 2017 at 6:21:05 AM UTC-5, Edward K. Ream wrote: Remember, to run the app, use the --gui=curses command-line option. To quit > the app, click on the ok button in the lower right corner, then hit return. > Also, when not editing, tab moves between widgets, and shift-tab

Re: ENB: Curses prototype: phase 2 design and process

On Thursday, April 20, 2017 at 6:21:05 AM UTC-5, Edward K. Ream wrote: > > > Rev e1e4e48 completes part A using an npyscreen.NPSApp class and > associated MultiLineEditableBoxed widget. It looks like npyscreen has what > we need, including a tree widget. > One more improvement: the various

Re: ENB: Curses prototype: phase 2 design and process

On Thursday, April 20, 2017 at 3:26:31 AM UTC-5, Edward K. Ream wrote: 2. The cursesGui ctor set self.consoleOnly = True, which tells g.trace to > use print immediately for traces instead of queuing up traces for Leo's log > window. Today's work will start with making things work when >

ENB: Curses prototype: phase 2 design and process

This post discuss the next phase of curses gui prototype. This is an Engineering Notebook post, of interest only to devs. This second phase is a crucial intermediate step. It should be doable in a few hours. *Phase 1 summary*1. cursesGui2.py contains three functional classes CursesGui,