Re: The LeoWapp prototype has succeeded!
Looking forward to checking it out. Congratulations and thanks for your hard work on this project! Rob... On Saturday, December 1, 2018 at 9:51:50 AM UTC-5, Edward K. Ream wrote: > > Rev c74341 demonstrates that Leo can keep the body pane in sync with Leo's > internal data structures. This was the last real hurdle. The LeoWapp > prototype has succeeded! > > In the end, detecting changes to the body pane was dead easy, for a > shocking reason. When the flx_body.on_key_press reaction gets called, the > JS editor (either ace or CodeMirror) has *already *updated its contents! > > In effect, the on_key_press reaction *is* the long-sought-after "on > changed" reaction!!! > > So the on_key_press reaction can *immediately *call a PY side action to > update Leo's data structures! The key handler does *not* need to know > how the JS editor has updated its text. Similarly, an on_click reaction > gets called *after* the JS editor updates the insert point and selection. > > Some key and click related work remains: > > 1. The key emitter calls should_be_leo_key() to determine whether Leo > should handle the key instead of the JS emitter. If so, the emitter calls > e.preventDefault(). I have verified that this will suffice, but > should_be_leo_key must do something besides return False ;-) > > 2. Both the on_key_press and on_click reactions should call an app_wrapper > action to update Leo's model of the body pane. > > *Summary* > > Today leoflexx.py passed its last essential test. The prototype of > LeoWapp has now, for sure, succeeded. > > 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. 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.
new module: leo/core/leoFastRedraw.py
This module contains the fast-redraw code that used to be in leoflexx.py. It deserves to be in Leo's core because it does not in any way depend on which gui is in effect. 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. 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.
Re: 3fd655 (devel): leoflexx.py supports --gui=browser and also runs stand-alone
On Sunday, December 2, 2018 at 11:46:43 AM UTC-6, Edward K. Ream wrote: > > From the devel branch, you can run Leo with the gui browser this way: > > python launchLeo.py --no-splash --gui=browser %* > > Later revs allow you to specify the particular browser: --gui=browser:firefox-browser You can use '-' instead of ':'. Also, the --no-plugins command-line option is a good idea. It reduces clutter in the log. 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. 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.
3fd655 (devel): leoflexx.py supports --gui=browser and also runs stand-alone
>From the devel branch, you can run Leo with the gui browser this way: python launchLeo.py --no-splash --gui=browser %* *Note*: %* specifies any remaining args on Windows. Modify as you like for Ubuntu, etc. You can continue to run leoflexx.py in stand-alone mode: python leoflexx.py I'll continue to do most work in the skeleton branch, updating devel from time to time. I did the latest work from devel for my own convenience. To do when using the --gui=browser option: - Suppress plugins. - Suppress startup messages. The signon in the browser log should suffice. There are many items on the leoflexx.py to-do list. I'll copy them to the leoflexx.py docstring soon. 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. 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.
Re: edit-pane-csv separator
On Fri, 30 Nov 2018 06:58:59 -0800 (PST) Josef wrote: > Hi Terry, > > after using edit-pane-csv for some time now, I have one big wish > left: it would be great if Leo could remember the settings for each > file, at least for @clean nodes. Ideally the csv pane would stay open > for these nodes. Would a button that toggled the pane work? I can't remember if the code has an easy way to set initial settings, but perhaps per-node settings could be saved in p.v.u. Cheers -Terry > I have many csv files around, which I need to maintain manually on a > regular basis, so it would be nice if Leo could remember the settings > for each of these files, and it would be even better if I would not > have to run the command edit-pane-csv on each file every time after I > closed the associated Leo file. > > Cheers - Josef > > On Friday, August 10, 2018 at 5:38:37 PM UTC+2, Terry Brown wrote: > > > > On Fri, 10 Aug 2018 08:14:53 -0700 (PDT) > > Josef > wrote: > > > > > Hi Terry > > > > > > I tried > > > > > > Leo 5.7.4 devel, build 20180807122609 > > > > > > and it did not work right away with a .latex file. It seems to > > > get confused by the @language latex in the first line. It worked > > > when I removed it. > > > > > > It would be nice if it would ignore leo directives. > > > > Hmm, it doesn't pay any attention to leo directives, and just > > defaults to ',' CSV mode. Not sure what was going on there. > > > > > Another quirk is, that every line needs to have the same number > > > of separators, but particularly when editing latex tables by hand > > > one does not always enter all cells if they are empty anyway. > > > This probably is a limitation of the Python CSV library, though. > > > > True... hmm, the design is that a series of lines with the same > > number of separators is what *defines* a table. Probably > > reasonable for CSV, but I can see the issue with LaTeX. > > > > The simplest way I can think of addressing that would be some way > > to normalize the number of delimiters in a table, either have the > > user select the whole table or incrementally bring in lines from > > above / below the table, adding empty cells to them. > > > > But if I remember LaTeX tables, that will impact line drawing, > > "1 & 2 \\" vs "1 & 2 & & \\" in a four column table for example, > > the first leaves the rest of the line blank whereas the second > > displays empty cells, if you're drawing lines between cells that > > is. I think. > > > I think it would also be nice if it could figure out the > > > separator by itself and start up with a good suggestion, similar > > > to the "sniffer" tool in the CSV module. > > > > Might be doable, although I'm guessing that usually you'd only need > > to change it once per session, and having it guess too often might > > make it less flexible in terms of editing different table types in > > the same node etc. I did think of adding a presets dropdown for > > CSV / tab / LaTeX / pipe etc. > > > > > That all said, thank you very much for this command. It makes my > > > life a lot easier. > > > > Glad to hear it. > > > > Cheers -Terry > > > -- 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.
skeleton branch merged into devel
All future work on LeoWapp will be done in devel. Only leo/plugins/leoflexx.py was added. I did not do a full merge of skeleton into devel so as to minimize the risk of unintended consequences. Instead, I merely checked out leoflexx.py from skeleton. As a safety feature, leoflexx.py raises an alert on startup, warning that LeoWapp is pre-alpha code. 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. 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.
Recuperation and schedule
I am in recuperation mode after finishing the last essential piece of the LeoWapp puzzle. I didn't realize how stressed I was until the pressure was off. I have reduced my programming and gotten more sleep. I'll be playing the piano more and getting more exercise. I already feel more refreshed. I'll be taking one or more vacations during the upcoming holidays, so there remains only about two more week of work on Leo in 2018. My plans are to finish leowapp.py and convert it to a proper Leo gui. This will take a few hours, spread over several days or longer. *Summary* I'll be dialing back the intensity of work while I recuperate. This rhythm of work and rest is essential for my health. I expect to be fully fit for programming again after the holidays. 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. 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.
Re: The LeoWapp prototype has succeeded!
On Sat, Dec 1, 2018 at 9:14 PM Xavier G. Domingo (xgid) wrote: > Let me be the first to give you my most sincere congratulations!! > Thanks. It is appreciated. > > You've made an excellent work in this project and it opens new and really > exciting opportunities for the future of Leo and the interactive data and > PIM worlds altogether! > > Some serious health issues have prevented me from being more involved with > Leo in the recent months, but I'm quite recovered now and I hope to be able > to make my contribution. > Glad to have you back with us. We have only just begun to explore what is possible. 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. 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.
