> > The jsonOutput attribute however is read-write. The form is populated from > some initial json and as the user makes changes via the form, the resulting > json is updated and saved back to the tiddler. So I thought I would need a > pointer to where the json should be stored and a value wouldn't work there. >
Makes sense and using a TextReference to encode this also does. So, I'd keep it. Perhaps double check that it supports full TextReferences. Not sure what helper functions the core provides in terms of "parse this text reference and give me an object representing the target", e.g. a tiddler title, some fieldname, perhaps a data index, etc. Eventually you don't even want to parse this, you just want to write some text into the provided reference, no matter what tiddler or field or data index. I guess I could make it more like an edit widget (since it is really about > editing json) and associate it with certain tiddler types (any > application/json which also had a schema referenced?). If that would work, > it would probably be more consistent with the rest of TiddlyWiki. > Sounds reasonable. Again, perhaps there's a (better) way to reuse those interfaces in terms of "read text from reference" and then "write text to reference"... rather than you or any other plugin author having to write that code. I'd presume this stuff exists. Perhaps ask @JEREMY as to where to find it, e.g. @ mention him on that GitHub issue. Best wishes, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cde0de34-5603-459a-94c5-20d29c9c8d1d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
