Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wed, Jul 16, 2014 at 9:14 AM, Edward K. Ream wrote: > I just upped code that starts to support @recovery trees in each per-file > @data tree: Rev 9a082a8... fixes several problems. All tests pass, including some by-hand tests of real-world scenarios. The only remaining items with this proj

Re: New persistence code ready for testing!

2014-07-16 Thread 'Terry Brown' via leo-editor
On Wed, 16 Jul 2014 11:41:37 -0700 (PDT) "Edward K. Ream" wrote: > > > On Wednesday, July 16, 2014 9:22:03 AM UTC-5, Edward K. Ream wrote: > > > I do notice that the icon box has a black border, indicating that > > the > @auto node is dirty. That's a recent problem. I'll fix it asap. > > T

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wednesday, July 16, 2014 9:22:03 AM UTC-5, Edward K. Ream wrote: > I do notice that the icon box has a black border, indicating that the @auto node is dirty. That's a recent problem. I'll fix it asap. This looks like an interaction problem with the bookmarks.py plugin. Not exactly sure

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wed, Jul 16, 2014 at 12:01 PM, Kent Tenney wrote: > @persistent seems to be Leo talking to itself. Hehe. Well, almost all data in Leo is in a node. The only exceptions are uA's. > - what is the reason for human readable? it's unclear what a human > can use the @persistent tree for other th

Re: New persistence code ready for testing!

2014-07-16 Thread Kent Tenney
On Wed, Jul 16, 2014 at 11:48 AM, Edward K. Ream wrote: > On Wed, Jul 16, 2014 at 9:46 AM, Kent Tenney wrote: > >> I was wondering if they are useful in user space. They seem like Leo >> bookkeeping. Presumably the user can break persistence by editing in that >> tree? > > Leo has *lots* of node

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wed, Jul 16, 2014 at 9:46 AM, Kent Tenney wrote: > I was wondering if they are useful in user space. They seem like Leo > bookkeeping. Presumably the user can break persistence by editing in that > tree? Leo has *lots* of nodes that are bookkeeping, including all settings nodes, @button node

Re: New persistence code ready for testing!

2014-07-16 Thread Kent Tenney
On Wed, Jul 16, 2014 at 9:14 AM, Edward K. Ream wrote: > On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney wrote: >> First impressions: >> >> - the @auto node icons indicate they are clones > > Only if they are clones :-) No, all of them, none are clones. Sounds like you're already on this. > >> - I

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wednesday, July 16, 2014 9:14:59 AM UTC-5, Edward K. Ream wrote: > > On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney wrote: > > First impressions: > > > > - the @auto node icons indicate they are clones > > Only if they are clones :-) > I do notice that the icon box has a black border, indic

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney wrote: > First impressions: > > - the @auto node icons indicate they are clones Only if they are clones :-) > - I'm not sure why the @persistence tree is visible, can it be used for > something? Maybe somehow useful in resolving issues? @persistence

Re: New persistence code ready for testing!

2014-07-16 Thread Kent Tenney
First impressions: - the @auto node icons indicate they are clones - I'm not sure why the @persistence tree is visible, can it be used for something? Maybe somehow useful in resolving issues? On Wed, Jul 16, 2014 at 8:29 AM, Jacob Peck wrote: > > On 7/16/2014 8:59 AM, Edward K. Ream wrote: >> >

Re: New persistence code ready for testing!

2014-07-16 Thread Jacob Peck
On 7/16/2014 8:59 AM, Edward K. Ream wrote: the simplest thing that could possibly work Ockham's Razor at work! Good :) Nice work, Edward. Keep it up! -->Jake -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Wednesday, July 16, 2014 2:16:45 AM UTC-5, Edward K. Ream wrote: > > On Tue, Jul 15, 2014 at 8:17 PM, 'Terry Brown' via leo-editor > wrote: > > ...it may be best simply to require an exact match, and fall back on creating nodes to hold uA's in case no match is found. As of the latest rev,

Re: New persistence code ready for testing!

2014-07-16 Thread Edward K. Ream
On Tue, Jul 15, 2014 at 8:17 PM, 'Terry Brown' via leo-editor wrote: >> > It seems that the uA persisting code really should try and save uA >> > info on nodes it can't match... I agree. > I guess it's a question of what the uA data is. No. It's simply a question of where to put restored node

Re: New persistence code ready for testing!

2014-07-15 Thread 'Terry Brown' via leo-editor
On Tue, 15 Jul 2014 17:50:21 -0500 "Edward K. Ream" wrote: > On Tue, Jul 15, 2014 at 7:04 AM, 'Terry Brown' via leo-editor > > > It seems that the uA persisting code really should try and save uA > > info on nodes it can't match... > > > So what I was thinking was that the orphan nodes could ha

Re: New persistence code ready for testing!

2014-07-15 Thread Edward K. Ream
On Tue, Jul 15, 2014 at 7:04 AM, 'Terry Brown' via leo-editor > It seems that the uA persisting code really should try and save uA info on > nodes it can't match... > So what I was thinking was that the orphan nodes could have an UNL (in their uAs :-) which points to the best guess imported node

Re: New persistence code ready for testing!

2014-07-15 Thread 'Terry Brown' via leo-editor
On Tue, 15 Jul 2014 04:39:06 -0700 (PDT) "Edward K. Ream" wrote: > > On Monday, July 14, 2014 2:00:48 PM UTC-5, Edward K. Ream wrote: > > > > 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

Re: New persistence code ready for testing!

2014-07-15 Thread Edward K. Ream
On Monday, July 14, 2014 2:00:48 PM UTC-5, Edward K. Ream wrote: > > 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,

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

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