On Thu, Sep 19, 2013 at 11:59 AM, Jacob Peck <[email protected]> wrote:
On 9/19/2013 12:57 PM, Edward K. Ream wrote: > > I'm really trying to store some persistent data in the outline itself. > It's part of a gamification process I'm working on - trying to motivate > myself some more to do things. The data can't be in the db, because I'm > not syncing that... it has to be in the outline somewhere, so that it is > saved with the rest of the data. > Well, the outline already stores data ;-) Many plugins use particular kinds of nodes to store particular data. Leo's core defines meanings for @settings, @test, @chapters and many others. I see no reason to get all excited about "protecting" data: all data is worth saving. The typical way is to put your data in some out-of-the-way place. The startup node comes to mind, but anywhere will do. In short, put your persistent data in an @my_kind_of_data node. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
