I thought Leo might already have a way to do this which is why I asked. I guess I'm still confused on the "get them as usual" part.
It's not clear to me how I would use an @data node in an @settings node and have it be accessible/read via some named reference to it in any arbitrary node and checked if it changed when saving? Specifically what I'm trying to do is say have a node: Headline: @data myString1 Body: This is Common Data Then in a child of an @clean myfile.txt node be able to reference "myString1" by name somehow and be replaced by "This is Common Data" when the file is written out. On Monday, May 4, 2015 at 7:27:25 AM UTC-4, Edward K. Ream wrote: > > On Mon, May 4, 2015 at 6:14 AM, john lunzer <lun...@gmail.com > <javascript:>> wrote: > > Could Leo have something like @int/@bool/@string/etc simple settings types >> but applicable to any node in an outline? >> > > ​Anything is possible, but I won't do this. Settings are complex and > capable enough as it is. > > Put common data in settings in myLeoSettings.leo or in the local .leo file > and get them as usual. > > In particular, @data nodes can hold any data you want. c.config.getData > has the following signature: > > def getData (self,setting,strip_comments=True,strip_data=True): > > You may want to set the two keyword args to False. > > Finally, your scripts communicate through g.app.permanentScriptDict​. This > dict is not cleared after a script executes. Keys and values are anything > you want. This is one alternative to using c.config.set/get. > > HTH. > > Edward > -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
