Re: ENB: rethinking Model/View/Controller split in Leo

On Wed, May 6, 2020 at 1:26 PM David Szent-Györgyi wrote: > Tkinter and enhancements for current Python are far more capable than the plain Tkinter in which Edward wrote the GUI that was part of Leo 4.2 and Leo 4.3. Thanks for this update. Vitalije recently created a prototype in Tk, so there

Fwd: [qubes-users] Removing Template VMs?

Am Dienstag, 5. Mai 2020 20:39:52 UTC+2 schrieb viktor@gmail.com: > Am Montag, 4. Mai 2020 22:25:13 UTC+2 schrieb dhorf-hfr...@hashmail.org: >> >> On Mon, May 04, 2020 at 12:28:27PM -0700, viktor@gmail.com wrote: >> > If I'd like to remove any old & **unused** Template VMs (e.g. Debian

Re: Problems with abbreviations with non-english keyboards

The usual way seems to be a shifted comma and period. I suggest looking at https://en.m.wikipedia.org/wiki/German_keyboard_layout You're just able to get the key symbols as the OS hands them out, and I presume someone with a German keyboard will utilize it the way they have for years, making the

Problems with abbreviations with non-english keyboards

I am finally getting around to #1563 . To do this I started a test file with --trace=keys. This clearly shows what is happening. The problem is what to do next. In Windows 10 I switched to the German keyboard and typed `alp;;` on my

Re: ENB: rethinking Model/View/Controller split in Leo

> >>> I've never had a problem with the term as used in Leo. To me, it > conveys 1) that a (clone) node looks different from another because it > appears in a different place, but 2) if you look closer, it's exactly the > same inside. > > I'm not saying that the term that the term should be

Re: ENB: rethinking Model/View/Controller split in Leo

>>> I've never had a problem with the term as used in Leo. To me, it conveys >>> 1) that a (clone) node looks different from another because it appears in a >>> different place, but 2) if you look closer, it's exactly the same inside. I'm not saying that the term that the term should be

Re: ENB: rethinking Model/View/Controller split in Leo

Actually, Zoom does let you share your screen. The host can let any participant take control, and they can share their screen. On Wednesday, May 6, 2020 at 6:20:59 PM UTC-4, tfer wrote: > > > In a week or so, I'd like to do some teleconferencing with Edward, (not > Zoom, but something with the

Re: [qubes-users] Removing Template VMs?

looks like posted to wrong mailing list Viktor :) -- 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 view this discussion

Removing Template VMs from Qubes OS!

Hello Matt & Leo Community, Am Do., 7. Mai 2020 um 02:14 Uhr schrieb Matt Wilkie : > looks like posted to wrong mailing list Viktor :) > @Matt Wilkie : Thanks for making me aware of my mistake. @Leo's Community : Now that I've made that 'mistake', I'd like to use it as an opportunity to ask

Re: Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

hmmm, not sure what's going on here. How about try adding a new file that will have no prior history. It can be a blank do nothing thing that we remove later. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Push to Leo Repo Failed with error:Protected branch update failed for refs/heads/devel.

Matt, thank you for the setting me up to contribute to the Leo repo. This finally got me past the problem with my password not getting me access. On my first attempt to push viewrendered3, after merging I got this error: Writing objects: 100% (117/117), 48.58 KiB | 3.04 MiB/s, done. Total

Re: ENB: rethinking Model/View/Controller split in Leo

> > In a week or so, I'd like to do some teleconferencing with Edward, (not >> Zoom, but something with the ability to share computer screens), so I can >> do a show and tell on some of the stuff in Leo I'm working on. >> >> Actually, Zoom does let you share your screen. The host can let any

Re: ENB: rethinking Model/View/Controller split in Leo

The "Clone" terminology used in Leo is also used in some 2d and 3d graphical design software among others, in the same manner: A 'live' reference to an object that will change in real-time... Just thought I'd make this fact known to people reading this thread :) On Wednesday, May 6, 2020 at

Re: Thoughts about the mvc prototype

On Tue, May 5, 2020 at 12:25 PM vitalije wrote: I am glad you like it. The issue with cloning top levels is fixed in > 1edad92fe9b8cd. It was caused by iter_all_v_items which didn't yield > anything when v is c.hiddenRootNode. Now it checks for this condition and > yields only rootItem. >

Re: ENB: rethinking Model/View/Controller split in Leo

On Sunday, May 3, 2020 at 4:11:48 PM UTC-5, vitalije wrote: in this prototype all those outline operations are made at the same time in > both tree widget data-model and in v-nodes. This eliminates need for > synchronization between these two models. No need for c.redraw_after..., > c.redraw,

Re: ENB: rethinking Model/View/Controller split in Leo

On Sun, May 3, 2020 at 5:12 PM SegundoBob wrote: several months ago, I concluded that Leo-Editor positions are a very bad > idea and that using GNX's instead would be much simpler and much more > robust. > I think that's an overstatement. Scripts are free to use either vnodes or positions as

