Hi Mario & Alex, About readability... one basic design goal of xFieldsPlugin is to make extended fields more accessible. Thus, the important bit (to me) is NOT that tiddler data are always best when contained in the tiddlers main text. In fact, I find that approach to be somewhat distracting and error prone.
The only thing required to make use of the enhanced accessibility xfield is to provide is a meaningful configuration defining which xfields will be displayed at what kind of tiddler. In that regard, using extended fields to store structured data of tiddlers and to make unified input methods available, I fail to see at this point where xfields would benefit from making use of JSON... other than the config itself, perhaps. On the other hand, I strongly tend to prefer the configuration tiddler to be structured via somewhat readable Wiki Markup. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
