Re: Request for discussion: a Leo JSON format

2012-05-05 Thread Ville M. Vainio
Also, check out this document I wrote earlier, for objtrees: http://openbookproject.googlecode.com/svn/trunk/leo_doc_zh/doc/treecaching.txt The format can be trivially changed to be dumped as proper json. -- You received this message because you are subscribed to the Google Groups leo-editor

Re: Request for discussion: a Leo JSON format

2012-05-05 Thread Seth Johnson
On Fri, May 4, 2012 at 7:19 PM, billp9619 billp9...@gmail.com wrote: Turns out a dictionary-of-lists-of-dictionaries format as I suggested is  a common approach on the internet. I borrowed  the idea from Dojo datastores...but loosely. Today on a forum I found a script to process it into an

leo corrupting @thin python files

2012-05-05 Thread nic cave-lynch
Hi I've found a sure-fire way of getting corrupted files in leo. I'd noticed it happening in leo 4.7.3, but aftre an upgrade to 4.10 I saw it again and finally tracked down a minimal case that breaks. - in a blank leo file create an @thin file eg @thin junk.py - in that file, put @language

Re: Request for discussion: a Leo JSON format

2012-05-05 Thread Edward K. Ream
On May 2, 11:07 am, Edward K. Ream edream...@gmail.com wrote: 2. The obvious, and easy next step would be to do import-from-json and export-to-json commands.  The import-from-json script should eventually be folded into Leo's do-all import-file command. Python's json module makes this step

RE: Request for discussion: a Leo JSON format

2012-05-05 Thread Ville Vainio
Take a look at the caching code, and dump the object as json instead of pickle. Sent from my Windows Phone From: Edward K. Ream Sent: 5/5/2012 6:17 PM To: leo-editor Subject: Re: Request for discussion: a Leo JSON format On May 2, 11:07 am, Edward K. Ream edream...@gmail.com wrote: 2. The