> > > I don't agree. The concurrency problems will, but the problems to have > Sqlite files under git are here right now > <https://stackoverflow.com/a/551409/5104752>: > > *In short, you’ll probably be unhappy trying to keep a database versioned >> using a source control system.* > > > There is no need to add db file to git. External files are kept in git. If you want any part of Leo outline to be kept in git, you can make it external file and add to git. I would argue that can give you even better diffs. It would be trivial to make script that would produce outline structure as plain text file which can be added to git. If you make a very simple change like sort siblings it can produce totally confusing diffs, when in fact the only thing that is really changed is order of nodes in outline. Yes that order would make also changes in external files but diffs of such text representation of tree structure would give very clear explanation why all those changes in external files did happen.
Further more, you can dump content of db to sql and add it to git. There is also possibility to have in db all history of all nodes. ...unless you use Fossil as VCS, of course! > > But then, *we all have to have clear in our minds *that using Sqlite as > the next Leo file format *is forcing us to take those files out of git, > or to use Fossil* as VCS. Yes or yes. And those are important facts!! > Although I personally would salute such change, I strongly disagree on this. It is not the case that using sqlite as file format or even using fossil for keeping history of every node in outline is forcing any change in VCS used for project as whole. > XML limitations, which are now starting to show now, like reloading >> settings time. >> > > I insist: reloading settings time in Leo is not a limitation of its XML > file format! As I have already tried to explain, that is a separate problem > which can be solved by its own and which should be independent of the > backend used as storage. > I agree with you on this question. It is not XML format that prevents fast reload. I believe it would be possible to make Leo reloadable even with XML as format. But I prefer to make it reloadable using sqlite. Among other reasons is that if you want just small fraction of XML file you have to parse it whole. OTOH, opening db file gives you opportunity to ask for any piece of information that you are interested in. You can even ask for some aggregate values of interest without loading whole file. Setup for reading XML file is much larger than for opening and querying db. If you want to make small change in XML document it requires even larger setup. It may be very well matter of preference and we should not discuss preferences, but my preference for file format is sqlite. After all if when finished sqlite-leo prototype not all users would want to use it and if there will be some who prefer XML, support for XML files need not to be abandoned ever. > > I agree in that exploration or prototyping is a good way to go forward, > but well... problem anticipation is also a great tool! It can help you save > a lot of time or even avoid some crashes. Shouldn't I warn you if I know > there's a big hole in the road some meters in front of you? ;-) > > Thanks for the warning. But again: I would separate the VCS integration question from the Leo > storage format. They are different issues which deserve deep analysis and > design on they own. > > >> Yes please! I really would like to understand how did you did to have >> this nice diff >> <http://www.google.com/url?q=http%3A%2F%2Fmutabit.com%2Frepos.fossil%2Fpanama-papers%2Ffdiff%3Fsbs%3D1%26v1%3D255e79b046584a36%26v2%3Dcbfe8929edf64212&sa=D&sntz=1&usg=AFQjCNE4vUh4DdtIcaZ7QQkoSfOY0RaT1Q> >> >> for your outlines in Grafoscopio! At which moment do you use the STON >> format? Is it just before making the diff? >> > It is ordinary page generated by fossil (one file executable, that needs no configuration nor installation, just download one file) on files that are added to fossil repository. Fossil supports several different diff views, graph of repository, wiki pages, issue tracking fully configurable by user, tech notes, ... Vitalije. -- 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.
