Co-indecently this Request would benifit from easy use of alternate view, update and edit templates within a tabbed internal toc
https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/sZNfQBxMs3c On Thursday, February 7, 2019 at 10:11:03 AM UTC+11, TonyM wrote: > > Matt, > > Others can comment if this is the best approach. However the desire for an > "extensible EditTemplate system" is there, however this also exists for an > "extensible ViewTemplate system". Personally I have proposed previously the > concept of an intermediate "Update Template", a view of the tiddler that > has selected update or edit fields displayed. But of course we may use more > templates. The idea of an update template is you can switch it on or off, > depending on the user and wiki update rights. It would make TiddlyWiki more > capable of Internet 2.0+ CMS by not forcing edits to take place in the > default editor, but in a customised presentation. > > I have in fact built a custom update template that is displayed from the > view template when selected. What appears is dependant on an update-list > field containing the fields and their order in which to appear on the > update view. To assist I have also defined each field used and provided > "field edit code" for example using the image picker on the field icon, > colour selector on color field, edit-text fields on others and time stamps > date pickers on others etc.... > > I have taken this field definition concept further an include a definition > for each field that is used when listing tiddlers, that is that field in a > table, it includes definition of the column header, display method in table > cells and more. > > I also want to create a template that appears on the "Viewer", for all > tiddlers (currentTiddler aware), and another for each tiddler in a toc > internal nav outliner. See this as an example > > <$macrocall > $name="toc-tabbed-internal-nav" > tag="TableOfContents" > selectedTiddler="$:/temp/toc/selectedTiddler" > unselectedText="<p>Select a topic in the table of contents. Click the > arrow to expand a topic.</p>" > missingText="<p>Missing tiddler.</p>" > /> > > My point being that what you suggest is called for, how it is done should > support other requirments and methods with serious merit. > > > Regards > > Tony > > > > On Thursday, February 7, 2019 at 1:31:23 AM UTC+11, Matthew Lauber wrote: >> >> All, >> Right now, we've got two types of Edit Templates, one for text and one >> for images. In one of my recent plugins ( >> https://github.com/mklauber/tw-CreatureManager) I ended up overwriting a >> bit of the core in order to implement a third type (for editing tiddlers >> with type "Creature"). In doing so, I realized it would be possible to >> implement an extensible EditTemplate system, where users could create edit >> templates for new types of tiddlers. If you look at >> https://github.com/mklauber/tw-CreatureManager/blob/master/%24__core_ui_EditTemplate.tid#L17 >> >> I check for a tiddler titled $:/core/uiEditTemplate/$type$, before >> defaulting to $:/core/ui/EditTemplate/default where I put the original >> contents of $:/core/ui/EditTemplate. Is this a good use of the type field, >> and what do people think of this as functionality? Is it something you'd >> like to see in the core? >> >> Matt Lauber >> > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/147c3dcb-ee54-416e-973e-53c935ae423e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
