On Tue, Mar 13, 2018 at 8:41 AM, drmikecrowe <drmikecr...@gmail.com> wrote:

I have a lot of configuration that must be defined as a Javascript object
> (or JSON).  I'm trying to decide on the best way to enter it into Leo.

​For such questions I think first of creating a Leo script.​

​Whether that's reasonable in your case depends completely on your desires.

Is there a good way of managing this in Leo?

​The answer to all such questions must surely be "yes".  However, that
answer, while being absolutely true (imo), doesn't help much ;-)

> I'm wondering if there's a way to build this JSON object via Leo, and
> somehow use clones to keep the data synchronized across different services
> within the project

​I agree with Terry that clones aren't likely to be the best way.

You could try making a suite of @button nodes that would use "raw"
json/yaml/whatever in some particular (known) node as a mini database​.
Python's json library module <https://docs.python.org/2/library/json.html>
would help you access the data in that node however you like.

But these are just first thoughts. You can do amazing things with Leo if
you are comfortable with python scripting.


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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to