You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 21, 2020. It is now read-only.
a dynamic realm would simply be defined as a filter that globally constrains all displayed GTD contents to matching items ...you could have a predefined list of such named filters
so, rather than have items permanently bound to a realm via assignment, or perhaps inderectly by their project, you could define a more ad-hoc-type realm via filte ...thinking less about how to assort stuff when writing — unless a context or project tag, etc... — and more about how to look for stuff when searching / dynamically scoping
it's a bit like the advanced search results using filters, only just not as a results list but rather as a way to globally constrain what you see, GTD-wise
in fact, this might not even just be a GTD5 thing but rather something for TW in general, a way to globally constrain what (regular tiddlers) are being listed and made available in the ui
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
allow to define dynamic realms by defining a filter expression, in addition to using the realm-as-a-field pattern on corresponding elements
allows to turn anything into a realm, e.g. "@shopping" can be made a realm simply by defining the necessary filter
The text was updated successfully, but these errors were encountered: