Here is my delima, due to the way dictionary tiddlers work, I cannot use them I’m forced to use fields, I have a WIP improvement for Mathcell but I am needing to hide the fields as my table generator can generate up to 26×99 fields, I could create a “$:/config/EditTemplateFields/Visibility/fieldname” for every single entry but after a while this could generate hundreds if not thousands of system filter tiddlers, ideally I want to create a “unique” tiddler type that is completely ignored from the dropdown list, as the fields will be reserved for mathcell, what i WANT is to have any field prefixed with say ; to be ignored from user fields as the Dropdown would essentially become unusable.
Anyone have any ideas?
The below is not the correct and complete way to do this. It would take time I don’t have now to get it right:
In $:/core/ui/EditTemplate/fields, around line 70, you can add another filter to the selection of fields:
<div class="tc-edit-fields">
<table class={{{ [all[current]fields[]] :filter[lookup[$:/config/EditTemplateFields/Visibility/]!match[hide]] :and[count[]!match[0]] :and[then[tc-edit-fields]] :else[[tc-edit-fields tc-edit-fields-small]] }}}>
<tbody>
<$list filter="[all[current]fields[]] :filter[!prefix[;]] :and[sort[title]]" variable="currentField" storyview="pop">
<!-- Add this: ^^^^^^^^^^^^^^^^^^^ -->
<$list filter=<<tf.config-filter>> variable="temp">
<tr class="tc-edit-field">
<td class="tc-edit-field-name">
The reason I know it’s not complete is that there’s another filter a few lines above used for setting the class name of the table. It should probably be added there too. And in the tiddler’s More Info > fields section, these are not hidden. These are easily fixable, but I don’t know how many other places might be affected.
Moreover, there is always a concern about modifying core tiddlers: it makes version upgrades much more difficult.
But it might get you moving in the right direction.
Sorry, this doesn’t address your question, but…
Could you expand on this? I often use dictionary tiddlers for unique index/value pairs (when I wouldn’t want to pollute the field space, whether the fields are visible or not) and have found them to be quite useful and versatile. I’m wondering what issues you’re encountering, and whether there might be a simpler workaround that doesn’t involve modifying the core.