And the previous version which was up and running briefly was SQLite,
confirmed proof of concept, but I am interested in a db server available
from anywhere, I work from several different machines during the day.

The principle I've described for Leo nodes will apply to versioning files,
commands ... etc. The combination of features in newt.db addresses
my interests wonderfully, so that part of the decision has been made for me.

Thanks,
Kent

On Mon, Mar 6, 2017 at 1:26 PM, 'Terry Brown' via leo-editor <
[email protected]> wrote:

> Hi - I wouldn't discount SQLite either, DB wise, unless you need connect
> to a *remote* server capability, but for local work it's quite capable.
> And a proper abstraction layer should make it possible to switch out the
> backend.
>
> Cheers -Terry
>
>
> ------------------------------
> *From:* Kent Tenney <[email protected]>
> *To:* leo-editor <[email protected]>
> *Sent:* Monday, March 6, 2017 10:41 AM
> *Subject:* Re: Well Kent, your vision for Leo is becoming clearer
>
> I'm not sure if my periodic outbursts qualify as 'vision' but in terms
> of where my characterization of Leo might differ from the norm, it
> would be my seeing Leo as a hierarchal data store rather than an
> editor, the D3 reference would imply generating data
> relationships viewed in the browser, I'd love to see that.
>
> I am slowly coding away at another implementation of my obsession
> with the notion of 'spatial versioning', meaning multiple versions which
> exist next to, above or below, etc. rather than temporal versioning:
> only before or after.
>
> It always seems to come down to storing data, so I've been studying
> Postgresql more, if the issue is data, a database makes sense. The
> next thing to fret is how much Python vs. how much Postgres, and
> what about json?
>
> Enter the code master, Jim Fulton, announcing newt.db
> http://www.newtdb.org
> which joins ZODB (persisting Python), Postgresql, and json.
>
> I once had node level spatial versioning working for Leo, I hope to return
> to it,
> in a form I can stick with.
>
> Thanks,
> Kent
>
> On Mon, Mar 6, 2017 at 9:34 AM, Edward K. Ream <[email protected]>
> wrote:
>
> I never really understood it until I saw the Atom editor
> <https://atom.io/> and d3 demo
> <https://bl.ocks.org/kaleguy/57266b6fff9f864403e007e9efd06401>.
>
> Cool stuff enabled by standard web technologies.
>
> 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 leo-editor+unsubscribe@ googlegroups.com
> <[email protected]>.
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/ group/leo-editor
> <https://groups.google.com/group/leo-editor>.
> For more options, visit https://groups.google.com/d/ optout
> <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 [email protected].
> To post to this group, send email to [email protected].
> 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 [email protected].
> To post to this group, send email to [email protected].
> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to