I already chatted about it with Jeremy some weeks ago. There is a little shortcoming(?) in regards to filters.
At the moment, if you want to compare a field with a value, you use: fieldname[value] This is fine in most cases. But what if your field is called "each" or "next"? Those names happen to also be filter functions. So there is no way yet to compare those field's values. This might be no issue now, but imagine you call your field "rest" and in version 5.0.8 we get a filter called "rest"… So here is my small proposal for an enhancement: If we want to compare a field, we put a colon after the fieldname. So filtering for the "next" field will now be possible because we write "next:[value]". This proposal works without changing anything in tiddlywiki, except for one small change in field.js. In field.js we simply need to replace a trailing ":" if there is one. Doing it this way we 1. Stay compatible with all filtering done in any TW5 out there 2. Are free in the usage of fieldnames as they won't clash with operators (filters) introduced in the future 3. Get a nice visual clue that the operator is in fact a fieldname I already implemented it in https://github.com/Skeeve/TiddlyWiki5/tree/field_enhancement so you can check it. -- 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 http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
