Tobias and Joshua,
Thanks for all the analysis and feedback. You've done all the work to
identify the issue and show the way toward a fix. Nice work. I will take a
look maybe this weekend.
> but use the default way of declaring them via *option:{{!!foo}}* not
*option:"!!foo"*
*[...]*
> the special handling for *schema* and *jsonOutput* should be removed, imho
The {{!!foo}} style would work for the schema attribute because that one is
readonly and only needs a value. 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.
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.
Brian
--
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/CAO5X8CxZzbe9r7Cer2JNLF_z9P%3DL57ijtGVBOE2%2BqSzA2jSfKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
