Hi,
On 06/07/17 01:06, vitalije wrote: [...] > > As you can see even if I work towards adoption of a new format for Leo > documents, some results of those endeavors may be found useful even > without changing format. > > I don't see why those settings affecting those objects can be > changed and we can see their immediate effect in real-time when > they are in Sqlite and cannot be when they are in an outline. > > > Maybe I didn't make myself clear. It is not my claim that it can't be > done without sqlite. What I wanted to say is that using the same code > for reading, analyzing, collecting settings from outlines and for > reading and dealing with documents makes it impossible to simplify > init code. OTOH complicated init code makes it difficult to show > real-time changes and requires restart. Maybe use of sqlite for > settings could have been just an excuse to introduce new separate code > for settings. But in my mind idea of using sqlite as a file format > have been for years, and not only in my mind but also in this forum it > was mentioned 9 years ago. > > On the road to sqlite file format next step is dealing with settings. > That is why I have started this thread. To discus about best way to > deal with them. It may look like I have lost my compass and mixed > several goals into one, but the truth is I am aware that these are > separate issues that just happen to lie on the road that leads to my > final goal. I try to deal with them one at the time. This time it is > Settingsville that I have to pass through. > Ville on this counts with my "moral" support (because my technical capability is departing from Leo and Python to Grafoscopio and Pharo) and this is a worthy exploration. Advocating for a simpler Leo format has been in this forum since several years ago (YAML, JSON, etc have been in our proposals and also closer integration with Fossil to resolve external files). Sqlite format is now about improving reload times, which can sum to explorations on liveness of the environment. At some point this is about which core assumptions can be reevaluated (like XML as storage medium), with some practical prototypes to see the implications. This has been pretty valuable in my case, I even reevaluate the programming language and development environment. Of course as a community, Leo doesn't need to go that far away, but this is an exploration that many have been waiting for. Xavier, I strongly recommend you and others the video about Sqlite as an storage format [1], that has been pretty inspirational about alternatives about where "masses wisdom" is going (Sqlite instead of XML, Fossil instead of Git / GitHub) and the opportunities this almost uncharted territory opens. [1] https://www.youtube.com/watch?v=8y_ABXwYtuc 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.
