I guess the trouble is not so much one of cookies or persistence in general... it really is: to come to a decision on where to store the ordering information of the list and to eventually implement it.
To me it sounds like two things are required: 1) an unchangeable hash identifying a tiddler even after name changes 2) a "kanban board" tiddler that serves as the store for order as well as state information with respect to the hashes in 1) 1) is simply done by adding a "hash" field that is populated when first needed and reused throughout whichever use case requires a reliable identifier which the tiddler title is not... I guess a 'hash' should really become a(n potentially optional yet universal) property of the thing called a tiddler. 2) states and ordered lists could be stored into a single (custom) "kanban" field using json, whereas (references to the hashes of ) task items would be grouped into states along with the ordering information. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