Re: ENB: rethinking Model/View/Controller split in Leo

On Sun, May 3, 2020 at 11:23 PM Thomas Passin wrote: About clones, we always talk about cloning nodes, but it seems to me that > what actually gets cloned is an entire subtree > Correct. > I'm not sure how a subtree is currently modeled in Leo. > This has a long history. The result of this

Re: ENB: rethinking Model/View/Controller split in Leo

On Wed, May 6, 2020 at 7:32 AM vitalije wrote: > The tree-refresh branch is not finished and some operations like this one doesn't work. But the essence of the applied algorithm is correct. Alright. I'll take a look at the code without cloning it :-) Edward -- You received this message

Re: ENB: rethinking Model/View/Controller split in Leo

I've expressed before that I feel that the use of the word "clone", does not really capture what we are doing here, in fact, due to its use in biology, it leads to some incorrect thinking about what is going on. In biology, a clone is a separate entity with its own life-cycle, they have the

Re: ENB: rethinking Model/View/Controller split in Leo

On Wednesday, May 6, 2020 at 6:01:31 AM UTC-5, Edward K. Ream wrote: > Clones are well defined only in a DAG. Similarly, "outline order" is well defined only in a DAG. Perhaps I should say that clones are not *uniquely* or *intuitively *defined in general graphs. We could go down a rabbit hole

Re: Thoughts about the mvc prototype

> > I am willing to work on tests if you are willing to share the programming. > Of course I am. > Creating full coverage unit tests might be easier if running the prototype > without any arguments created an empty outline. The necessary changes are > straightforward. I can push the

Re: ENB: rethinking Model/View/Controller split in Leo

On Sunday, May 3, 2020 at 4:11:48 PM UTC-5, vitalije wrote: *What about user scripts that modify outline?* > > User scripts should work without any modification. They can freely modify > outline using the standard Position class or even directly manipulating > v-nodes. This will certainly

Re: ENB: rethinking Model/View/Controller split in Leo

> > > I checked out tree-refresh, then attempted to clone qt_tree.py: > > Traceback (most recent call last): > > File "c:\leo.repo\leo-editor\leo\core\leoCommands.py", line 2282, in > executeAnyCommand > return command(event) > > File "c:\leo.repo\leo-editor\leo\core\leoGlobals.py", line

Re: Thoughts about the mvc prototype

On Wed, May 6, 2020 at 6:50 AM vitalije wrote: >> I am willing to work on tests if you are willing to share the programming. > Of course I am. Thanks. First, it's time to fix #1563. > I would like to at least have the ability to run it using an existing > outline. It might be best if the

Re: ENB: rethinking Model/View/Controller split in Leo

On Wednesday, May 6, 2020 at 12:51:50 PM UTC+2, Edward K. Ream wrote: > > On Sunday, May 3, 2020 at 4:11:48 PM UTC-5, vitalije wrote: > > in this prototype all those outline operations are made at the same time >> in both tree widget data-model and in v-nodes. This eliminates need for >>

Re: ENB: rethinking Model/View/Controller split in Leo

On Wed, May 6, 2020 at 7:17 AM vitalije wrote: >> I don't mind if c.redraw becomes a do-nothing. I just want to know how it's going to work. For outline modifications initiated by scripts we will have to redraw the > outline. To make it quick I plan to use diff algorithm similar to one I >

Re: ENB: rethinking Model/View/Controller split in Leo

On Wed, May 6, 2020 at 9:37 AM 'tfer' via leo-editor < leo-editor@googlegroups.com> wrote: I've expressed before that I feel that the use of the word "clone", does > not really capture what we are doing here, in fact, due to its use in > biology > Hmm. In the Leo world the term "clone" is a term

Re: ENB: rethinking Model/View/Controller split in Leo

On Monday, May 4, 2020 at 8:23:17 AM UTC-4, Edward K. Ream wrote: > > Leo does not support a tk gui. It hasn't for at least a decade. See > leoPlugins.leo#Plugins-->Gui. > > It's possible to run tk code from Leo, but that is another matter entirely. > The Leo distributions had a virtue that is

Re: ENB: rethinking Model/View/Controller split in Leo

On Wednesday, May 6, 2020 at 1:26:08 PM UTC-4, Edward K. Ream wrote: > > On Wed, May 6, 2020 at 9:37 AM 'tfer' via leo-editor < > leo-e...@googlegroups.com > wrote: > > I've expressed before that I feel that the use of the word "clone", does >> not really capture what we are doing here, in fact,

Re: ENB: rethinking Model/View/Controller split in Leo

On Wednesday, May 6, 2020 at 8:21:59 AM UTC-5, Edward K. Ream wrote: >> I would still recommend that p.clone and other methods for model modifications get redirected to tree.clone_node, tree.move_node_up... > I have a queasy feeling about this. It would seem to imply major changes to the