a checklist is an example that's easy to collectively under…
a checklist is an example that's easy to collectively understand but in general what i'd like [[knovigator feature request]] is branches that ARE IN A STATE & can be TRANSITIONED TO OTHER STATES according to rules, so that you can use a branch to represent the progress of something, to develop something, to reach a destination, to accomplish
Replies
!promise:100 draw me a sketch and an example of how you might use it
do you mean a sketch as in how it'd appear in the interface? i'm not sure,, the top of the branch would have to be marked somehow w/ what state the branch is in,, i guess my first thought would be to put it below the line w/ the pfp on the left, above where the text starts,, maybe in a little offset box
the hard part is what exactly are the tools for transitioning between states,, a basic one is that you can just manually mark something as moving to a state,, w/ just that there's lots of productive stuff you can do, if people are willing to follow some very simple instructions (big if), like you can just say, i'll mark the ones that need doing with "Picture To Enhance" & then once you've done one please mark it "Done"
there's a basic choice to be made between allowing things to be in a SINGLE STATE at once, vs having them be TAGGED w/ states,,, tagging is more flexible of course & what you lose is making it simple to transition things, you've made it so a simple transition from state A to B which is the most common operation is taking away the A tag & also putting the B tag, & if you don't have some way to do that atomically then you'll get things just lost in inconsistent states where they've had their A tag removed but nothing added & they vanish, or have a B added while they still have an A tag & get confusing,, so i'd say have a single state & tools that transition to another single state, possibly w/ tagging as another option but that's adding interface complexity obvs