Tony, I like your idea. Here's a sketch for a workflow/UI: A'la EditorMagic, typing some trigger e.g <! could open a popup at caret position, showing a small floating editor. Comments are added there. Closing it converts the trigger into e.g <!-- # --> where # is e.g a calculated number unique within the tiddler (but another tiddler might have the same number). The number of comments a tiddler has is very limited so a rough but pragmatic strategy could be to number any new comment with "the current highest number +1".
Hovering or clicking this marker shows the comment. Or, clicking some button for the whole editview tiddler, opens all comments perhaps located where the preview area is located. (Nice if they're vertically located where the comment marker is but not sure if that's possible.) What really happens as soon as you add a comment is that a ghost tiddler is created. Every new comment is a new field in this ghost tiddler. When a tiddler is deleted, its ghost tiddler should probably also be deleted. What happens if a comment marker is deleted? I guess saving the tiddler makes a run through of the existing markers and the existing ghostly comments and anything not matching up is removed. Thoughts? <:-) > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/28ea887e-2de4-4def-a4cb-01ff50c1ba1c%40googlegroups.com.
