The "proper" way to do this would be to annotate each the
relationships between things. In TW the relationship is represented
by tagging one thing (say, tiddler "Mark") with the name of the other
thing ("Festival"), but unfortunately that means that connection
itself can't have extra data attached to it.
So I can think of three solutions:
1. represent the relationship between Person and Event in a tiddler of its own.
For example you could have a tiddler named something like
"Mark::::::Festival" to represent that connection. Then that tiddler
can have additional tags, like "tentative", "important", "call back"
or whatever, and those tags are applicable to the connection between
Mark and the Festival.
This would be powerful and awesome, but would mean a huge amount of
fiddling with TW.
2. get really clever with custom fields.
You could use some elaborate naming scheme with custom fields to
represent tag-like relationships with additional info. Eg tiddler
"Mark" could have a custom field "attending" with value "Festival",
then other custom fields like "attending_confidence" = "maybe".
Also powerful, but also much fiddling.
3. store an ordering somewhere.
You could attach a "preferred order" list of items to a tiddler, as a
custom field or even just hidden inside a comment in the tiddler
contents. It could list stuff that is tagged with this tiddler, in
your preferred order. Then your drag and drop can just adjust that
list.
You'd have to have a policy of where to show items that aren't on the
ordering list, but I guess you'd want those at the end.
This would require much less fiddling with TW, but isn't as powerful.
Whichever you choose, someone's gonna have to write a drag-n-drop thing.
I've previously discussed this kind of idea with Roger Sperberg, but I
never had time enough to write any code. If he's still in touch with
the list, I suspect he'll be very interested.
Cheers
;Daniel
--
Daniel Baird
/to be or not to be/ => /(2b|[^2]b)/ => /(2|[^2])b/ => /.b/
...optimise your regexes, people!