Josua, thanks for this work. I am very excited about using this in the long run to share "objects" in tiddlywiki like in your examples of book and professors etc... If we can use publicly available json schemas all the better.
The truth is I still need a deeper understanding of JSON to proceed without tripping up too often, but it is wonderful we have this capacity now. Thank you very much Tony On Tuesday, August 13, 2019 at 5:55:31 AM UTC+10, Joshua Fontany wrote: > > Hi everyone! > > I am really excited to announce that I have my proof of concept ready for > "modular" User Interfaces for TiddlyWiki! > > I'm also very excited to officially announce updated JsonMangler and > JsonEditor plugins for TW v5.1.20! > > There were some last minute tweaks, but I've gotten new example wikis up > and running. Any comments or bug reports are greatly appreciated! > > https://joshuafontany.github.io/TW5-JsonMangler/ > > https://joshuafontany.github.io/TW5-jsoneditor/ > > But, hey, wait Josh, that first thing you said. What does that mean? > > Screenshots are always nice. :D > > [image: JsonUI_conceptUI_viewTemplate_08.12.2019.png] > > [image: JsonUI_conceptUI_editTemplate_08.12.2019.png] > > > I'll try to keep the explanation high-level, but basically: > > > - A Jsoneditor Widget uses a 'schema definition' (a json tiddler) to > render one of two "data json tiddlers". > - The first data-tiddler holds wiki-text (not raw data!) for the View > Template. This wikitext points to fields on the current tiddler and > renders > a custom UI elements for each. > - The second data-tiddler holds wiki-text for the Edit Template! It > points to fields on the current tiddler and renders custom UI elements for > each. > - Finally, we have two system tiddlers - one tagged > $:/tags/ViewTemplate and the other tagged $:/tags/EditTemplate. > - The only real difference between the two template tiddler's TEXT is > that one points a JsonEditor to the view-data, and the other points to the > edit-data. > > > In this way, we can "group, organize, and modularize" our UI elements. > This helps to greatly reduce cognative-load (how much stress it take you to > think through designs). > > Also, simply tag a new Tiddler in the wiki with the `Character` tag, and > all of that slick UI automatically appears and is completely responsive. ;D > > More information can be found in the "JsonUI" tiddler in my example wiki: > https://joshuafontany.github.io/TW5-jsoneditor/#JsonUI > > This is only a VERY rough proof-of-concept using a commonly known > fictional character (lots of reference data). I have ideas for more complex > (behind the scenes complex) versions later on. There are also a few > gremlins to work out (jsoneditor tabs re-set state on each wiki update - > wooops), and I'm going to be updating my fork of the base json-editor > library, would like to be able to set a custom Font-Awesome glyph for the > collapse button based on a tiddler's value, etc, etc. > > This was inspired by working with other languages that use "Model, View, > Vew-Model" architecture, and I think we can start to make some really cool > complex things by combining this with all of the other plugins that are out > there!! > > Let me know if you all have any questions! > > Best, > Joshua Fontany > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/94e32118-ea1f-4ab8-81af-ca9529573676%40googlegroups.com.
