I would love to think there is a rule like this, but as is often the case it depends on your definition. See tiddlywiki.com define these here already. https://tiddlywiki.com/#TiddlerFields
By standard fields I am talking about fieldnames already used for a purpose in a tiddler, examples may include description, caption, color, Icon. Even if you make use of these fields for you own purpose the core will continue to regard them. These fields have meaningfull definitions and its Great for the user/designer to be aware of these and use them in the same way.
- The system also maintains a few of them such as modified/created fields and there is value not interfering with them as they are valuable as a source of truth.
- There is value knowing which fields
The simple need is when you use [all[current]fields[]] and more globally [fields[]] you will get many fields listed. I want to be able to detect other fields on a tiddler and only handle them. We can call these fields custom.fields and they tend to arrive from plugins or user data entry.
- Going forward if I build a system for field handling
field-prefix andfield-type-prefix I may want to add these to a system fields list, to remove them from the custom.fields list. In part because I have the templates to handle these fields
The problem is they contain “standard.fields” and other “core.fields” which access a manual list. It is these manual lists I believe should be in the core or at least available in a core plugin perhaps?
- perhaps as tv-standard.fields etc…
- Its just like registering or documenting core and system fields, we will either not reuse or if we do so we do it with the knowledge, so too does the core.