On Tue, Nov 26, 2013 at 7:45 AM, Jacob Peck <[email protected]> wrote:


> But Leo already *has* a caching mechanism.  Why not use it?!? This could
>> speed up @shadow dramatically.
>>
>>  Would such a scheme still allow .leo outlines and external files to
> exist in a VCS or cloud-synced storage?
>

Sure.  It's just a way of speeding up loads and (maybe) stores.


>
> Err, rather, I guess I'm *really* asking for pointers to Leo's caching
> mechanism.  If it's the db, I'd consider this a *very* dangerous change...
>  in my experience, syncing the db causes Leo to crash, lock up, or exhibit
> other strange behaviors.  I've settled to having a per-installation db,
> unsynced.


You mean putting the db in a sccs?  That's not its intended usage!



> Oh, another idea: allow 'hidden nodes' that would inform @shadow -- i.e.
> they exist in the .leo XML source, but are hidden and un-editable by the
> user -- updates to the @file/@shadow/@whatever trees would update the
> hidden @shadow nodes.
>

Not sure how much you understand about the @shadow algorithm.  The private
(cached) file contains *everything* in the external file, especially the
sentinels.  So your proposal is a subset of what already happens.


In general, I think hidden nodes are needed for Leo for other purposes --
> hidden persistent data embedded in the outline, for one... state of
> long-running, but interruptable database queries (for those using Leo as a
> database, like your brother Speed has, I gather) for another, etc...


Not hidden nodes; hidden attributes.  @file nodes contain attributes that
allow the re-creation of non-essential stuff like marks.



>  But if we contemplate using @shadow for *all* files, then it does matter,
>> in practice, whether @shadow can "guess" correctly.
>>
>>  The hidden nodes I mentioned above could solve these issues.


No. The need to guess arises even with *perfect* information in the
private file.

All in all, an exciting insight, but it *definitely* needs a lot of hard
> thought.
>

Yup.

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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to