Re: A new file format for Leo documents (sqlite3 database file)

On Thu, 29 Jun 2017 14:49:43 -0700 (PDT) vitalije wrote: > Ran 904 tests in 94.022s > > FAILED (errors=6, skipped=25) I had six errors testing master without modifications a couple of days ago, so sounds like everything passed. Well done. Cheers -Terry -- You received this message because y

Re: A new file format for Leo documents (sqlite3 database file)

setting leoID from os.getenv('USER'): 'vitalije' reading settings in /home/vitalije/programi/leo/trunk-git/leo/config/leoSettings.leo reading settings in /home/vitalije/programi/leo/trunk-git/leo/config/myLeoSettings.leo reading settings in /home/vitalije/programi/leo/trunk-git/leo/core/LeoPyRef

Re: A new file format for Leo documents (sqlite3 database file)

On Thu, 29 Jun 2017 13:25:54 -0700 (PDT) vitalije wrote: > In the other thread I have announced my experiment but it seems that > I haven't explain it very well. Let me try another way. Actually what you describe below is sort of what I thought you'd ended up doing. Sounds very interesting. To

Re: A new file format for Leo documents (sqlite3 database file)

Congrats Vitalije! Sometimes prototyping is the best way to argument in favor of an idea and is nice to see your prototyping going well. In my case, Grafoscopio [1] is a prototype of the ideas I would like to see in Leo: liveness & interactivity, a simpler storage format (XML is too cumbersome) a

A new file format for Leo documents (sqlite3 database file)

In the other thread I have announced my experiment but it seems that I haven't explain it very well. Let me try another way. The trouble I bumped into few days ago with changing shortcut settings was just a primer that set me in motion. My initial experiment with collecting all settings in sqli

Re: How good Leo handles settings?

On Thursday, June 29, 2017 at 4:16:38 PM UTC+2, Terry Brown wrote: > > Hey Vitalije, what are you working on exactly? Not wanting to > duplicate any effort and wondering if you're working on the sqlite > settings idea or something else, and if you have any thoughts on the > sqlite approach sep

Re: How good Leo handles settings?

On Thu, Jun 29, 2017 at 8:47 AM, Kent Tenney wrote: > >setting: long - primary key for settings table > >name: text - setting name > >body: text - text data for setting for docs. and @data settings > >type: long - link to types table (@bool, @int, @data, etc.) > >parent: long - link to settings t

Re: How good Leo handles settings?

Hey Vitalije, what are you working on exactly? Not wanting to duplicate any effort and wondering if you're working on the sqlite settings idea or something else, and if you have any thoughts on the sqlite approach separating file specific settings from the file they apply to, vs. the current syste

Re: How good Leo handles settings?

On Thu, 29 Jun 2017 08:47:01 -0500 Kent Tenney wrote: > >setting: long - primary key for settings table > >name: text - setting name > >body: text - text data for setting for docs. and @data settings > >type: long - link to types table (@bool, @int, @data, etc.) > >parent: long - link to settings

Re: How good Leo handles settings?

>setting: long - primary key for settings table >name: text - setting name >body: text - text data for setting for docs. and @data settings >type: long - link to types table (@bool, @int, @data, etc.) >parent: long - link to settings table for hierarchy >outline: long - link to outline table Hows

Re: How good Leo handles settings?

On Thursday, June 29, 2017 at 5:43:08 AM UTC-5, Edward K. Ream wrote: > Or Leo could cache leoSettings.leo and myLeoSettings.leo, pretty much as described in #511 . > I've just added caching to the list of items to be handled by the renamed >

Re: How good Leo handles settings?

On Thursday, June 29, 2017 at 4:57:04 AM UTC-5, Edward K. Ream wrote: > > On Wednesday, June 28, 2017 at 11:53:42 AM UTC-5, vitalije wrote: > So Leo opens *two* documents (the settings files) before opening ekr.leo, > and then Leo reads ekr.leo twice. > > Is it really necessary? It is if we insis

Re: I've stoped *saying* all tests pass in commit messages

On Wed, Jun 28, 2017 at 11:26 AM, Terry Brown wrote: > Here are the fails I get from d1608d30. > ​Thanks for this. I've just created #512 . One fix would be to call self.skipTest in various​ ​"difficult" tests unless I happen to be running t

Re: How good Leo handles settings?

On Wednesday, June 28, 2017 at 11:53:42 AM UTC-5, vitalije wrote: So Leo actually reads four Leo documents before it starts opening your > document and it read it twice. > When I open ekr.leo, I see the following: reading settings in C:\leo.repo\leo-editor\leo\config\leoSettings.leo reading se

Re: How good Leo handles settings?

On Wed, Jun 28, 2017 at 6:09 PM, Edward K. Ream wrote: @Edward, I have another question. Where is the point where the actual > reading of Leo document ends and data is transferred in the tree. > > To be more concrete I have found in method getLeoFileHelper of > FileCommands class the following l

Re: Enhancement #511: reload-leo command

On Thursday, June 29, 2017 at 4:15:38 AM UTC-5, Edward K. Ream wrote: > > #511: reload-leo command > promises to make > Leo a killer app for python development. It distills the back and forth in > this > conversation >

Enhancement #511: reload-leo command

#511: reload-leo command promises to make Leo a killer app for python development. It distills the back and forth in this conversation . reload-leo would complete/moot #417: c