Ahh, it looks like what you have made can do everything (or almost everything, I don't know if it can make lists of non-unique items) what I made can do and is probably more flexible. I think our motivations are very different, I started from the idea that fields should be polymorphic and whatever is interacting with them should determine how they act. So I was trying to make the tags field just another field. So in the sense that both allow any field to act the same way as the tags field they are pretty much equivalent.
Looking at the code you have a much more elegant solution, although I would like a way to use it that is more consistent with the other action widgets, for example I think that filters may not be appropriate for add or remove actions. It looks like the filtering doesn't impose uniqueness so if we do update $tw.utils.stringifyList that should take care of that objection. I don't think it would be too difficult to make inputs like $add=foo that would create the proper filter to add foo to the list, with some other similar options that have special filters associated with them. That way it could keep the flexibility from the filters and still have a way to give arguments that is consistent with the other action widgets. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3d4be008-8392-4547-bc64-21dad301b5a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
