I would like to suggest support for a dynamic view feature, in which the tree contents represented to the user at a particular time is a subset of all the cards the in the document.
Currently, a special case of this hypothetical feature is supported in the form of viewing or exporting the subtree determined by some chosen card and its descendants. The generalization proposed would permit the user to define multiple views of the document, among which the user could switch while editing the document, determining which cards throughout the document are shown or hidden.
A cursory listing of common use cases might include:
Exploration of various arrangements or contents of passages, chapters, or chapter sequences, before resolving the preferred one, in a much more fine-grained and general way than would be possible simply through entire-document versioning.
Maintaining an abridged manuscript text in the same source document as the full text.
Assigning topic summaries or event synopses to major cards, which can viewed on the cards instead of the manuscript text, to aid arrangement or development or essential text fragments.
One possible design, though not necessarily the friendliest to the user, would be that the views would be defined as a chain of filter rules, each rule being defined by a tag, a choice between an exclude or include rule type, and a choice of whether the rule affects only the text of a card contents or also its descendants.
I would like to suggest support for a dynamic view feature, in which the tree contents represented to the user at a particular time is a subset of all the cards the in the document.
Currently, a special case of this hypothetical feature is supported in the form of viewing or exporting the subtree determined by some chosen card and its descendants. The generalization proposed would permit the user to define multiple views of the document, among which the user could switch while editing the document, determining which cards throughout the document are shown or hidden.
A cursory listing of common use cases might include:
One possible design, though not necessarily the friendliest to the user, would be that the views would be defined as a chain of filter rules, each rule being defined by a tag, a choice between an exclude or include rule type, and a choice of whether the rule affects only the text of a card contents or also its descendants.