from a couple years ago, I'm as convinced as ever this is what
I want for a dev environment, instant access to versions of node
content which are 'next' to each other, not before and after.
##################################################
OK, I've written a simple implementation of 'spatial versioning'
A database maintains a table 'choices' with 3 columns:
- id (node gnx)
- index (currently selected choice)
- data (a json dict with numeric keys, the value a dict {'h':p.h, 'b':p.b})
The gui element turns out to be not required, in fact, I expect
it would be horrible to have tabs for each choice.
I have 2 buttons: 'right' and 'left'
clicking 'right' increments the index and pulls headline and body from the
db,
making a copy of the current node h&b if it's a new index
clicking 'left' decrements the index ...
The Leo file knows nothing about any of this.
A plugin sets up db access and provides one function:
update_choice(p, offset):
p is the current position, offset is 1 or -1
There is lots of room for enhancement, but it already looks to
offer what I've been wanting: access to ad-hoc 'what if' scenarios
instead of the more formal 'and then' world view of VCS.
Thanks,
Kent
##################################################
On Tue, Jan 17, 2017 at 10:04 AM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:
> Hi,
>
>
> On 17/01/17 11:00, 'Terry Brown' via leo-editor wrote:
>
>>
>> I think there's a two birds with one stone opportunity here if the
>> development proceeds with a generic interface to multiple backends, of
>> which Fossil could be one. I'm thinking not so much of git but a
>> server based DB like Mongo or Postgres or MySQL ... suddenly
>> collaborative Leo outline editing is a big step closer.
>>
>> Cheers -Terry
>>
>
> You have a distributed server based DB for collaborative editing already
> with fossil, with and integrated pwoerful query and programming language
> and almost no requirements for installation. That's why my explorations
> started there. There is, still, road ahead, and my own explorations could
> not suit Leo's approach, but the crosspollination of ideas surely will be a
> big win.
>
>
> Cheers,
>
> Offray
>
> --
> 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 post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>
--
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
