On Monday, March 6, 2017 at 11:41:26 AM UTC-5, Kent Tenney wrote: > > 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. >
Leo is what it is, and what it happens to be is an editor. I don't think anything is going to change that and I don't think it should change. But, perhaps, Leo could be the editor of choice for your for your hierarchical data store Abstraction is important. I see the big three primary layers as: data, "actions on data", visualization. I think Leo's focus is primarily on "actions on data" with enough visualization (tree pane) to make acting on data fluid. > 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. > I'd love to hear more about this or read some docs about what you're working on. Any time I hear the word 'spatial' in relation to data my ears perk up a little. > 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. > This may not be very helpful but you might want to take a look at Fossil <http://fossil-scm.org/>, which is a versioning system that uses a database to store version artifacts. Dr Richard Hipp and co has put about a decade of work into merging the ideas versioning and databases. There are a lot of design documents and I've been told the C code is pretty clean and well commented. > Thanks, > Kent > Anyway, I'm excited to hear about what comes out your work. As an aside, I think Offray is exploring some ideas related to versioning and databases as well. > On Mon, Mar 6, 2017 at 9:34 AM, Edward K. Ream <[email protected] > <javascript:>> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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.
