The second phase of the pyzo project is complete!

The pyzo_in_leo plugin now creates *all* of pyzo's docks, including a new Editors dock. This is a huge milestone in the project. A new, simple, strategy was the key. In another post I said: QQQ I shall replace start_pyzo_in_leo with the following functions in the plugin: - pyzo_start: a copy

Re: The shifting sands of positions in face of multiple outline modifications

Edward, Thanks a lot. See below: On Fri, Aug 16, 2019 at 10:10 AM Edward K. Ream wrote: [...] > As Vitalije says" > > - Adding (or deleting) the last sibling will not change the position of > any existing node. This includes adding/deleting the last top-level node. > - If you can recast your

Re: The shifting sands of positions in face of multiple outline modifications

Vitalije, Thanks a lot for all the code. It gives me a huge head start seeing a vnode version of the same position code I wrote. I can already tell from looking at your code that I don't understand positions and vnodes at all. Maybe while trying to adapt your code, I will be enlightened. Hopefully

Re: What's wrong with render plugin?

On Friday, August 16, 2019 at 9:00:07 AM UTC-5, Edward K. Ream wrote: > I have just created #1287 for this. Fixed at rev 91ac803 in devel. There are some subtleties involved. See the last comment in #1287. Please reopen if necessary. E

Re: The shifting sands of positions in face of multiple outline modifications

On Fri, Aug 16, 2019 at 6:42 AM Brian Theado wrote: What are the rules which can be followed in order to safely deal with > positions during outline modification. *Edward or Vitalije or anyone > else, do you know?* > As Vitalije says" - Adding (or deleting) the last sibling will not change the

Re: What's wrong with render plugin?

On Fri, Aug 16, 2019 at 7:26 AM Rob wrote: > I see the same thing: > >- A node w/ @rst header renders as expected. >- Child nodes of this node do not. >- If a parent node on these have an `@language rest`, then all child >nodes render as expected. > > That was as I had intended.

Re: The shifting sands of positions in face of multiple outline modifications

moveToTopAndCloneToAtDay should be like: def moveToTopAndCloneToAtDay(c, p): """ Move the node identified by position p to the first child of an ancestor @ftlist node and also clone it to a sibling @day node with date matching today's date """ ftlist = findFtlis

Re: The shifting sands of positions in face of multiple outline modifications

moveOrCloneToTop should be something like: def moveOrCloneToTop(p, ftlist): """ If p or a clone of p is already a direct child of ftlist, then move the node to the first child of ftlist. Otherwise, create a clone of p and move the clone """ if ftlist.v not in p.v.pare

Re: The shifting sands of positions in face of multiple outline modifications

Outline modifications that do not invalidate positions are: 1. appending nodes at the end of children with for example: p1 = p.insertAsLastChild() # now p is still valid 2. deleting the last child But for your use case I would probably use v nodes directly. import time def clone

Re: What's wrong with render plugin?

I see the same thing: - A node w/ @rst header renders as expected. - Child nodes of this node do not. - If a parent node on these have an `@language rest`, then all child nodes render as expected. I don't know what that looked like in previous versions of Leo as I didn't use @rst mu

Re: ENB: next steps for pyzo-in-leo

On Tuesday, August 13, 2019 at 6:22:23 AM UTC-5, Edward K. Ream wrote: Melding pyzo's config code with Leo's remains, by far, the most important > and challenging part of the pyzo-in-leo project. > *Status* 1. I added a call to callLater(pyzo.shells.addShell) at the end of make_all_docks. Thi

The shifting sands of positions in face of multiple outline modifications

I'm writing some commands for myself to help manage lists of things. I will bind the commands to keystrokes which I will be able to use to quickly add new items and highlight which items I've recently worked on. These commands will also create clones inside "@day " (and automatically create the @da