Hi,
On 06/07/17 08:42, Josef wrote: > Just my 2 cents worth: > > you can't merge sqlite databases easily - git does not know how to do > that. However, most of the time merging XML files will just do the > right thing, and if not, you can look at the human readable diff to > figure out what went wrong. > > - Josef > Maybe what I have done in Grafoscopio [1] case could be helpful, despite the fact that I have not problems with reloading settings, being it developed in Pharo, a live coding environment, where such changes happen almost instantly, while the system is running, without any reload. [1] http://mutabit.com/grafoscopio/index.en.html The storage format for notebooks is STON [2], a JSON inspired Smalltalk version of a human friendly data serialization language. Grafoscopio documents are partly integrated with Fossil [3], which allows to store all history for outlines and other related artifacts (as you can see in the Grafoscopio documentation timeline [4]). Because of this combination, diff are trivial, and you don't even need to bother with cluttered XML, for reading diffs. Here is, for example, last outline diff in the repository [5] [2] https://github.com/svenvc/ston/blob/master/ston-paper.md [3] http://fossil-scm.org/ [4] http://mutabit.com/repos.fossil/grafoscopio/timeline?n=700&y=all&t=&ms=exact [5] http://mutabit.com/repos.fossil/grafoscopio/ci/ef1f36aaf1d4352e?sbs=1 For me there is a deeper question in Vitalije's search and is "How can improve Leo liveness and responsiveness". This has been discussed in the past with the idea of services, talking with IPython kernels, implementing something like Emacs Babel or using other ideas from other Python IDE's (I don't remember the name). Sqlite could be a base for such improvements, with the advantage of the active prototyping Vitalije is doing. I imagine that, at some time, Sqlite needs not only to store data, but also the history of data, so it can be queried and exported to diff friendly plain text formats (in a similar way that Grafoscopio uses STON and Fossil for that). I know that Sqlite now provides support for storing and querying JSON, so that could be an interesting path to explore. So Sqlite + text exportation + history of outlines could be a way to keep the diff friendly Leo's format feature while exploring how to improve settings loads in the short term and improved liveness and responsiveness in the middle/long term. 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 [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.
