As I suggested to Adam here...
https://groups.google.com/d/msg/tiddlywiki/0x8a2vdUvdE/CzUK-g-BDsIJ
...this would be my approach to tackle persistence:
1. save an unchangeable hash (as a custom field) to each tiddler
- so as to be able to identify a tiddler even after name changes
2. save order as well as state information in (a custom field of the)
list tiddler containing references to hashes in 1)
- could be a simple field with multi-line content like...
- item order:
- hash1
- hash2
- hash3
Things to notice:
1. There may be multiple lists, so the tiddler containing them may need
a number of custom 'item-order' fields
- I would suggest some generic way to generate a unique id
- or let the user define a unique I just as he would for
chkSomeSlider or txtSomeTabs
2. Saving an ordered list for the first time may reuire to write changes
to a number of tiddlers
- how can this be achieved with maximum usability / optimized
performance in mind
- is there even a performance issue?
Cheers, Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
