Re: New persistence code ready for testing!

2014-07-14 Thread Edward K. Ream
On Mon, Jul 14, 2014 at 11:49 AM, 'Terry Brown' via leo-editor wrote: > I asked a vague question about the status of vc.find_absolute_unl_node > and vc.find_position_for_relative_unl the other day, what I meant was, > what do they do that g.recursiveUNLFind doesn't? Thanks for this reminder. I'

Re: New persistence code ready for testing!

2014-07-14 Thread 'Terry Brown' via leo-editor
On Mon, 14 Jul 2014 11:29:19 -0500 "Edward K. Ream" wrote: > On Mon, Jul 14, 2014 at 10:46 AM, Kent Tenney > wrote: > > >> Whew! I'm glad we're on the same page now :-) > > > Indeed, hate to see fisticuffs on this list [-; > > Yeah, I was about to give you a phone call ;-) > > > Initial tes

Re: New persistence code ready for testing!

2014-07-14 Thread Kent Tenney
On Mon, Jul 14, 2014 at 11:29 AM, Edward K. Ream wrote: > On Mon, Jul 14, 2014 at 10:46 AM, Kent Tenney wrote: > >>> Whew! I'm glad we're on the same page now :-) > >> Indeed, hate to see fisticuffs on this list [-; > > Yeah, I was about to give you a phone call ;-) > >> Initial test is REALLY e

Re: New persistence code ready for testing!

2014-07-14 Thread Edward K. Ream
On Mon, Jul 14, 2014 at 10:46 AM, Kent Tenney wrote: >> Whew! I'm glad we're on the same page now :-) > Indeed, hate to see fisticuffs on this list [-; Yeah, I was about to give you a phone call ;-) > Initial test is REALLY exciting, in addition to complete support for the > 'choices' stuff,

Re: New persistence code ready for testing!

2014-07-14 Thread Edward K. Ream
On Mon, Jul 14, 2014 at 10:41 AM, 'Terry Brown' via leo-editor wrote: > So how hard does the new code try to recover from breakage? At present, Leo attempts no error recovery. > Does it use the new indexed UNLs to fall-back on position index when > headlines fail? I have no idea what you mean

Re: New persistence code ready for testing!

2014-07-14 Thread Kent Tenney
On Mon, Jul 14, 2014 at 10:11 AM, Edward K. Ream wrote: > On Mon, Jul 14, 2014 at 10:06 AM, Kent Tenney wrote: > >> I think I see the problem. >> > Such links should persist *provided* you don't change the outline > structure > (including headlines) of the @auto file outside of Leo.

Re: New persistence code ready for testing!

2014-07-14 Thread 'Terry Brown' via leo-editor
On Mon, 14 Jul 2014 06:48:18 -0700 (PDT) "Edward K. Ream" wrote: > As of rev 25101ddf3b0c... Leo now saves and restores clone links and > uA's in @auto trees! > > For example, use the todo plugin to add an icon to a node in an @auto > file. Save the file and reload. The icon will still be the

Re: New persistence code ready for testing!

2014-07-14 Thread Edward K. Ream
On Mon, Jul 14, 2014 at 10:06 AM, Kent Tenney wrote: > I think I see the problem. > Such links should persist *provided* you don't change the outline structure (including headlines) of the @auto file outside of Leo. > I read this as changing outside Leo breaking the import, not just th

Re: New persistence code ready for testing!

2014-07-14 Thread Kent Tenney
On Mon, Jul 14, 2014 at 9:52 AM, Edward K. Ream wrote: > On Mon, Jul 14, 2014 at 9:22 AM, Kent Tenney wrote: > >>> Such links should persist *provided* you don't change the outline structure >>> (including headlines) of the @auto file outside of Leo. > >> This is a show-stopper for me, and probab

Re: New persistence code ready for testing!

2014-07-14 Thread Edward K. Ream
On Mon, Jul 14, 2014 at 9:22 AM, Kent Tenney wrote: >> Such links should persist *provided* you don't change the outline structure >> (including headlines) of the @auto file outside of Leo. > This is a show-stopper for me, and probably evidence of my outlier status. > I'm as likely to work in vi

Re: New persistence code ready for testing!

2014-07-14 Thread Kent Tenney
On Mon, Jul 14, 2014 at 8:48 AM, Edward K. Ream wrote: > As of rev 25101ddf3b0c... Leo now saves and restores clone links and uA's in > @auto trees! > > For example, use the todo plugin to add an icon to a node in an @auto file. > Save the file and reload. The icon will still be there. > > Ditto

Re: leoPersistence.py: persistent gnx's and uA's for @auto etc.

2014-07-14 Thread Edward K. Ream
On Mon, Jul 14, 2014 at 8:14 AM, Kent Tenney wrote: > I'm afraid this level of detail is beyond me. It's hard to understand without digging into the code. But read on... > I don't understand Leo looking for nodes, I would expect the @auto parsing > component to be asking if a node had been see

New persistence code ready for testing!

2014-07-14 Thread Edward K. Ream
As of rev 25101ddf3b0c... Leo now saves and restores clone links and uA's in @auto trees! For example, use the todo plugin to add an icon to a node in an @auto file. Save the file and reload. The icon will still be there. Ditto for clones links for between node a node C inside an @auto file a

Re: leoPersistence.py: persistent gnx's and uA's for @auto etc.

2014-07-14 Thread Kent Tenney
I'm afraid this level of detail is beyond me. I don't understand Leo looking for nodes, I would expect the @auto parsing component to be asking if a node had been seen previously, something like prior = found_in_auto_node_UA(): if prior is not None: restore_prior_attrs(prior) else: reviewin

Re: leoPersistence.py: persistent gnx's and uA's for @auto etc.

2014-07-14 Thread Edward K. Ream
On Sun, Jul 13, 2014 at 5:55 AM, Edward K. Ream wrote: > Yesterday I started work on leoPersistence.py. It is a re-imagining of > leoViews.py. Work is going well: leoPersistence.py is a big collapse in complexity compared with leoViews.py. gnx's can now be restored in the easy case. The **ha