Jed, I have found an answer for the following item
*Hide Edit GenTag in tiddlers not containing the defined fields* Just hide in view and edit mode and add back a filtered invocation of <<TagLikeList fieldName label showEmpty wikify>> and in the edit template <<EditTagLikeList fieldName label wikify>> Thanks Tony On Sunday, 18 March 2018 15:42:42 UTC+11, TonyM wrote: > > Jed, > > Thanks for that GenTags plugin. I have being playing With Gen Tags and > think it is great. > > To me its key use case is introducing subjects, categories, and other > organising "tags" that allow their own set of values, such that they are > not to be mixed with the other tags which are used for a range of purposes. > > This is basically advanced field handling however It maintains a standard > field, that listops can act against. > > I do not think we need to be concerned with the existing date and tags > fields because they are in a sense "core" functionality. I have already > manipulated them without too much complexity such as letting modified be > set to created date, but there is value in created being an immutable > field. With additional tools such as GenTags we need not change the > existing tags field because it too represents a minimum (but very powerful) > default organising principal including driving settings and the UI. Thus I > feel there is no backwards compatibility problems if we leave existing > "system" fields alone while supporting new field handling tools. > > Please forgive me, however we all try to stand on the shoulders of giants, > in this case your GenTags makes you a giant, however I can see a need for a > possible enhancement or two. I will describe them here should you wish to > consider implementing them. > > *Tags as Tiddlers.* > As you know a tag pill allows us to click on the tag name and create a > tiddler by that name. I tend to use this to document what the tag > represents, and sometimes I provide the lists to interrogate which tiddlers > are so tagged in that tiddler. > It would be nice if GenTags tagpill popup title would show if there was a > tiddler or it was missing (italics) like in regular tags, and clicking on > it would create a tiddler. I think this will only be a matter of changing > this title into a link. > > *Open all items so Tagged* > I use the open all plugin $:/plugins/ajh/openall which presents an Icon in > the Tagpill popup that allows me to open all tiddlers tagged with that tag. > Of course it is not aware of GenTags and does not work for them. > It would be great if we could also do this in the GenTags popup, it is > only a matter of issuing an open tiddler message for all tiddlers already > listed in the tagpill list. This would allow all tiddlers in the GenTags > set to be opened at once. > > *Hide Edit GenTag in tiddlers not containing the defined fields* > I have being looking through the code to see if I could stop the Edit > GenTags showing in tiddlers in edit mode, until the relevant field exists. > This would allow most tiddlers not to see my extra tag field exists, and > save valuable screen real estate, until the field in question exist in the > tiddler. For example my additional tags field called subject will not > appear in edit mode until I create the field subject in a give tiddler. I > would use a menu item using MyMenus plugin to create the subject field, and > thus subsequently display the Subject tags. > > With the Current Plugin, and possibly with the above enhancements I will > publish a use case and demonstration in the forums. I want to support and > Promote this long sought after tool which I believe has being neglected. > > I also expect the structure of the GenTags solution could be co-opted to > support other advanced field tools as discussed previously. It is an > elegant solution. > > Thanks again for your work. > Tony > > > > On Saturday, 17 March 2018 19:37:25 UTC+11, Jed Carty wrote: >> >> To partially back up what TonyM said, I did make the GenTags plugin that >> lets any field act like a tags field. >> http://ooktech.com/jed/ExampleWikis/GenericTagFields/ >> >> I believe that the way to go with this is not to make specific fields act >> in a certain way but to make it so that any field can be used as a tags or >> date (or other) kind of field. Improving field handling removes the need >> for a second tags field because it would allow you to use any field as a >> tags field. Unfortunately we can't do this for the existing date and tags >> fields because of backwards compatibility issues but I think moving forward >> this is the way to go for any new features. >> > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b5ec2d67-a7ba-40ba-a64c-87fee4b7f5b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
