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 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 control. That gives you diffs and easy reverts.
Here is a /partial /list of limitations of the code:
1. Only simple control characters are supported. Ctrl-S will work,
Atl-S, Ctrl-Shift-S etc. will not. This is a limitation of the curses
module and can not be fixed.
2. Shift arrows are not (yet) supported. *npyscreen apparently does
not support selection ranges in text! * Subclasses could do so, but
that would be non-trivial.
3. The body pane changes in sync with the outline pane. but editing
the log or body pane is a bit strange. You switch between tabs with
tab or shift-tab. To actually edit, you have to edit edit mode, as
shown on the on-screen prompts. See the screen shot. Deleting lines
of body text must be done /outside/ of edit mode. Doing a more Leonine
job is basically out of the question: it would require a complete
rewrite of the base classes.
4. Cut/paste is theoretically supported, but in the absence of
selections only paste might work. And paste may work only in limited
contexts...
5. Some commands can be run from the minibuffer, but there is no tab
completion and no indication of what the correct command names are.
6. Dialogs don't work well, or at all. They may (temporarily?)
overwrite the screen.
7. You must resize your console to be big enough. Otherwise, Leo will
crash on startup.
*Summary*
The present code /might/ just barely be useful, but there are no
guarantees of any kind.
This is pre-alpha code. Data loss is a real possibility. You *must* be
prepared to recover from data loss.
I am not the best tester, because I do not have an actual need for
this code. It's up to real users to report their experiences and
problems. I will be willing to add features, but only if a) you really
need them and b) there are no obvious workarounds.
I have spent almost two months on the project. I will fix major
problems, but I am not promising to do more than that.
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 leo-editor+unsubscr...@googlegroups.com
<mailto:leo-editor+unsubscr...@googlegroups.com>.
To post to this group, send email to leo-editor@googlegroups.com
<mailto:leo-editor@googlegroups.com>.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Libre de virus. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
