With respect to the method discussed here: *Cornell's Note Taking Method* https://groups.google.com/forum/#!topic/tiddlywiki/4OSPF3TeEWE
...rather than starting to implement anything right away, I have decided to try and define a system and corresponding requirements for implementing the method: http://cornell.tiddlyspot.com If you're interested, please let me know... - what you think of what you read - if you can imagine how that would work - if you find it comprehensible and coherent - what you think of the design choices - what's missing ~ When I set out to jot down those requirements, I stumbled over one *major problem* that any requirements engineer would have trying to use TiddlyWiki for the job. A basic requirements system needs one thing, above all else: requirement IDs that never change (like an issue tracker would, as well). In other words, every single line-item you see in that wiki should be a tiddler with a requirements ID which, today, I would manually sort into a requirements tree... and later hopefully into one that is nested-drag-sortable. I would find it very welcome and practical if at some point TiddlyWiki provided means to... - define a template tiddler - have an incrementable id field at that tiddler, possibly prefixed, e.g. *req-1* - have the id field increment every time a new tiddler is created based on the template - perhaps be able to define the number of zero-padded digits, so you get *req-00001* - be able to link to any tiddler via its requirement-id - I guess implementing *<<req 00001>>* can already be done Best wishes, 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. For more options, visit https://groups.google.com/d/optout.
