On Tuesday, September 23, 2014 3:34:08 AM UTC-4, Stephan Hradek wrote: > > > That's the reason why I wrote listselect. I'm not yet sure whether I will > drop listselect as it has features I don't think is yet possible to > implement with the select widget. Maybe you can tell me when you're done > with your experiments. > > While <select> is not an exact replacement and has a bit more of a complex (and flexible) syntax, it seems to work for me. I am using it in a particular way over and over so I am not sure which corner-cases might not be covered.
I am using it to define the field of a tiddler from a list of tiddlers tagged with a certain keyword. I am using your newtiddler plugin and ContactDB example and extending it to make cross-links between separate lists. For instance, I can add the following to the editPerson tiddler <$select field='company'> <$list filter=[tag[company]]> <option><$view field='title'/></option> </$list> </$select> and then maintain a separate renamed ContactDB structure to keep the company names (i.e.: editCompany, companyEntry, companySkeleton, viewCompany). Thanks, /Mike -- 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. For more options, visit https://groups.google.com/d/optout.
