Progress item "reminder" field

[ben]

From @rsek in discord:

problem A: it's a common design pattern in SF/IS mechanics to have to remember that some specific progress track (most often a vow) will later benefit from some specific asset ability. most of these are long-term tracks managed over multiple sessions.

problem B: annotating an object to describe that in dataforged sounds freakin tedious. and there's probably better uses of my time. (this is what i meant by "i'm not sold that it's [it=more annotation in dataforged] is the right direction to go.")

question: more structure may be more trouble than it's worth here - so is there a less structured way to providing some kind of reminder?

possible workaround with current functionality: include a note in the progress track text input field? problem with that workaround: could get cluttered/ugly; no particular way of collapsing it out of view.

feature proposal: some means of noting an arbitrary (read: user-set) text reminder/description on a progress track widget. while the progress track is active, keep it out of view (as in, not in the progress widget's normal display - but still viewable/editable, just not at the "top level" of the interface). include it with progress roll alert that is sent to chat.

in practice, this would probably look like an optional that could be used for any extended notes/description that aren't appropriate to include in the <input type="text"> that's currently used for setting a progress track's title/name.

i reckon that has general-purpose utility. those extended descriptions could additionally be included in the chat alert for progress rolls; normally those happen once per track, so it probably wouldn't get too spammy, and it might be handy to have the additional context. (this is the bit that would resolve the 'reminder to do X when progress is rolled' aspect)

[DiceT]

You already have the STAR checkbox that displays a progress track on the Legacies tab. This, in theory, should be enough of a reminder. That functionality could be extended to a Reminders tab, I suppose, which would make a bit of a tiered level of tracks (Legacies --> Reminders --> Everything Else).

In a system as sophisticated as this, there's a fine line between the lifting that the system should do and the lifting the player should do. This is right on that line, imho.

[rsek]

may bear revisiting (if only to close it) in light of #386 and journal-based progress