Hi Joshua, > > - The dataTiddler will have other fields to store more character data > as JSON objects, such as !!attributes, !!health, !!inventory, !!factions, > !!relationships, etc. > > I see, that's the crucial bit I didn't get the first time around.
Now to the real question: What makes *bootstrap* any of your concern? What do you need it for? Why would you need any of its css? *Musings:* Yes, being able to define an editor for a sophisticated fields containing json while specifying the schema defining whatever it is to contain is great. On top it would be great if TiddlyWiki can actually read / parse / address even write any such field-content-json via *TextReferences *or perhaps some macro that does so, e.g. <<json SomeTiddler some-json-field ".type">>. The problematic bit is that you can structure that json anyway you want but eventually you really don't want that. You want well-defined objects that respect a schema that some viewer know how to handle or some editor or other respects. Not having studied all that in detail, it appears, *jsoneditor* is one such interface. 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/de5ea394-b6fc-4b33-b182-aec84b32c9e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
