I do expect I am overloading this thread, however as I come to understand this no touch listing, I am gaining more insight and the filters/functions needed to handle no touch flags.
- Yes I am continuing a “speculative wandering”
Recent Observations
- I love relink and continue to use it, but I can also see how it may give rise to some distraction, the reason is that there are other ways to handle a subset of the problems that relink addresses. With the right tools a title can be stored only in one place and referential integrity retained.
- Despite this relink retains an importiant role here
- There are opportunities to leverage the algorithms in no-touch flags to make a robust set of relationship tools that has “minimal touch”, ie store the relationship in one place but have it visible in more then one place.
- As recently discussed the idea of virtual fields, where we can provide a field=value pair as if we edited a given tiddler, but have not. This is difficult to apply to the core as it already has its methods, arguably it has a type of technical debt. However if we introduce a new set of algorithms we can build a solution quite capable of handling this, allowing for virtual fields to be assigned.
- Is the value in a real field?
- if not is it in a virtual field for the currentTiddler?
- if not shall we use the value in a named tiddler?
- if not is their a global default?
Realisations
Careful generalisations of the ideas coming from recent observations will provide a powerful set of algorithms that would facilitate a number of ideas that I have being involved with in recent weeks. But I know see the opportunity for some powerful “entity relationship” tools. I will expand on this once I do some more POC’s
- Tiddler relationships with referential integrity
- No touch referential integrity
- No touch flags (the original topic)
- Enhanced list management and tools
- Virtual fields and cascades
- disregard and regard algorithums.